some time ago I updated a existing nagiosql 3.2.X instance to 3.4.1 - since this update from webgui it's not possible anymore to restart Nagios Daemon.
OS: Debian 10
NagiosQL: 3.4.1
Nagios: 4.3.4-3
I will attach a screenshot of the message - the nagios.cmd file is located here "/var/lib/nagios4/rw/nagios.cmd" and the path is also configured in NagiosQL.
Has anyone a hint or an idea how this can be fixed by myself?
NagiosQL uses the PID file to determine if the Nagios daemon is running or not. If the Nagios demon does not write a PID file this leads to this problem.
You can work around this by specifying an existing file, e.g. nagios.cmd, for the PID file in the configuration domain. NagiosQL only checks if the file exists - it does not read its content.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey there,
some time ago I updated a existing nagiosql 3.2.X instance to 3.4.1 - since this update from webgui it's not possible anymore to restart Nagios Daemon.
OS: Debian 10
NagiosQL: 3.4.1
Nagios: 4.3.4-3
I will attach a screenshot of the message - the nagios.cmd file is located here "/var/lib/nagios4/rw/nagios.cmd" and the path is also configured in NagiosQL.
Has anyone a hint or an idea how this can be fixed by myself?
Thanks in advance
NagiosQL uses the PID file to determine if the Nagios daemon is running or not. If the Nagios demon does not write a PID file this leads to this problem.
You can work around this by specifying an existing file, e.g. nagios.cmd, for the PID file in the configuration domain. NagiosQL only checks if the file exists - it does not read its content.