Development for LHC@home

I've completed 3 tasks today but all of them have finished with the message app not supported shutting down. Attached the log of the longest one, the other two just run 5-10min with the same end message.
http://lhcathomedev.cern.ch/vLHCathome-dev/results.php?userid=374

2016-04-21 11:03:34 (6456): Setting checkpoint interval to 600 seconds. (Higher value of (Preference: 60 seconds) or (Vbox_job.xml: 600 seconds))
2016-04-21 11:34:26 (6456): Status Report: Job Duration: '64800.000000'
2016-04-21 11:34:26 (6456): Status Report: Elapsed Time: '6005.172062'
2016-04-21 11:34:26 (6456): Status Report: CPU Time: '3787.392278'
2016-04-21 13:14:32 (6456): Status Report: Job Duration: '64800.000000'
2016-04-21 13:14:32 (6456): Status Report: Elapsed Time: '12011.862814'
2016-04-21 13:14:32 (6456): Status Report: CPU Time: '7062.929675'
2016-04-21 14:54:38 (6456): Status Report: Job Duration: '64800.000000'
2016-04-21 14:54:38 (6456): Status Report: Elapsed Time: '18017.661955'
2016-04-21 14:54:38 (6456): Status Report: CPU Time: '11542.560790'
2016-04-21 16:34:43 (6456): Status Report: Job Duration: '64800.000000'
2016-04-21 16:34:43 (6456): Status Report: Elapsed Time: '24022.470469'
2016-04-21 16:34:43 (6456): Status Report: CPU Time: '14407.690756'
2016-04-21 18:13:00 (6456): Guest Log: [ERROR] App is not supported. Shutting down!
2016-04-21 18:13:00 (6456): VM Completion File Detected.
2016-04-21 18:13:00 (6456): VM Completion Message: 0

[ERROR] App is not supported. Shutting down!

Ignore this message, I don't know why we get this message but it is cosmetic.

Ignore this message, I don't know why we get this message but it is cosmetic.

Tasks shutting down after 10 min is not.

That is very true! We were out of jobs. Have just submitted some more. Hopefully we can automate this soon and have constant job pressure. The error message issue has been identified and a fix should be there in an hour when new tasks are started.

Thanks, Laurence.
Is there any way, we can see, if JOBS are available?
We can see boinc-tasks on the SSP.

Not for now. If the task finishes successfully after about 10 minutes with the message "Normal DAEMON_SHUTDOWN encountered", this suggests that we are out of jobs. However as the results are currently going to dev null, we should not put too many cycles into this. The only purpose here is to identify issues and improve the application.

Console F2 no output.
Console F3,F4,F5, (F6) have output.
However, no progress display and the info in F4 and F5 seem to contain no useful(real-time) information.

No running.log in "show Graphics"

I got this error:

stderr.log:

+ for i in '$ol'
+ '[' -f log.08060270._020799.job.log.tgz.1 ']'
+ flist='*.diag ./jobSmallFiles.tgz ./output.list ./output.list ./log.08060270._020799.job.log.1 ./log.08060270._020799.job.log.1 log.08060270._020799.job.log.tgz.1'
+ for i in '$ol'
+ '[' -f HITS.08060270._020799.pool.root.1 ']'
+ flist='*.diag ./jobSmallFiles.tgz ./output.list ./output.list ./log.08060270._020799.job.log.1 ./log.08060270._020799.job.log.1 log.08060270._020799.job.log.tgz.1 HITS.08060270._020799.pool.root.1'
+ tar czvf result.tar.gz lGcKDmwAJEon7jp7oou28CBqABFKDmABFKDmKJHKDmABFKDmFD4epn.diag ./jobSmallFiles.tgz ./output.list ./output.list ./log.08060270._020799.job.log.1 ./log.08060270._020799.job.log.1 log.08060270._020799.job.log.tgz.1 HITS.08060270._020799.pool.root.1
++ pwd
+ gfal-copy file:////var/lib/condor/execute/dir_24345/result.tar.gz https://data-bridge-test.cern.ch/myfed/atlas-boinc/output/3717416_ATLAS_result
gfal-copy error: 110 (Connection timed out) - DESTINATION OVERWRITE Connection timed out

Cannot start new task.
It is stuck at requesting credentials.
Server issue?

sever fellover
http://lhcathomedev.cern.ch/vLHCathome-dev/forum_thread.php?id=203&postid=2985#2985

Console F1 bootscreen ok.
Credetials seem to work, but tasks shutting down after 7 min.

NO JOBS?

http://lhcathomedev.cern.ch/vLHCathome-dev/result.php?resultid=156950

You are right! Out of jobs. More submitted.

Seems to be working.
Thanks.

Jobs are quite large.
Upload size about 140MB.

Running job output should appear here.

Output at console F2 and "running.log"

Each output file is about 20MB. Where do you get the figure of 140MB?

I waited, until a job was close to finish and monitored the transfer with process explorer.It took about 20 min on a 1Mbit/s upload.

EDIT: jobs run for about 3h on my machine.

At the end of the job, you should see in Console 5 (stderr.log) a gfal-copy command. After than has run it should show the bandwidth experienced.

Bandwidth: xxx

At the end of the job, you should see in Console 5 (stderr.log) a gfal-copy command. After than has run it should show the bandwidth experienced.

Bandwidth: xxx

I just happened to look whilst it was doing a gfal-copy, it did put up the headers for various columns to describe the copying but it then scrolled up so fast as it moved on to the next job/process I didn't get to read it. Can't find it in any of the logs yet.

How many jobs are being run at a time ?

I was looking at F5 with everything scrolling up fast !
F4 is still showing that the bandwidth was 510497 (23,866,170 bytes)

Not sure how many jobs it has done but has been running for over 5 hours now.