Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #10931] Exception stack trace on icinga2 client when the master reloads the configuration #3816
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10931
Created by seferovic on 2016-01-05 13:04:53 +00:00
In my test environment I have a master server which sends commands to icinga2 agents. On reload of the master server the connection to the agent is being destroyed (?!) and the icinga2 agent logs following
I am not sure if this should be considered a bug, but I don't expect to see such exceptions in main log only because the master reloaded the config... but I might be wrong, so please excuse the newbie ;)
Updated by mfriedrich on 2016-01-11 13:13:14 +00:00
It is fairly normal that a reload of the Icinga 2 master closes the tcp connections causing the client to log an error message. It might be helpful to hide the stack trace in such cases though it sometimes contains valuable information.
Updated by tgelf on 2016-01-20 12:24:15 +00:00
Might be related to this code snippet (or something similar):
Icinga should not try to process available data if there is no such, especially when it already decided to destroy the socket. I'll reset priority to normal, I guess this could be easy to fix. Those exceptions are pretty disturbing as you get a lot of them in larger setups, they are disturbing/confusing if in case you are looking for problems in your logs.
Updated by ziaunys on 2016-01-26 18:57:22 +00:00
I'm not sure if this is related, but I constantly see this exception in the logs of all my Icinga2 (2.4.1) agents:
I don't know if this actually causes problems because I don't understand the error.
Updated by seferovic on 2016-02-11 12:05:41 +00:00
Sorry for the late feedback. I just installed latest snapshot and unfortunately I run into a "endless restart loop" due to configuration changes. This is probably closed, but I will review it once more after resolving the actual problem at hand.