You are right. I thought tmpfiles.d had a hook so it would recreate the
needed files/directories on a service (re)start, but apparently this is
not the case. I think we can safely set the status of this report to
Invalid. Thanks for both raising the issue and bringing it to a well
understood conclu
We use libnss-ldapd.
I think it may be sufficient to claim:
"System users generally have to be resolvable during early boot already.
This means they should not be provided by any networked service ..." [1]
So, is this even a bug? If your OS uses systemd, then you need to ensure
your system users
** Changed in: nagios-nrpe (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871194
Title:
nagios-nrpe-server fails to launch after reboot
To manage notificat
Thanks for clarifying. Systemd should support resolving users via LDAP,
with a caveat: the service providing the users should be running when
the user resolution is requested [1]. This may be a problem at boot
time, but not once the boot has completed. This is why I was insisting
on trying to start
Paride,
IF the nagios user is in LDAP, then /var/run/nagios will not be created
by systemd at boot time, or any time after that.
I can confirm that the following sequences fail to get nagios-nrpe-
server running:
sudo service nagios-nrpe-server restart
sudo service nagios-nrpe-server stop
sudo
I mean starting it manually using systemd, like this:
systemctl stop nagios-nrpe-server # just in case
systemctl start nagios-nrpe-server # does this succeed?
Starting the service like this shouldn't be any different than starting
it at boot.
** Changed in: nagios-nrpe (Ubuntu)
Status
Paride, unfortunately, when systemd fails to create /var/lib/nagios
during system boot, the nagios-nrpe-server service can not be started
manually. If the operator creates the missing directory and chowns it to
nagios, they can then start the service manually.
** Changed in: nagios-nrpe (Ubuntu)
Hi Danny, thanks for the digging. Can the service be started manually,
when all the other services (including LDAP) are already running?
I'm setting the status of this report to Incomplete for the moment,
which is our way to keep track of bugs where we're waiting for further
feedback. Please chang
I am still testing but it looks like the problem for me is that we have
(had) the nagios user in LDAP. Systemd says that the tmpfiles.d stuff
will NOT work when you specify a non-local user. I think it is more
correct to provision our system-level users in system-level files.
I should have a more
Checking the systemd-tempfiles documentation
(https://freedesktop.org/software/systemd/man/tmpfiles.d.html#Description)
makes me think we could use RuntimeDirectory to fix this issue:
System daemons frequently require private runtime directories below /run
to store communication sockets and simila
10 matches
Mail list logo