. . The new command line was : -use_sleep_ex 1 -sbs 384 -v

Option to try is -v 6 .
6 is important here.

. . Sorry but I was hoping that it would speed things up enough to get more info.

Nope. Debug/verbose build will speedup things ultimately but because of info and new optimizations I can gather from its output, not because it faster per se. Increased verbosity comes with performance degradation - rule of thumb (for human operation too btw ;) ).

BTW, most likely failures in task come from not correct -v option use.
Will make it more foolproof as result.

. . OK, I get it I am a chatterbox :)

. . I will try again with that change to the command line.

. . But I meant I thought that adding the -sbs 384 would speed it up, I thought I had caused the error crashes by using that. I never suspected the -v command because of a missing '6'. :(

. . I have not found a host for text files but someone pointed me to this site for images:

. . First image -

https://s31.postimg.org/aldaojnff/Change_CUDA50to_So_G_r3472.png

. . [edit]This is the changeover from nonVLAR to Guppie running SoG

. . Second Image -

https://s32.postimg.org/4nce3zuut/Test_Guppi1.png

. . [edit]This is the early stage of 1st Guppi

. . Third image -

https://s32.postimg.org/jk1m7dbc5/Test_Guppi1_full_flight.png

. . This is 1st Guppi still in early stages, seems OK

. . Fourth image -

https://s32.postimg.org/3nq82xyid/Test_Guppi1_75percent.png

. . At this point Guppi has been running for 2 to 3 hours and I expected it to finish within the next hour or so, but it took another 4 hours.

. . [edit]Notice that the GPU and Frame Buffer usage is lower than with nonVLAR task, and the temp is down nearly 20 deg as a result. But surprisingly the usage seems to be dropping even further at the 75% mark which seems to explain why it still took another 4 hours to complete.

.

Could you archive stderr.txt from corresponding slot and send a link to it for download along with link to completed result on webpage.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Could you archive stderr.txt from corresponding slot and send a link to it for download along with link to completed result on webpage.

. . Here are some of the results of errored out tasks -

http://setiathome.berkeley.edu/result.php?resultid=4984162341

http://setiathome.berkeley.edu/result.php?resultid=4984162694

. . The one successful task -

http://setiathome.berkeley.edu/result.php?resultid=4984156421

. . I cannot identify the nonVLAR task that was running during the changeover.

Could you archive stderr.txt from corresponding slot and send a link to it for download along with link to completed result on webpage.

. . I am not sure how to link to an archive I create locally.

Could you archive stderr.txt from corresponding slot and send a link to it for download along with link to completed result on webpage.

. . I am not sure how to link to an archive I create locally.

To upload it to some cloud storage of course.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Could you archive stderr.txt from corresponding slot and send a link to it for download along with link to completed result on webpage.

. . I am not sure how to link to an archive I create locally.

To upload it to some cloud storage of course.

. . OK I thought that is what I had to do.

. . Can you suggest one? The only one I know of only supports image files not text or archives.

. . Can you suggest one? The only one I know of only supports image files not text or archives.

If you've got an Apple account or Microsoft account both of them provide free online storage.
I think Google also have some offerings if you've got a Google account (eg Gmail).
Or there's Dropbox.

---

Grant
Darwin NT

. . Can you suggest one? The only one I know of only supports image files not text or archives.

If you've got an Apple account or Microsoft account both of them provide free online storage.
I think Google also have some offerings if you've got a Google account (eg Gmail).
Or there's Dropbox.

. . Thanks I will try dropbox.
.

Could you archive stderr.txt from corresponding slot and send a link to it for download along with link to completed result on webpage.

. . Second trial, they run OK for 140 mins (give or take one minute) then error out.


http://setiathome.berkeley.edu/result.php?resultid=4986875001

http://setiathome.berkeley.edu/result.php?resultid=4986873722

http://setiathome.berkeley.edu/result.php?resultid=4986874828

http://setiathome.berkeley.edu/result.php?resultid=4986874828

. . They get exit message of EXIT_DISK_LIMIT_EXCEEDED, but there is almost 2GB free on the SETI drive.

. . They get exit message of EXIT_DISK_LIMIT_EXCEEDED, but there is almost 2GB free on the SETI drive.

Check your preferences for disk size settings (Disk: use at most _ GB; Disk: leave free at least; Disk: use at most _% of total)

It's also possible that you're breaking the disk resource limit set in each workunit:

<rsc_disk_bound>33554432.000000</rsc_disk_bound>

but that's 32 MB, so one heck of a long log.

Let one run for a couple of hours (so approaching the danger point), then cheack the file sizes in the slot directory.

stderr transferred to the server is the final 64 KB of the file - but there's a big range between 64 KB and 32 MB. That's probably why Raistmer asked for it by dropbox - you can't paste 32 MB into a thread here, either.

Check your preferences for disk size settings (Disk: use at most _ GB; Disk: leave free at least; Disk: use at most _% of total)

Both on the web settings, and the Boinc manager settings (Depending upon if you use the local or the web settings)

. . They are on a 2GB flashdrive and have access to all of it, no limits.

. . They get exit message of EXIT_DISK_LIMIT_EXCEEDED, but there is almost 2GB free on the SETI drive.

Check your preferences for disk size settings (Disk: use at most _ GB; Disk: leave free at least; Disk: use at most _% of total)

It's also possible that you're breaking the disk resource limit set in each workunit:

<rsc_disk_bound>33554432.000000</rsc_disk_bound>

but that's 32 MB, so one heck of a long log.

Let one run for a couple of hours (so approaching the danger point), then cheack the file sizes in the slot directory.

. . I think that may be it. When I checked the stderr file on one WU shortly before it crashed out the log was already up to 25MB. Hmm Raistmer wanted verbosity set to 6, maybe I will need to run a lower value.

It's also possible that you're breaking the disk resource limit set in each workunit:

<rsc_disk_bound>33554432.000000</rsc_disk_bound>

but that's 32 MB, so one heck of a long log.

Let one run for a couple of hours (so approaching the danger point), then cheack the file sizes in the slot directory.

You're probably right, because the text of the stderr does not start in the usual way, with data about the GPU app and version numbers and so on, but goes directly to this:

<core_client_version>7.6.22</core_client_version>
<![CDATA[
<message>
Disk usage limit exceeded
</message>
<stderr_txt>
or completion
Partial PulseFind_3 (before buffer read): Awaited 1 iterations for completion
Partial PulseFind_3 (before buffer read): Awaited 1 iterations for completion
Partial PulseFind_3 (before buffer read): Awaited 1 iterations for completion

. . The question is can that limit be increased?

.

stderr transferred to the server is the final 64 KB of the file - but there's a big range between 64 KB and 32 MB. That's probably why Raistmer asked for it by dropbox - you can't paste 32 MB into a thread here, either.

. . That's for sure. I need to set up dropbox again, something went wrong with the first try.

It's also possible that you're breaking the disk resource limit set in each workunit:

<rsc_disk_bound>33554432.000000</rsc_disk_bound>

but that's 32 MB, so one heck of a long log.

The question is can that limit be increased?

Yes, it can, but you're venturing further into advanced territory. Be careful, and follow the instructions exactly. If anything doesn't immediately feel comfortable, back off and revert any changes.

0) Be running a short cache when testing!
1) Quit BOINC entirely - that's "Shut down connected client", not just the Manager.
2) Locate the file client_state.xml in the BOINC data directory.
3) Right-click and 'Edit', or 'Open with --- Notepad'. Don't use an XML editor.
4) Open Search & Replace with ctrl+H
5) Paste the entire code line above into the find box.
6) Paste it again into the Replace with box.
7) Edit the Replace version with an extra digit before the decimal point, to make the number ten times bigger.
8) 'Replace all'
9) Save and close
10) Restart BOINC

