Development for LHC@home

I have disabled this function and it works fine.
My suggestion is to disable it by default, as it causes more problems than it cures.
Comments?

I never had problems with VM's stopping due to no heartbeat on time and my system is really not underloaded ;)

Maybe the reason for that is that my VM's always run with priority 'below normal'.

The heartbeat is there as a protection mechanism for hanging/frozen VMs and is working well. There are a few false positives and this is something that we will investigate soon.

2017-10-29 02:11:28 (11632): Guest Log: [INFO] Job finished in slot1 with 200.
2017-10-29 02:11:32 (11632): Guest Log: [INFO] New Job Starting in slot1
2017-10-29 02:11:32 (11632): Guest Log: [INFO] Condor JobID: 4937643.52 in slot1
2017-10-29 02:11:44 (11632): Guest Log: [INFO] Starting pilot in slot1
2017-10-29 02:16:15 (11632): VM Heartbeat file specified, but missing heartbeat.
2017-10-29 02:16:15 (11632): Powering off VM.
2017-10-29 02:21:27 (11632): VM did not power off when requested.
2017-10-29 02:21:27 (11632): VM was NOT successfully terminated.
2017-10-29 02:21:27 (11632): Deregistering VM. (boinc_cb5acb2e8204d4d1, slot#3)

A Heartbeat Error allaround of the Projects!
Because of the Change from Summertime to CET?

https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=366806

I got one of those on a task that was just over 12 hours run time.

(once in a while I get those over at LHC too)

Atlas did not crashed with Heartbeat in this time, but CMS, LHCb and Theory also -dev and production, for my Computer.