I started doing FAH last week and completed two smaller WUs just fine, then let my computer rest for some hours. I started a third, rather large WU Friday night, and the original ETA was roughly a little over five days. But since I'm going away next week, I clicked the "Finish" button so I wouldn't have to worry about another WU being downloaded and not finishing before next week.
Today, however, right before I left for work, I noticed that the client status was "Client: local Updating Inactive", the WU was no longer on the list, and most of the sections of the window were grayed out. I had been keeping tabs on the WU's progress, and wasn't expecting it to be finished for another day or so. I didn't know what to think, so I left my computer running and left the house, figuring it'd be back to normal by the time I got back. It's now about hours later, and nothing has changed.
What should I do? Leave it running, or Quit and restart the program? I checked my firewall, and both FAH program rules are still set to "allow". In the meantime, I'm going to leave it running.
Client: local Updating Inactive mid-session
Moderators: Site Moderators, FAHC Science Team
-
- Posts: 5
- Joined: Tue Jan 08, 2013 6:02 am
Re: Client: local Updating Inactive mid-session
Welcome to foldingforum.org, miranda822.
There's a good chance that FAH is still running and if you do nothing, it will probably finish at about the predicted time. It is currently unmonitored and although it's not essential, I know I'd feel more comfortable knowing what's going on. There is some illusive bug which causes FAHControl to lose contact with FAHClient and get stuck "updating." So far nobody has been able to isolate it. The simplest solution is to restart the computer and restart FAH. It should resume work at whatever stage the current WU is. You'll need to click Finish again.
There's a good chance that FAH is still running and if you do nothing, it will probably finish at about the predicted time. It is currently unmonitored and although it's not essential, I know I'd feel more comfortable knowing what's going on. There is some illusive bug which causes FAHControl to lose contact with FAHClient and get stuck "updating." So far nobody has been able to isolate it. The simplest solution is to restart the computer and restart FAH. It should resume work at whatever stage the current WU is. You'll need to click Finish again.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
-
- Posts: 472
- Joined: Sun May 30, 2010 2:28 pm
Re: Client: local Updating Inactive mid-session
Also, to verify that the FAHClient (SMP) is really doing work, you can run Task Manager to see that the CPU Usage is 100%.
Assuming a Windows system:
1) Right-click on an empty area of the taskbar, and left-click on 'Start Task Manager'.
2) Select the 'Performance' tab, the CPU Usage should be 100%.
Assuming a Windows system:
1) Right-click on an empty area of the taskbar, and left-click on 'Start Task Manager'.
2) Select the 'Performance' tab, the CPU Usage should be 100%.
art_l_j_PlanetAMD64
Over 1.04 Billion Total Points
Over 185,000 Work Units
Over 3,800,000 PPD
Overall rank (if points are combined) 20 of 1721690
In memory of my Mother May 12th 1923 - February 10th 2012
Over 1.04 Billion Total Points
Over 185,000 Work Units
Over 3,800,000 PPD
Overall rank (if points are combined) 20 of 1721690
In memory of my Mother May 12th 1923 - February 10th 2012
-
- Posts: 5
- Joined: Tue Jan 08, 2013 6:02 am
Re: Client: local Updating Inactive mid-session
Thanks for your help. I quit FAH, restarted my computer, and restarted FAH, though apparently it loaded before my Internet connection finished loading. Now it says "Connecting" instead of "Updating", and has for the past few minutes. I quit FAH again and restarted it (without restarting my computer), same result.
EDIT: Connection's back, and I've got approximately 1.51 days to go for this WU, which means it was running despite the update bug. Yay!
I'll keep that in mind, thanks. Right now the Usage is far below that since it's still "connecting".art_l_j_PlanetAMD64 wrote:Also, to verify that the FAHClient (SMP) is really doing work, you can run Task Manager to see that the CPU Usage is 100%.
Assuming a Windows system:
1) Right-click on an empty area of the taskbar, and left-click on 'Start Task Manager'.
2) Select the 'Performance' tab, the CPU Usage should be 100%.
EDIT: Connection's back, and I've got approximately 1.51 days to go for this WU, which means it was running despite the update bug. Yay!