Describe the bug
Thruk is being managed using Nagstamon on our side.
Everything works fine but the "Recheck" or "Recheck All" options in Nagstamon. They just do nothing instead of rechecking the issues.
Thruk Version
Thruk V3.12 in OMD stable for Ubuntu 22.04
To Reproduce
Steps to reproduce the behavior:
Connect Nagstamon to Thruk
Warning or Critical Service Issue for a check must be visible
Try to "Recheck" this issue from Nagstamon (or click "Recheck All")
Expected behavior
The issue should be rechecked (visible by a change in the "last checked" date).
Desktop (please complete the following information):
Windows 11, Nagstamon 3.12 and 3.14
Additional context
In Thruk itself, rechecking works fine.
When executing the recheck from Nagstamon, nothing happens on Thruk's side - even no entry in the thruk log.
Apache error log returns an error code 500, so I turned on the "dump_io" module to see what is posted to the server.
After Nagstamon posts this:
cmd_typ=7&cmd_mod=2&host=localhost&service=Check_Unknown&start_time=2024-03-05+15%3A51%3A00&force_check=on&btnSubmit=Commit
The error log from Apache says:
[Tue Mar 05 15:51:05.398973 2024] [fcgid:warn] [pid 9497] [client SomeIP:60166] mod_fcgid: stderr: Can't locate object method "seek" via package "IO::Handle" at /usr/lib/thruk/perl5/Plack/Request.pm line 78.
The command issued from Thruk itself is not much different, it just additionally contains the "referer", the "CSRFtoken" and a "backend". Is any of them mandatory? (CSRF has been turned off for the machines using Nagstamon already).
FYI - this is the same issue as No1013 described in the Nagstamon project, I just don't know whether this may be a Thruk issue or a Nagstamon issue.
Describe the bug Thruk is being managed using Nagstamon on our side. Everything works fine but the "Recheck" or "Recheck All" options in Nagstamon. They just do nothing instead of rechecking the issues.
Thruk Version Thruk V3.12 in OMD stable for Ubuntu 22.04
To Reproduce Steps to reproduce the behavior:
Expected behavior The issue should be rechecked (visible by a change in the "last checked" date).
Desktop (please complete the following information): Windows 11, Nagstamon 3.12 and 3.14
Additional context In Thruk itself, rechecking works fine. When executing the recheck from Nagstamon, nothing happens on Thruk's side - even no entry in the thruk log. Apache error log returns an error code 500, so I turned on the "dump_io" module to see what is posted to the server. After Nagstamon posts this:
cmd_typ=7&cmd_mod=2&host=localhost&service=Check_Unknown&start_time=2024-03-05+15%3A51%3A00&force_check=on&btnSubmit=Commit
The error log from Apache says:[Tue Mar 05 15:51:05.398973 2024] [fcgid:warn] [pid 9497] [client SomeIP:60166] mod_fcgid: stderr: Can't locate object method "seek" via package "IO::Handle" at /usr/lib/thruk/perl5/Plack/Request.pm line 78.
The command issued from Thruk itself is not much different, it just additionally contains the "referer", the "CSRFtoken" and a "backend". Is any of them mandatory? (CSRF has been turned off for the machines using Nagstamon already).
FYI - this is the same issue as No1013 described in the Nagstamon project, I just don't know whether this may be a Thruk issue or a Nagstamon issue.