Page 1 of 1
Project: 10001 (Run 644, Clone 2, Gen 1) - ERROR 0x8b
Posted: Tue Dec 22, 2009 6:15 pm
by tonic
Code: Select all
[16:42:53] + Attempting to get work packet
[16:42:53] - Connecting to assignment server
[16:42:54] - Successful: assigned to (129.74.85.48).
[16:42:54] + News From Folding@Home: Welcome to Folding@Home
[16:42:54] Loaded queue successfully.
[16:42:56] + Closed connections
[16:42:56]
[16:42:56] + Processing work unit
[16:42:56] Core required: FahCore_b4.exe
[16:42:56] Core found.
[16:42:56] Working on Unit 02 [December 22 16:42:56]
[16:42:56] + Working ...
[16:42:56] *********************** Log Started 22/Dec/2009 16:42:56 *********************$
[16:42:56] ************************** ProtoMol Folding@Home Core ************************$
[16:42:56] Version: 19
[16:42:56] Type: 180
[16:42:56] Core: ProtoMol
[16:42:56] Website: http://folding.stanford.edu/
[16:42:56] Copyright: (c) 2009 Stanford University
[16:42:56] Author: Joseph Coffland <joseph@cauldrondevelopment.com>
[16:42:56] Args: -dir work/ -suffix 02 -checkpoint 15 -forceasm -lifeline 30820
[16:42:56] -version 602
[16:42:56] ************************************ Build ***********************************$
[16:42:56] Date: Dec 16 2009
[16:42:56] Time: 08:56:00
[16:42:56] Revision: 1746
[16:42:56] Compiler: Intel(R) C++ g++ 4.1 mode 1110
[16:42:56] Options: -std=gnu++98 -mia32 -O3 -funroll-loops
[16:42:56] -axSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 -restrict
[16:42:56] Platform: Linux 2.4.27-3-386
[16:42:56] Bits: 32
[16:42:56] ************************************ System **********************************$
[16:42:56] OS: Linux 2.6.28-15-generic i686
[16:42:56] CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
[16:42:56] CPU ID: GenuineIntel Family 6 Model 15 Stepping 11
[16:42:56] CPUs: 4 Logical, 1 Physical
[16:42:56] Memory: 1.92 GB
[16:42:56] ******************************************************************************$
[16:42:56] Project: 10001 (Run 644, Clone 2, Gen 1)
[16:42:56] Reading tar file par_all27_prot_lipid.inp
[16:42:56] Reading tar file scpismQuartic.inp
[16:42:56] Reading tar file ww_exteq_nowater1.pdb
[16:42:56] Reading tar file ww_exteq_nowater1.psf
[16:42:56] Reading tar file checkpt
[16:42:56] Reading tar file ww_exteq_nowater1.22.pos
[16:42:56] Reading tar file ww_exteq_nowater1.22.vel
[16:42:56] Reading tar file protomol.conf
[16:42:56] Reading tar file core.xml
[16:42:56] Digital signatures verified
[16:42:56] ERROR: Exception in thread 2: @ fah/net/Socket.cpp:139:bind 0: Could not bind $
[16:42:56] Completed 0 out of 200000 steps (0%)
[16:45:51] Completed 2000 out of 200000 steps (1%)
[16:48:48] Completed 4000 out of 200000 steps (2%)
[16:51:45] Completed 6000 out of 200000 steps (3%)
[16:55:04] Completed 8000 out of 200000 steps (4%)
[16:58:27] Completed 10000 out of 200000 steps (5%)
[17:01:54] Completed 12000 out of 200000 steps (6%)
[17:05:28] Completed 14000 out of 200000 steps (7%)
[17:09:09] Completed 16000 out of 200000 steps (8%)
[17:13:01] Completed 18000 out of 200000 steps (9%)
[17:17:09] Completed 20000 out of 200000 steps (10%)
[17:20:47] Completed 22000 out of 200000 steps (11%)
[17:24:24] Completed 24000 out of 200000 steps (12%)
[17:28:16] Completed 26000 out of 200000 steps (13%)
[17:32:17] Completed 28000 out of 200000 steps (14%)
[17:36:00] Completed 30000 out of 200000 steps (15%)
[17:39:53] Completed 32000 out of 200000 steps (16%)
[17:44:01] Completed 34000 out of 200000 steps (17%)
[17:48:03] Completed 36000 out of 200000 steps (18%)
[17:51:59] Completed 38000 out of 200000 steps (19%)
[17:56:21] Completed 40000 out of 200000 steps (20%)
[17:57:07] CoreStatus = 8B (139)
[17:57:07] Client-core communications error: ERROR 0x8b
[17:57:07] Deleting current work unit & continuing...
[17:57:07] - Preparing to get new work unit...
[17:57:07] + Attempting to get work packet
[17:57:07] - Connecting to assignment server
[17:57:08] - Successful: assigned to (129.74.85.48).
[17:57:08] + News From Folding@Home: Welcome to Folding@Home
[17:57:08] Loaded queue successfully.
[17:57:08] + Closed connections
Error is:
[17:57:07] CoreStatus = 8B (139)
[17:57:07] Client-core communications error: ERROR 0x8b
I have previously completed several of WUs on the same machine (and in the same client).
Also, I seem to get this error on all of the 100001 units:
Code: Select all
[16:42:56] ERROR: Exception in thread 2: @ fah/net/Socket.cpp:139:bind 0: Could not bind $
but it doesn't seem to have any effect as many of the WUs with it complete successfully. Strange.
Re: Project: 10001 (Run 644, Clone 2, Gen 1)
Posted: Tue Dec 22, 2009 6:17 pm
by tonic
I just got the same Client-core communications error at 33% on:
Project: 10001 (Run 160, Clone 4, Gen 1)
Re: Project: 10001 (Run 644, Clone 2, Gen 1)
Posted: Tue Dec 22, 2009 7:00 pm
by toTOW
What CPU ? Which OS ? 32 or 64 bits ? Overclocking ? ...
Re: Project: 10001 (Run 644, Clone 2, Gen 1)
Posted: Tue Dec 22, 2009 7:10 pm
by tonic
Most of that info is in the log, it seems that FahCore_b4 outputs more of this data than the other cores. The OS is Ubuntu 9.04 (x86) and the CPU isn't overclocked.
16:42:56] ************************************ System **********************************$
[16:42:56] OS: Linux 2.6.28-15-generic i686
[16:42:56] CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
[16:42:56] CPU ID: GenuineIntel Family 6 Model 15 Stepping 11
[16:42:56] CPUs: 4 Logical, 1 Physical
[16:42:56] Memory: 1.92 GB
[16:42:56] ******************************************************************************$
Re: Project: 10001 (Run 644, Clone 2, Gen 1)
Posted: Tue Dec 22, 2009 7:12 pm
by toTOW
I should pay more attention
Re: Project: 10001 (Run 644, Clone 2, Gen 1)
Posted: Tue Dec 22, 2009 7:18 pm
by jrweiss
Q9450, no OC, XP Pro 32-bit. Got 10001 running on 3 of 4 cores right now. From the logs, only 1 anomaly so far:
(Run 93, Clone 5, Gen 7) finished
(Run 93, Clone 5, Gen 8) currently at 98%
(Run 474, Clone 2, Gen 0) finished
(Run 626, Clone 5, Gen 0) finished
(Run 626, Clone 5, Gen 1) "finished unit" at 39% (?!?)
(Run 627, Clone 4, Gen 1) currently at 34%
(Run 747, Clone 1, Gen 1) currently at 6%
Re: Project: 10001 (Run 644, Clone 2, Gen 1)
Posted: Tue Dec 22, 2009 7:46 pm
by MtM
The finishing before 100% is afaik no bug, it was mentioned this could happen and it's expected. The trajectory just fails at that point, there is no further computation possible but it's not an EUE caused by a bug so it's not outputting it as such ( in which it differs from the previous cores ).
Re: Project: 10001 (Run 644, Clone 2, Gen 1)
Posted: Wed Dec 23, 2009 2:38 am
by guest3412
I have a similar error:
Code: Select all
[02:20:32] ERROR: Exception in thread 1: @ fah\net\Socket.cpp:139:<unknown> 0: Could not bind socket to 127.0.0.1: No error
and this is the first time I've noticed it I'm running vista sp2 x64 Stock Clocks. My other clients running on this PC are not getting this error, as I have a quad core I run 4 single clients simultaneously, unless I need the processing power for something else I only shut one or two down. I have had another one of my clients running the "b4" a couple days and it has not shown an error. The other 2 clients are running the "78" core still. I tried to remove the directory and new client, and the "b4" client downloads again and again, still same error. It would be nice if I could simply note this error and not select a "b4" client, vs another client, don't ya think?
Code: Select all
[02:20:05] - Machine ID: 2
[02:20:05]
[02:20:05] Work directory not found. Creating...
[02:20:05] Could not open work queue, generating new queue...
[02:20:05] - Preparing to get new work unit...
[02:20:05] + Attempting to get work packet
[02:20:05] - Connecting to assignment server
[02:20:06] - Successful: assigned to (129.74.85.48).
[02:20:06] + News From Folding@Home: Welcome to Folding@Home
[02:20:06] Loaded queue successfully.
[02:20:07] + Closed connections
[02:20:07]
[02:20:07] + Processing work unit
[02:20:07] Core required: FahCore_b4.exe
[02:20:07] Core not found.
[02:20:07] - Core is not present or corrupted.
[02:20:07] - Attempting to download new core...
[02:20:07] + Downloading new core: FahCore_b4.exe
[02:20:16] Verifying core Core_b4.fah...
[02:20:16] Signature is VALID
[02:20:16]
[02:20:16] Trying to unzip core FahCore_b4.exe
[02:20:19] Decompressed FahCore_b4.exe (16222720 bytes) successfully
[02:20:24] + Core successfully engaged
[02:20:29]
[02:20:29] + Processing work unit
[02:20:29] Core required: FahCore_b4.exe
[02:20:29] Core found.
[02:20:29] Working on queue slot 01 [December 23 02:20:29 UTC]
[02:20:29] + Working ...
[02:20:31] *********************** Log Started 23/Dec/2009 02:20:31 ***********************
[02:20:31] ************************** ProtoMol Folding@Home Core **************************
[02:20:31] Version: 19
[02:20:31] Type: 180
[02:20:31] Core: ProtoMol
[02:20:31] Website: http://folding.stanford.edu/
[02:20:31] Copyright: (c) 2009 Stanford University
[02:20:31] Author: Joseph Coffland <joseph@cauldrondevelopment.com>
[02:20:31] Args: -dir work/ -suffix 01 -priority 96 -checkpoint 3 -lifeline 7132
[02:20:31] -version 623
[02:20:31] ************************************ Build *************************************
[02:20:31] Date: Dec 16 2009
[02:20:31] Time: 17:02:04
[02:20:31] Revision: 1746
[02:20:31] Compiler: Intel(R) C++ MSVC 1500 mode 1110
[02:20:31] Options: /TP /nologo /EHsc /wd4297 /wd4103 /wd1786 /arch:IA32 /Ox
[02:20:31] /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qrestrict /MT
[02:20:31] Platform: Windows XP
[02:20:31] Bits: 32
[02:20:31] ************************************ System ************************************
[02:20:31] OS: Microsoft Windows Vista Home Premium
[02:20:31] CPU: AMD Phenom(tm) II X4 940 Processor
[02:20:31] CPU ID: AuthenticAMD Family 16 Model 4 Stepping 2
[02:20:31] CPUs: 4 Logical, 4 Physical
[02:20:31] Memory: 4.00 GB
[02:20:31] ********************************************************************************
[02:20:31] Project: 10000 (Run 2070, Clone 0, Gen 1)
[02:20:31] Reading tar file par_all27_prot_lipid.inp
[02:20:31] Reading tar file scpismQuartic.inp
[02:20:31] Reading tar file ww_exteq_nowater1.pdb
[02:20:31] Reading tar file ww_exteq_nowater1.psf
[02:20:31] Reading tar file checkpt
[02:20:31] Reading tar file ww_exteq_nowater1.18.pos
[02:20:31] Reading tar file ww_exteq_nowater1.18.vel
[02:20:31] Reading tar file protomol.conf
[02:20:31] Reading tar file core.xml
[02:20:31] Digital signatures verified
[02:20:32] Completed 0 out of 1000000 steps (0%)
[02:20:32] ERROR: Exception in thread 1: @ fah\net\Socket.cpp:139:<unknown> 0: Could not bind socket to 127.0.0.1: No error
Re: Project: 10001 (Run 644, Clone 2, Gen 1)
Posted: Wed Dec 23, 2009 3:40 am
by uncle fuzzy
You'll see that error on the second client to start. Only the first can bind socket. It's cosmetic and not a problem. It's how it reacts to running on multicore cpus.
Rhttp://foldingforum.e: Project: 10001 (Run 644, Clone 2, Ge
Posted: Wed Dec 23, 2009 4:46 am
by bruce
The error 0x8b makes this an important report so I've added it to the title.
Code: Select all
[16:42:56] ERROR: Exception in thread 2: @ fah/net/Socket.cpp:139:bind 0: Could not bind $
In some cases, this message is getting truncated. It should read
. . . Could not bind socket to 127.0.0.1: No error (and you can see that in other reports in this topic.)
The words "
No error" should be interpreted as "this is a warning message with no impact on anything except the viewer, if you happen to use it" so since the viewer is rarely used, the message is nothing to worry about. It's strictly cosmetic in nature.
Re: Project: 10001 (Run 644, Clone 2, Gen 1) - ERROR 0x8b
Posted: Wed Dec 23, 2009 8:33 pm
by guest3412
umm why the "ERROR" in the beginning if there's no error? Confusing, also since I use the console version exclusively, I see all the "code" and it's nice to see it running threw the loops, I'll admit that the work unit ran threw with out a hitch since I just let it run after posting this message and noting that the work unit did complete successfully despite the error. Thanks ya'll, I'll keep the folding coming and hope that you have a wonderful holiday season!
Re: Project: 10001 (Run 644, Clone 2, Gen 1) - ERROR 0x8b
Posted: Wed Dec 23, 2009 9:24 pm
by bruce
The first client you start connects successfully to 127.0.0.1.
The second client that you start knows nothing of this and it attempts to connect to 127.0.0.1 but it cannot, so it gets an error.
FAH moves on to process the it's WU. The fact that this did not work isn't an error, as far a FAH is concerned, because the first connection worked successfully.
You need to ignore the message. There are lots of things that FAH does which mean things to the developers but they're not important to donors.