Development for LHC@home

ERROR:root:No message received! Nothing to do!

For over at least 1 hour . . .

ERROR:root:No message received! Nothing to do!

For over at least 1 hour . . .

Over 8 hours, now. Shall we leave em running, pause them a while or what!

ERROR:root:No message received! Nothing to do! . . .

I'm not sure I understand... Where is this error message coming from and what job queue are you saying is empty? I see plenty of tasks available on the server status page and my hosts haven't had any problem getting work, but maybe that's not what you are referring to.

CP is referring to the CMS job queue which feeds jobs into the VM from CERN. The error message he sees is on the 5th VM console output (shown by the "Show VM Console" button, followed by CTRL-ALT-F5 to select the 5th screen). Right now there is a problem at the CMS end which the admins know about and will fix asap.

The BOINC tasks are what you see on the server status page and there's no shortage of these - each BOINC task runs 24 hours and just starts a new VM each time.

Patience...

More jobs have been submitted.

Cheers!
Lets un-suspend the tasks and see what happens.

All is well here.

I might try this on another OS version next to see how that goes.

---

Mad Scientist For Life

Cheers!
Lets un-suspend the tasks and see what happens.

Ahh well, my VM sulked instead of restarting.
Aborted and running a new one.

Cheers!
Lets un-suspend the tasks and see what happens.

Ahh well, my VM sulked instead of restarting.
Aborted and running a new one.

I see you are running with a Win8.1 OS and that happened to be the one I was thinking about testing next (Win7 works on a desktop and my laptop along with vLHC and Atlas at the same time)

You seem to get about every other task to be completes.

So 8.1 must work if the other things are running properly.

Were you changing the *preferences* while it was running?

http://boincai05.cern.ch/CMS-dev/result.php?resultid=55937

And like we do with Atlas and on rare occasion vLHC check for any *image.vdi that needs to be *removed* since at times they just sit there instead of doing it automatically.

Hi, just started my first task. It's been running for 4,5 hours now and the whole CMSJobAgent-stderr.log is full of "ERROR:root:No message received! Nothing to do!" with not a single line that is different than that. Is everything normal?

Hi,

The jobs run for 24 hours and having checked my CMSJobAgent-stderr.log file I do have a lot of those error messages but do have some others indicating work is happening.

What does your local stderr.txt file (in the Slots folder) show ?

Mine has lines at the end like...


2015-07-02 18:27:00 (6984): Status Report: Job Duration: '86400.000000'
2015-07-02 18:27:00 (6984): Status Report: Elapsed Time: '24000.000000'
2015-07-02 18:27:00 (6984): Status Report: CPU Time: '3446.873295'
2015-07-02 20:06:57 (6984): Status Report: Job Duration: '86400.000000'
2015-07-02 20:06:57 (6984): Status Report: Elapsed Time: '30000.495445'
2015-07-02 20:06:57 (6984): Status Report: CPU Time: '4248.531234'
2015-07-02 21:46:55 (6984): Status Report: Job Duration: '86400.000000'
2015-07-02 21:46:55 (6984): Status Report: Elapsed Time: '36000.495445'
2015-07-02 21:46:55 (6984): Status Report: CPU Time: '5017.319762'

indicating something is being done !
Also, CPU time used (in BOINC manager) for the task increases

Ah okay thanks PDW! My 'CMSJobAgent-stderr.log' still only consists of the error messages (one every minute!), but in the stderr.txt file I have three completed jobs showing at the end (and of course the CPU time increases in the BOINC manager).

I would say that it is a little bit confusing that CMSJobAgent-stderr.log only shows errors when it is the file that is found through the BOINC manager and not like the stderr file for which you have to navigate through the folders.

Maybe write some lines for completed jobs in it too?


One other thing regarding the CMSJobAgent-stderr.log file:

There seem to be some characters in it that can't be shown correctly:

As you can see the first character and the one after the '!' are the ones I'm talking about.
Overall the beginning and the end of the line seem a little bit odd. Is that intended?

I just looked again at the CMSJobAgent-stderr.log file and mine was a screen full of error messages but I couldn't find how to scroll back to see earlier ones. To be honest I looked once when I first started running the tasks and just found it easier to look at my local log files.

The weird character looks like the start of a formatting command that couldn't be handled (interpreted) by the output device so was output as best it could. You need to get an answer from a developer if you want specifics but I don't believe it is anything to worry about.

That's what I thought too. I just wanted to point it out to the developers.

We should get some interesting data from the latest LHC design features



(scanned from tomorrow's edition of the UK magazine "New Scientist". Work that one out if you can!)

Serious design flaw right there.

The picnic area should be much, much closer to the pub !

That's why you should always consult with your users before finalising the design!

There seem to be some characters in it that can't be shown correctly:

As you can see the first character and the one after the '!' are the ones I'm talking about.
Overall the beginning and the end of the line seem a little bit odd. Is that intended?

Those look like some old VT-series terminal escape characters, perhaps designed to set some screen attribute and turn it off again.

I think it would run better if the Pub and the Picnic Area used the Wormhole so you are ready for a voyage to another Galaxy and a planet that has another Pub and Picnic Area

There seem to be some characters in it that can't be shown correctly:

As you can see the first character and the one after the '!' are the ones I'm talking about.
Overall the beginning and the end of the line seem a little bit odd. Is that intended?

Those look like some old VT-series terminal escape characters, perhaps designed to set some screen attribute and turn it off again.

Yes, (escape)[(number)m -- turning on and off colour text attributes. On the right terminal they show up as red or some such.

---

Okay, so back to the point...
It seems that the CERN job queue (databridge, copilot, whatever) has been unable to supply jobs for some weeks.
Do you guys want us to continue running BOINC jobs, or leave off until an announcement?