Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #4871] Some errors are not shown in Admin > Logs #1218

Closed
icinga-migration opened this issue Oct 14, 2013 · 2 comments
Closed

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/4871

Created by adrianlzt on 2013-10-14 13:06:28 +00:00

Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2015-05-18 12:17:51 +00:00 (in Redmine)

Icinga Version: 1.9.3
Icinga Web Version: 1.9.1
IDO Version: 1.9.3
OS Version: RHEL 6.4
DB Type: MySQL
DB Version: 5..5
Browser Version: Chrome 29.0.1547.76

While I was browsing through the Icinga-web interface, a yellow box shows in the top right corner saying that an error has happened and I should look at the Logs.

In the logs anything was shown.

If I capture the http traffic between my computer and the Icinga server, I can see a 500 error.
(Packet 520 in the captura_error_500.cap file attached)

To trace this error I have to capture traffic between the Icinga node and the mysql node (I use ido2db), and there it was shown that the max_allowed_packet was too small.

Thanks!

Attachments

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-04-26 09:11:33 +00:00

The problem is merely related to how the framework processes data. exceptions and their output is passed to the caller (JS clientside) directly rendering these yellow popups on the top right corner. The server itself doesn't log/see these exceptions.

@icinga-migration
Copy link
Author

Updated by berk on 2015-05-18 12:17:51 +00:00

  • Target Version set to Backlog

@icinga-migration icinga-migration added this to the Backlog milestone Jan 17, 2017
@dnsmichi dnsmichi removed this from the Backlog milestone Dec 19, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants