Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 88
Posts: 88   Pages: 9   [ Previous Page | 1 2 3 4 5 6 7 8 9 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 114320 times and has 87 replies Next Thread
NixChix
Veteran Cruncher
United States
Joined: Apr 29, 2007
Post Count: 1187
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Beta test for Say No to Schistosoma (May 24, 2012) Issues Thread

Got 3 beta units and found them running on 2 computera. Shut down both computers. All 3 jobs resumed at last checkpoint.

Cheers coffee
----------------------------------------

[May 25, 2012 6:57:08 AM]   Link   Report threatening or abusive post: please login first  Go to top 
deltavee
Ace Cruncher
Texas Hill Country
Joined: Nov 17, 2004
Post Count: 4846
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Beta test for Say No to Schistosoma (May 24, 2012) Issues Thread

Got several all on w7 boxes. Not able to break any of the WUs on the boxes I currently have access to. Received one resend whose previous user had the following, but has since validated:

<core_client_version>6.12.34</core_client_version>
<![CDATA[
<message>
- exit code -1073741790 (0xc0000022)
</message>
<stderr_txt>

</stderr_txt>
]]>
----------------------------------------

[May 25, 2012 7:28:47 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Beta test for Say No to Schistosoma (May 24, 2012) Issues Thread

This error is discussed in this BFS article: http://boincfaq.mundayweb.com/index.php?view=175

Also discussed in our own FAQ's as an old Vista issue [which means it could happen too on W8] See http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=12856 for workaround for anyone who suffers the ''too fast to survive". Possibly, this is the bug the techs are after, but it is likely related to our hard effort in breaking things [Non So]?

--//--

edit: hmmm, Google was asked for the xxxx1790 error and pops up xxxx1510. Cracks in the ceiling? Searching the forums, tracked it back to a first of very few reports: https://secure.worldcommunitygrid.org/forums/...ead,25646_offset,0#229703 suggesting AV/Security software obstruction. Not a biggest surprise as it really is a new science app build that the guards need to learn about... Beta testing "hands on" once again called for.
----------------------------------------
[Edit 4 times, last edit by Former Member at May 25, 2012 9:49:51 AM]
[May 25, 2012 8:09:06 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Crystal Pellet
Veteran Cruncher
Joined: May 21, 2008
Post Count: 1316
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Beta test for Say No to Schistosoma (May 24, 2012) Issues Thread

On 1 machine I got 4 resends (2 wingman: exit code -1073741790 and 2 wingman: couldn't start CreateProcess() failed) with the initial 4 days deadline (Win7, no new host)
BOINC 7.0.28 and 8 tasks running High Priority of another (no WCG) project. Minimum work buffer 3 days acting as 'connect every 3 days'.
I don't expect so much intelligence, that WCG resends become 100% of the initial deadline then.
On another machine the resends have the for resends normal 40% reduced deadline (BOINC 6.12.34)
----------------------------------------

[May 25, 2012 9:39:49 AM]   Link   Report threatening or abusive post: please login first  Go to top 
nanoprobe
Master Cruncher
Classified
Joined: Aug 29, 2008
Post Count: 2998
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Beta test for Say No to Schistosoma (May 24, 2012) Issues Thread

I received 2 resends. When I checked they were both user aborted. thinking
Thanks for the gift biggrin
Tried restarts, shutdowns and even pulled the plug on 1 machine. All the WUs restarted/resumed normally.
Well done techs.
----------------------------------------
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.


[May 25, 2012 10:00:44 AM]   Link   Report threatening or abusive post: please login first  Go to top 
genes
Advanced Cruncher
USA
Joined: Jan 28, 2006
Post Count: 132
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Beta test for Say No to Schistosoma (May 24, 2012) Issues Thread

Got 2 each on 2 Win7 quads, one an x86 and one an x64, sharing with CFSW. Killed BOINC and restarted when they were running, one had gotten up to 83.333% done, no significant loss of work done.
[May 25, 2012 10:46:49 AM]   Link   Report threatening or abusive post: please login first  Go to top 
JollyJimmy
Advanced Cruncher
USA
Joined: Aug 23, 2005
Post Count: 115
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Beta test for Say No to Schistosoma (May 24, 2012) Issues Thread

So, I received 19 beta units (woohoo!! dancing ) and when I check this morning, 2 of them are still running, and the remaining 17 have all errored out with zero credit with exit code -1073741790 (0xc0000022). No fair! crying
I have seen the FAQ comments about this being due to an abrupt shutdown, however, that is not a plausible explanation here:
I am running BOINC on three machines, two i9 desktops and one i5 Laptop. The units that have errored out are all from the desktops (laptop units still in progress). I do not have direct access to the desktops, but the likelihood of these errors being caused by unexpected shutdowns is close to zip - the machines are typically running undisturbed, almost idle, and one of them is even plugged into a UPS. Also the beta units that errored out were returned to WCGrid over the course of several hours: No way these machines had "many" unexpected reboots in that timeframe.
Both machines are running 64bit BOINC (as a service, and yes, on Vista!), version 6.10.58. Here are the units that failed:
BETA_ SN2S_ ABE97928_ 0000031_ 0251_ 2--
BETA_ SN2S_ ABE97928_ 0000034_ 0794_ 1--
BETA_ SN2S_ ABE97928_ 0000032_ 0935_ 1--
BETA_ SN2S_ ABE97928_ 0000032_ 0929_ 1--
BETA_ SN2S_ ABE97928_ 0000032_ 0624_ 1--
BETA_ SN2S_ ABE97928_ 0000032_ 0477_ 1--
BETA_ SN2S_ ABE97928_ 0000028_ 0339_ 1--
BETA_ SN2S_ ABE97928_ 0000030_ 0442_ 1--
BETA_ SN2S_ ABE97928_ 0000028_ 0236_ 1--
BETA_ SN2S_ ABE97928_ 0000034_ 0956_ 0--
BETA_ SN2S_ ABE97928_ 0000034_ 0104_ 0--
BETA_ SN2S_ smp005470_ 0000002_ 0165_ 1--
BETA_ SN2S_ smp005470_ 0000001_ 0378_ 0--
BETA_ SN2S_ smp005470_ 0000001_ 0277_ 1--
BETA_ SN2S_ smp005470_ 0000001_ 0260_ 1--
BETA_ SN2S_ smp005470_ 0000001_ 0463_ 0--
BETA_ SN2S_ smp005470_ 0000000_ 0097_ 0--
----------------------------------------
[May 25, 2012 11:08:06 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Beta test for Say No to Schistosoma (May 24, 2012) Issues Thread

So, I received 19 beta units (woohoo!! dancing ) and when I check this morning, 2 of them are still running, and the remaining 17 have all errored out with zero credit with exit code
(0xc0000022). No fair! crying
I have seen the FAQ comments about this being due to an abrupt shutdown, however, that is not a plausible explanation here:
I am running BOINC on three machines, two i9 desktops and one i5 Laptop. The units that have errored out are all from the desktops (laptop units still in progress). I do not have direct access to the desktops, but the likelihood of these errors being caused by unexpected shutdowns is close to zip - the machines are typically running undisturbed, almost idle, and one of them is even plugged into a UPS. Also the beta units that errored out were returned to WCGrid over the course of several hours: No way these machines had "many" unexpected reboots in that timeframe.
Both machines are running 64bit BOINC (as a service, and yes, on Vista!), version 6.10.58. Here are the units that failed:
BETA_ SN2S_ ABE97928_ 0000031_ 0251_ 2--
BETA_ SN2S_ ABE97928_ 0000034_ 0794_ 1--
BETA_ SN2S_ ABE97928_ 0000032_ 0935_ 1--
BETA_ SN2S_ ABE97928_ 0000032_ 0929_ 1--
BETA_ SN2S_ ABE97928_ 0000032_ 0624_ 1--
BETA_ SN2S_ ABE97928_ 0000032_ 0477_ 1--
BETA_ SN2S_ ABE97928_ 0000028_ 0339_ 1--
BETA_ SN2S_ ABE97928_ 0000030_ 0442_ 1--
BETA_ SN2S_ ABE97928_ 0000028_ 0236_ 1--
BETA_ SN2S_ ABE97928_ 0000034_ 0956_ 0--
BETA_ SN2S_ ABE97928_ 0000034_ 0104_ 0--
BETA_ SN2S_ smp005470_ 0000002_ 0165_ 1--
BETA_ SN2S_ smp005470_ 0000001_ 0378_ 0--
BETA_ SN2S_ smp005470_ 0000001_ 0277_ 1--
BETA_ SN2S_ smp005470_ 0000001_ 0260_ 1--
BETA_ SN2S_ smp005470_ 0000001_ 0463_ 0--
BETA_ SN2S_ smp005470_ 0000000_ 0097_ 0--

If you look at the edits of my previous post, the security software is the closer suspect v.v. the -1073741790. One confirmed that back in 2009. What AV/Sec.Ware are you running? Any Event viewer entries of AV message log records [whence you can get to that information]? Is there a BOINC data dir scan exclusion set?

--//--
----------------------------------------
[Edit 2 times, last edit by Former Member at May 25, 2012 11:28:31 AM]
[May 25, 2012 11:26:10 AM]   Link   Report threatening or abusive post: please login first  Go to top 
kateiacy
Veteran Cruncher
USA
Joined: Jan 23, 2010
Post Count: 1027
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Beta test for Say No to Schistosoma (May 24, 2012) Issues Thread

I guess this isn't news since I run Linux, but I received 8 betas spread over 3 machines (running Ubuntu 10.04, Xubuntu 11.10, and Xubuntu 12.04). I did some required system updates and rebooted each machine, and the betas restarted correctly at checkpoints.
----------------------------------------

[May 25, 2012 12:18:15 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Beta test for Say No to Schistosoma (May 24, 2012) Issues Thread

One is running on an older laptop, celeron. Did a full shut down and restart (did laundry, painted house, read war and peace while waiting) finally restarted no issues apparant.

Have another machine that was lucky enough to get them, a 2 core AMD with a gig or so of ram in it. It was crunching other stuff and did not want to goto the beta's so I suspended each task until it had no choice BUT to run the beta's which it is doing now. Communicated with the client a lot during this event.

As soon as I get an hour or so on them Ill shut the machine down and see what happens. I think it will run fine though.

Will let you know of any other issues.

Aaron
[May 25, 2012 12:19:16 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 88   Pages: 9   [ Previous Page | 1 2 3 4 5 6 7 8 9 | Next Page ]
[ Jump to Last Post ]
Post new Thread