locking for external command pipe?
Posted: Wed Aug 21, 2013 2:59 pm
I was browsing my Nagios log for errors and found some broken up external commands. (The date expansion is my own)
I know that my server was under a crazy heavy load and iowait was through the rood when this happened so there were extenuating circumstances, but...
Should I be using file locking when writing to the named pipe? Does nagios itself use and/or honor locking on the pipe? Is there a chance of collision of messages coming into the pipe like my last error message seems to indicate?
Code: Select all
[Wed Aug 21 05:05:20 2013] Warning: Unrecognized external command -> P;
[Wed Aug 21 05:05:20 2013] Warning: Unrecognized external command -> PROCESS_SERVICE;
[Wed Aug 21 05:05:20 2013] Warning: Unrecognized external command -> PROCESS;
[Wed Aug 21 05:05:20 2013] Warning: Unrecognized external command -> PROCESS_SERVICE_CHECK_;
[Wed Aug 21 19:15:04 2013] Warning: Unrecognized external command -> P[1377112504] PROCESS_SERVICE_CHECK_RESULT;HOST1;SERVICE1;0;SERVICE1 OK
I know that my server was under a crazy heavy load and iowait was through the rood when this happened so there were extenuating circumstances, but...
Should I be using file locking when writing to the named pipe? Does nagios itself use and/or honor locking on the pipe? Is there a chance of collision of messages coming into the pipe like my last error message seems to indicate?