Killed installation linking a F@H monitoring program

If you're new to FAH and need help getting started or you have very basic questions, start here.

Moderators: Site Moderators, FAHC Science Team

Post Reply
StitchExperimen
Posts: 37
Joined: Thu Jul 04, 2013 9:29 pm

Killed installation linking a F@H monitoring program

Post by StitchExperimen »

Generally as title says.

I uninstalled the program and re-installed and no luck, used registry cleaner, no luck, latest config file I changed the password, no luck.

Won't log into account.

Latest log of 5:

Don't know how to put this in a box for sure, so sorry.

Code: Select all

*********************** Log Started 2013-07-05T22:31:09Z ***********************
22:31:09:************************* Folding@home Client *************************
22:31:09:      Website: http://folding.stanford.edu/
22:31:09:    Copyright: (c) 2009-2013 Stanford University
22:31:09:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
22:31:09:         Args: --open-web-control
22:31:09:       Config: C:/ProgramData/FAHClient/config.xml
22:31:09:******************************** Build ********************************
22:31:09:      Version: 7.3.6
22:31:09:         Date: Feb 18 2013
22:31:09:         Time: 15:25:17
22:31:09:      SVN Rev: 3923
22:31:09:       Branch: fah/trunk/client
22:31:09:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
22:31:09:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
22:31:09:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
22:31:09:     Platform: win32 XP
22:31:09:         Bits: 32
22:31:09:         Mode: Release
22:31:09:******************************* System ********************************
22:31:09:          CPU: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
22:31:09:       CPU ID: GenuineIntel Family 6 Model 58 Stepping 9
22:31:09:         CPUs: 8
22:31:09:       Memory: 7.88GiB
22:31:09:  Free Memory: 6.04GiB
22:31:09:      Threads: WINDOWS_THREADS
22:31:09:  Has Battery: false
22:31:09:   On Battery: false
22:31:09:   UTC offset: -6
22:31:09:          PID: 1700
22:31:09:          CWD: C:/ProgramData/FAHClient
22:31:09:           OS: Windows 7 Professional
22:31:09:      OS Arch: AMD64
22:31:09:         GPUs: 2
22:31:09:        GPU 0: NVIDIA:3 GK104 [GeForce GTX 660 Ti]
22:31:09:        GPU 1: NVIDIA:3 GK104 [GeForce GTX 660 Ti]
22:31:09:         CUDA: 3.0
22:31:09:  CUDA Driver: 5050
22:31:09:Win32 Service: false
22:31:09:***********************************************************************
22:31:09:<config>
22:31:09:  <!-- Folding Slot Configuration -->
22:31:09:  <power v='full'/>
22:31:09:
22:31:09:  <!-- HTTP Server -->
22:31:09:  <allow v='192.168.3.158'/>
22:31:09:
22:31:09:  <!-- Network -->
22:31:09:  <proxy v=':8080'/>
22:31:09:
22:31:09:  <!-- Remote Command Server -->
22:31:09:  <command-allow-no-pass v='192.168.3.158'/>
22:31:09:  <password v='*********'/>
22:31:09:
22:31:09:  <!-- Slot Control -->
22:31:09:  <pause-on-battery v='false'/>
22:31:09:
22:31:09:  <!-- User Information -->
22:31:09:  <passkey v='********************************'/>
22:31:09:  <team v='198'/>
22:31:09:  <user v='StitchExperimen'/>
22:31:09:
22:31:09:  <!-- Folding Slots -->
22:31:09:  <slot id='0' type='GPU'/>
22:31:09:  <slot id='1' type='GPU'/>
22:31:09:</config>
22:31:09:Trying to access database...
22:31:09:Successfully acquired database lock
22:31:09:Enabled folding slot 00: READY gpu:0:GK104 [GeForce GTX 660 Ti]
22:31:09:Enabled folding slot 01: READY gpu:1:GK104 [GeForce GTX 660 Ti]
22:31:09:WU00:FS00:Starting
22:31:09:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/ProgramData/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/NVIDIA/Fermi/Core_15.fah/FahCore_15.exe -dir 00 -suffix 01 -version 703 -lifeline 1700 -checkpoint 15 -gpu 0 -gpu-vendor nvidia
22:31:09:WU00:FS00:Started FahCore on PID 5940
22:31:09:WU00:FS00:Core PID:1780
22:31:09:WU00:FS00:FahCore 0x15 started
22:31:09:WU01:FS01:Starting
22:31:09:WU01:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/ProgramData/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/NVIDIA/Fermi/Core_15.fah/FahCore_15.exe -dir 01 -suffix 01 -version 703 -lifeline 1700 -checkpoint 15 -gpu 1 -gpu-vendor nvidia
22:31:09:WU01:FS01:Started FahCore on PID 1712
22:31:09:WU01:FS01:Core PID:5864
22:31:09:WU01:FS01:FahCore 0x15 started
22:31:09:WU00:FS00:0x15:
22:31:09:WU00:FS00:0x15:*------------------------------*
22:31:09:WU00:FS00:0x15:Folding@Home GPU Core
22:31:09:WU00:FS00:0x15:Version                2.25 (Wed May 9 17:03:01 EDT 2012)
22:31:09:WU00:FS00:0x15:Build host             AmoebaRemote
22:31:09:WU00:FS00:0x15:Board Type             NVIDIA/CUDA
22:31:09:WU00:FS00:0x15:Core                   15
22:31:09:WU00:FS00:0x15:
22:31:09:WU00:FS00:0x15:Window's signal control handler registered.
22:31:09:WU00:FS00:0x15:Preparing to commence simulation
22:31:09:WU00:FS00:0x15:- Looking at optimizations...
22:31:09:WU00:FS00:0x15:- Files status OK
22:31:09:WU00:FS00:0x15:sizeof(CORE_PACKET_HDR) = 512 file=<>
22:31:09:WU00:FS00:0x15:- Expanded 124914 -> 502918 (decompressed 402.6 percent)
22:31:09:WU00:FS00:0x15:Called DecompressByteArray: compressed_data_size=124914 data_size=502918, decompressed_data_size=502918 diff=0
22:31:09:WU00:FS00:0x15:- Digital signature verified
22:31:09:WU00:FS00:0x15:
22:31:09:WU00:FS00:0x15:Project: 7625 (Run 286, Clone 0, Gen 108)
22:31:09:WU00:FS00:0x15:
22:31:09:WU00:FS00:0x15:Assembly optimizations on if available.
22:31:09:WU00:FS00:0x15:Entering M.D.
22:31:09:WARNING:Denied 1:127.0.0.1 access to URI: /ping?_=1373063469330&callback=jQuery1900995554378721863_1373063469329
22:31:10:WU01:FS01:0x15:
22:31:10:WU01:FS01:0x15:*------------------------------*
22:31:10:WU01:FS01:0x15:Folding@Home GPU Core
22:31:10:WU01:FS01:0x15:Version                2.25 (Wed May 9 17:03:01 EDT 2012)
22:31:10:WU01:FS01:0x15:Build host             AmoebaRemote
22:31:10:WU01:FS01:0x15:Board Type             NVIDIA/CUDA
22:31:10:WU01:FS01:0x15:Core                   15
22:31:10:WU01:FS01:0x15:GPU device info vendor=0 device=0 name=NA match=0 deviceId=1
22:31:10:WU01:FS01:0x15:
22:31:10:WU01:FS01:0x15:Window's signal control handler registered.
22:31:10:WU01:FS01:0x15:Preparing to commence simulation
22:31:10:WU01:FS01:0x15:- Looking at optimizations...
22:31:10:WU01:FS01:0x15:- Files status OK
22:31:10:WU01:FS01:0x15:sizeof(CORE_PACKET_HDR) = 512 file=<>
22:31:10:WU01:FS01:0x15:- Expanded 126952 -> 507182 (decompressed 399.5 percent)
22:31:10:WU01:FS01:0x15:Called DecompressByteArray: compressed_data_size=126952 data_size=507182, decompressed_data_size=507182 diff=0
22:31:10:WU01:FS01:0x15:- Digital signature verified
22:31:10:WU01:FS01:0x15:
22:31:10:WU01:FS01:0x15:Project: 7626 (Run 637, Clone 1, Gen 91)
22:31:10:WU01:FS01:0x15:
22:31:10:WU01:FS01:0x15:Assembly optimizations on if available.
22:31:10:WU01:FS01:0x15:Entering M.D.
22:31:11:WU00:FS00:0x15:Will resume from checkpoint file 00/wudata_01.ckp
22:31:11:WU00:FS00:0x15:Tpr hash 00/wudata_01.tpr:  436544440 2486264209 1500011268 3733429431 4132157845
22:31:11:WU00:FS00:0x15:GPU device id=0
22:31:11:WU00:FS00:0x15:Working on Protein
22:31:11:WU00:FS00:0x15:Client config unavailable.
22:31:11:WU00:FS00:0x15:Starting GUI Server
22:31:11:WU01:FS01:0x15:Will resume from checkpoint file 01/wudata_01.ckp
22:31:11:WU01:FS01:0x15:Tpr hash 01/wudata_01.tpr:  2606697426 2374371542 1360483007 4041259457 962935358
22:31:11:WU01:FS01:0x15:GPU device id=1
22:31:11:WU01:FS01:0x15:Working on Protein
22:31:11:WU01:FS01:0x15:Client config unavailable.
22:31:12:WU01:FS01:0x15:Starting GUI Server
22:32:12:WU00:FS00:0x15:Resuming from checkpoint
22:32:12:WU00:FS00:0x15:fcCheckPointResume: retreived and current tpr file hash:
22:32:12:WU00:FS00:0x15:   0    436544440    436544440
22:32:12:WU00:FS00:0x15:   1   2486264209   2486264209
22:32:12:WU00:FS00:0x15:   2   1500011268   1500011268
22:32:12:WU00:FS00:0x15:   3   3733429431   3733429431
22:32:12:WU00:FS00:0x15:   4   4132157845   4132157845
22:32:12:WU00:FS00:0x15:fcCheckPointResume: file hashes same.
22:32:12:WU00:FS00:0x15:fcCheckPointResume: state restored.
22:32:12:WU00:FS00:0x15:fcCheckPointResume: name 00/wudata_01.log Verified 00/wudata_01.log
22:32:12:WU00:FS00:0x15:fcCheckPointResume: name 00/wudata_01.trr Verified 00/wudata_01.trr
22:32:12:WU00:FS00:0x15:fcCheckPointResume: name 00/wudata_01.xtc Verified 00/wudata_01.xtc
22:32:12:WU00:FS00:0x15:fcCheckPointResume: name 00/wudata_01.edr Verified 00/wudata_01.edr
22:32:12:WU00:FS00:0x15:fcCheckPointResume: state restored 2
22:32:12:WU00:FS00:0x15:Resumed from checkpoint
22:32:12:WU00:FS00:0x15:Setting checkpoint frequency: 400000
22:32:12:WU00:FS00:0x15:Completed   7200001 out of 40000000 steps (18%).
22:32:12:WU01:FS01:0x15:Resuming from checkpoint
22:32:12:WU01:FS01:0x15:fcCheckPointResume: retreived and current tpr file hash:
22:32:12:WU01:FS01:0x15:   0   2606697426   2606697426
22:32:12:WU01:FS01:0x15:   1   2374371542   2374371542
22:32:12:WU01:FS01:0x15:   2   1360483007   1360483007
22:32:12:WU01:FS01:0x15:   3   4041259457   4041259457
22:32:12:WU01:FS01:0x15:   4    962935358    962935358
22:32:12:WU01:FS01:0x15:fcCheckPointResume: file hashes same.
22:32:12:WU01:FS01:0x15:fcCheckPointResume: state restored.
22:32:12:WU01:FS01:0x15:fcCheckPointResume: name 01/wudata_01.log Verified 01/wudata_01.log
22:32:12:WU01:FS01:0x15:fcCheckPointResume: name 01/wudata_01.trr Verified 01/wudata_01.trr
22:32:12:WU01:FS01:0x15:fcCheckPointResume: name 01/wudata_01.xtc Verified 01/wudata_01.xtc
22:32:12:WU01:FS01:0x15:fcCheckPointResume: name 01/wudata_01.edr Verified 01/wudata_01.edr
22:32:12:WU01:FS01:0x15:fcCheckPointResume: state restored 2
22:32:12:WU01:FS01:0x15:Resumed from checkpoint
22:32:12:WU01:FS01:0x15:Setting checkpoint frequency: 400000
22:32:12:WU01:FS01:0x15:Completed   7200001 out of 40000000 steps (18%).
22:34:04:FS00:Shutting core down
22:34:04:FS01:Shutting core down
22:34:09:WU00:FS00:0x15:Client no longer detected. Shutting down core 
22:34:09:WU00:FS00:0x15:
22:34:09:WU00:FS00:0x15:Folding@home Core Shutdown: CLIENT_DIED
22:34:09:Clean exit
7im
Posts: 10179
Joined: Thu Nov 29, 2007 4:30 pm
Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
Location: Arizona
Contact:

