Project 10005 ERROR: Exception in thread 1:

[SantaFe]

Okay, I first noticed this in my Linux F@H uniprocessor client (6.02), but am also getting the same error in my Win 7 clients as well which is the one I pasted. I got Project 10005 in both F@H clients. While I don't get this in Core 1, I got the following message when the core2 client starts a new run.

Code: Select all

[18:50:46] + Processing work unit
[18:50:46] Core required: FahCore_b4.exe
[18:50:46] Core found.
[18:50:46] Working on queue slot 05 [February 11 18:50:46 UTC]
[18:50:46] + Working ...
[18:50:46] - Calling '.\FahCore_b4.exe -dir work/ -suffix 05 -checkpoint 30 -service -forceasm -verbose -lifeline 1880 -version 623'

[18:50:49] *********************** Log Started 11/Feb/2010 18:50:49 ***********************
[18:50:49] ************************** ProtoMol Folding@Home Core **************************
[18:50:49]   Version: 22
[18:50:49]      Type: 180
[18:50:49]      Core: ProtoMol
[18:50:49]   Website: http://folding.stanford.edu/
[18:50:49] Copyright: (c) 2009 Stanford University
[18:50:49]    Author: Joseph Coffland <joseph@cauldrondevelopment.com>
[18:50:49]      Args: -dir work/ -suffix 05 -checkpoint 30 -service -forceasm -verbose
[18:50:49]            -lifeline 1880 -version 623
[18:50:49] ************************************ Build *************************************
[18:50:49]      Date: Jan 21 2010
[18:50:49]      Time: 19:16:23
[18:50:49]  Revision: 1756
[18:50:49]  Compiler: Intel(R) C++ MSVC 1500 mode 1110
[18:50:49]   Options: /TP /nologo /EHsc /wd4297 /wd4103 /wd1786 /arch:IA32 /Ox
[18:50:49]            /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qrestrict /MT
[18:50:49]  Platform: Windows XP
[18:50:49]      Bits: 32
[18:50:49]      Mode: Release
[18:50:49] ************************************ System ************************************
[18:50:49]        OS: Microsoft Windows 7 Home Premium
[18:50:49]       CPU: Intel(R) Core(TM)2 Duo CPU T6600 @ 2.20GHz
[18:50:49]    CPU ID: GenuineIntel Family 6 Model 23 Stepping 10
[18:50:49]      CPUs: 2 Logical, 1 Physical
[18:50:49]    Memory: 3.96 GB
[18:50:49]   Threads: Windows
[18:50:49] ********************************************************************************
[18:50:49] Project: 10005 (Run 2276, Clone 0, Gen 0)
[18:50:49] Reading tar file par_all27_prot_lipid.inp
[18:50:49] Reading tar file scpismQuartic.inp
[18:50:49] Reading tar file ww_structure_14_charm.pdb
[18:50:49] Reading tar file ww_structure_14_charm.psf
[18:50:49] Reading tar file ww_structure_14_charm.vel
[18:50:49] Reading tar file protomol.conf
[18:50:49] Reading tar file core.xml
[18:50:49] Digital signatures verified
[18:50:49] Completed 0 out of 500000 steps (0%)
[18:50:49] GUI Server started
[18:50:49] ERROR: Exception in thread 1: @ fah\net\Socket.cpp:139:<unknown> 0: Could not bind socket to 127.0.0.1: No error 
[18:58:15] Completed 5000 out of 500000 steps (1%)
[19:03:56] Completed 10000 out of 500000 steps (2%)
[19:11:38] Completed 15000 out of 500000 steps (3%)
[19:18:58] - Autosending finished units... [February 11 19:18:58 UTC]
[19:18:58] Trying to send all finished work units
[19:18:58] + No unsent completed units remaining.
[19:18:58] - Autosend completed

Funny thing is, it connects fine to the internet & sends one in when the Core2 client's finished. So why the Error message with the no error at the end?

Like I sad before, it happens in my Win 7 Desktop, Win 7 Studio 1745 laptop, and my Xubuntu 9.10 Linux Desktop, and all in my second client.

[toTOW]

[18:50:49] ERROR: Exception in thread 1: @ fah\net\Socket.cpp:139:<unknown> 0: Could not bind socket to 127.0.0.1: No error

This can be considered as a cosmetic issue, you don't have to worry about it.

Basically, it has to do with binding the viewer interface to network, and it is only displayed when multiple clients are running on the same machine. First started core won't display this message because it successfully binds to network, but it will appear on all cores started after, because the bind is already in place.

[SantaFe]

Okay Thanks!!! Wondered if it wasn't connecting suddenly & got confused when later on it did.

[brityank]

Thank you SantaFe and toTOW - I too noticed this and wondered.

Fold on!