I’m on xubuntu 18.04. Grafana has been working fine for years. Now I get this when starting from terminal. It sometimes show different line errors so I’ll post two instances. Any help would be appreciated. I’m not a pro at linux though.
grafana-server.service - Grafana instance
Loaded: loaded (/usr/lib/systemd/system/grafana-server.service; disabled; ven
Active: active (running) since Sat 2022-12-31 01:29:37 CST; 9h ago
Docs: http://docs.grafana.org
Main PID: 2136 (grafana-server)
Tasks: 13 (limit: 4915)
CGroup: /system.slice/grafana-server.service
└─2136 /usr/sbin/grafana-server --config=/etc/grafana/grafana.ini --p
Dec 31 10:29:38 johnnydell grafana-server[2136]: logger=cleanup t=2022-12-31T10:
Dec 31 10:39:38 johnnydell grafana-server[2136]: logger=cleanup t=2022-12-31T10:
Dec 31 10:49:38 johnnydell grafana-server[2136]: logger=cleanup t=2022-12-31T10:
Dec 31 10:59:38 johnnydell grafana-server[2136]: logger=cleanup t=2022-12-31T10:
Dec 31 11:09:38 johnnydell grafana-server[2136]: logger=cleanup t=2022-12-31T11:
Dec 31 11:19:38 johnnydell grafana-server[2136]: logger=cleanup t=2022-12-31T11:
Dec 31 11:24:44 johnnydell systemd[1]: /usr/lib/systemd/system/grafana-server.se
Dec 31 11:24:44 johnnydell systemd[1]: /usr/lib/systemd/system/grafana-server.se
Dec 31 11:24:44 johnnydell systemd[1]: /usr/lib/systemd/system/grafana-server.se
Dec 31 11:24:44 johnnydell systemd[1]: /usr/lib/systemd/system/grafana-server.se
Another instance when starting
johnny@johnnydell:~$ sudo systemctl daemon-reload | sudo systemctl start grafana-server | sudo systemctl status grafana-server
● grafana-server.service - Grafana instance
Loaded: loaded (/usr/lib/systemd/system/grafana-server.service; disabled; vendor preset: enabled)
Active: active (running) since Sat 2022-12-31 01:29:37 CST; 10h ago
Docs: http://docs.grafana.org
Main PID: 2136 (grafana-server)
Tasks: 13 (limit: 4915)
CGroup: /system.slice/grafana-server.service
└─2136 /usr/sbin/grafana-server --config=/etc/grafana/grafana.ini --pidfile=/run/grafana/grafana-server.pid --packaging=deb cfg:default.paths.logs=/var/log/grafana cfg:default.paths.data=/var/lib/grafana cfg:default.paths.plugins=/var/lib/grafana/plugins cfg:d
Dec 31 11:19:38 johnnydell grafana-server[2136]: logger=cleanup t=2022-12-31T11:19:38.729117178-06:00 level=info msg="Completed cleanup jobs" duration=5.46247ms
Dec 31 11:24:44 johnnydell systemd[1]: /usr/lib/systemd/system/grafana-server.service:29: Unknown lvalue 'ProtectClock' in section 'Service'
Dec 31 11:24:44 johnnydell systemd[1]: /usr/lib/systemd/system/grafana-server.service:32: Unknown lvalue 'ProtectHostname' in section 'Service'
Dec 31 11:24:44 johnnydell systemd[1]: /usr/lib/systemd/system/grafana-server.service:33: Unknown lvalue 'ProtectKernelLogs' in section 'Service'
Dec 31 11:24:44 johnnydell systemd[1]: /usr/lib/systemd/system/grafana-server.service:36: Unknown lvalue 'ProtectProc' in section 'Service'
Dec 31 11:29:38 johnnydell grafana-server[2136]: logger=cleanup t=2022-12-31T11:29:38.729422531-06:00 level=info msg="Completed cleanup jobs" duration=4.891356ms
Dec 31 11:37:01 johnnydell systemd[1]: /usr/lib/systemd/system/grafana-server.service:29: Unknown lvalue 'ProtectClock' in section 'Service'
Dec 31 11:37:01 johnnydell systemd[1]: /usr/lib/systemd/system/grafana-server.service:32: Unknown lvalue 'ProtectHostname' in section 'Service'
Dec 31 11:37:01 johnnydell systemd[1]: /usr/lib/systemd/system/grafana-server.service:33: Unknown lvalue 'ProtectKernelLogs' in section 'Service'
Dec 31 11:37:01 johnnydell systemd[1]: /usr/lib/systemd/system/grafana-server.service:36: Unknown lvalue 'ProtectProc' in section 'Service'
lines 1-19/19 (END)
It started working again after 3 days. Not sure why the cleanup or whatever took so long. Is there something i need to do or is there a way to do a manual cleanup? Here’s one line. It took longer than that of course. Not sure about those other errors either.
When was the last time you used Grafana before this message appeared?
Also, Could you please provide us with the backend logs (the default location in Linux is /var/log/grafana/grafana.log) so that we can have more information about the error message?
I’ve been running it continuously for years for my weather sensors. This happened after a reboot. I run the commands below to start it after I reboot. All the errors and cleanup messages are gone now after 3 days.
rtl_433 -M protocol -M level -C si -F "influx://localhost:8086/write?db=weather&p=gBh2mt44a=weather"
I am not able to tell as why so many cleanup jobs are appearing and what triggers it.
Please change the default log level to debug mode. To do this go to the server where grafana is installed and edit the configuration file (/var/log/grafana/grafana.log)
There you will this section;
#################################### Logging ##########################
[log]
# Either "console", "file", "syslog". Default is console and file
# Use space to separate multiple modes, e.g. "console file"
;mode = console file
# Either "debug", "info", "warn", "error", "critical", default is "info"
;level = info
Set the parameter level to debug and remove the colon in the beginning i.e.
level = debug
Then restart the grafana service and resent the logs once the issue occurs again.