Re: Killed installation linking a F@H monitoring program

Post by 7im »

What monitor program?

Use tags.
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
bollix47
Posts: 2974
Joined: Sun Dec 02, 2007 5:04 am
Location: Canada

Re: Killed installation linking a F@H monitoring program

Post by bollix47 »

Code: Select all

22:31:09:  <!-- HTTP Server -->
22:31:09:  <allow v='192.168.3.158'/>
22:31:09:
22:31:09:  <!-- Network -->
22:31:09:  <proxy v=':8080'/>
22:31:09:
22:31:09:  <!-- Remote Command Server -->
22:31:09:  <command-allow-no-pass v='192.168.3.158'/>
22:31:09:  <password v='*********'/>
22:31:09:
Looks like you removed the local machine from your configuration - 127.0.0.1

e.g. mine looks like this: 127.0.0.1,192.168.2.100-192.168.2.149 on both the local computer and the remote computers.

You would, of course, use a different I.P. range for your remotes, if any. If no remotes are involved then just 127.0.0.1 is required.
StitchExperimen
Posts: 37
Joined: Thu Jul 04, 2013 9:29 pm

Re: Killed installation linking a F@H monitoring program

Post by StitchExperimen »

Problem solved data lost I think.


The program was
HFM.net: code.google.com/p/hfm-net/

