No new job after successful returning one and no gracefull VM-shutdown
... show a difference between the run time and CPU time of 9-10 hours. Are these examples of what Crystal Pellet is referring to?
The VM is running over 1 hour without processing a job.
The connection was successful reset, but no new job was sent.
12/14/16 10:53:18 CCBListener: failed to receive message from CCB server vccondor01.cern.ch
12/14/16 10:53:18 CCBListener: connection to CCB server vccondor01.cern.ch failed; will try to reconnect in 60 seconds.
12/14/16 10:53:48 condor_write(): Socket closed when trying to write 2312 bytes to collector vccondor01.cern.ch, fd is 12, errno=104 Connection reset by peer
12/14/16 10:53:48 Buf::write(): condor_write() failed
12/14/16 10:54:18 CCBListener: registered with CCB server vccondor01.cern.ch as ccbid 188.8.131.52:9618?addrs=184.108.40.206-9618+[2001-1458-301-98--100-99]-9618#1227380
On the other 3 VM's I'm getting new jobs.
Normally the VM should gracefully shutdown after 10 minutes idling.
I've the VM-loggings available.
|ID: 28112 · Reply Quote|