[HTCondor-devel] confused about condor_squawk tool


Date: Fri, 14 Dec 2012 16:47:47 -0600
From: Nathan Panike <nwp@xxxxxxxxxxx>
Subject: [HTCondor-devel] confused about condor_squawk tool
I was looking at flocking and it looked like condor_squawk would be
useful for debugging the flocking code.  So I did

"ln condor_vacate condor_squawk"

in my development directory and ran

condor_squawk -daemon schedd
 > dump

and then the following appears in my Schedlog.

12/14/12 16:41:03 condor_read(): Socket closed when trying to read 4 bytes from <128.105.14.28:49689>
12/14/12 16:41:03 condor_read(): Socket closed when trying to read 5 bytes from <128.105.14.28:49689>
12/14/12 16:41:03 IO: EOF reading packet header
12/14/12 16:41:03 DaemonCore: Can't receive command request from 128.105.14.28 (perhaps a timeout?)
12/14/12 16:41:05 Dumping state for Squawk
12/14/12 16:41:16 condor_read(): Socket closed when trying to read 5 bytes from <128.105.14.28:60642>
12/14/12 16:41:16 IO: EOF reading packet header

Is condor_squawk expected to work; is there something else I can use to
dump the flocking state?  condor_status does not seem to do the trick.

Nathan Panike
[← Prev in Thread] Current Thread [Next in Thread→]