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

Alert history does not show - Background job failed. #1236

Open nathanmetcalf opened 1 year ago

nathanmetcalf commented 1 year ago

Describe the bug Viewing "Alert History" - Logs for any service, results in "Background Job Failed" and the below logs in thruk.log

Thruk Version Version of Thruk (and OMD if applicable) Nagios 4.3.4 Thruk 3 Livestatus 1.5.0p23

To Reproduce Steps to reproduce the behavior:

  1. Go to 'Services'
  2. Click on any service
  3. Click on "View Alert history for this service"
  4. See error

Expected behavior Alert history should show

Screenshots image image

Desktop (please complete the following information): Firefox 108.0.2 (64-bit)

Additional context N/A

NH3CL commented 11 months ago

No solution for this?

Additional info from my thruk.log: `2023-12-13 11:15:27 [client 9] error: Filter: Unexpected escape character.

2023-12-13 11:15:27 [client 9] error: And: error combining filters for table 'log': expected 5 filters, but only 4 are on stack `

sni commented 11 months ago

i cannot reproduce this here which makes it hard to provide a solution.

NH3CL commented 11 months ago

What additional info do you need? I'm happy to help as this is a very frustrating bug here....

sni commented 11 months ago

Well, there is something in the livestatus which nagios does not like, but i cannot reproduce it. I even tried setting up nagios with livestatus. But it still works. However, this was a livestatus 1.2.8p27 on nagios 4.4.6 and it seems like it is unnecessarily complicated to get nagios running with livestatus. Have you ever considered simply using Naemon?

Besides that, you could enable "Debug Profiles" at the bottom of the "user profiles" page (user.cgi). This requires the admin role.

image image image image

Might reveil something. Also you could have a look at the livestatus.log if it contains futher details. Or enable debug log level for livestatus which should log all queries.