Unknown lvalue warning on service start

[jayjupdhig]

Hi there

There are some warnings on grafana service start / system boot with

Grafana Version: 9.1.3 on Raspbian 10.x (must current version via apt upgrade today)

[ 4.707209] systemd[1]: /usr/lib/systemd/system/grafana-server.service:26: Unknown lvalue 'ProtectClock' in section 'Service', ignoring [ 4.719518] systemd[1]: /usr/lib/systemd/system/grafana-server.service:29: Unknown lvalue 'ProtectHostname' in section 'Service', ignoring [ 4.732157] systemd[1]: /usr/lib/systemd/system/grafana-server.service:30: Unknown lvalue 'ProtectKernelLogs' in section 'Service', ignoring [ 4.744864] systemd[1]: /usr/lib/systemd/system/grafana-server.service:33: Unknown lvalue 'ProtectProc' in section 'Service', ignoring [ 4.757100] systemd[1]: /usr/lib/systemd/system/grafana-server.service:39: Unknown lvalue 'RestrictSUIDSGID' in section 'Service', ignoring

I was able to hide them with adding a #-character to the service unit file..

When i search for that issue, i always read: " ... it's fixed in version 8.x.y."

E.g.:

• https://support.plesk.com/hc/en-us/articles/4407862074898-Advanced-Monitoring-shows-the-following-error-in-Plesk-on-Ubuntu-18-Debian-9-The-tab-content-cannot-be-loaded-because-the-Grafana-service-is-stopped

• 8.2.0 grafana-server service doesn't start: Unknown lvalue #40247 (but in my case, the service works)

Thank you very very much for your feedbacks...

With best regards, Jan

[kminehart]

Hi Jan,

This warning typically appears on older versions of systemd. Luckily the systemd developers don't crash the application when it runs into an unrecognized config option.

I did some research and it seems that Raspbian 10 (buster), like Debian 10, is an LTS version and is end-of-life in 2024, and the current LTS version is 11. According to this page, Raspbian 10 has a systemd package 241 from February, 2019. (3 separate links)

• RestrictSUIDSGID and ProtectHostName were introduced in May 2019 on version 242.
• ProtectKernelLogs was introduced in November, 2019 version 244.
• ProtectProc and ProcSubset were introduced in 2020 on 247.

I don't think I would suggest upgrading your distribution to resolve these warnings; who knows what else that kind of upgrade could impact. Since these options only restrict the application and don't enhance any features, I wouldn't worry too much about it.

[jayjupdhig]

ok thx