VMware Linux bigadv

I'm not following, it may well be uploading the file fine. But it then stops dead at that stage in the log quoted above. I've left it over an hour and it was still at the same stage in the log so I had to manually reboot the client to get it to progress. This is the second time in a row it has happened and this last time was with a small (non-bigadv unit).

It may save a few minutes but that's no good if I have to reboot it every time.
 
Strange, I'm not seeing that at all on my machine.

I get the same errors as you over the same period of time (1-2min) but the Folding client just gets the next WU after that time and carries on. And the Langouste just caches the result and sends it.

I know its sending the results fine because I can see them in the stats showing up at the right time and my figures are good.

Anyway you do what you think is best :) I've just installed Langouste windows client on Gemini :)
 
It is odd yes, might just be FoldingOne being funny, we shall see when FoldingTwo completes it's first WU on the new 1.60 image later today.

It might as have something to do with me ticking the replicate physical adapter box in the images adapter setup.
 
(Optional) Select Replicate physical network connection state if you use the virtual machine on a laptop or other mobile device. As you move from one wired or wireless network to another, the IP address is automatically renewed.
Click to expand...
 

Hmm see I set it to that when I had those IP issues and it seemed to sort it. Guess maybe it did nothing and I just assumed it did, might be causing this issue I guess. Only one way to find out! ;)
 
Hmm, FoldingTwo uploaded and then downloaded a new WU fine, however it strangely picked up a P6962 A3 WU for 4424 ish points. You had this Biffa? Maybe they are low on BigAdv units.
 
lol, I dunno I've been seeing it more with VMware, it used to happen once in a blue moon on just Windows.

Yes, two i7 920s @ 4GHz.

FoldingTwo just picked up a P7134 A3, it is really killing my PPD, down to 22k.
 
Hmm, remember you have to return 80% good results to keep getting bigadv, if you drop below that you will get some advmethods SMP's

But yes I'm getting the odd A3 standard WU's every now and then.

Only reason I asked is that I would have thought your daily average would be closer to 70K than 13K
 
Ah I see. Well I've not had any units fail in quite a while. Out of interest do you have advmethods enabled or disabled for BigAdv units? I disabled it after those issues that loudbob had.

It is 13k as I fold about 350k a month for those EVGA bucks.
 
Last edited:
Tch so I'm helping the opposition? Sheesh. :p

advmethods should *ALWAYS* be turned off, both as not having the switch in command line and turned off in Advanced options when in -configonly
if you are doing bigadv
 
Bah I'm no threat these days! :p

Thanks thought as much, lastly does packet size in the config page have any bearing on anything?

I really should be sleeping! :rolleyes: :D
 
Biffa said:
Hmm, remember you have to return 80% good results to keep getting bigadv, if you drop below that you will get some advmethods SMP's

But yes I'm getting the odd A3 standard WU's every now and then.

Only reason I asked is that I would have thought your daily average would be closer to 70K than 13K
Click to expand...

I'm using the following:

i7 860 @ 4.0 GHz - VMware
i7 930 @ 4.2 GHZ - VMware
2 x GTX 430's (810 MHz & 900 MHz)

http://dl.dropbox.com/u/25298160/Folding%20Web%20Stats/summary.html

Even with 2 x 2684's my ppd is 52k (10k for the GPU's). With 6901's it goes upto 85k.
 
lol, I've had vary few 69XXs. FoldingTwo just BSOD and then got a P2686 lol! Just my luck...

I really am chucking money down the drain on the lottery with luck like that! ;)
 
Right up until this morning it was working fine, no more of my usual "issues". However strangely both systems went down and rebooted at the same time (going on the Windows Task Manager Up Time).

However this is extremely odd, they both have EXACTLY the same uptime of about 12 hours (down to the second) so something happened this morning around 08:30. My first thought was a power outtage which is rare in our area but the servers uptime is over 4 days. Just one of those mysteries I expect I'll never get to the bottom of...:confused: :o
 
FoldingTwo now has the same issue with it getting stuck downloading a unit. I've left it 45 minutes and nothing:

