Development for LHC@home

It tried for 2 mins before shutting down. I have increased this to 10 minutes and changed the exit code to 0.

I noticed the increase to 10 minutes (thanks) and the returned BOINC-task is not longer treated as a computation error, what's fine,
cause the volunteer could already have returned several success jobs and would be punished with zero credits (thanks again ;)).

With vLHC CMS-tasks I had problems to get X509 credentials this morning.
My host returned the first 2 vLHC-tasks after the VM's shutdown, before I was aware of the problem.
For the 3rd task, I was able to get the credentials after 15 minutes for 1 VM bypassing the wrapper for a moment.
After that it lasted several empty runs, before a new cmsRun-job started. A fourth vLHC-task got the credentials immediately.

https://lhcathome.cern.ch/vLHCathome/result.php?resultid=6607007

(at T4T)

I sure have been getting lots of those lately.

: VM Heartbeat file specified, but missing file system status

followed by Hypervisor System Log:ACCESSDENIED

Hypervisor Errors......good old Oracle VB

---

Mad Scientist For Life

https://lhcathome.cern.ch/vLHCathome/result.php?resultid=6607007

(at T4T)

I sure have been getting lots of those lately.

: VM Heartbeat file specified, but missing file system status

followed by Hypervisor System Log:ACCESSDENIED

Hypervisor Errors......good old Oracle VB

Any ideas why? The ACCESSDENIED may be due the the screen shot feature that was added so may not be the actual error.