When I was in F@H and tried to change it to 198.186.3.159 I typed in 158 and restarted the program and now it won't connect. At one point it said the password was incorrect.

I tried removing the program and keeping the data and then re-installing to get it back to defaults and it won't connect to Stanford servers.

How do I get this back to default?
Last edited by StitchExperimen on Fri Jul 05, 2013 11:58 pm, edited 1 time in total.
bollix47
Posts: 2974
Joined: Sun Dec 02, 2007 5:04 am
Location: Canada

Re: Killed installation linking a F@H monitoring program

Post by bollix47 »

You would have to uninstall the program including data. You could also edit config.xml (not recommended) but that can be a bit dangerous and requires a lot of care to ensure the configuration doesn't get corrupted.

As long as the client is configured correctly and is running, HFM should have no problem connecting to it. When configuring HFM I always use the Computer name rather than it's I.P. address.
StitchExperimen
Posts: 37
Joined: Thu Jul 04, 2013 9:29 pm

Re: Killed installation linking a F@H monitoring program

Post by StitchExperimen »

Okay problem solved. Haven't figured if I lost the project data yet still configuring.....
bollix47
Posts: 2974
Joined: Sun Dec 02, 2007 5:04 am
Location: Canada

Re: Killed installation linking a F@H monitoring program

Post by bollix47 »

Yes, when you uninstall including data then the project you were working on would get deleted as well. Looking at your log the progress wasn't too far along and the server may re-assign the same work unit so hopefully there won't be a significant slowdown to the project. Normally, we would have set the slot to Finish before uninstalling but since communication wasn't possible the option could not be set through FAHControl.
Post Reply