Project: 0 (Run 0, Clone 0, Gen 0)

[DreadedOne509]

Remember this issue, and fix from long ago, just not the actual fix or reason for it.
Attempted a search, but no joy, you can't search for Project anything since 'project'
is too common, and searching for combinations of Run, Clone, Gen with and without the
zeros and with and without quotes are too common as well.

Linux Ubuntu 8.04 SMP client
C2Q 6600 (one client)
2 GB RAM
Dedicated folding machine is stuck on stupid
with Project 0 (R0, C0, G0).

Tried deleting the Work folder, core, queue.dat
and unitinfo.dat files, still no joy.

Double and triple checked networking, rebooted the computer
and networking restart to no avail.

Any help?

Edit: I should note, I can ping the servers, internal devices and external devices no problem.

[Ivoshiee]

Delete the WU again and restart the client.

[codysluder]

Are you talking about being redirected to an invalid server at address 0.0.0.0 or are you talking about the client telling you that it can't run Project: 0 (Run 0, Clone 0, Gen 0)? As far as I know, deleting queue.dat and restarting the client has always gotten rid of the WU Project: 0 (Run 0, Clone 0, Gen 0) but there's nothing you can do if the client is telling you that 0.0.0.0 is an invalid IP address. The latter means the server is out of work for clients configured like yours is.

[siadi]

looks like a client.cfg misconfigured to me. have u tried reconfiguring? or perhaps u didn't set a specific settings? if so, then try making a setting for ur client.

[bruce]

Please post FAHlog.txt

[DreadedOne509]

It kept getting issued Project 0 (r0, c0, g0) and would of course stall there.

I ended up having to remove the client and associated files and installing from scratch
to get it working again.

The config was fine, I use the same for all of my dedictaed machines changing only
machine specific information (if any).

[bruce]

Please post FAHlog.txt

[DreadedOne509]

Please post FAHlog.txt

I no longer have the fahlog.txt as mentioned above; the only way I could
get it working again was by doing a complete removal and fresh install.
I did this before anyone asked for the log.

[MstrBlstr]

Here is an example.

Code: Select all

--- Opening Log file [January 20 02:12:43] 


# SMP Client ##################################################################
###############################################################################

                       Folding@Home Client Version 6.02

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: /home/adminbb/Library/FAH
Executable: ./fah6
Arguments: -smp 4 -local -verbosity 9 

[02:12:43] - Ask before connecting: No
[02:12:43] - User name: TH_Foldinator (Team 4)
[02:12:43] - User ID: 3F60B1711EC5151A
[02:12:43] - Machine ID: 1
[02:12:43] 
[02:12:43] Loaded queue successfully.
[02:12:43] - Autosending finished units...
[02:12:43] Trying to send all finished work units
[02:12:43] + No unsent completed units remaining.
[02:12:43] - Autosend completed
[02:12:43] 
[02:12:43] + Processing work unit
[02:12:43] At least 4 processors must be requested.Core required: FahCore_a2.exe
[02:12:43] Core found.
[02:12:43] Working on Unit 03 [January 20 02:12:43]
[02:12:43] + Working ...
[02:12:43] - Calling './mpiexec -np 4 -host 127.0.0.1 ./FahCore_a2.exe -dir work/ -suffix 03 -np 4 -checkpoint 15 -verbose -lifeline 6987 -version 602'

[02:12:43] 
[02:12:43] *------------------------------*
[02:12:43] Folding@Home Gromacs SMP Core
[02:12:43] Version 2.01 (Wed Aug 13 13:11:25 PDT 2008)
[02:12:43] 
[02:12:43] Preparing to commence simulation
[02:12:43] - Ensuring status. Please wait.
[02:12:53] - Looking at optimizations...
[02:12:53] - Working with standard loops on this execution.
[02:12:53] - Files status OK
[02:12:53] 
[02:12:53] Project: 0 (Run 0, Clone 0, Gen 0)
[02:12:53] 
[02:12:53] Error: Could not write local file.  Exiting.
[02:12:53] - Shutting down core
[04:04:49] ***** Got an Activate signal (2)
[04:04:49] Killing all core threads

Folding@Home Client Shutdown.


--- Opening Log file [January 20 04:04:52] 


# SMP Client ##################################################################
###############################################################################

                       Folding@Home Client Version 6.02

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: /home/adminbb/Library/FAH
Executable: ./fah6
Arguments: -smp 4 -local -verbosity 9 

