Project:9011 run:145 clone:2 gen:75

Moderators: Site Moderators, FAHC Science Team

Ricky
Posts: 483
Joined: Sat Aug 01, 2015 1:34 am
Hardware configuration: 1. 2 each E5-2630 V3 processors, 64 GB RAM, GTX980SC GPU, and GTX980 GPU running on windows 8.1 operating system.
2. I7-6950X V3 processor, 32 GB RAM, 1 GTX980tiFTW, and 2 each GTX1080FTW GPUs running on windows 8.1 operating system.
Location: New Mexico

Re: Project:9011 run:145 clone:2 gen:75

Post by Ricky »

I had noticed that I presently have the cleanup problem. From process explorer I see that only FAH has anything associated with the work\03 folder.

Code: Select all

FAHClient.exe	2584	File	C:\Users\win1\AppData\Roaming\FAHClient\work\03\wudata_01.tpr
FAHClient.exe	2584	File	C:\Users\win1\AppData\Roaming\FAHClient\work\03\wudata_01.tpr
FAHCoreWrapper.exe	12704	File	C:\Users\win1\AppData\Roaming\FAHClient\work\03\wudata_01.tpr
FAHCoreWrapper.exe	12704	File	C:\Users\win1\AppData\Roaming\FAHClient\work\03\wudata_01.tpr
FahCore_a4.exe	17792	File	C:\Users\win1\AppData\Roaming\FAHClient\work\03\wudata_01.tpr
FahCore_a4.exe	17792	File	C:\Users\win1\AppData\Roaming\FAHClient\work\03\wudata_01.tpr
This is the log filtered by errors. Task manager shows that I have 7.1 GB of my 64 GB used. I have 1267 threads and 27.7k handles running.

Code: Select all

******************************* Date: 2016-03-11 *******************************
22:31:40:ERROR:std::exception: bad allocation
22:32:10:ERROR:std::exception: bad allocation
23:30:58:ERROR:WU01:FS00:Exception: Failed to remove directory './work/01': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\01\wudata_01.tpr"
23:30:58:ERROR:WU01:FS00:Exception: Failed to remove directory './work/01': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\01\wudata_01.tpr"
23:31:11:ERROR:FS00:
23:31:11:ERROR:FS00:-------------------------------------------------------
23:31:11:ERROR:FS00:Program Folding@home, VERSION 4.5.4
23:31:11:ERROR:FS00:Source code file: gromacs-4.5.4\src\gmxlib\smalloc.c, line: 171
23:31:11:ERROR:FS00:
23:31:11:ERROR:FS00:Fatal error:
23:31:11:ERROR:FS00:Not enough memory. Failed to calloc ld elements of size ld for 
23:31:11:ERROR:FS00:(called from file (null), line 56)
23:31:11:ERROR:FS00:For more information and tips for troubleshooting, please check the GROMACS
23:31:11:ERROR:FS00:website at http://www.gromacs.org/Documentation/Errors
23:31:11:ERROR:FS00:-------------------------------------------------------
23:31:11:ERROR:FS00:
23:31:11:ERROR:FS00:Thanx for Using GROMACS - Have a Nice Day
23:31:12:ERROR:FS00:
23:31:12:ERROR:FS00:-------------------------------------------------------
23:31:12:ERROR:FS00:Program Folding@home, VERSION 4.5.4
23:31:12:ERROR:FS00:Source code file: gromacs-4.5.4\src\gmxlib\smalloc.c, line: 171
23:31:12:ERROR:FS00:
23:31:12:ERROR:FS00:Fatal error:
23:31:12:ERROR:FS00:Not enough memory. Failed to calloc ld elements of size ld for 
23:31:12:ERROR:FS00:(called from file (null), line 24)
23:31:12:ERROR:FS00:For more information and tips for troubleshooting, please check the GROMACS
23:31:12:ERROR:FS00:website at http://www.gromacs.org/Documentation/Errors
23:31:12:ERROR:FS00:-------------------------------------------------------
23:31:12:ERROR:FS00:
23:31:12:ERROR:FS00:Thanx for Using GROMACS - Have a Nice Day
23:31:58:ERROR:WU01:FS00:Exception: Failed to remove directory './work/01': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\01\wudata_01.tpr"
23:33:35:ERROR:WU01:FS00:Exception: Failed to remove directory './work/01': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\01\wudata_01.tpr"
23:36:13:ERROR:WU01:FS00:Exception: Failed to remove directory './work/01': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\01\wudata_01.tpr"
23:40:27:ERROR:WU01:FS00:Exception: Failed to remove directory './work/01': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\01\wudata_01.tpr"
23:47:18:ERROR:WU01:FS00:Exception: Failed to remove directory './work/01': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\01\wudata_01.tpr"
23:58:24:ERROR:WU01:FS00:Exception: Failed to remove directory './work/01': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\01\wudata_01.tpr"
00:16:21:ERROR:WU01:FS00:Exception: Failed to remove directory './work/01': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\01\wudata_01.tpr"
00:41:08:ERROR:WU03:FS00:Exception: Failed to remove directory './work/03': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\03\wudata_01.tpr"
00:41:08:ERROR:WU03:FS00:Exception: Failed to remove directory './work/03': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\03\wudata_01.tpr"
00:42:09:ERROR:WU03:FS00:Exception: Failed to remove directory './work/03': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\03\wudata_01.tpr"
00:43:46:ERROR:WU03:FS00:Exception: Failed to remove directory './work/03': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\03\wudata_01.tpr"
00:45:23:ERROR:WU01:FS00:Exception: Failed to remove directory './work/01': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\01\wudata_01.tpr"
00:46:23:ERROR:WU03:FS00:Exception: Failed to remove directory './work/03': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\03\wudata_01.tpr"
00:50:37:ERROR:WU03:FS00:Exception: Failed to remove directory './work/03': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\03\wudata_01.tpr"
00:57:28:ERROR:WU03:FS00:Exception: Failed to remove directory './work/03': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\03\wudata_01.tpr"
01:08:34:ERROR:WU03:FS00:Exception: Failed to remove directory './work/03': boost::filesystem::remove: The process cannot access the file because it is being used by another process: ".\work\03\wudata_01.tpr"
bruce
Posts: 20910
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Project:9011 run:145 clone:2 gen:75

