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: 72
Posts: 72   Pages: 8   [ Previous Page | 1 2 3 4 5 6 7 8 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 250040 times and has 71 replies Next Thread
mdparkhill
Advanced Cruncher
Joined: May 2, 2007
Post Count: 60
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
smile Re: problematic batches? <error_code>-1282</error_code>

Well here's some more bad batches:
Result Name: ts01_ b424_ se0000_ 5--



<core_client_version>6.2.28</core_client_version>
<![CDATA[
<message>
The system cannot write to the specified device. (0x1d) - exit code 29 (0x1d)
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.
ENERGY CHANGE TOLERANCE EXCEEDED
Encountered error. Exiting.

</stderr_txt>
]]>

Result Name: ts06_ b001_ pr89a0_ 5--



<core_client_version>6.2.28</core_client_version>
<![CDATA[
<message>
- exit code 1282 (0x502)
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.

</stderr_txt>
]]>

Result Name: ts06_ a010_ pr91b1_ 3--



<core_client_version>6.2.28</core_client_version>
<![CDATA[
<message>
- exit code 1282 (0x502)
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.

</stderr_txt>
]]>

I wonder who gets beat up the most the techs or the scientist who write the bad code?????
----------------------------------------

[Apr 13, 2010 6:07:33 AM]   Link   Report threatening or abusive post: please login first  Go to top 
pirogue
Veteran Cruncher
USA
Joined: Dec 8, 2008
Post Count: 685
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: problematic batches?

Are the paths in the WUs hard-coded?????
My BOINC install is under D:\BOINC. This error indicates that it was trying to find a file under C:\BOINC.
As a fan of the Mythbusters, I can only say "Well, there's your problem!".

Result Name: ts06_ b002_ pr67b1_ 3--
<core_client_version>6.10.43</core_client_version>
<![CDATA[
<message>
The system cannot write to the specified device. (0x1d) - exit code 29 (0x1d)
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.
forrtl: severe (29): file not found, unit 30, file C:\BOINC\Data\slots\16\fort.30
Image PC Routine Line Source
wcg_dddt2_charmm_ 00B15D6E Unknown Unknown Unknown

Stack trace terminated abnormally.

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

----------------------------------------
[Edit 2 times, last edit by pirogue at Apr 13, 2010 7:45:37 PM]
[Apr 13, 2010 7:43:32 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: problematic batches?

Path hardcoded?... not in my lifetime have I heard of that v.v. BOINC. The paths are determined by whatever the user tells them to be.

Suggest you do a full Registry Scan. Principally the Data_dir is not allowed to be a sub directory to the folder where the core client is installed.

Typically under windows with 6.10.43 the locations would be

C:\program files\BOINC or c:\program files(x86)\BOINC

The data_dir would be

C:\ProgramData\BOINC or whatever location you pointed at during the install process.

If you decided to move the data_dir manually there's both the registry key that needs changing and possibly user created config setting.
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Apr 13, 2010 7:55:39 PM]   Link   Report threatening or abusive post: please login first  Go to top 
pirogue
Veteran Cruncher
USA
Joined: Dec 8, 2008
Post Count: 685
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: problematic batches?

C:\BOINC is nowhere to be found in the registry.

I used the BOINC installer and changed the folders to D:\BOINC and D:\BOINC\Data. I've been running it this way for way over a year and well over 40,000 results.

One of the wingmen had the same error, but it was looking for a different directory.

Here's that one:
Result Name: ts06_ b002_ pr67b1_ 1--
<core_client_version>6.10.43</core_client_version>
<![CDATA[
<message>
Na uvedenzazensyst neme zapisovat. (0x1d) - exit code 29 (0x1d)
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.
forrtl: severe (29): file not found, unit 30, file C:\ProgramData\BOINC\slots\1\fort.30
Image PC Routine Line Source
wcg_dddt2_charmm_ 00B15D6E Unknown Unknown Unknown

Stack trace terminated abnormally.

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

----------------------------------------
[Edit 1 times, last edit by pirogue at Apr 13, 2010 8:09:07 PM]
[Apr 13, 2010 8:08:21 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: problematic batches?

hmmm, that is more than weird to have the drive reference screwing up. When did you install 6.10.43 and what was your exact WOS
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Apr 13, 2010 8:30:01 PM]   Link   Report threatening or abusive post: please login first  Go to top 
pirogue
Veteran Cruncher
USA
Joined: Dec 8, 2008
Post Count: 685
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: problematic batches?

I installed/upgraded on 4/11 on Windows 7 x64.
I also did a GREP in the BOINC directory and there were no hits for C:\BOINC.
----------------------------------------

[Apr 13, 2010 8:43:47 PM]   Link   Report threatening or abusive post: please login first  Go to top 
JmBoullier
Former Community Advisor
Normandy - France
Joined: Jan 26, 2007
Post Count: 3715
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: problematic batches?

I think this error (the application not able to write a file where it should never have tried to write it) may have nothing to do with this particular installation.
I remember we had something similar long ago while starting another new project. I hope I will be able to find it back but that may take time. smile

I would rather suspect some routine in CHARMM not correctly building the path of the file it wants to use. Since the WU could start it has certainly been passed the right directories at the beginning.

But of course I may be wrong... smile
----------------------------------------
Team--> Decrypthon -->Statistics/Join -->Thread
[Apr 14, 2010 10:36:28 AM]   Link   Report threatening or abusive post: please login first  Go to top 
pirogue
Veteran Cruncher
USA
Joined: Dec 8, 2008
Post Count: 685
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: problematic batches?

argh. I had another mystery error. This time the file name wasn't given.


Result Name: ts05_ a293_ ps0000_ 1--
<core_client_version>6.10.36</core_client_version>
<![CDATA[
<message>
The system cannot write to the specified device. (0x1d) - exit code 29 (0x1d)
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.
----------------------------------------

[Apr 15, 2010 4:31:30 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: problematic batches?

It's the same with ts05_ a307_ps0000_ 1 and ts05_ a242_ps0000_ 0 with the latter one having the same error on the first repair WU as well.
[Apr 15, 2010 4:45:37 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: problematic batches?

ts05 b197

Result Log

Result Name: ts05_ b197_ ps0000_ 1--



<core_client_version>6.6.38</core_client_version>
<![CDATA[
<message>
The system cannot write to the specified device. (0x1d) - exit code 29 (0x1d)

14 hours in 35% crunched when failed.
Chris
[Apr 15, 2010 11:29:43 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 72   Pages: 8   [ Previous Page | 1 2 3 4 5 6 7 8 | Next Page ]
[ Jump to Last Post ]
Post new Thread