-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Session Exception on Notification Endpoint since IcingaWeb2 2.12.1 #5154
Comments
Hey, please have a look at the php error log. There may be a clue (another stacktrace) why this is happening. |
php error log = apache error log? I guess the docker container pipes everything to standard out, correct? If that is the case then there has not been any log entries during that time according to our logging server. We could upgrade again but I would need some clarification on where to look in the official docker. |
Yes. Though, it's stderr were it's piped to. And if you let Icinga Web also log there (by using |
Hey, did you find more in the logs? |
I see this error in our log:
Maybe that helps? |
Oooh, sorry, I didn't try it for myself until now and thus didn't notice that it belongs to Icinga DB Web where a similar issue has been opened last week. 🤦♂️ |
Duplicate of Icinga/icingadb-web#955 |
Describe the bug
When opening https://example.com/icingadb/notifications?history.event_time%20%3E%2030%20minutes%20ago&format=json we get this error:
As we use this in our monitoring clients it breaks the client for us.
To Reproduce
Provide a link to a live example, or an unambiguous set of steps to reproduce this issue. Include configuration, logs, etc. to reproduce, if relevant.
Expected behavior
Notifications should be returned correctly. This worked in 2.12.0.
Screenshots
See above.
Your Environment
Include as many relevant details about the environment you experienced the problem in
Git Commit cd2daeb
Git Commit Datum 2023-11-15
icinga2 --version
): 2.13.8 (since 2.14.0 breaks sync for us)php --version
): 7.4.33The text was updated successfully, but these errors were encountered: