130.237.232.237

Moderators: Site Moderators, FAHC Science Team

Post Reply
3.0charlie
Posts: 13
Joined: Wed Jul 29, 2009 4:34 pm

Re: 130.237.232.237

Post by 3.0charlie »

Now this is new; it took ~ 2 hours to fetch a new WU (P6901 R16 C4 G99), and it was folded properly, being completed this morning at 2am. Stats show the credit at the 3am update, but the Client does not show the upload as being 'successful'. It kept on trying to send the WU for 7 hours.

I manually shut down the Client, and restarted it. It downloaded a new WU (6901 R19 C6 G65), and happily started folding. With an ETA of less than 11 hours, I'll see tonight how it behaves Live.
Folding for Hardware Canucks
Top
bollix47
Posts: 2957
Joined: Sun Dec 02, 2007 5:04 am
Location: Canada

Re: 130.237.232.237

Post by bollix47 »

For an update to my previous post in this thread see:

viewtopic.php?p=206031#p206031
Top
matt__
Posts: 9
Joined: Tue Jan 11, 2011 6:58 pm

Re: 130.237.232.237

Post by matt__ »

Just had a look at my logs.. Between Jan. 27th (which is as far back as my logs go) and today, I've had a total of 10724 of these errors (FILE_IO_ERROR specifically.)

How can I have my client avoid this server entirely?? It doesn't seem like it ever tries another server, so this system is going entirely unused.

Code: Select all

[20:37:15] 
[20:37:15] *------------------------------*
[20:37:15] Folding@Home Gromacs SMP Core
[20:37:15] Version 2.27 (Thu Feb 10 09:46:40 PST 2011)
[20:37:15] 
[20:37:15] Preparing to commence simulation
[20:37:15] - Looking at optimizations...
[20:37:15] - Created dyn
[20:37:15] - Files status OK
[20:37:15] Couldn't Decompress
[20:37:15] Called DecompressByteArray: compressed_data_size=0 data_size=0, decom
pressed_data_size=0 diff=0
[20:37:15] -Error: Couldn't update checksum variables
[20:37:15] Error: Could not open work file
[20:37:15] 
[20:37:15] Folding@home Core Shutdown: FILE_IO_ERROR
[20:37:15] CoreStatus = 75 (117)
[20:37:15] Error opening or reading from a file.
[20:37:15] Too many errors during run. Purging queue.
[20:37:16] 
[20:37:16] + Processing work unit
[20:37:16] Core required: FahCore_a5.exe
[20:37:16] Core found.
[20:37:16] Working on queue slot 01 [February 2 20:37:16 UTC]
[20:37:16] + Working ...
[20:37:16] - Calling './FahCore_a5.exe -dir work/ -nice 19 -suffix 01 -np 8 -checkpoint 15 -verbose -lifeline 24676 -version 634'

[20:37:16] 
[20:37:16] *------------------------------*
[20:37:16] Folding@Home Gromacs SMP Core
[20:37:16] Version 2.27 (Thu Feb 10 09:46:40 PST 2011)
[20:37:16] 
[20:37:16] Preparing to commence simulation
[20:37:16] - Looking at optimizations...
[20:37:16] - Created dyn
[20:37:16] - Files status OK
[20:37:16] Error: Missing work file=<>
[20:37:16] 
[20:37:16] Folding@home Core Shutdown: MISSING_WORK_FILES
[20:37:16] CoreStatus = 74 (116)
[20:37:16] The core could not find the work files specified. Removing from queue
[20:37:16] Deleting current work unit & continuing...
[20:37:16] Trying to send all finished work units
[20:37:16] + No unsent completed units remaining.
[20:37:16] - Preparing to get new work unit...
[20:37:16] Cleaning up work directory
[20:37:16] + Attempting to get work packet
[20:37:16] Passkey found
[20:37:16] - Will indicate memory of 5975 MB
[20:37:16] - Connecting to assignment server
[20:37:16] Connecting to http://assign.stanford.edu:8080/
[20:37:17] Posted data.
[20:37:17] Initial: ED82; - Successful: assigned to (130.237.232.237).
[20:37:17] + News From Folding@Home: Welcome to Folding@Home
[20:37:17] Loaded queue successfully.
[20:37:17] Sent data
[20:37:17] Connecting to http://130.237.232.237:8080/
[20:37:17] Posted data.
[20:37:17] Initial: 0000; - Receiving payload (expected size: 512)
[20:37:17] Conversation time very short, giving reduced weight in bandwidth avg
[20:37:17] - Downloaded at ~1 kB/s
[20:37:17] - Averaged speed for that direction ~1 kB/s
[20:37:17] + Received work.
[20:37:17] + Closed connections
[20:37:22] 
[20:37:22] + Processing work unit
[20:37:22] Core required: FahCore_a5.exe
[20:37:22] Core found.
[20:37:22] Working on queue slot 02 [February 2 20:37:22 UTC]
[20:37:22] + Working ...
[20:37:22] - Calling './FahCore_a5.exe -dir work/ -nice 19 -suffix 02 -np 8 -checkpoint 15 -verbose -lifeline 24676 -version 634'

[20:37:22] 
[20:37:22] *------------------------------*
[20:37:22] Folding@Home Gromacs SMP Core
[20:37:22] Version 2.27 (Thu Feb 10 09:46:40 PST 2011)
[20:37:22] 
[20:37:22] Preparing to commence simulation
[20:37:22] - Looking at optimizations...
[20:37:22] - Created dyn
[20:37:22] - Files status OK
[20:37:22] Couldn't Decompress
[20:37:22] Called DecompressByteArray: compressed_data_size=0 data_size=0, decompressed_data_size=0 diff=0
[20:37:22] -Error: Couldn't update checksum variables
[20:37:22] Error: Could not open work file
[20:37:22] 
[20:37:22] Folding@home Core Shutdown: FILE_IO_ERROR
[20:37:23] CoreStatus = 75 (117)
[20:37:23] Error opening or reading from a file.
[20:37:23] Deleting current work unit & continuing...
Top
bollix47
Posts: 2957
Joined: Sun Dec 02, 2007 5:04 am
Location: Canada

Re: 130.237.232.237

Post by bollix47 »

To avoid this server completely remove -bigadv from your configuration.

To try and get a different work unit while keeping -bigadv try deleting(rm in linux) queue.dat, unitinfo.txt, work/*.*, and machinedependent.dat from the smp folder.
Top
matt__
Posts: 9
Joined: Tue Jan 11, 2011 6:58 pm

Re: 130.237.232.237

Post by matt__ »

bollix47 wrote:To avoid this server completely remove -bigadv from your configuration.

To try and get a different work unit while keeping -bigadv try deleting(rm in linux) queue.dat, unitinfo.txt, work/*.*, and machinedependent.dat from the smp folder.
Thanks for the tip. Tried all that and it didn't work so I guess I'm stuck without bigadv for now. Bummer too - 8 core Xeon @ 3GHz. The few bigadv units it's managed to do scored some huge points.
Top
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:
Contact 7im

Re: 130.237.232.237

Post by 7im »

kasson wrote:Not sure about the "server reports problems." I have one idea--just tweaked a server setting. I don't suppose you have a backup of the results file to re-send?
Regarding the "dud" work units, it appears neither the new nor the old server software filters them properly. We'll have to come up with a manual solution.
How is that manual solution coming along? People are still posting about getting the 512k error...
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Top
Leonardo
Posts: 260
Joined: Tue Dec 04, 2007 5:09 am
Hardware configuration: GPU slots on home-built, purpose-built PCs.
Location: Eagle River, Alaska

Re: 130.237.232.237

Post by Leonardo »

I just got the 512K error as well, same server. I deleted the Work folder, queue.dat, unitinfo.txt, and machineindependent.dat, after which, it downloaded a proper work unit.
Image
Top
kasson
Pande Group Member
Posts: 1459
Joined: Thu Nov 29, 2007 9:37 pm

Re: 130.237.232.237

Post by kasson »

I'm taking this server off assign until we have a chance to fix the problem. This may mean a period of no bigadv availability. You should receive normal SMP units to fold.
Top
kasson
Pande Group Member
Posts: 1459
Joined: Thu Nov 29, 2007 9:37 pm

Re: 130.237.232.237

Post by kasson »

Ok--we have manually (or via script) fixed most of the offending TPR files. There are a few we're still cleaning up. We're resuming assigns--let us know if the problem resolves or continues. BTW you might need to clean out your work directory if the problem doesn't immediately resolve.
Top
rhavern
Posts: 425
Joined: Mon Dec 03, 2007 8:45 am
Location: UK

Re: 130.237.232.237

Post by rhavern »

I haven't experienced any of the issues mentioned, but I have just picked up P6903 R10 C19 G17 from this server at 1425 GMT.
Folding since 1 WU=1 point
ImageImage
Top
3.0charlie
Posts: 13
Joined: Wed Jul 29, 2009 4:34 pm

Re: 130.237.232.237

Post by 3.0charlie »

matt, I had those same CoreStatus=75 errors, and using memtest86 I found a dead stick of ram.

Dr. Kasson, this assignment server is a pain to deal with. I basically started from fresh (Ubuntu 11.04 - just in case the OS got corrupted with the dead ram stick), with a new Fah install this evening and -bigadv -smp 48 flags. Right off the bat, this server was assigned, and it simply never downloaded a Core nor did it manage to get a WU. Getting the re-assignment to 130.237.232.141 was also unsuccessful as of writing this.

edit: after 1.5 hours, downloading an A5 Core started... then stopped.
edit2: overnight, it took 4 Core downloads - first 3 were corrupted - and over 5 hours to finally receive a P6901, which is being folded.
Folding for Hardware Canucks
Top
WitchDoctorB
Posts: 11
Joined: Thu Nov 13, 2008 2:34 am

Re: 130.237.232.237

Post by WitchDoctorB »

I was unable to upload two bigadv to server 130.237.232.237 over the weekend

I am interesed to know if the server has experienced any problems over the weekend and if any one has problems uploading files for bigadv using AT&T U-verse.

I made the cardinal sin of updating/changing more than on thing at the same time so I don't know how I broke it...

Code: Select all

21:24:30:WU02:FS00:Sending unit results: id:02 state:SEND error:OK project:6904 run:1 clone:9 gen:57 core:0xa5 unit:0x0000003f52be746d4dfbc82f2514e679
21:24:31:WU02:FS00:Uploading 212.03MiB to 130.237.232.237
21:24:31:WU02:FS00:Connecting to 130.237.232.237:8080
21:24:31:WU00:FS00:Sending unit results: id:00 state:SEND error:OK project:6903 run:6 clone:21 gen:30 core:0xa5 unit:0x0000002e52be746d4de9252f3f8a22d3
21:24:31:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
21:24:31:WU02:FS00:Connecting to 130.237.232.237:80
21:24:31:WU00:FS00:Uploading 212.12MiB to 130.237.232.237
21:24:31:WU00:FS00:Connecting to 130.237.232.237:8080
21:24:31:WU01:FS00:Starting
21:24:31:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
21:24:31:WU00:FS00:Connecting to 130.237.232.237:80
21:24:31:WU01:FS00:Running FahCore: /usr/bin/FAHCoreWrapper /var/lib/fahclient/cores/www.stanford.edu/~pande/Linux/AMD64/Core_a5.fah/FahCore_a5 -dir 01 -suffix 01 -version 701 -checkpoint 15 -np 48
21:24:31:WU01:FS00:Started FahCore on PID 1763
21:24:31:Started thread 8 on PID 1623
21:24:31:WU01:FS00:Core PID:1767
21:24:31:WU01:FS00:FahCore 0xa5 started
21:24:31:WARNING:WU02:FS00:Exception: Failed to send results to work server: Failed to connect to 130.237.232.237:80: Network is unreachable
21:24:31:WARNING:WU00:FS00:Exception: Failed to send results to work server: Failed to connect to 130.237.232.237:80: Network is unreachable
21:24:31:WU02:FS00:Sending unit results: id:02 state:SEND error:OK project:6904 run:1 clone:9 gen:57 core:0xa5 unit:0x0000003f52be746d4dfbc82f2514e679
21:24:31:WU01:FS00:0xa5:
21:24:31:WU01:FS00:0xa5:*------------------------------*
21:24:31:WU01:FS00:0xa5:Folding@Home Gromacs SMP Core
21:24:31:WU01:FS00:0xa5:Version 2.27 (Thu Feb 10 09:46:40 PST 2011)
21:24:31:WU01:FS00:0xa5:
21:24:31:WU01:FS00:0xa5:Preparing to commence simulation
21:24:31:WU01:FS00:0xa5:- Looking at optimizations...
21:24:31:WU01:FS00:0xa5:- Files status OK
21:24:31:WU02:FS00:Uploading 212.03MiB to 130.237.232.237
21:24:31:WU00:FS00:Sending unit results: id:00 state:SEND error:OK project:6903 run:6 clone:21 gen:30 core:0xa5 unit:0x0000002e52be746d4de9252f3f8a22d3
21:24:31:WU02:FS00:Connecting to 130.237.232.237:8080
21:24:31:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
21:24:31:WU02:FS00:Connecting to 130.237.232.237:80
21:24:31:WU00:FS00:Uploading 212.12MiB to 130.237.232.237
21:24:31:WARNING:WU02:FS00:Exception: Failed to send results to work server: Failed to connect to 130.237.232.237:80: Network is unreachable
21:24:31:WU00:FS00:Connecting to 130.237.232.237:8080
21:24:31:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
21:24:31:WU00:FS00:Connecting to 130.237.232.237:80
21:24:31:WARNING:WU00:FS00:Exception: Failed to send results to work server: Failed to connect to 130.237.232.237:80: Network is unreachable
21:24:47:WU01:FS00:0xa5:- Expanded 57245716 -> 71846524 (decompressed 50.4 percent)
21:24:48:WU01:FS00:0xa5:Called DecompressByteArray: compressed_data_size=57245716 data_size=71846524, decompressed_data_size=71846524 diff=0
21:24:48:WU01:FS00:0xa5:- Digital signature verified
21:24:48:WU01:FS00:0xa5:
21:24:48:WU01:FS00:0xa5:Project: 6903 (Run 1, Clone 4, Gen 55)
21:24:48:WU01:FS00:0xa5:
21:24:48:WU01:FS00:0xa5:Assembly optimizations on if available.
21:24:48:WU01:FS00:0xa5:Entering M.D.
21:24:58:WU01:FS00:0xa5:Mapping NT from 48 to 48 
21:25:05:WU01:FS00:0xa5:Completed 0 out of 250000 steps  (0%)
21:25:31:WU02:FS00:Sending unit results: id:02 state:SEND error:OK project:6904 run:1 clone:9 gen:57 core:0xa5 unit:0x0000003f52be746d4dfbc82f2514e679
21:25:31:WU02:FS00:Uploading 212.03MiB to 130.237.232.237
21:25:31:WU02:FS00:Connecting to 130.237.232.237:8080
21:25:31:WU00:FS00:Sending unit results: id:00 state:SEND error:OK project:6903 run:6 clone:21 gen:30 core:0xa5 unit:0x0000002e52be746d4de9252f3f8a22d3
21:25:31:WU00:FS00:Uploading 212.12MiB to 130.237.232.237
21:25:31:WU00:FS00:Connecting to 130.237.232.237:8080
21:25:37:WU00:FS00:Upload 0.29%
21:25:38:WU02:FS00:Upload 0.24%
21:25:43:WU00:FS00:Upload 0.68%
21:26:44:Server connection id=1 on 0.0.0.0:36330 from 127.0.0.1
21:26:44:Started thread 9 on PID 1623
21:35:26:FS00:Finishing
21:41:56:WU00:FS00:Upload 0.85%
21:41:56:WARNING:WU00:FS00:Exception: Failed to send results to work server: Transfer failed
21:41:56:WU00:FS00:Sending unit results: id:00 state:SEND error:OK project:6903 run:6 clone:21 gen:30 core:0xa5 unit:0x0000002e52be746d4de9252f3f8a22d3
21:41:56:WU00:FS00:Uploading 212.12MiB to 130.237.232.237
21:41:56:WU00:FS00:Connecting to 130.237.232.237:8080
21:42:02:WU00:FS00:Upload 0.53%
21:42:08:WU00:FS00:Upload 0.77%
21:42:14:WU00:FS00:Upload 1.00%
21:42:21:WU00:FS00:Upload 1.41%
21:42:25:WU02:FS00:Upload 0.32%
21:42:25:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
21:42:25:WU02:FS00:Sending unit results: id:02 state:SEND error:OK project:6904 run:1 clone:9 gen:57 core:0xa5 unit:0x0000003f52be746d4dfbc82f2514e679
21:42:25:WU02:FS00:Uploading 212.03MiB to 130.237.232.237
21:42:25:WU02:FS00:Connecting to 130.237.232.237:8080
21:42:28:WU00:FS00:Upload 1.65%
21:42:31:WU02:FS00:Upload 0.32%
21:42:37:WU02:FS00:Upload 0.59%
21:42:43:WU02:FS00:Upload 0.85%
21:42:49:WU02:FS00:Upload 1.24%
21:42:55:WU02:FS00:Upload 1.74%
21:45:44:WU01:FS00:0xa5:Completed 2500 out of 250000 steps  (1%)
21:53:22:FS00:Paused
21:53:22:FS00:Shutting core down
21:53:25:WU01:FS00:0xa5:Client no longer detected. Shutting down core.
21:53:25:WU01:FS00:0xa5:
21:53:25:WU01:FS00:0xa5:Folding@home Core Shutdown: CLIENT_DIED
21:53:25:WU01:FS00:FahCore returned: INTERRUPTED (102 = 0x66)
21:58:11:WU00:FS00:Upload 1.71%
21:58:11:WARNING:WU00:FS00:Exception: Failed to send results to work server: Transfer failed
21:58:11:WU00:FS00:Sending unit results: id:00 state:SEND error:OK project:6903 run:6 clone:21 gen:30 core:0xa5 unit:0x0000002e52be746d4de9252f3f8a22d3
21:58:11:WU00:FS00:Uploading 212.12MiB to 130.237.232.237
21:58:11:WU00:FS00:Connecting to 130.237.232.237:8080
21:58:37:WU02:FS00:Upload 2.00%
21:58:37:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
21:58:37:WU02:FS00:Sending unit results: id:02 state:SEND error:OK project:6904 run:1 clone:9 gen:57 core:0xa5 unit:0x0000003f52be746d4dfbc82f2514e679
21:58:37:WU02:FS00:Uploading 212.03MiB to 130.237.232.237
21:58:37:WU02:FS00:Connecting to 130.237.232.237:8080
21:58:43:WU02:FS00:Upload 0.53%
21:58:49:WU02:FS00:Upload 0.94%
21:58:55:WU02:FS00:Upload 1.24%
21:59:01:WU02:FS00:Upload 1.53%
21:59:07:WU02:FS00:Upload 1.83%
21:59:13:WU02:FS00:Upload 2.06%
21:59:19:WU02:FS00:Upload 2.42%
22:11:50:FS00:Unpaused
22:11:50:WU01:FS00:Starting
22:11:50:WU01:FS00:Running FahCore: /usr/bin/FAHCoreWrapper /var/lib/fahclient/cores/www.stanford.edu/~pande/Linux/AMD64/Core_a5.fah/FahCore_a5 -dir 01 -suffix 01 -version 701 -checkpoint 15 -np 48
22:11:50:WU01:FS00:Started FahCore on PID 3033
22:11:50:Started thread 10 on PID 1623
22:11:50:WU01:FS00:Core PID:3037
22:11:50:WU01:FS00:FahCore 0xa5 started
22:11:51:WU01:FS00:0xa5:
22:11:51:WU01:FS00:0xa5:*------------------------------*
22:11:51:WU01:FS00:0xa5:Folding@Home Gromacs SMP Core
22:11:51:WU01:FS00:0xa5:Version 2.27 (Thu Feb 10 09:46:40 PST 2011)
22:11:51:WU01:FS00:0xa5:
22:11:51:WU01:FS00:0xa5:Preparing to commence simulation
22:11:51:WU01:FS00:0xa5:- Looking at optimizations...
22:11:51:WU01:FS00:0xa5:- Files status OK
22:11:52:FS00:Finishing
22:11:58:WU01:FS00:0xa5:- Expanded 57245716 -> 71846524 (decompressed 50.4 percent)
22:11:58:WU01:FS00:0xa5:Called DecompressByteArray: compressed_data_size=57245716 data_size=71846524, decompressed_data_size=71846524 diff=0
22:11:58:WU01:FS00:0xa5:- Digital signature verified
22:11:58:WU01:FS00:0xa5:
22:11:58:WU01:FS00:0xa5:Project: 6903 (Run 1, Clone 4, Gen 55)
22:11:58:WU01:FS00:0xa5:
22:11:59:WU01:FS00:0xa5:Assembly optimizations on if available.
22:11:59:WU01:FS00:0xa5:Entering M.D.
22:12:05:WU01:FS00:0xa5:Using Gromacs checkpoints
22:12:14:WU01:FS00:0xa5:Mapping NT from 48 to 48 
22:13:30:WU01:FS00:0xa5:Resuming from checkpoint
22:14:07:WU01:FS00:0xa5:Verified 01/wudata_01.log
22:14:08:WU01:FS00:0xa5:Verified 01/wudata_01.trr
22:14:08:WU01:FS00:0xa5:Verified 01/wudata_01.xtc
22:14:08:WU01:FS00:0xa5:Verified 01/wudata_01.edr
22:14:09:WU01:FS00:0xa5:Completed 1845 out of 250000 steps  (0%)
22:14:58:WU02:FS00:Upload 2.54%
22:14:58:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
22:14:58:WU02:FS00:Sending unit results: id:02 state:SEND error:OK project:6904 run:1 clone:9 gen:57 core:0xa5 unit:0x0000003f52be746d4dfbc82f2514e679
22:14:58:WU02:FS00:Uploading 212.03MiB to 130.237.232.237
22:14:58:WU02:FS00:Connecting to 130.237.232.237:8080
22:15:38:WU00:FS00:Upload 0.24%
22:15:38:WARNING:WU00:FS00:Exception: Failed to send results to work server: Transfer failed
22:15:38:WU00:FS00:Sending unit results: id:00 state:SEND error:OK project:6903 run:6 clone:21 gen:30 core:0xa5 unit:0x0000002e52be746d4de9252f3f8a22d3
22:15:38:WU00:FS00:Uploading 212.12MiB to 130.237.232.237
22:15:38:WU00:FS00:Connecting to 130.237.232.237:8080
22:15:44:WU00:FS00:Upload 0.44%
22:15:50:WU00:FS00:Upload 0.65%
22:15:56:WU00:FS00:Upload 1.09%
22:16:02:WU00:FS00:Upload 1.56%
22:16:08:WU00:FS00:Upload 1.86%
22:16:14:WU00:FS00:Upload 2.15%
22:16:20:WU00:FS00:Upload 2.39%
22:18:45:WU01:FS00:0xa5:Completed 2500 out of 250000 steps  (1%)
22:30:37:WU02:FS00:Upload 0.15%
22:30:37:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
22:30:37:WU02:FS00:Sending unit results: id:02 state:SEND error:OK project:6904 run:1 clone:9 gen:57 core:0xa5 unit:0x0000003f52be746d4dfbc82f2514e679
22:30:37:WU02:FS00:Uploading 212.03MiB to 130.237.232.237
22:30:37:WU02:FS00:Connecting to 130.237.232.237:8080
22:30:43:WU02:FS00:Upload 0.41%
22:30:49:WU02:FS00:Upload 0.71%
22:30:55:WU02:FS00:Upload 1.00%
22:31:02:WU02:FS00:Upload 1.30%
22:31:54:WU00:FS00:Upload 2.50%
22:31:54:WARNING:WU00:FS00:Exception: Failed to send results to work server: Transfer failed
22:31:54:WU00:FS00:Sending unit results: id:00 state:SEND error:OK project:6903 run:6 clone:21 gen:30 core:0xa5 unit:0x0000002e52be746d4de9252f3f8a22d3
22:31:54:WU00:FS00:Uploading 212.12MiB to 130.237.232.237
22:31:54:WU00:FS00:Connecting to 130.237.232.237:8080
22:32:00:WU00:FS00:Upload 0.32%
22:32:06:WU00:FS00:Upload 0.62%
22:32:12:WU00:FS00:Upload 0.80%
22:32:18:WU00:FS00:Upload 1.00%
22:32:24:WU00:FS00:Upload 1.27%
22:32:30:WU00:FS00:Upload 1.47%
22:32:36:WU00:FS00:Upload 1.65%

I switched from Charter Internet/Direct TV/ATT phone to all Uverse to save a little cash a little over a week ago. I also updated my 4p from v7.1.38 to the latest version 7.1.48 client for folding.

It starts to upload the result but then stops. I had two units in the send queue and one folding. I tried to open the 8080 and 80 ports in the modem, who knows if I did that correctly, but still the same. So now I don't know if its My install on the computer, Uverse, or the work server. However, I ended up corrupting the queue file while toubleshooting (reinstalling) and lost the units.

Now I have purged the installation and installed v7.1.48 on Ubuntu 10.10. Since I have uploaded an SMP without problems and now have a 6903 folding. I am concerned of a repeat failed upload but it will take several hours to reach that test.



My other computer did upload SMP and GPU with out problems...
Image
Top
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 130.237.232.237

Post by bruce »

You should never have to open port 80. By default, your browser uses it so it's always open if you can reach the internet. Port 8080 is rarely closed, the only common exception is where an employer or a government decides they need to install a proxy for any number of reasons, including protecting the people from the evils of the internet. (There may be an exception or two that I'm not thinking of right now.)

The server log for 130.237.232.237 shows no real changes over the past several days.
Top
WitchDoctorB
Posts: 11
Joined: Thu Nov 13, 2008 2:34 am

Re: 130.237.232.237

Post by WitchDoctorB »

Thanks...I'll see how the re-install goes. I hope its not some sort of Uverse cap.
Image
Top
bollix47
Posts: 2957
Joined: Sun Dec 02, 2007 5:04 am
Location: Canada

Re: 130.237.232.237

Post by bollix47 »

Reject

Tue Mar 20 17:00:00 PST 2012 130.237.232.237 folding-2 lindahl SMP full Reject 0.05 0 0 10991 16 0 934 934 934 - - - - 0 0 - - 1 - 1 0 L; 10 6.33 50 10000 2800 - 12 - - 8080
Tue Mar 20 17:10:01 PST 2012 130.237.232.237 folding-2 lindahl SMP full Reject 0.00 0 0 10991 16 0 934 934 934 - - - - 0 0 - - 1 - 1 0
Top
Post Reply

Return to “Issues with a specific server”