[04:04:52] - Ask before connecting: No
[04:04:52] - User name: TH_Foldinator (Team 4)
[04:04:52] - User ID: 3F60B1711EC5151A
[04:04:52] - Machine ID: 1
[04:04:52] 
[04:04:52] Loaded queue successfully.
[04:04:52] - Autosending finished units...
[04:04:52] Trying to send all finished work units
[04:04:52] + No unsent completed units remaining.
[04:04:52] - Autosend completed
[04:04:52] 
[04:04:52] + Processing work unit
[04:04:52] At least 4 processors must be requested.Core required: FahCore_a2.exe
[04:04:52] Core found.
[04:04:52] Working on Unit 03 [January 20 04:04:52]
[04:04:52] + Working ...
[04:04:52] - Calling './mpiexec -np 4 -host 127.0.0.1 ./FahCore_a2.exe -dir work/ -suffix 03 -np 4 -checkpoint 15 -verbose -lifeline 7573 -version 602'

[04:04:53] 
[04:04:53] *------------------------------*
[04:04:53] Folding@Home Gromacs SMP Core
[04:04:53] Version 2.01 (Wed Aug 13 13:11:25 PDT 2008)
[04:04:53] 
[04:04:53] Preparing to commence simulation
[04:04:53] - Ensuring status. Please wait.
[04:05:02] - Looking at optimizations...
[04:05:02] - Working with standard loops on this execution.
[04:05:02] - Files status OK
[04:05:02] 
[04:05:02] Project: 0 (Run 0, Clone 0, Gen 0)
[04:05:02] 
[04:05:02] Error: Could not write local file.  Exiting.
[04:05:02] - Shutting down core
[04:05:31] ***** Got an Activate signal (2)
[04:05:31] Killing all core threads

Folding@Home Client Shutdown.


--- Opening Log file [January 20 04:05:54] 


# SMP Client ##################################################################
###############################################################################

                       Folding@Home Client Version 6.02

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: /home/adminbb/Library/FAH
Executable: ./fah6
Arguments: -smp 4 -local -verbosity 9 

[04:05:54] - Ask before connecting: No
[04:05:54] - User name: TH_Foldinator (Team 4)
[04:05:54] - User ID: 3F60B1711EC5151A
[04:05:54] - Machine ID: 1
[04:05:54] 
[04:05:54] Work directory not found. Creating...
[04:05:54] Loaded queue successfully.
[04:05:54] - Autosending finished units...
[04:05:54] Trying to send all finished work units
[04:05:54] + No unsent completed units remaining.
[04:05:54] - Autosend completed
[04:05:54] 
[04:05:54] + Processing work unit
[04:05:54] At least 4 processors must be requested.Core required: FahCore_a2.exe
[04:05:54] Core found.
[04:05:54] Working on Unit 03 [January 20 04:05:54]
[04:05:54] + Working ...
[04:05:54] - Calling './mpiexec -np 4 -host 127.0.0.1 ./FahCore_a2.exe -dir work/ -suffix 03 -np 4 -checkpoint 15 -verbose -lifeline 7616 -version 602'

[04:05:54] 
[04:05:54] *------------------------------*
[04:05:54] Folding@Home Gromacs SMP Core
[04:05:54] Version 2.01 (Wed Aug 13 13:11:25 PDT 2008)
[04:05:54] 
[04:05:54] Preparing to commence simulation
[04:05:54] - Ensuring status. Please wait.
[04:06:04] - Looking at optimizations...
[04:06:04] - Working with standard loops on this execution.
[04:06:04] - Files status OK
[04:06:04] 
[04:06:04] Project: 0 (Run 0, Clone 0, Gen 0)
[04:06:04] 
[04:06:04] Error: Could not write local file.  Exiting.
[04:06:04] - Shutting down core
[10:05:54] - Autosending finished units...
[10:05:54] Trying to send all finished work units
[10:05:54] + No unsent completed units remaining.
[10:05:54] - Autosend completed
[16:05:54] - Autosending finished units...
[16:05:54] Trying to send all finished work units
[16:05:54] + No unsent completed units remaining.
[16:05:54] - Autosend completed
[22:05:54] - Autosending finished units...
[22:05:54] Trying to send all finished work units
[22:05:54] + No unsent completed units remaining.
[22:05:54] - Autosend completed

[P5-133XL]

The config was fine, I use the same for all of my dedictaed machines changing only
machine specific information (if any).

It all depends on how you are changing the config file. that file, contrary to its looks, is actually a binary file (i.e. non text) and if you are editing it with a text editor it will inevitably become corrupted. To change the file, you really should be using the client and absolutely no editing allowed unless you are using a hex editor or some other utility that is specificly designed for editing binary files.