Well this actually relates to my other problem (You can find it under
"Problem with computers remaining in pool"). I was hoping I could find
something useful in the log on the Windows node that keeps going down
(since the CollectorLog on the head node doesn't really tell me
anything). So the master log tends to repeat this set of logs: 11/25 15:35:56 DaemonCore: Command received via UDP from host <141.213.33.40:1487> 11/25 15:35:56 DaemonCore: received command 60011 (DC_NOP), calling handler (handle_nop()) 11/25 15:35:56 Child 6064 died, but not a daemon -- Ignored 11/26 15:35:55 Preen pid is 5984 11/26 15:35:56 DaemonCore: Command received via UDP from host <141.213.33.40:4864 > 11/26 15:35:56 DaemonCore: received command 60011 (DC_NOP), calling handler (handle_nop()) 11/26 15:35:56 Child 5984 died, but not a daemon -- Ignored 11/27 15:35:55 Preen pid is 508 11/27 15:35:56 DaemonCore: Command received via UDP from host < 141.213.33.40:4492> 11/27 15:35:57 DaemonCore: received command 60011 (DC_NOP), calling handler (handle_nop()) 11/27 15:35:57 Child 508 died, but not a daemon -- Ignored 11/27 16:31:19 DaemonCore: Command received via UDP from host <141.213.33.30:42707> 11/27 16:31:20 DaemonCore: received command 60014 (DC_INVALIDATE_KEY), calling handler (handle_invalidate_key()) 11/28 15:35:55 Preen pid is 3060 11/28 15:35:56 DaemonCore: Command received via UDP from host <141.213.33.40:4808> 11/28 15:35:56 DaemonCore: received command 60011 (DC_NOP), calling handler (handle_nop()) 11/28 15:35:56 Child 3060 died, but not a daemon -- Ignored I don't actually know if this will help me at all. I just tried turning up the logging to see if I get anything that might help over the weekend. Kevin Erik Paulson wrote: On Fri, Dec 01, 2006 at 01:47:57PM -0500, Kevin Owen wrote:Where can I find documentation about command numbers? I'm trying to decipher the MasterLog, but I don't know what any of the commands mean.Command numbers aren't documented anywhere, they're only haphazardly printed into the log and usually aren't that important for debugging. Can you post the portion of your log you're having trouble with? -Erik _______________________________________________ Condor-users mailing list To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a subject: Unsubscribe You can also unsubscribe by visiting https://lists.cs.wisc.edu/mailman/listinfo/condor-users The archives can be found at either https://lists.cs.wisc.edu/archive/condor-users/ http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR |