Closed csammons0x1c closed 5 years ago
this has been fixed meanwhile, please update to the latest stable release.
Thank you for your reply. Could you please tell me what the fix is? I've just updated to version 2.30-3 but testing displays the same behavior as before when clicking "(Logs)".
let me double check, maybe its a new issue. Does this happen for all hosts and services?
I have two backends:
This issue happens for all hosts and services to backend 1.
have you recently updated livestatus? I heard of some issues with livestatus 1.5. Cannot reproduce it right now with naemons livestatus anyway.
Yes, I updated from Livestatus 1.2.2p2 as that version was too old for Nagios v4. So far I have tried Livestatus 1.5.0p18 and 1.5.0p19.
if i remember correclty, 1.4 worked ok.
I downgraded to Livestatus 1.4.0p38 and the issue was resolved.
Thank you for your help!
great :-)
Describe the bug Clicking on '(Logs)' next to "View Alert History For This Service" for a host or service fails with the following error:
nagios: ERROR: 400: The request contains an invalid header. - Filter: Unexpected escape character. (X.X.X.X:6557)
This issue appears to be similar to issues #894 and #917 although these only seem to have addressed an escaped character in history.pm. This fix is already in place in the 2.28-1 version of Thruk and has no impact on this particular issue.
Thruk Version Thruk 2.28-1 Livestatus 1.5.0p19 Nagios 4.4.3
To Reproduce Steps to reproduce the behavior:
Expected behavior This should display log history for the host or service.
Desktop Chrome 75.0.3770.142 Firefox 68.0.1 (64-bit)
Additional context
Sending the above query directly to the livestatus socket is successful and does not give the 400 error response code.