128.143.199.97 & 128.143.231.202 (unable to submit WU's)

Moderators: Site Moderators, FAHC Science Team

Post Reply
drexlerderek
Posts: 3
Joined: Sun Mar 18, 2012 3:52 am

128.143.199.97 & 128.143.231.202 (unable to submit WU's)

Post by drexlerderek »

I'm running notfreds diskless folding client. I've been unable to connect for about two days now. I'm using the same client for two other units without problems.

Code: Select all

--- Opening Log file [March 18 03:36:38 UTC] 


# Linux SMP Console Edition ###################################################
###############################################################################

                       Folding@Home Client Version 6.29

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: /etc/folding/1
Executable: ./fah6
Arguments: -local -forceasm -smp 8 

[03:36:38] - Ask before connecting: No
[03:36:38] - User name: drexlerderek (Team 86565)
[03:36:38] - User ID: 
[03:36:38] - Machine ID: 1
[03:36:38] 
[03:36:38] Loaded queue successfully.
[03:36:38] - Preparing to get new work unit...
[03:36:38] Cleaning up work directory
[03:36:38] Project: 7501 (Run 0, Clone 30, Gen 478)


[03:36:38] + Attempting to send results [March 18 03:36:38 UTC]
[03:36:38] + Attempting to get work packet
[03:36:38] Passkey found
[03:36:38] - Connecting to assignment server
[03:36:39] - Successful: assigned to (128.143.199.97).
[03:36:39] + News From Folding@Home: Welcome to Folding@Home
[03:36:39] Loaded queue successfully.
[03:37:00] - Couldn't send HTTP request to server
[03:37:00] + Could not connect to Work Server
[03:37:00] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[03:37:17] + Attempting to get work packet
[03:37:17] Passkey found
[03:37:17] - Connecting to assignment server
[03:38:01] - Successful: assigned to (128.143.199.97).
[03:38:01] + News From Folding@Home: Welcome to Folding@Home
[03:38:01] - Couldn't send HTTP request to server
[03:38:01] + Could not connect to Work Server (results)
[03:38:01]     (128.143.199.97:8080)
[03:38:01] + Retrying using alternative port
[03:38:01] Loaded queue successfully.
[03:41:49] - Couldn't send HTTP request to server
[03:41:49] + Could not connect to Work Server (results)
[03:41:49]     (128.143.199.97:80)
[03:41:49] - Error: Could not transmit unit 01 (completed March 16) to work server.


[03:41:49] + Attempting to send results [March 18 03:41:49 UTC]
[03:43:17] - Couldn't send HTTP request to server
[03:43:17] + Could not connect to Work Server (results)
[03:43:17]     (128.143.231.202:8080)
[03:43:17] + Retrying using alternative port
[03:44:40] - Couldn't send HTTP request to server
[03:44:40] + Could not connect to Work Server (results)
[03:44:40]     (128.143.231.202:80)
[03:44:40]   Could not transmit unit 01 to Collection server; keeping in queue.
[03:44:40] Project: 7504 (Run 8, Clone 25, Gen 112)


[03:44:40] + Attempting to send results [March 18 03:44:40 UTC]
[03:45:55] - Couldn't send HTTP request to server
[03:45:55] + Could not connect to Work Server (results)
[03:45:55]     (128.143.199.97:8080)
[03:45:55] + Retrying using alternative port
[03:46:58] - Couldn't send HTTP request to server
[03:46:58] + Could not connect to Work Server (results)
[03:46:58]     (128.143.199.97:80)
[03:46:58] - Error: Could not transmit unit 02 (completed March 16) to work server.


[03:46:58] + Attempting to send results [March 18 03:46:58 UTC]
[03:48:45] - Couldn't send HTTP request to server
[03:48:45] + Could not connect to Work Server (results)
[03:48:45]     (128.143.231.202:8080)
[03:48:45] + Retrying using alternative port
[03:50:22] - Couldn't send HTTP request to server
[03:50:22] + Could not connect to Work Server (results)
[03:50:22]     (128.143.231.202:80)
[03:50:22]   Could not transmit unit 02 to Collection server; keeping in queue.
[03:50:22] Project: 7506 (Run 0, Clone 195, Gen 124)


[03:50:22] + Attempting to send results [March 18 03:50:22 UTC]
[03:52:06] - Couldn't send HTTP request to server
[03:52:06] + Could not connect to Work Server (results)
[03:52:06]     (128.143.199.97:8080)
[03:52:06] + Retrying using alternative port
[03:53:29] - Couldn't send HTTP request to server
[03:53:29] + Could not connect to Work Server (results)
[03:53:29]     (128.143.199.97:80)
[03:53:29] - Error: Could not transmit unit 03 (completed March 16) to work server.


[03:53:29] + Attempting to send results [March 18 03:53:29 UTC]
[03:54:36] - Couldn't send HTTP request to server
[03:54:36] + Could not connect to Work Server (results)
[03:54:36]     (128.143.231.202:8080)
[03:54:36] + Retrying using alternative port
[03:56:44] - Couldn't send HTTP request to server
[03:56:44] + Could not connect to Work Server (results)
[03:56:44]     (128.143.231.202:80)
[03:56:44]   Could not transmit unit 03 to Collection server; keeping in queue.
[03:56:44] Project: 7507 (Run 0, Clone 48, Gen 166)


[03:56:44] + Attempting to send results [March 18 03:56:44 UTC]
[03:57:48] - Couldn't send HTTP request to server
[03:57:48] + Could not connect to Work Server (results)
[03:57:48]     (128.143.199.97:8080)
[03:57:48] + Retrying using alternative port
[03:58:55] - Couldn't send HTTP request to server
[03:58:55] + Could not connect to Work Server (results)
[03:58:55]     (128.143.199.97:80)
[03:58:55] - Error: Could not transmit unit 04 (completed March 16) to work server.


[03:58:55] + Attempting to send results [March 18 03:58:55 UTC]
[04:01:04] - Couldn't send HTTP request to server
[04:01:04] + Could not connect to Work Server (results)
[04:01:04]     (128.143.231.202:8080)
[04:01:04] + Retrying using alternative port
bruce
Posts: 20822
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 128.143.199.97 & 128.143.231.202 (unable to submit WU's)

Post by bruce »

Each of those servers is accepting between 100 and 150 WUs per hour. I'm not sure why yours are not uploading.
PantherX
Site Moderator
Posts: 6986
Joined: Wed Dec 23, 2009 9:33 am
Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB

Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400
Location: Land Of The Long White Cloud
Contact:

Re: 128.143.199.97 & 128.143.231.202 (unable to submit WU's)

Post by PantherX »

Welcome to the F@H Forum drexlerderek,

Can you please read this thread and see if you can solve your issue -> viewtopic.php?f=18&t=17794
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time

Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
drexlerderek
Posts: 3
Joined: Sun Mar 18, 2012 3:52 am

Re: 128.143.199.97 & 128.143.231.202 (unable to submit WU's)

Post by drexlerderek »

Thanks for the welcome.

I looked at the linked thread, but I'm not sure how to add the verbosity flag to the diskless folding client, as there doesn't seem to be any option in the config file. Perhaps I'm missing something, though this is the same setup I'm using on my other machines and they upload to the same servers without a problem. I used to run the folding@home windows console client on the computer until the other day and never had a problem.

Code: Select all

DEFAULT fold
DEFAULT64 fold64
TIMEOUT 150
PROMPT 1
DISPLAY fold.txt

LABEL fold
	KERNEL kernel32
	APPEND initrd=initrd USER=drexlerderek TEAM=86565 PASSKEY=xxxx BIG=yes MEM= ADVMETHODS=yes SMPCPUS=8 BACKUP=3 REBOOT=enabled INSTALL=no BENCHMARK=no BLANK=0 SAMBA=2 GROUP=DISKLESS PROXY_HOST= PROXY_PORT= PROXY_USER= PROXY_PASS= INTF= IP= MASK= GATEWAY= DNS= TFTP= SHELL=yes

LABEL fold64
        KERNEL kernel64
        APPEND initrd=initrd USER=drexlerderek TEAM=86565 PASSKEY=xxxx BIG=yes MEM= ADVMETHODS=yes SMPCPUS=8 BACKUP=3 REBOOT=enabled INSTALL=no BENCHMARK=no BLANK=0 SAMBA=2 GROUP=DISKLESS PROXY_HOST= PROXY_PORT= PROXY_USER= PROXY_PASS= INTF= IP= MASK= GATEWAY= DNS= TFTP= SHELL=yes

LABEL benchmark
	KERNEL kernel32
	APPEND initrd=initrd USER=notfred2630 TEAM=2630 PASSKEY= BIG=yes MEM= ADVMETHODS=yes SMPCPUS=4 BACKUP=15 REBOOT=enabled INSTALL=yes BENCHMARK=yes BLANK=0 SAMBA=2 GROUP=DISKLESS PROXY_HOST= PROXY_PORT= PROXY_USER= PROXY_PASS= INTF= IP= MASK= GATEWAY= DNS= TFTP= SHELL=yes

LABEL benchmark64
	KERNEL kernel64
	APPEND initrd=initrd USER=notfred2630 TEAM=2630 PASSKEY= BIG=yes MEM= ADVMETHODS=yes SMPCPUS=4 BACKUP=15 REBOOT=enabled INSTALL=yes BENCHMARK=yes BLANK=0 SAMBA=2 GROUP=DISKLESS PROXY_HOST= PROXY_PORT= PROXY_USER= PROXY_PASS= INTF= IP= MASK= GATEWAY= DNS= TFTP= SHELL=yes
bruce
Posts: 20822
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 128.143.199.97 & 128.143.231.202 (unable to submit WU's)

Post by bruce »

This forum can help you if there's a problem with the Stanford servers or the clients that you download from Stanford. The notfred client is written and supported by a 3rd party (known as notfred). The best way to get help with the notfred client is to ask at his forum: http://techreport.com/
drexlerderek
Posts: 3
Joined: Sun Mar 18, 2012 3:52 am

Re: 128.143.199.97 & 128.143.231.202 (unable to submit WU's)

Post by drexlerderek »

Will do, Thanks!
Post Reply