alhazmy13 / Synology-NAS-monitoring

influxDB, Grafana, snmp and telegraf
203 stars 27 forks source link

trouble accessing grafana after installation #8

Open rbos98 opened 2 years ago

rbos98 commented 2 years ago

I downloaded the image succesfully, and tried to launch it according to the instructions given. it seems to be up and running now, however when looking at the docker container logs, i can see its shutting down various services, meaning i am not able to access grafana because it is not running anyway. Is your system still operational?

2022-05-25 11:28:52,873 INFO exited: syslog (exit status 0; expected)

2022-05-25 11:57:32,174 INFO exited: syslog (exit status 0; expected)
84 items.

2022-05-25 11:28:52,873 INFO exited: syslog (exit status 0; expected)

2022-05-25 11:32:51,349 INFO reaped unknown pid 39

2022-05-25 11:53:25,835 WARN received SIGTERM indicating exit request

2022-05-25 11:53:26,081 INFO waiting for sshd, chronograf to die

2022-05-25 11:53:27,106 INFO stopped: chronograf (terminated by SIGTERM)

2022-05-25 11:53:29,110 INFO waiting for sshd to die

2022-05-25 11:53:31,512 INFO stopped: sshd (exit status 0)

/usr/lib/python3/dist-packages/supervisor/options.py:470: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.

self.warnings.warn(

2022-05-25 11:56:55,987 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.

2022-05-25 11:56:55,988 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing

2022-05-25 11:56:55,997 INFO RPC interface 'supervisor' initialized

2022-05-25 11:56:55,998 CRIT Server 'unix_http_server' running without any HTTP authentication checking

2022-05-25 11:56:55,998 INFO supervisord started with pid 1

2022-05-25 11:56:57,000 INFO spawned: 'sshd' with pid 8

2022-05-25 11:56:58,403 INFO spawned: 'influxdb' with pid 9

2022-05-25 11:56:58,405 INFO spawned: 'syslog' with pid 10

2022-05-25 11:56:58,407 INFO spawned: 'telegraf' with pid 11

2022-05-25 11:56:58,414 INFO spawned: 'grafana' with pid 12

2022-05-25 11:56:58,416 INFO spawned: 'chronograf' with pid 13

2022-05-25 11:56:58,426 INFO spawned: 'snmpwalk' with pid 14

2022-05-25 11:56:58,822 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2022-05-25 11:57:00,525 INFO success: influxdb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2022-05-25 11:57:00,525 INFO success: syslog entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2022-05-25 11:57:00,525 INFO success: telegraf entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2022-05-25 11:57:00,526 INFO success: grafana entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2022-05-25 11:57:00,526 INFO success: chronograf entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2022-05-25 11:57:00,526 INFO success: snmpwalk entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2022-05-25 11:57:00,526 INFO exited: influxdb (exit status 1; not expected)

2022-05-25 11:57:00,526 INFO exited: grafana (exit status 1; not expected)

2022-05-25 11:57:00,528 INFO spawned: 'influxdb' with pid 67

2022-05-25 11:57:00,530 INFO spawned: 'grafana' with pid 68

2022-05-25 11:57:01,562 INFO success: influxdb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2022-05-25 11:57:02,400 INFO success: grafana entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2022-05-25 11:57:02,400 INFO exited: snmpwalk (exit status 0; expected)

2022-05-25 11:57:02,400 INFO exited: influxdb (exit status 1; not expected)

2022-05-25 11:57:02,403 INFO spawned: 'influxdb' with pid 92

2022-05-25 11:57:03,459 INFO success: influxdb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2022-05-25 11:57:05,200 INFO exited: grafana (exit status 0; expected)

2022-05-25 11:57:06,201 INFO reaped unknown pid 103

2022-05-25 11:57:08,263 INFO reaped unknown pid 43

2022-05-25 11:57:08,986 INFO exited: influxdb (exit status 0; expected)

2022-05-25 11:57:12,997 INFO reaped unknown pid 46

2022-05-25 11:57:29,159 INFO exited: telegraf (exit status 0; expected)

2022-05-25 11:57:32,174 INFO exited: syslog (exit status 0; expected)

EugeneGGHQ commented 2 years ago

Just adding a +1 to this @alhazmy13 0 Grafana doesn't appear to be able to launch after following your steps.

dszymczuk commented 2 years ago

Same issue.

ChiefGyk3D commented 2 years ago

same result

rbos98 commented 2 years ago

Something to do with snmpwalk or something? I am not quite sure. Hope alhazmy13 is still around somewhere..

xoomercom commented 2 years ago

Installed following directions to a t.

Unable to access grafana at :3003

Please help.

rlrl commented 1 year ago

can someone try this? shell into the container and change the grafana db permissions:

sudo docker exec -it alhazmy13-telegraf-influxdb-grafana1 /bin/bash chown grafana.grafana /var/lib/grafana/grafana.db

then restart the container

i have this working after trying many things, but that was the last thing i tried

astlgit commented 1 year ago

was having the same issues. I just moved everything out of the grafana folder,(mostly the grafana.db) and everything started right up. only thing now is everything is gone, in terms of all my pages/dashboards, which I assume are in the file I had to move to another folder. anyone know how to bring all that back, without starting over. seems this problem is with the grafana.db file and the permissions with it as the way grafana does permissions has changed since v7.3.

rlrl commented 1 year ago

maybe copy everything back and chown grafana.grafana everything?

astlgit commented 1 year ago

@rlrl That worked.

edenraf commented 1 year ago

I have a similar issue. I could not access the web interface at the start. then I chown grafana.grafana and I got access to the web interface. I installed dashboard 14590. All values are NA except for NAS uptime which shows the correct time.

I still have errors in the log for alhazmy13-telegraf-influxdb-grafana1:

2023-05-01 10:48:49,486 INFO exited: snmpwalk (exit status 1; not expected) 2023-05-01 10:48:49,488 INFO spawned: 'snmpwalk' with pid 90 2023-05-01 10:48:50,490 INFO success: snmpwalk entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-05-01 10:48:55,508 INFO exited: snmpwalk (exit status 1; not expected) 2023-05-01 10:48:55,510 INFO spawned: 'snmpwalk' with pid 96 2023-05-01 10:48:56,512 INFO success: snmpwalk entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

costispavlou commented 1 year ago

same issue, can you explain what to do?

edenraf commented 1 year ago

same issue, can you explain what to do?

Never was able to fix it. Gave up

notoriousjere commented 11 months ago

Same issue