nagios.cmd is been read only when debug != 0

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
zeus
Posts: 1
Joined: Thu Oct 01, 2020 9:08 am

nagios.cmd is been read only when debug != 0

Post by zeus »

greetings,

I experience a weird behavior of passive checks ... until I set debug to any value except 0, nagios.cmd is not been read and all passive checks scripts are getting stalled and waiting ... but just I do

Code: Select all

cat nagios.cmd 
all of them are getting finished successfully...

the only log entry related to the issue is this:

Code: Select all

Oct  1 17:16:23 noc nagios: job 7812 (pid=37133): read() returned error 35
neither nagios.log nor nagios.debug doesn't contain anything relevant to the problem

OS: FreeBSD 11.4-RELEASE-p3
nagios version: 4.4.6

any idea where to look at?
Locked