Search found 8 matches
- Wed Aug 18, 2010 2:33 pm
- Forum: Issues with a specific server
- Topic: 171.64.65.56 ???
- Replies: 141
- Views: 39574
171.64.65.56/171.67.108.25
Are still not reliably accepting finished work units... [12:30:14] Completed 2000000 out of 2000000 steps (100%) [12:30:14] DynamicWrapper: Finished Work Unit: sleep=10000 [12:30:24] [12:30:24] Finished Work Unit: [12:30:24] - Reading up to 687408 from "work/wudata_01.trr": Read 687408 [12...
- Sun Aug 15, 2010 2:37 pm
- Forum: Issues with a specific server
- Topic: 171.64.65.56
- Replies: 44
- Views: 14020
171.64.65.56/171.67.108.25
I can't seem to get this work unit (slot 7) sent... [01:52:59] Completed 2000000 out of 2000000 steps (100%) [01:53:00] DynamicWrapper: Finished Work Unit: sleep=10000 [01:53:10] [01:53:10] Finished Work Unit: [01:53:10] - Reading up to 687408 from "work/wudata_07.trr": Read 687408 [01:53:...
- Thu Jun 24, 2010 4:38 pm
- Forum: Issues with a specific WU
- Topic: Project: 6013 (Run 0, Clone 188, Gen 121)
- Replies: 3
- Views: 621
Re: Project: 6013 (Run 0, Clone 188, Gen 121)
Update: I never did get an answer on how to delete the work unit and move on to another one. I deleted the queue.dat file and work directory about 5 times and got the same WU every time. What I did was to put a rule into my DSL router to block access to the work server I was getting assigned to and ...
- Wed Jun 23, 2010 2:54 pm
- Forum: Issues with a specific WU
- Topic: Project: 6013 (Run 0, Clone 188, Gen 121)
- Replies: 3
- Views: 621
Project: 6013 (Run 0, Clone 188, Gen 121)
I am having the same problem with a 6013. Here is a snippet of the log. [10:37:45] Folding@Home Gromacs SMP Core [10:37:45] Version 2.19 (Mar 12, 2010) [10:37:45] [10:37:45] Preparing to commence simulation [10:37:45] - Looking at optimizations... [10:37:45] - Created dyn [10:37:45] - Files status O...
- Sat Apr 24, 2010 6:32 pm
- Forum: Issues with a specific server
- Topic: Problems uploading to http://171.64.65.54:8080/
- Replies: 7
- Views: 1441
Re: Problems uploading to http://171.64.65.54:8080/
The problem is resolved. The latest 6041 failed to send, just as the previous 2. When I was looking at the machine, I noticed a 20% processor utilization that shouldn't have been there. Upon further investigation, I found that an AVG network scanner process was consuming that 20% and also increasing...
- Fri Apr 23, 2010 6:17 pm
- Forum: Issues with a specific server
- Topic: Problems uploading to http://171.64.65.54:8080/
- Replies: 7
- Views: 1441
Re: Problems uploading to http://171.64.65.54:8080/
My upload speed is 320 Kpbs. I just uploaded a 6025 (20361897 of data, according to the log) in about 10 minutes. When it tries to upload the 6041's, it never actually sends any data. I can see the line on my DSL router that goes to my computer room. When I upload from the other machine, I can see d...
- Fri Apr 23, 2010 3:24 pm
- Forum: Issues with a specific server
- Topic: Problems uploading to http://171.64.65.54:8080/
- Replies: 7
- Views: 1441
Problems uploading to http://171.64.65.54:8080/
I'm recently having problems uploading large 6041 work units to http://171.64.65.54:8080/. Here is what happens when the work unit finishes. [09:43:19] Completed 200000 out of 250000 steps (80%) [10:16:28] Completed 202500 out of 250000 steps (81%) [10:49:42] Completed 205000 out of 250000 steps (82...
- Fri Apr 10, 2009 3:35 pm
- Forum: Issues with a specific server
- Topic: 171.65.103.162:8080 Cant upload
- Replies: 2
- Views: 852
171.65.103.162:8080 Cant upload
I can't seem to upload to this server. It appears to have started sometime yesterday evening. This is happening on all 4 cores of a FreeBSD workstation. Thanks, David Chamberlain --- Opening Log file [April 10 15:21:21] # Linux Console Edition ####################################################### ...