search

sni / Thruk

Thruk is a multibackend monitoring webinterface for Naemon, Nagios, Icinga and Shinken using the Livestatus API.
http://www.thruk.org
Other
409 stars 149 forks source link

Error nagios core 4.5.0 #1329

Closed sistemmsn closed 5 months ago

sistemmsn commented 11 months ago

Describe the bug A clear and concise description of what the bug is.

Thruk Version Version of Thruk: 3.10

To Reproduce Steps to reproduce the behavior: After restarting the Nagios service several times it detects it, but when I want to save it cycles, this is happening to me in version 4.5.0, but in 4.4.14 it works without problems

Screenshots image image image image image

Desktop (please complete the following information):

FoUStep commented 10 months ago

I have the same issue, and the issue also occurs with Thruk v.3.12.

It doesn't look like a permission issue, reverting back to an older nagios version works and I even played with permissions (777 and www-data for Debian to the maximum) does not make a difference on live, the folder or the entire structure.

sni commented 10 months ago

Is there anything in Nagios livestatus log? "failed to connect" basically just means the livestatus socket does not respond.

FoUStep commented 10 months ago

Is there anything in Nagios livestatus log? "failed to connect" basically just means the livestatus socket does not respond.

/usr/local/nagios/var/livestatus.log 2024-01-29 13:21:33 deinitializing 2024-01-29 13:21:33 Waiting for main to terminate... 2024-01-29 13:21:33 Waiting for client threads to terminate... 2024-01-29 13:21:33 Logfile cache: flushing complete cache.

/usr/local/nagios/var/nagios.log [1706530893] Nagios 4.5.0 starting... (PID=868161) [1706530893] Local time is Mon Jan 29 13:21:33 CET 2024 [1706530893] LOG VERSION: 2.0 [1706530893] qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized [1706530893] qh: core query handler registered [1706530893] qh: echo service query handler registered [1706530893] qh: help for the query handler registered [1706530893] wproc: Successfully registered manager as @wproc with query handler [1706530893] wproc: Registry request: name=Core Worker 868165;pid=868165 [1706530893] wproc: Registry request: name=Core Worker 868164;pid=868164 [1706530893] wproc: Registry request: name=Core Worker 868163;pid=868163 [1706530893] wproc: Registry request: name=Core Worker 868162;pid=868162 [1706530893] livestatus: Livestatus 1.2.8p11 by Mathias Kettner. Socket: '/usr/local/nagios/var/rw/live' [1706530893] livestatus: Please visit us at http://mathias-kettner.de/ [1706530893] livestatus: Hint: please try out OMD - the Open Monitoring Distribution [1706530893] livestatus: Please visit OMD at http://omdistro.org [1706530893] livestatus: Finished initialization. Further log messages go to /usr/local/nagios/var/livestatus.log [1706530893] Event broker module '/usr/local/lib/mk-livestatus/livestatus.o' initialized successfully.

All seems okay, Nagios 4.5.0 itself works, but Thruk cannot connect.

FoUStep commented 8 months ago

Still the same issue with Nagios Core 4.5.1 and the latest Thruk version 3.14.2.

491: failed to connect - failed to connect to /usr/local/nagios/var/rw/live: Connection refused.

The permissions and Thruk work fine if I downgrade to Nagios Core 4.4.14 on Debian 12. I update Nagios and Thruk regularly to their respective latest versions without any issues, but since 4.5.0, it has trouble connecting Thruk to Nagios through Livestatus (1.2.8p11), which I am not sure if that needs an updated version.

sni commented 8 months ago

no idea tbh, i am not closely following the nagios project anymore. So if it works with an old version of that, i'd assume the issue is somewhere in nagios itself.

sistemmsn commented 5 months ago

Hello, how are you, apparently it is a nagios bug with the livestatus compilation, I am closing the problem because in the end it is from nagios, thank you

Annex the temporary solution of nagios https://support.nagios.com/forum/viewtopic.php?t=75312