Code: 
Tue Apr 19 19:23:25 2011 Langouste3 0.15.6 (compiled Thu Feb 24 18:59:29 MST 2011 by root@Build)
Tue Apr 19 19:23:25 2011 Langouste3 comes with ABSOLUTELY NO WARRANTY; for details
Tue Apr 19 19:23:25 2011 see `COPYING.txt' file located in source directory
Tue Apr 19 19:23:25 2011 Default Langouste helper temp directory: /tmp/langouste-fah/
Tue Apr 19 19:23:25 2011 Listening on 127.0.0.1:8080
Tue Apr 19 19:23:25 2011 Going into backgound...
Thu Apr 21 13:25:13 2011 Accepted connection from: 127.0.0.1:40267
Thu Apr 21 13:25:13 2011 PID for socket: 719
Thu Apr 21 13:25:13 2011 PID 719: issending: 0
Thu Apr 21 13:25:13 2011 ===> PID 719 is (most likely) contacting WU server, content length: 102843730
Thu Apr 21 13:25:13 2011 ===> Helper pid: -1
Thu Apr 21 13:25:13 2011 ===> PID 719: numcores: 0
Thu Apr 21 13:25:13 2011 ===> now: 1303392313, last helper launched at: 0
Thu Apr 21 13:25:13 2011 ===> Launching helper: '/proc/719/cwd/langouste-helper.sh' (exe name: '/usr/local/fah/fah6')...
Thu Apr 21 13:25:13 2011 ===> Forked 28155
Thu Apr 21 13:25:13 2011 (0) Local: received 16384 bytes, sent 0 bytes
Thu Apr 21 13:25:13 2011 Accepted connection from: 127.0.0.1:40268
Thu Apr 21 13:25:13 2011 PID for socket: 719
Thu Apr 21 13:25:13 2011 PID 719: issending: 0
Thu Apr 21 13:25:13 2011 ===> PID 719 is (most likely) contacting WU server, content length: 102843730
Thu Apr 21 13:25:13 2011 ===> Helper pid: -1
Thu Apr 21 13:25:13 2011 ===> PID 719: numcores: 0
Thu Apr 21 13:25:13 2011 ===> now: 1303392313, last helper launched at: 1303392313
Thu Apr 21 13:25:13 2011 ===> WARNING: can only launch one helper in 2 minutes (per client)
Thu Apr 21 13:25:13 2011 (0) Local: received 16384 bytes, sent 0 bytes
Thu Apr 21 13:25:13 2011 Accepted connection from: 127.0.0.1:40269
Thu Apr 21 13:25:13 2011 PID for socket: 719
Thu Apr 21 13:25:13 2011 PID 719: issending: 0
Thu Apr 21 13:25:13 2011 ===> PID 719 is (most likely) contacting WU server, content length: 102843730
Thu Apr 21 13:25:13 2011 ===> Helper pid: -1
Thu Apr 21 13:25:13 2011 ===> PID 719: numcores: 0
Thu Apr 21 13:25:13 2011 ===> now: 1303392313, last helper launched at: 1303392313
Thu Apr 21 13:25:13 2011 ===> WARNING: can only launch one helper in 2 minutes (per client)
Thu Apr 21 13:25:13 2011 (0) Local: received 121 bytes, sent 0 bytes
Thu Apr 21 13:25:13 2011 Accepted connection from: 127.0.0.1:40270
Thu Apr 21 13:25:13 2011 PID for socket: 719
Thu Apr 21 13:25:13 2011 PID 719: issending: 0
Thu Apr 21 13:25:13 2011 ===> PID 719 is (most likely) contacting WU server, content length: 102843730
Thu Apr 21 13:25:13 2011 ===> Helper pid: -1
Thu Apr 21 13:25:13 2011 ===> PID 719: numcores: 0
Thu Apr 21 13:25:13 2011 ===> now: 1303392313, last helper launched at: 1303392313
Thu Apr 21 13:25:13 2011 ===> WARNING: can only launch one helper in 2 minutes (per client)
Thu Apr 21 13:25:13 2011 (0) Local: received 16384 bytes, sent 0 bytes
Thu Apr 21 13:25:14 2011 Accepted connection from: 127.0.0.1:40271
Thu Apr 21 13:25:14 2011 PID for socket: 719
Thu Apr 21 13:25:14 2011 PID 719: issending: 0
Thu Apr 21 13:25:14 2011 ===> PID 719 is (most likely) contacting WU server, content length: 102843730
Thu Apr 21 13:25:14 2011 ===> Helper pid: -1
Thu Apr 21 13:25:14 2011 ===> PID 719: numcores: 0
Thu Apr 21 13:25:14 2011 ===> now: 1303392314, last helper launched at: 1303392313
Thu Apr 21 13:25:14 2011 ===> WARNING: can only launch one helper in 2 minutes (per client)
Thu Apr 21 13:25:14 2011 (0) Local: received 121 bytes, sent 0 bytes
Thu Apr 21 13:25:14 2011 Accepted connection from: 127.0.0.1:40272
Thu Apr 21 13:25:14 2011 PID for socket: 719
Thu Apr 21 13:25:14 2011 PID 719: issending: 0
Thu Apr 21 13:25:14 2011 ===> PID 719 is (most likely) contacting WU server, content length: 102843730
Thu Apr 21 13:25:14 2011 ===> Helper pid: -1
Thu Apr 21 13:25:14 2011 ===> PID 719: numcores: 0
Thu Apr 21 13:25:14 2011 ===> now: 1303392314, last helper launched at: 1303392313
Thu Apr 21 13:25:14 2011 ===> WARNING: can only launch one helper in 2 minutes (per client)
Thu Apr 21 13:25:14 2011 (0) Local: received 117 bytes, sent 0 bytes
Thu Apr 21 13:25:14 2011 Accepted connection from: 127.0.0.1:40273
Thu Apr 21 13:25:14 2011 PID for socket: 719
Thu Apr 21 13:25:14 2011 PID 719: issending: 0
Thu Apr 21 13:25:14 2011 ===> PID 719 is contacting main assignment server
Thu Apr 21 13:25:14 2011 (0) resolving 'assign.stanford.edu:8080'
Thu Apr 21 13:25:14 2011 PID 28155 (child) exited
Thu Apr 21 13:25:14 2011 (0) Connecting to: 171.67.108.200:8080
Thu Apr 21 13:25:14 2011 (0) Connected.
Thu Apr 21 13:25:15 2011 (0) Local connection closed (bsize: 0).
Thu Apr 21 13:25:15 2011 (0) Local: received 559 bytes, sent 396 bytes
Thu Apr 21 13:25:15 2011 (0) Remote: received 396 bytes, sent 559 bytes
Thu Apr 21 13:25:15 2011 Accepted connection from: 127.0.0.1:40275
Thu Apr 21 13:25:15 2011 PID for socket: 719
Thu Apr 21 13:25:15 2011 PID 719: issending: 0
Thu Apr 21 13:25:15 2011 ===> PID 719 is (most likely) contacting WU server, content length: 512
Thu Apr 21 13:25:15 2011 (0) resolving '171.67.108.22:8080'
Thu Apr 21 13:25:15 2011 (0) Connecting to: 171.67.108.22:8080
Thu Apr 21 13:25:15 2011 (0) Connected.
Thu Apr 21 13:26:14 2011 Accepted connection from: 127.0.0.1:40277
Thu Apr 21 13:26:14 2011 PID for socket: 28169
Thu Apr 21 13:26:14 2011 PID 28169: issending: 1
Thu Apr 21 13:26:14 2011 (1) resolving '171.67.108.22:8080'
Thu Apr 21 13:26:14 2011 (1) Connecting to: 171.67.108.22:8080
Thu Apr 21 13:26:14 2011 (1) Connected.

Code: 
[13:20:51] Completed 250000 out of 250000 steps (100%)
[13:21:03] DynamicWrapper: Finished Work Unit: sleep=10000
[13:21:13]
[13:21:13] Finished Work Unit:
[13:21:13] - Reading up to 56585136 from "work/wudata_05.trr": Read 56585136
[13:21:13] trr file hash check passed.
[13:21:13] - Reading up to 45885052 from "work/wudata_05.xtc": Read 45885052
[13:21:14] xtc file hash check passed.
[13:21:14] edr file hash check passed.
[13:21:14] logfile size: 203082
[13:21:14] Leaving Run
[13:21:16] - Writing 102843218 bytes of core data to disk...
[13:21:17] ... Done.
[13:23:26] - Autosending finished units... [April 21 13:23:26 UTC]
[13:23:26] Trying to send all finished work units
[13:23:26] + No unsent completed units remaining.
[13:23:26] - Autosend completed
[13:24:52] - Shutting down core
[13:24:52]
[13:24:52] Folding@home Core Shutdown: FINISHED_UNIT
[13:25:13] CoreStatus = 64 (100)
[13:25:13] Unit 5 finished with 56 percent of time to deadline remaining.
[13:25:13] Updated performance fraction: 0.800322
[13:25:13] Sending work to server
[13:25:13] Project: 2685 (Run 7, Clone 11, Gen 51)


[13:25:13] + Attempting to send results [April 21 13:25:13 UTC]
[13:25:13] - Reading file work/wuresults_05.dat from core
[13:25:13] (Read 102843218 bytes from disk)
[13:25:13] Connecting to http://171.67.108.22:8080/
[13:25:13] - Couldn't send HTTP request to server
[13:25:13] + Could not connect to Work Server (results)
[13:25:13] (171.67.108.22:8080)
[13:25:13] + Retrying using alternative port
[13:25:13] Connecting to http://171.67.108.22:80/
[13:25:13] - Couldn't send HTTP request to server
[13:25:13] + Could not connect to Work Server (results)
[13:25:13] (171.67.108.22:80)
[13:25:13] - Error: Could not transmit unit 05 (completed April 21) to work server.
[13:25:13] - 1 failed uploads of this unit.
[13:25:13] Keeping unit 05 in queue.
[13:25:13] Trying to send all finished work units
[13:25:13] Project: 2685 (Run 7, Clone 11, Gen 51)


[13:25:13] + Attempting to send results [April 21 13:25:13 UTC]
[13:25:13] - Reading file work/wuresults_05.dat from core
[13:25:13] (Read 102843218 bytes from disk)
[13:25:13] Connecting to http://171.67.108.22:8080/
[13:25:13] - Couldn't send HTTP request to server
[13:25:13] + Could not connect to Work Server (results)
[13:25:13] (171.67.108.22:8080)
[13:25:13] + Retrying using alternative port
[13:25:13] Connecting to http://171.67.108.22:80/
[13:25:13] - Couldn't send HTTP request to server
[13:25:13] + Could not connect to Work Server (results)
[13:25:13] (171.67.108.22:80)
[13:25:13] - Error: Could not transmit unit 05 (completed April 21) to work server.
[13:25:13] - 2 failed uploads of this unit.


[13:25:13] + Attempting to send results [April 21 13:25:13 UTC]
[13:25:13] - Reading file work/wuresults_05.dat from core
[13:25:14] (Read 102843218 bytes from disk)
[13:25:14] Connecting to http://171.67.108.25:8080/
[13:25:14] - Couldn't send HTTP request to server
[13:25:14] + Could not connect to Work Server (results)
[13:25:14] (171.67.108.25:8080)
[13:25:14] + Retrying using alternative port
[13:25:14] Connecting to http://171.67.108.25:80/
[13:25:14] - Couldn't send HTTP request to server
[13:25:14] + Could not connect to Work Server (results)
[13:25:14] (171.67.108.25:80)
[13:25:14] Could not transmit unit 05 to Collection server; keeping in queue.
[13:25:14] + Sent 0 of 1 completed units to the server
[13:25:14] - Preparing to get new work unit...
[13:25:14] Cleaning up work directory
[13:25:14] + Attempting to get work packet
[13:25:14] Passkey found
[13:25:14] - Will indicate memory of 3072 MB
[13:25:14] - Connecting to assignment server
[13:25:14] Connecting to http://assign.stanford.edu:8080/
[13:25:15] Posted data.
[13:25:15] Initial: 43AB; - Successful: assigned to (171.67.108.22).
[13:25:15] + News From Folding@Home: Welcome to Folding@Home
[13:25:15] Loaded queue successfully.
[13:25:15] Sent data
[13:25:15] Connecting to http://171.67.108.22:8080/
[13:25:24] Posted data.
[13:25:24] Initial: 0000; - Receiving payload (expected size: 24867038)

I must be missing something! :confused:
 
Question (for future reference):

Does the Vmware Player 3.0 recognise the i7 970 and above? (i.e. 12 threads on one box)
 
You must log in or register to reply here.
Back
Top Bottom