Development for LHC@home

The graceful shutdown of VMs has now been implemented. When the VM is older than 24 hours,
after the current run has finished the VM will shut itself down using the completion_trigger_file method.

It's not working as expected.

Run 4 ended after 27 hours and 50 minutes elapsed time and 25 hours and 12 minutes cpu time.

Me waiting for the shutdown, however:

Run 5 started and after 2 minutes
Run 6 started and after 2 minutes
Run 7 started and after 2 minutes
Run 8 started.

Enough waiting, so I shutdown the VM myself graceful with a trigger file.

The forced shutdown at 36 hours works.

Shame it had got as far as the 223rd record on the last job but hopefully it shouldn't usually run for that long.

The forced shutdown at 36 hours works.

Shame it had got as far as the 223rd record on the last job but hopefully it shouldn't usually run for that long.

The kill after 36 hours wallclock is just for when the graceful method did not work.
So far I did not notice the graceful shutdown myself, but appearently it's working for others:

2016-02-04 22:13:04 (69032): Status Report: Elapsed Time: '96000.000000'
2016-02-04 22:13:04 (69032): Status Report: CPU Time: '70718.410000'
2016-02-04 22:56:28 (69032): Guest Log: [INFO] CMS glidein Run 5 ended
2016-02-04 22:57:28 (69032): Guest Log: [INFO] Time exceeded. Shutting down!
2016-02-04 22:57:28 (69032): VM Completion File Detected.
2016-02-04 22:57:28 (69032): Powering off VM.

So far I did not notice the graceful shutdown myself, but appearently it's working for others

Now I had 2 tasks ending gracefully myself:

2016-02-06 15:20:13 (10296): Status Report: Elapsed Time: '85725.281227'
2016-02-06 15:20:13 (10296): Status Report: CPU Time: '82063.249643'
2016-02-06 16:55:12 (10296): Guest Log: [INFO] CMS glidein Run 10 ended
2016-02-06 16:56:12 (10296): Guest Log: [INFO] Time exceeded. Shutting down!
2016-02-06 16:56:12 (10296): VM Completion File Detected.
2016-02-06 16:56:12 (10296): Powering off VM.

2016-02-06 15:20:38 (14984): Status Report: Elapsed Time: '85152.827036'
2016-02-06 15:20:38 (14984): Status Report: CPU Time: '81513.798520'
2016-02-06 16:11:40 (14984): Guest Log: [INFO] CMS glidein Run 13 ended
2016-02-06 16:12:40 (14984): Guest Log: [INFO] Time exceeded. Shutting down!
2016-02-06 16:12:40 (14984): VM Completion File Detected.
2016-02-06 16:12:40 (14984): Powering off VM.

How are you managing to get new jobs? I recently get the message that I need a huge amount of memory.

How are you managing to get new jobs? I recently get the message that I need a huge amount of memory.

That were CMS-tasks from the VirtualLHC@home project using the same VM and software.
A few hundreds of CMS-tasks were submitted over there yesterday and quickly gone.

How are you managing to get new jobs? I recently get the message that I need a huge amount of memory.

It is actually disk space.

Server is messed up.