[Condor-users] strange schedd log noise (repeating myself)

[Maxim Kovgan <maxim.kvg@xxxxxxxxx>]

Hello, *!
We've set 6.7.13 up, on the submission machine, 
I had at first many of these lines: 
12/3 01:32:04 IO: Failed to read packet header
in SchedLog


The machine runs Scientific Linux CERN 3 (a RHEL3 clone )
I have disabled ip filtering, so we're not rejecting ourselves.

I've increased debug level on schedd:
ALL_DEBUG = D_FULLDEBUG 
results with this:
=========== Start this ==========================
12/3 01:32:03 DaemonCore: Command received via TCP from host
<132.MY.OWN.IP:10839>
12/3 01:32:03 DaemonCore: received command 1111 (QMGMT_CMD), calling
handler (handle_q)
12/3 01:32:03 condor_read(): Socket closed when trying to read buffer
12/3 01:32:03 IO: Failed to read packet header
12/3 01:32:03 QMGR Connection closed
12/3 01:32:04 DaemonCore: Command received via TCP from host
<132.MY.OWN.IP:11406>
12/3 01:32:04 DaemonCore: received command 1111 (QMGMT_CMD), calling
handler (handle_q)
12/3 01:32:04 condor_read(): Socket closed when trying to read buffer
12/3 01:32:04 IO: Failed to read packet header
12/3 01:32:04 QMGR Connection closed
12/3 01:32:04 DaemonCore: Command received via TCP from host
<132.MY.OWN.IP:12725>
12/3 01:32:04 DaemonCore: received command 1111 (QMGMT_CMD), calling
handler (handle_q)
12/3 01:32:04 condor_read(): Socket closed when trying to read buffer
12/3 01:32:04 IO: Failed to read packet header
12/3 01:32:04 QMGR Connection closed
=========== End this ==========================


Schedd works, but these annoying messages are ... annoying. 
I don't have any idea what's causing this 'condor_read(): Socket closed
when trying to read buffer' error..

Do you ?

And... who is thie QMGR ? Shall I know him ?


Best regards,
Max.


I hope you millionaires are having fun! I just invested half your life
savings in yeast!!