SCHEDULER - Interrupted system call

[Shane Reber]

Hello everybody, hope someone can help. I am finding this message repeating itself over and over in my /etc/rc.log:

SCHEDULER: Attempt to read the Pipe
socket error: Interrupted system call
SCHEDULER: Pipe read failed - Interrupted system call

What is this? It appears probably 30-50 times a day, and searching for it here on ITRC has produced nothing so far. Syslog doesn't appear to be giving me any clues, it looks normal.

Help!!
Thanks,
Shane

[Jeff Machols]

Shane,

the rc.log is the output for applications starting at boot. It looks like you have a startup script in /sbin/init.d that isn't creating it's own log file so by default it uses rc.log. Do you have maestro or autosys on that machine?

[Shane Reber]

Neither of those programs show in a swlist. The confusing part is that, although I know one of my startup programs is throwing messages in rc.log, rc.log does not tell me which one it is. I also have recieved no system emails about these events. My server is working ok, but this error mssg nearly filled root.

[Jeff Machols]

In the meantime, you can copy /dev/null to /etc/rc.log. That will remove the file and free up some space. You can run

fuser /etc/rc.log

that will show what processes are using the file and you should be able to narrow it down from there.