• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Anyone else's F@H appear to not be working?

J

JeffCos

Golden Member
Mine's been saying Working 0/0 since last night. Then when I click on it to open the window it says Waiting for core large WU startup(#) right now the number is 5. Last night it was 2. The bottom of the screen says working. Someone wanna tell me what's wrong?
 
The new core should have downloaded automatically if it was needed. Both my clients are running fine here.

If I were in your situation, I would dump the current work unit (use the -delete x startup switch) and let it try on a new one.

Console Client Configuration Options
-config
Allows users to change their configuration information. This includes user & team names (reflected in the stats), whether or not to ask before a network connection is made to fetch/send work, set up proxy servers, preferred work unit type (Folding/Genome), process priority, CPU usage requested (5-100%), whether or not to use assembly loops, whether or not to use deadline information, and Machine ID changes.
-delete x
Delete item #x from work queue. This option should only be used if there is a serious error with the current unit that the client does not automatically recover from (e.g. crash-inducing). This should not normally happen, and if it does, we would be grateful if you could send us the FAHlog.txt file from the unit that causes the error.
-license
Displays the end-user license agreement
-queueinfo
Get information on queued work units. Includes for each unit the status (READY/FINISHED/EMPTY), unit type (Folding/Genome), originating server, and date when the unit was received (local time in GMT), as well as deadline if the server sent that information.
-send x
Send result #x back to server. Exits after trying to send unit (successfully or unsuccessfully). Use "-send all" to send all results outstanding. If unit x is not a completed work unit then the client exits without doing anything.
-verbosity x
Sets the output level, from 1 to 9 (max). The default is 3. This option should be used if the user wishes to see more detailed client output, particularly useful if there is a problem which needs to be reported to the F@H client development team.
-forceasm
Instruct the core to use SSE/3DNow assembly instructions if possible, even if it has previously made the determination that the machine may not be handling this well.
-advmethods
Request to be assigned any new Cores or work units.
-local
Use configuration files from local directory. This option has no meaning on Linux, but is vital on Windows and Macintosh for running multiple clients on a machine. It instructs the client to read its config information from the client.cfg file in the current directory rather than, on Windows, from the installation directory specified in the registry, or, on Macintosh, the Library/Folding@home directory. Information such as the user name, team name, proxy information, machine ID are maintained in the client.cfg file. The flag ensures that work does not conflict. Use "-local" only if you are planning on running more than one instance of Folding@Home on the same machine (this is only useful if you are running on a multi-processor machine). Create as many directories as there are processors on the machine, copy the exe files and client.cfg file into each of these directories, run "FAH3Console -local -config" on each and specify unique machine IDs for each directory (under the Advanced Settings option). From then onwards you may run each copy by switching to its directory and running with the -local flag.
-help
Print out the command line flags available and then exit.
Click to expand...
 
To use the -delete x flag, first use the -queueinfo flag to find out the number to put in the place of x.
 
Originally posted by: JeffCos
ok so which number do i put after the delete flag? 9 or 96?

Here's a screen shot http://pics.bbzzdd.com/users/JeffCos/whichnumber.JPG
Click to expand...
Does F@H sit at near 100% CPU usage when the system is idle? Somehow I think the new core is just presenting the progress info differently, and nothing needs to be deleted. If F@H is truly hung, then you would -delete 09 (the first number).

BTW, what is the speed of the system that this WU is running on?
 
Normally it runs at 100%, but today it's only running 77-80%. But when i hold the mouse over the icon in the systray it still says working 0/0. it's a p4 2.66.

I did what Sid and Gleem said and deleted 9, started it back up and got a 1141 Gromacs. So there must have been something wrong with that last WU or Core. But it's working now, thanks guys.
 
The WU that hung was one of the new QMDs from server .113

They found the solution to a problem and will have another fix to the core on Monday. (And so another 8MB download)
 
Hmmmm, are they starting to skimp on the beta testing?

No biggie, but it will mean more babysitting if they are releasing unstable WUs into the wild nowadays.

-Sid
 
Beta on Linux started Feb. 17

Beta on Windows started Feb. 23

Feb. 25 similar thing like happened to JeffCos reported, must have been one of first sent.

Feb. 25 - Feb. 28 - Problems galore.

March 1 released to advmethods 😕

Advmethods is advanced beta testing.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top