Development for LHC@home

Have I missed something ?

Why are the 24 hour jobs no longer stopping after circa 24 hours ?
Three Boinc tasks that started about lunchtime today have all completed and validated in only 6 to 7 hours.

Was this to be expected ?

It will finish the "run" that it is on, when going past the 24H limit.
A "run" takes about 6h, so it is possible, worst case, to run for 30h.

This was done to not loose they job it was working on, when hitting 24h.

Have I missed something ?

Why are the 24 hour jobs no longer stopping after circa 24 hours ?
Three Boinc tasks that started about lunchtime today have all completed and validated in only 6 to 7 hours.

Was this to be expected ?

You may have run foul of the new rule stopping tasks if all the jobs in one "run" terminate with non-zero exit codes. I'll try to investigate later (just got in from work, haven't watched the news yet...).

---

The stderr output for the tasks don't have the Guest Log details in them that the previous version did.

It does have the line...
Detected: Heatbeat check (file: '$s' every 0.000000 seconds)

Is it really checking every 0.000000 seconds ?

PS. Wouldn't bother with the news, if you saw yesterday's and you'll see tomorrow's you'll be fine :-)

I just see the VM Completion File Detected message but no reason. Looks like the logging has broken. Will investigate.

My quick check only gives status 65 non-zero exit codes for you, from Wed & Thurs; those would be the site-local-config file errors we accidentally introduced. Nothing for today.
Which host(s)? You don't have much RAC on any of them so I'm not sure which one(s) you are using -- peering behind the curtains with admin rights doesn't give the convenient "last time host contacted server" column.

---

Another one just did the same, hosts 471, 472, 485 & 761

touch: cannot touch `/home/boinc/shared/heartbeat': No such file or directory
sudo: sorry, you must have a tty to run sudo
sudo: sorry, you must have a tty to run sudo
sudo: sorry, you must have a tty to run sudo
sudo: sorry, you must have a tty to run sudo
sudo: sorry, you must have a tty to run sudo
sudo: sorry, you must have a tty to run sudo
sudo: sorry, you must have a tty to run sudo
sudo: sorry, you must have a tty to run sudo
sudo: sorry, you must have a tty to run sudo
sudo: sorry, you must have a tty to run sudo
sudo: sorry, you must have a tty to run sudo
sudo: sorry, you must have a tty to run sudo
sudo: sorry, you must have a tty to run sudo
sudo: sorry, you must have a tty to run sudo
sudo: sorry, you must have a tty to run sudo
sudo: sorry, you must have a tty to run sudo

Just found this in cron-stderr.
Maybe related.

I think I know why this might be failing. Are the consoles working for you? Will try to look at it today if I can. The tasks and jobs seem to be running fine though.

They were yesterday, haven't checked today (will be another 30 minutes before I can).

Consoles are fine, shows the events being processed etc.

I think that with the new image the /etc/sudoers file had changed and contains requiretty. Have just pushed an update to the bootstrap script that removes this and it should be there once CVMFS is updated and a new task is started. Will check the output of some tasks this evening to see if it worked.