171.67.108.11 gone into REJECT status
Moderators: Site Moderators, FAHC Science Team
Re: 171.67.108.11 gone into REJECT status
Back into REJECT status again...
-
- Pande Group Member
- Posts: 2058
- Joined: Fri Nov 30, 2007 6:25 am
- Location: Stanford
Re: 171.67.108.11 gone into REJECT status
We've been doing maintenance on this server, so it's been up and down this morning/late afternoon. It's up now and we're done with our maintenance.
Prof. Vijay Pande, PhD
Departments of Chemistry, Structural Biology, and Computer Science
Chair, Biophysics
Director, Folding@home Distributed Computing Project
Stanford University
Departments of Chemistry, Structural Biology, and Computer Science
Chair, Biophysics
Director, Folding@home Distributed Computing Project
Stanford University
Re: 171.67.108.11 gone into REJECT status
Seems like its out again
Also everything else Stanford wise seems to be out as well (excluding this forum of course)
Also everything else Stanford wise seems to be out as well (excluding this forum of course)
-
- Site Moderator
- Posts: 6349
- Joined: Sun Dec 02, 2007 10:38 am
- Location: Bordeaux, France
- Contact:
Re: 171.67.108.11 gone into REJECT status
This forum is not hosted on Stanford network, but at a private hosting company.
By the way, I can access to FAH main site and stats ... so I don't think it's down ... that might be an issue on your end, or at your ISP end.
By the way, I can access to FAH main site and stats ... so I don't think it's down ... that might be an issue on your end, or at your ISP end.
Re: 171.67.108.11 gone into REJECT status
Hmm just tried going through Hide My Ass proxy and everything loads
Stupid ISP what they up to? got machines sat here doing nothing now
EDIT: Seems to be ok now, all finished wu's uploaded and new ones downloaded
Stupid ISP
Stupid ISP what they up to? got machines sat here doing nothing now
EDIT: Seems to be ok now, all finished wu's uploaded and new ones downloaded
Stupid ISP
Re: 171.67.108.11 gone into REJECT status
& back into REJECT again...
Teddy
Teddy
-
- Posts: 50
- Joined: Thu Oct 30, 2008 2:29 pm
- Location: Spijkenisse, The Netherlands
Re: 171.67.108.11 gone into REJECT status
The same problem here.
Code: Select all
[09:42:51] + Attempting to send results [February 3 09:42:51 UTC]
[09:42:53] - Couldn't send HTTP request to server
[09:42:53] + Could not connect to Work Server (results)
[09:42:53] (171.67.108.11:8080)
[09:42:53] + Retrying using alternative port
[09:42:54] - Couldn't send HTTP request to server
[09:42:54] + Could not connect to Work Server (results)
[09:42:54] (171.67.108.11:80)
[09:42:54] - Error: Could not transmit unit 02 (completed February 3) to work server.
[09:42:54] - Read packet limit of 540015616... Set to 524286976.
[09:42:54] + Attempting to send results [February 3 09:42:54 UTC]
[09:43:35] - Couldn't send HTTP request to server
[09:43:35] + Could not connect to Work Server (results)
[09:43:35] (171.67.108.25:8080)
[09:43:35] + Retrying using alternative port
[09:44:11] - Couldn't send HTTP request to server
[09:44:11] + Could not connect to Work Server (results)
[09:44:11] (171.67.108.25:80)
[09:44:11] Could not transmit unit 02 to Collection server; keeping in queue.
[09:44:11] + Working...
-
- Posts: 50
- Joined: Thu Oct 30, 2008 2:29 pm
- Location: Spijkenisse, The Netherlands
Re: 171.67.108.11 gone into REJECT status
Problem solved here. This was notice after sending in new results. Receive new work from 171.67.108.11.
Re: 171.67.108.11 gone into REJECT status
Code: Select all
Mon Feb 9 14:15:20 PST 2009 171.67.108.11 GPU vsp07v vvoelz full Reject 0.51 31 0 66
-
- Site Moderator
- Posts: 6349
- Joined: Sun Dec 02, 2007 10:38 am
- Location: Bordeaux, France
- Contact:
Re: 171.67.108.11 gone into REJECT status
It looks like it's back :
Code: Select all
Mon Feb 9 16:45:20 PST 2009 171.67.108.11 GPU vsp07v vvoelz full Accepting
Re: 171.67.108.11 gone into REJECT status
& its back into REJECT again for the last hr or so...
Teddy
Teddy
Re: 171.67.108.11 gone into REJECT status
Checked this morning and it seems that this server is in reject status
Code: Select all
[07:57:50] + Attempting to send results [February 22 07:57:50 UTC]
[07:57:51] - Couldn't send HTTP request to server
[07:57:51] + Could not connect to Work Server (results)
[07:57:51] (171.67.108.11:8080)
[07:57:51] + Retrying using alternative port
[07:57:52] - Couldn't send HTTP request to server
[07:57:52] + Could not connect to Work Server (results)
[07:57:52] (171.67.108.11:80)
[07:57:52] - Error: Could not transmit unit 06 (completed February 22) to work server.
[07:57:52] Keeping unit 06 in queue.
[07:57:52] Project: 5771 (Run 3, Clone 52, Gen 172)
[07:57:52] + Attempting to send results [February 22 07:57:52 UTC]
[07:57:53] - Couldn't send HTTP request to server
[07:57:53] + Could not connect to Work Server (results)
[07:57:53] (171.67.108.11:8080)
[07:57:53] + Retrying using alternative port
[07:57:54] - Couldn't send HTTP request to server
[07:57:54] + Could not connect to Work Server (results)
[07:57:54] (171.67.108.11:80)
[07:57:54] - Error: Could not transmit unit 06 (completed February 22) to work server.
[07:57:54] + Attempting to send results [February 22 07:57:54 UTC]
[07:57:55] - Couldn't send HTTP request to server
[07:57:55] + Could not connect to Work Server (results)
[07:57:55] (171.67.108.25:8080)
[07:57:55] + Retrying using alternative port
[08:01:28] - Couldn't send HTTP request to server
[08:01:28] + Could not connect to Work Server (results)
[08:01:28] (171.67.108.25:80)
[08:01:28] Could not transmit unit 06 to Collection server; keeping in queue.
[08:01:28] - Preparing to get new work unit...
[08:01:28] + Attempting to get work packet
[08:01:28] - Connecting to assignment server
[08:01:28] - Successful: assigned to (171.64.122.70).
[08:01:28] + News From Folding@Home: GPU folding beta
[08:01:28] Loaded queue successfully.
[08:01:30] Project: 5771 (Run 3, Clone 52, Gen 172)
[08:01:30] + Attempting to send results [February 22 08:01:30 UTC]
[08:01:31] - Couldn't send HTTP request to server
[08:01:31] + Could not connect to Work Server (results)
[08:01:31] (171.67.108.11:8080)
[08:01:31] + Retrying using alternative port
[08:01:32] - Couldn't send HTTP request to server
[08:01:32] + Could not connect to Work Server (results)
[08:01:32] (171.67.108.11:80)
[08:01:32] - Error: Could not transmit unit 06 (completed February 22) to work server.
[08:01:32] + Attempting to send results [February 22 08:01:32 UTC]
[08:05:05] - Couldn't send HTTP request to server
[08:05:05] + Could not connect to Work Server (results)
[08:05:05] (171.67.108.25:8080)
[08:05:05] + Retrying using alternative port
[08:08:38] - Couldn't send HTTP request to server
[08:08:38] + Could not connect to Work Server (results)
[08:08:38] (171.67.108.25:80)
[08:08:38] Could not transmit unit 06 to Collection server; keeping in queue.
[08:08:38] + Closed connections
[08:08:38]
[08:08:38] + Processing work unit
[08:08:38] Core required: FahCore_14.exe
[08:08:38] Core not found.
[08:08:38] - Core is not present or corrupted.
[08:08:38] - Attempting to download new core...
[08:08:38] + Downloading new core: FahCore_14.exe
[08:08:38] - Error: HTTP GET returned error code 404
[08:08:38] + Error: Could not download core
[08:08:38] + Core download error (#2), waiting before retry...
[08:08:50] + Downloading new core: FahCore_14.exe
[08:08:51] - Error: HTTP GET returned error code 404
[08:08:51] + Error: Could not download core
[08:08:51] + Core download error (#3), waiting before retry...
[08:09:15] + Downloading new core: FahCore_14.exe
[08:09:16] - Error: HTTP GET returned error code 404
[08:09:16] + Error: Could not download core
[08:09:16] + Core download error (#4), waiting before retry...
[08:09:36] + Downloading new core: FahCore_14.exe
[08:09:37] - Error: HTTP GET returned error code 404
[08:09:37] + Error: Could not download core
[08:09:37] + Core download error (#5), waiting before retry...
[08:10:31] + Downloading new core: FahCore_14.exe
[08:10:31] - Error: HTTP GET returned error code 404
[08:10:31] + Error: Could not download core
[08:10:31] + Core download error (#6), waiting before retry...
[08:11:53] + Downloading new core: FahCore_14.exe
[08:11:53] - Error: HTTP GET returned error code 404
[08:11:53] + Error: Could not download core
[08:11:53] + Core download error (#7), waiting before retry...
[08:14:40] + Downloading new core: FahCore_14.exe
[08:14:40] - Error: HTTP GET returned error code 404
[08:14:40] + Error: Could not download core
[08:14:40] + Core download error (#8), waiting before retry...
[08:20:12] + Downloading new core: FahCore_14.exe
[08:20:13] - Error: HTTP GET returned error code 404
[08:20:13] + Error: Could not download core
[08:20:13] + Core download error (#9), waiting before retry...
[08:31:01] + Downloading new core: FahCore_14.exe
[08:31:01] - Error: HTTP GET returned error code 404
[08:31:01] + Error: Could not download core
[08:31:01] + Core download error (#10), waiting before retry...
[08:52:33] + Downloading new core: FahCore_14.exe
[08:52:33] - Error: HTTP GET returned error code 404
[08:52:33] + Error: Could not download core
[08:52:33] + Core download error (#11), waiting before retry...
[09:35:17] + Downloading new core: FahCore_14.exe
[09:35:17] - Error: HTTP GET returned error code 404
[09:35:17] + Error: Could not download core
[09:35:17] + Core download error (#12), waiting before retry...
[10:23:22] + Downloading new core: FahCore_14.exe
[10:23:22] - Error: HTTP GET returned error code 404
[10:23:22] + Error: Could not download core
[10:23:22] + Core download error (#13), waiting before retry...
[11:04:28] Project: 5771 (Run 3, Clone 52, Gen 172)
[11:04:28] + Attempting to send results [February 22 11:04:28 UTC]
[11:04:30] + Results successfully sent
[11:04:30] Thank you for your contribution to Folding@Home.
[11:04:30] + Number of Units Completed: 1905
[11:11:33] + Downloading new core: FahCore_14.exe
[11:11:33] - Error: HTTP GET returned error code 404
[11:11:33] + Error: Could not download core
[11:11:33] + Core download error (#14), waiting before retry...
[11:59:43] + Downloading new core: FahCore_14.exe
[11:59:44] - Error: HTTP GET returned error code 404
[11:59:44] + Error: Could not download core
[11:59:44] + Core download error (#15), waiting before retry...
[12:47:53] + Downloading new core: FahCore_14.exe
[12:47:53] - Error: HTTP GET returned error code 404
[12:47:53] + Error: Could not download core
[12:47:53] + Core download error (#16), waiting before retry...
[13:35:59] + Downloading new core: FahCore_14.exe
[13:35:59] - Error: HTTP GET returned error code 404
[13:35:59] + Error: Could not download core
[13:35:59] + Core download error (#17), waiting before retry...
[14:24:01] + Downloading new core: FahCore_14.exe
[14:24:07] - Error: HTTP GET returned error code 404
[14:24:07] + Error: Could not download core
[14:24:07] + Core download error (#18), waiting before retry...
-
- Posts: 188
- Joined: Fri Jan 04, 2008 11:02 pm
- Hardware configuration: Hewlett-Packard 1494 Win10 Build 1836
GeForce [MSI] GTX 950
Runs F@H Ver7.6.21
[As of Jan 2021] - Location: England
Re: 171.67.108.11 gone into REJECT status
It seems like any server with 108 in third slot is possible trouble!
I've had, over the months, problems with 13 ,17 and currently 171.67.108.20.
Not being into these things, I can't offer insight, but this range does seem to cause a lot of hassle, needless or otherwise.
One more try with 6.23 which -seems to like this source of WU's, and then back to 5.03 for a simpler life!
I've had, over the months, problems with 13 ,17 and currently 171.67.108.20.
Not being into these things, I can't offer insight, but this range does seem to cause a lot of hassle, needless or otherwise.
One more try with 6.23 which -seems to like this source of WU's, and then back to 5.03 for a simpler life!
Re: 171.67.108.11 gone into REJECT status
The whole network is starting to look a bit more fragile again.
BTW Server 11 has gone back into "REJECT" status.
I knew this was coming as my GPU clients quickly start to bank up unsent units & I just happened to be home from work to notice it
Teddy
BTW Server 11 has gone back into "REJECT" status.
I knew this was coming as my GPU clients quickly start to bank up unsent units & I just happened to be home from work to notice it
Teddy
Re: 171.67.108.11 gone into REJECT status
Looks fine now, accepting, with nearly 200K WU waiting to be distributed, and both CPU and net loads look sane at 2.27 and 26 respectively.