Joined: 14 Jan 10
When a task is suspended for a longer period and is resumed hours later, the running job resumes and ends properly:
Disk usage: 5416 Kb
CPU usage: 29077 s
Clean tmp ...
Run finished successfully
21:45:56 +0200 2019-07-03 [INFO] New Job Starting in slot1
21:45:56 +0200 2019-07-03 [INFO] Condor JobID: 502386.83 in slot1
21:46:01 +0200 2019-07-03 [INFO] MCPlots JobID: 50577439 in slot1
08:38:21 +0200 2019-07-04 [INFO] Job finished in slot1 with 0.
But no new jobs are requested, because the credentials are not valid anymore.
07/04/19 07:27:43 CCBListener: no activity from CCB server in 32733s; assuming connection is dead.
07/04/19 07:27:43 CCBListener: connection to CCB server vccondor01.cern.ch failed; will try to reconnect in 60 seconds.
07/04/19 07:27:43 condor_write(): Socket closed when trying to write 2316 bytes to collector vccondor01.cern.ch, fd is 12, errno=104 Connection reset by peer
07/04/19 07:27:43 Buf::write(): condor_write() failed
07/04/19 07:28:43 authenticate_self_gss: acquiring self credentials failed. Please check your Condor configuration file if this is a server process. Or the user environment variable if this is a user process.
GSS Major Status: General failure
GSS Minor Status Error Chain:
globus_gsi_gssapi: Error with GSI credential
globus_gsi_gssapi: Error with gss credential handle
globus_credential: Error with credential: The proxy credential: /tmp/x509up_u0
with subject: /O=Volunteer Computing/O=CERN/CN=180436/CN=2100061058
expired 286 minutes ago.
The automatic shutdown after the 12 hours elapsed run time is not functioning too.