If the tasks run for more than a day, they'll probably still fail. Rinse and repeat, this time multiplying the bound by 100. And so on.

I need to set up dropbox again, something went wrong with the first try.

You may also use:
http://www.zippyshare.com/

Note:
Since zippyshare uses some misleading [Download] buttons (ads) on the resulting pages you (all) may want to first add uBlock Origin to your browser:
https://chrome.google.com/webstore/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm

https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

It's also possible that you're breaking the disk resource limit set in each workunit:

<rsc_disk_bound>33554432.000000</rsc_disk_bound>

but that's 32 MB, so one heck of a long log.

The question is can that limit be increased?

Yes, it can, but you're venturing further into advanced territory. Be careful, and follow the instructions exactly. If anything doesn't immediately feel comfortable, back off and revert any changes.

If the tasks run for more than a day, they'll probably still fail. Rinse and repeat, this time multiplying the bound by 100. And so on.

. . Thanks Richard I will give that a try.

I need to set up dropbox again, something went wrong with the first try.

You may also use:
http://www.zippyshare.com/

Note:
Since zippyshare uses some misleading [Download] buttons (ads) on the resulting pages you (all) may want to first add uBlock Origin to your browser:
https://chrome.google.com/webstore/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm

https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/

. . Thanks for that I will investigate.