Post by bruce »

Are you looking at that protein with FAHViewer?
Ricky
Posts: 483
Joined: Sat Aug 01, 2015 1:34 am
Hardware configuration: 1. 2 each E5-2630 V3 processors, 64 GB RAM, GTX980SC GPU, and GTX980 GPU running on windows 8.1 operating system.
2. I7-6950X V3 processor, 32 GB RAM, 1 GTX980tiFTW, and 2 each GTX1080FTW GPUs running on windows 8.1 operating system.
Location: New Mexico

Re: Project:9011 run:145 clone:2 gen:75

Post by Ricky »

Bruce,

No, I only used FAHViewer a few times when I first started last summer.

To help understand the problem I would like to try killing the client process in processes explorer rather than rebooting. Then I could restart the client to see if the problem would clear-up the same as a reboot. How would I restart the client? Do I just start in the program files (x86) folder, or should I do something else first? Would I need to kill the wrapper also? I believe I should pause folding first.

It is interesting to note that there were 2 copies of the client associated with the files while the cleanup problem existed. After reboot, I have the following shown for the folders in process explorer:

Code: Select all

FahCore_21.exe	4412	File	C:\Users\win1\AppData\Roaming\FAHClient\work\00\01\log.txt
FahCore_21.exe	4412	File	C:\Users\win1\AppData\Roaming\FAHClient\work\00\01\log.txt
FahCore_21.exe	4412	File	C:\Users\win1\AppData\Roaming\FAHClient\work\00\01\log.txt
FahCore_21.exe	4412	File	C:\Users\win1\AppData\Roaming\FAHClient\work\00\wudata_01.lock
FahCore_21.exe	4412	File	C:\Users\win1\AppData\Roaming\FAHClient\work\00\logfile_01.txt
FahCore_21.exe	4412	File	C:\Users\win1\AppData\Roaming\FAHClient\work\00\01
FAHClient.exe	6288	File	C:\Users\win1\AppData\Roaming\FAHClient\work\00\logfile_01.txt

Code: Select all

FahCore_a4.exe	224	File	C:\Users\win1\AppData\Roaming\FAHClient\work\02\logfile_01.txt
FahCore_a4.exe	224	File	C:\Users\win1\AppData\Roaming\FAHClient\work\02\wudata_01.log
FahCore_a4.exe	224	File	C:\Users\win1\AppData\Roaming\FAHClient\work\02\wudata_01.trr
FahCore_a4.exe	224	File	C:\Users\win1\AppData\Roaming\FAHClient\work\02\wudata_01.xtc
FahCore_a4.exe	224	File	C:\Users\win1\AppData\Roaming\FAHClient\work\02\wudata_01.edr
FAHClient.exe	6288	File	C:\Users\win1\AppData\Roaming\FAHClient\work\02\logfile_01.txt

Code: Select all

FAHClient.exe	6288	File	C:\Users\win1\AppData\Roaming\FAHClient\work\03\logfile_01.txt
FahCore_18.exe	6992	File	C:\Users\win1\AppData\Roaming\FAHClient\work\03\01\log.txt
FahCore_18.exe	6992	File	C:\Users\win1\AppData\Roaming\FAHClient\work\03\01\log.txt
FahCore_18.exe	6992	File	C:\Users\win1\AppData\Roaming\FAHClient\work\03\wudata_01.lock
FahCore_18.exe	6992	File	C:\Users\win1\AppData\Roaming\FAHClient\work\03\wudata_01.lock
FahCore_18.exe	6992	File	C:\Users\win1\AppData\Roaming\FAHClient\work\03\logfile_01.txt
FahCore_18.exe	6992	File	C:\Users\win1\AppData\Roaming\FAHClient\work\03\01
bruce
Posts: 20910
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Project:9011 run:145 clone:2 gen:75

Post by bruce »

Two copies of FAHClient should never be run at the same time. Do you know how that happened? That explains the problem better than my guess that it was a FAHViewer issue.

No, do not start the program in the program files (x86) folder. In "all programs" you should find a folder called 'fahclient" which contains a shortcut called "Folding@home" that starts the program you've killed. It sets the proper "start in" directory so the working files can be found (unlike starting it from Program Files.) That shortcut also hides the output of the client but it appears in your log and can be viewed from FAHControl.
Post Reply