"Unknown" stuck in the Soft state

[smersh]

Hello,
Some time ago it has been reported that services sometimes are stuck in the soft state.

https://support.nagios.com/forum/viewto ... ilit=stuck

The issue should be fixed in 5.5. However my installation often displays this behaviour, but only with Unknown Service States. No Warning or Critical stuck.

Please check attached images.

Not all the services in the picture are stuck, some of them are correctly in the hard state type.

Regards,
NJ

[scottwilkerson]

What version of XI are you running? This was fixed in 5.5.1

[smersh]

I'm running 5.5.1

[scottwilkerson]

I attempted to re-create this and my service switched to a HARD state as expected after reaching the max_check_attempts.

Does this only happen with particular down hosts? or hosts that are unreachable?

Do you have any dependencies set on these services?

I noticed these just changed state, do these services remain in an unknown state?

Please also post the output of

Code: Select all

ps-ef|grep nagios.cfg

[smersh]

1. There is no any parenting in my config, so the host is down. Hosts never get unreachable here, it's a star network.
2. No, everything remains as you have seen in the screenshot until the host is up again.
3. The host does not need to be necessarily down. For example, trying to re-create the problem, if I change the read community name at the host such that check_snmp plugin can not read data anymore, I can easily observe the problem. All services become unknown when check_snmp does not get the reply, however only some of them become Hard, even after a while (much longer then it actually needs to accomplish 3 of 3 checks).
4. If I create a new host with a non-existent IP then this host is proceeded correctly, all services become hard as they should. But they become hard on the very first check, because they have never been in any other state yet.

Code: Select all

[root@gnt-nagiosxi ~]# ps -ef|grep nagios.cfg
nagios   54814     1 12 01:25 ?        00:00:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios   54833 54814  0 01:25 ?        00:00:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
root     55201 33918  0 01:25 pts/0    00:00:00 grep --color=auto nagios.cfg

Thanks!

[scottwilkerson]

I am going to try to replicate this but so far I have been unsuccessful.

[smersh]

Any progress with my problem?
Do I need to ticket it?

NJ

[scottwilkerson]

Any progress with my problem?
Do I need to ticket it?

NJ

I would, I have not been able to replicate this at all

[smersh]

Ok, thank you.

[scottwilkerson]

Ok, thank you.

Locking will continue in Ticket