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: 62
Posts: 62   Pages: 7   [ Previous Page | 1 2 3 4 5 6 7 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 7722 times and has 61 replies Next Thread
cw64
Advanced Cruncher
Joined: Oct 6, 2007
Post Count: 120
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: New error type?

Result Name: ny306_ 00031_ 13--



<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
ERROR:: Exit at: .\nblist.cc line:711

</stderr_txt>
]]>


Caught one W7-64
----------------------------------------

[Nov 29, 2010 12:23:24 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: New error type?

Here's the error I got today, fortunately after only two minutes so not much computing time was wasted. It's my first HPF2 error in about a week.

Result Name: of660_ 00031_ 12--


<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
ERROR:: Exit at: .\nblist.cc line:711

</stderr_txt>
]]>


Boinc Manager shows the message "Output file of660_00031_12_0 for task of660_00031_12_0 absent" (not sure if the missing output file caused the error or was the result of it). I'm running Windows Vista Business SP2.
----------------------------------------
[Edit 1 times, last edit by Former Member at Mar 19, 2011 8:52:04 PM]
[Mar 19, 2011 8:42:29 PM]   Link   Report threatening or abusive post: please login first  Go to top 
gabranth99
Cruncher
Joined: Mar 1, 2011
Post Count: 26
Status: Offline
Reply to this Post  Reply with Quote 
Re: New error type?

Result Log

Result Name: og264_ 00018_ 1--
<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
ERROR:: Exit at: .\nblist.cc line:711

</stderr_txt>
]]>


im back on linux now after i got an error from milkyway for a total of 3 errors ill have to see if i get errors on linux as i suspect the errors are due to windows
[Apr 3, 2011 12:33:46 AM]   Link   Report threatening or abusive post: please login first  Go to top 
seippel
Former World Community Grid Tech
Joined: Apr 16, 2009
Post Count: 392
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: New error type?

sparkler99,

We are aware of this particular error, but haven't been able to recreate it locally yet. From other reports, it does appear to be limited to Windows and usually happens early in the work unit so not much computing time is lost.

Seippel
[Apr 4, 2011 9:39:28 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: New error type?

I got the error again, this time with only an hour left before completion :(

Boinc log showed output file absent message. I'm using Windows Vista (surprise surprise!)

Result Name: og987_ 00053_ 3--



<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
ERROR:: Exit at: .\nblist.cc line:711

</stderr_txt>
]]>
[Apr 8, 2011 12:27:35 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: New error type?

I got the error again, this time with only an hour left before completion :(

<snip>

As mentioned by seippel in the post before yours, they are "aware of this particular error, but haven't been able to recreate it locally yet."

Keep posting this SAME kind of error messages won't enable them to discover the solution more quickly, so please just let it alone for the time being (and temporarily deselect HPF2 from the machines which keep generating this error).
[Apr 8, 2011 5:14:59 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: New error type?

Sorry but I was disappoitned that I lost 11 hours of crunching time. (doh!)

I have a suggestion...Why not put in an exception handler to nbblist.cc to grant claimed credit when that error occurs. My c-knowledge is a bit rusty, but the code would look something like this. What do you think?

try
{
/* nbblist.cc line 711 goes here */
}
catch (err)
{
give_poor_user_claimed_credit = "Y";
throw(err);
}
----------------------------------------
[Edit 2 times, last edit by Former Member at Apr 16, 2011 12:00:28 AM]
[Apr 8, 2011 10:54:57 PM]   Link   Report threatening or abusive post: please login first  Go to top 
sk..
Master Cruncher
http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif
Joined: Mar 22, 2007
Post Count: 2324
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
ok340 Not OK

Result Log

Result Name: ok340_ 00012_ 12--
<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
ERROR:: Exit at: .\nblist.cc line:711

</stderr_txt>
]]>

Opteron systems seem to fail more often on this project (it's been like this for 2 years). Fortunately I only have two such quads attached and I'm sure there are not too many others.
[May 20, 2011 7:44:34 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: ok340 Not OK

I havn't seen that error in awhile, by any chance are you running FA@H on the same system.. if so that still is a known issue that tends to cause this error. now as far as this error on AMD based chips all the time that I don't know.. running 20 threads off a quad and hex core systems here. hex one was a retrofit of a old dual core and so far no problems have popped up with this project.. my other system quad is doing FA@H. hope this helps you..
[May 21, 2011 1:29:00 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: ok340 Not OK

The *line:711* (formerly line:401) has/had a habit to appear when an AutoDock based science [FA@H, HFCC, never hearing of a DDDT1 or FLU1 correlation] is already running on one of the other cores... sometimes. It's not an AMD special, since I've seen this happen on my Intel Duo Centrino and Q6600 when on Windows and never ever on Linux.

--//--
[May 21, 2011 1:57:24 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 62   Pages: 7   [ Previous Page | 1 2 3 4 5 6 7 | Next Page ]
[ Jump to Last Post ]
Post new Thread