BOINC writes messages into workunit files?


log in

Advanced search

Message boards : Number crunching : BOINC writes messages into workunit files?

Author Message
Profile Link
Avatar
Send message
Joined: 18 Sep 03
Posts: 823
Credit: 1,543,753
RAC: 416
Germany
Message 1298630 - Posted: 25 Oct 2012, 14:56:45 UTC

When I started up my desktop computer today (or actually wake it up from hibernation) it asked for new WUs from SETI... so far OK. But than all but one WU failed with download error, according to log the files were too big and md5 failed.

I opened one of those and found the following at the beginning:

25-Oct-2012 08:15:07 [SETI@home] Started download of 17au12aa.26060.372290.140733193388045.10.59
25-Oct-2012 08:15:10 [Milkyway@Home] Sending scheduler request: To fetch work.
25-Oct-2012 08:15:10 [Milkyway@Home] Requesting new tasks for ATI GPU
<workunit>
<workunit_header>
<name>17au12aa.26060.372290.140733193388045.10.59</name>
<group_info>
<tape_info>
<name>17au12aa</name>
<start_time>2456158.4523021</start_time>
<last_block_time>2456158.4523021</last_block_time>
<last_block_done>372290</last_block_done>
<missed>0</missed>
<tape_quality>0</tape_quality>
<beam>10</beam>
(...)


Other WU files looked pretty much the same, contained messages about the failed downloads, the beginning of their own download and whatever else BOINC wanted to tell me...

The first 3 lines should actually be in the stdoutdae.txt, which, after it was just created since the old one reached the limit, only contained 4 messages about resuming computation/network (the usual after waking up). Nothing more. Apparently all other messages since than were written either to the downloaded WUs or to NUL (or something I haven't found yet).

Any ideas on how that could happen? My BOINC data directory is excluded from my antivirus, so it shouldn't be that at least.

I had such problem already once, trashed quite many Rosetta WUs before I noticed and stopped it, at that time the only way to fix it was to reboot the computer, restarting BOINC didn't help and I haven't look into the downloaded files, so didn't know what was wrong with them. This time I deleted the new and almost empty stdoutdae.txt and restarting BOINC was enough, but I'm not sure if it was actually necessary, I just deleted it because something seemed to be wrong with this file.

BTW: I fixed all those WUs, so you won't find any errors on my computer.
____________
.

Profile Link
Avatar
Send message
Joined: 18 Sep 03
Posts: 823
Credit: 1,543,753
RAC: 416
Germany
Message 1304434 - Posted: 10 Nov 2012, 12:40:02 UTC

Happened again when BOINC noticed after wakeing up from hibernation mode, that the old file reached the size limit. The first 4 lines went to the new file, the rest either to currently downloading files or not saved anywhere if no downloads were active (or I couldn't find it). Deleting the new stdoutdae.txt file when BOINC was running didn't help, had to restart BOINC, than it worked again normal.

As a workaround I increased the size limit for that file, but I still hope, that someone will have an idea for a permanent solution.
____________
.

Message boards : Number crunching : BOINC writes messages into workunit files?

Copyright © 2014 University of California