• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

-verbosity 9 flag kills my client every time

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Audioaficionado

Sparkomatic Moderator
Joined
Apr 29, 2002
I tried adding the maximun verbosity flag just to see all the nitty-gritty details. Well every time I start the client with the flag at 9, it dies. I backed off to 5 and all seems well.

Anyone else have this problem before?

I'm running the latest 4 beta and 1.53 core.

BTW what's the default verbosity without the flag?
 
Audioaficionado said:
I tried adding the maximun verbosity flag just to see all the nitty-gritty details. Well every time I start the client with the flag at 9, it dies. I backed off to 5 and all seems well.

Anyone else have this problem before?

I'm running the latest 4 beta and 1.53 core.

BTW what's the default verbosity without the flag?

Sorry for the cap but what are these flags
 
It's supposed to tell you more information in your FAH.log so you can see what might be causing an error and better trouble shoot the process.

I just upped it to -verbosity 7 and the client is still running. I don't really see any more text output than before.
 
That is weird Audio... have you tried setting -verbosity 9 then deleting the core? I think default is 5 but not sure.
 
No, I just change my flags in the registry and stop and restart the F@H client service to activate them.

-verbosity 7 is working. I'll wait until the next WU as I don't want to screw up this almost completed one.
 
Update: I didn't need to delete the core. I just restarted the client with the -verbosity 9 just after a new WU was initiated. I still don't see anything more verbose except the flag arguments line.

[09:21:44] - Calling 'FahCore_78.exe -dir work/ -suffix 01 -checkpoint 15 -service -forceSSE -verbose -lifeline 2972 -version 400'

BTW how do you adjust the checkpoint times?

Code:
                       Folding@home Client Version 4.00-Prerelease

                          [url]http://folding.stanford.edu[/url]

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

Arguments: -service -advmethods -forceSSE -verbosity 9 

Warning:
 By using the -forceSSE flag, you are overriding program
 safeguards that monitor the stability of SSE
 instructions on your system. If you did not intend
 to do this, please restart the program without
 -forceSSE. If work units are not completing fully,
 then please discontinue use of the flag.

[09:21:42] - Ask before connecting: No
[09:21:42] - User name: audioaficionado (Team 32)
[09:21:42] - User ID = 78CCF22251040BAD
[09:21:42] - Machine ID: 1
[09:21:42] 
[09:21:42] Loaded queue successfully.
[09:21:42] + Benchmarking ...
[09:21:44] The benchmark result is 6724
[09:21:44] 
[09:21:44] - Autosending finished units...
[09:21:44] Trying to send all finished work units
[09:21:44] + Processing work unit
[09:21:44] Core required: FahCore_78.exe
[09:21:44] Core found.
[09:21:44] Working on Unit 01 [November 11 09:21:44]
[09:21:44] + No unsent completed units remaining.
[09:21:44] - Autosend completed
[09:21:44] + Working ...
[09:21:44] - Calling 'FahCore_78.exe -dir work/ -suffix 01 -checkpoint 15 -service -forceSSE -verbose -lifeline 2972 -version 400'

[09:21:44] 
[09:21:44] *------------------------------*
[09:21:44] Folding@home Gromacs Core
[09:21:44] Version 1.53 (October 2, 2003)
[09:21:44] 
[09:21:44] Preparing to commence simulation
[09:21:44] - Assembly optimizations manually forced on.
[09:21:44] - Not checking prior termination.
[09:21:45] - Expanded 196017 -> 950393 (decompressed 484.8 percent)
[09:21:45] 
[09:21:45] Project: 354 (Run 2, Clone 95, Gen 4)
[09:21:45] 
[09:21:45] Assembly optimizations on if available.
[09:21:45] Entering M.D.
[09:22:05] (Starting from checkpoint)
[09:22:05] Protein: p354_A21nat_273_GS
[09:22:05] 
[09:22:05] Writing local files
[09:22:05] Completed 25000 out of 2500000 steps  (1)
[09:22:05] Extra SSE boost OK.
[09:30:57] Writing local files
[09:30:59] Completed 50000 out of 2500000 steps  (2)
 
that's really weird. why would the level of detail on the output matter to the client? esp. when related to the work unit? glad you got it to work @ 9, for whatever the flag arguments line is worth to you.

haven't found info on the checkpoint times. I would be interested in knowing this as well.
 
Now that the forum is back up :rolleyes:

The checkpoint 15 is the default for 15 minutes.

Since my machine crunches frames in five minutes and five minutes is the minumum checkpoint time, it's a moot feature for me as I think every frame gets saved when completed.

It would be handy for my slow machines. I think you just set the '-checkpoint 5' flag to get 5 minute checkpoint saves.

Just put in your startup shortcut or in the FAH service parameter registry entry.
 
Why are you using flags to set the checkpoint time? There is an option right in the config file that lets you set it all the way down to 3~ mins.

[23:50:05] Completed 30000 out of 500000 steps (6)
[23:52:31] Timered checkpoint triggered.
[23:54:57] Timered checkpoint triggered.

I also noticed that the verbosity 9 flag shows this,

[09:21:44] - Calling 'FahCore_78.exe -dir work/ -suffix 01 -checkpoint 15 -service -forceSSE -verbose -lifeline 2972 -version 400'

The verbosity 9 flag is more for errors and not for normal running, I use it on stanfords beta team so that if the workunit that I am running errors I can show them what happend.
 
I got rid of the verbosity flag as it seemed to be causing unstability on my F@H instance. I haven't had anymore issues since I removed the flag.

Also the client is overwriting the config file daily. I don't see any space for checkpoint in the file anyway.
 
Back