LHC@home

the VM still sometimes fails to use the local squid.

Do you still have some VMs with errors?

VMs are using the local squid again
Working OK so far.
Thanks Laurence.

2018-07-14 03:46:43 (2620): Guest Log: [DEBUG] Detected squid proxy http://192.168.100.137:3128

2018-07-14 03:47:59 (2620): Guest Log: VERSION PID UPTIME(M) MEM(K) REVISION EXPIRES(M) NOCATALOGS CACHEUSE(K) CACHEMAX(K) NOFDUSE NOFDMAX NOIOERR NOOPEN HITRATE(%) RX(K) SPEED(K/S) HOST PROXY ONLINE

2018-07-14 03:47:59 (2620): Guest Log: 2.4.4.0 3533 1 25768 6661 3 1 183731 10240000 2 65024 0 15 93.3333 13 21 http://s1cern-cvmfs.openhtc.io/cvmfs/grid.cern.ch DIRECT 0

(3909): Guest Log: VERSION PID UPTIME(M) MEM(K) REVISION EXPIRES(M) NOCATALOGS CACHEUSE(K) CACHEMAX(K) NOFDUSE NOFDMAX NOIOERR NOOPEN HITRATE(%) RX(K) SPEED(K/S) HOST PROXY ONLINE
2018-07-11 02:53:10 (3909): Guest Log: 2.4.4.0 3540 1 25728 6631 3 1 183741 10240000 2 65024 0 15 100 0 0 http://s1cern-cvmfs.openhtc.io/cvmfs/grid.cern.ch http://192.168.100.137:3128 1
2018-07-11 02:53:11 (3909): Guest Log: [INFO] Reading volunteer information

The heartbeat interval is 20mins and it should beat every minute. So the VM is killed if it takes longer than 20mins to boot or has frozen for 20 minutes.

I'm seeing an increase in heartbeat failures, possibly because the failure of the VM to use the local squid is slowing the startup process considerably. Can't be more precise since the history has been deleted.

Could the timeouts be increased to allow for slow(er) hosts, internet connections, etc and all the stuff (AV updates and whatnot) that go on at startup?

About 4 weeks ago Laurence changed the bootstrap script that is executed by every Theory, CMS and LHCb VM. This script transfers the proxy setting from your local BOINC client into your starting VM

and configures the VM internal CVMFS to use the local proxy..

This should be implemented. If the VM detects a BOINC proxy has been configured with the default squid port, it will try to use it for CVMFS.

sometimes it works...

and sometimes it doesn't...

This should be implemented. If the VM detects a BOINC proxy has been configured with the default squid port, it will try to use it for CVMFS.

Edit: note that this will currently only work with Theory, LHCb and CMS

... Should I need to change this at my end or should it come with the task.?

It's configured server side.
As long as your clients don't show any error you may leave it as it is.

BTW:
Nice to see that the file has been delivered by your proxy.
:-)

..... It could be that the old Sixtrack URL is in a job template or is used by some clients.

Thanks for the warning, Ivan. It's not easy for those who run different combinations of LHC jobs on different hosts to stop only CMS, so will this result in the BOINC server just not sending out CMS jobs (Laurence's fix) ?

I hope so, but I'll remind him just in case.

While our validators have been able to re-validate a majority of tasks ...

Hi Nils,

are you sure that process is finished?

The following tasks are still shown as "validation pending".

.... we are back in normal operation since yesterday evening....

Thanks, Nils... but..
I've still got 25 tasks waiting for validation but the database "can't find workunit" Have these been lost?

From a prevoius post "Sorry, if any running tasks have been removed, this is by accident and we apologize for that."