169.230.26.30
Moderators: Site Moderators, FAHC Science Team
169.230.26.30
This server is reported as being up and working, but will not download WU's, also ping attempts time out. This has been happening all day:
Server status:
169.230.26.30 classic fahserver1 vvoelz full Accepting 0.03 4 1 109 686 130 3 96.42 243
Log file:
[21:55:52] + Attempting to get work packet
[21:55:52] - Connecting to assignment server
[21:55:53] - Successful: assigned to (169.230.26.30).
[21:55:53] + News From Folding@Home: Welcome to Folding@Home
[21:55:53] Loaded queue successfully.
[21:55:53] + Could not connect to Work Server
[21:55:53] - Error: Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
Server status:
169.230.26.30 classic fahserver1 vvoelz full Accepting 0.03 4 1 109 686 130 3 96.42 243
Log file:
[21:55:52] + Attempting to get work packet
[21:55:52] - Connecting to assignment server
[21:55:53] - Successful: assigned to (169.230.26.30).
[21:55:53] + News From Folding@Home: Welcome to Folding@Home
[21:55:53] Loaded queue successfully.
[21:55:53] + Could not connect to Work Server
[21:55:53] - Error: Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
-
- Posts: 120
- Joined: Fri Jan 25, 2008 3:20 am
- Hardware configuration: Q6600 | P35-DQ6 | Crucial 2 x 1 GB ram | VisionTek 3870
GPU2 Version 6.20| CPU three 6.20 Clients
Re: 169.230.26.30
I have had an issue with this server also. I was able to get work by Stopping the client and restarting it. Let it run through 6 failed attempts and then stop the client and restart the client.
If your client is run as a service, run a command prompt as Administrator (Vista) to start services.msc
I don't know what the issue is with the server not responding to ping or IP
If your client is run as a service, run a command prompt as Administrator (Vista) to start services.msc
I don't know what the issue is with the server not responding to ping or IP
Re: 169.230.26.30
Looks like it's acting up again. So far 12 failed attempts before restart of client, 6 so far after restart. Firefox is reporting that the "connection to the server was reset while the page was loading".
All clients stopped due to Stanford's upcoming September 2011 decision
-
- Posts: 128
- Joined: Mon Dec 03, 2007 9:38 pm
- Hardware configuration: CPU folding on only one machine a laptop
GPU Hardware..
3 x 460
1 X 260
4 X 250
+ 1 X 9800GT (3 days a week) - Location: Chester U.K
Re: 169.230.26.30
Yes, I'm getting pretty fed up with machines sitting there for hours trying to get work from troublesome servers. This has been going on for weeks and weeks. I'm in the seventh year with this project but I'm gone soon unless something is done.
Pete
Pete
-
- Posts: 128
- Joined: Mon Dec 03, 2007 9:38 pm
- Hardware configuration: CPU folding on only one machine a laptop
GPU Hardware..
3 x 460
1 X 260
4 X 250
+ 1 X 9800GT (3 days a week) - Location: Chester U.K
Re: 169.230.26.30
O.K, That's good news
Pete
Pete
-
- Posts: 1024
- Joined: Sun Dec 02, 2007 12:43 pm
Re: 169.230.26.30
I can open http://169.230.26.30:8080/ but not http://169.230.26.30:80/
Does that agree with your observations?
Does that agree with your observations?
-
- Site Moderator
- Posts: 6349
- Joined: Sun Dec 02, 2007 10:38 am
- Location: Bordeaux, France
- Contact:
Re: 169.230.26.30
Yes, this server doesn't seem to be able to assign on port 80 ...
But standard 8080 port is working.
But standard 8080 port is working.
Re: 169.230.26.30
169.230.26.30 is unavailable ...
169.230.26.30 classic fahserver1 vvoelz full Reject 1.40 9 0 35 686 128 21 147.3 84566 84566 348685 22 - - - 1534
Edit: I just pulled new work from this server, all is well
Code: Select all
[01:20:24] - Preparing to get new work unit...
[01:20:24] + Attempting to get work packet
[01:20:24] - Connecting to assignment server
[01:20:24] - Successful: assigned to (0.0.0.0).
[01:20:24] + News From Folding@Home: Welcome to Folding@Home
[01:20:24] Work Unit has an invalid address.
[01:20:24] - Error: Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[01:20:41] + Attempting to get work packet
[01:20:41] - Connecting to assignment server
[01:20:42] - Successful: assigned to (0.0.0.0).
[01:20:42] + News From Folding@Home: Welcome to Folding@Home
[01:20:42] Work Unit has an invalid address.
[01:20:42] - Error: Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[01:20:57] + Attempting to get work packet
[01:20:57] - Connecting to assignment server
[01:20:58] - Successful: assigned to (0.0.0.0).
[01:20:58] + News From Folding@Home: Welcome to Folding@Home
[01:20:58] Work Unit has an invalid address.
[01:20:58] - Error: Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[01:21:25] + Attempting to get work packet
[01:21:25] - Connecting to assignment server
[01:21:25] - Successful: assigned to (0.0.0.0).
[01:21:25] + News From Folding@Home: Welcome to Folding@Home
[01:21:25] Work Unit has an invalid address.
[01:21:25] - Error: Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[01:22:20] + Attempting to get work packet
[01:22:20] - Connecting to assignment server
[01:22:21] - Successful: assigned to (0.0.0.0).
[01:22:21] + News From Folding@Home: Welcome to Folding@Home
[01:22:21] Work Unit has an invalid address.
[01:22:21] - Error: Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[01:23:52] + Attempting to get work packet
[01:23:52] - Connecting to assignment server
[01:23:52] - Successful: assigned to (0.0.0.0).
[01:23:52] + News From Folding@Home: Welcome to Folding@Home
[01:23:52] Work Unit has an invalid address.
[01:23:52] - Error: Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[01:26:40] + Attempting to get work packet
[01:26:40] - Connecting to assignment server
[01:26:41] - Successful: assigned to (0.0.0.0).
[01:26:41] + News From Folding@Home: Welcome to Folding@Home
[01:26:41] Work Unit has an invalid address.
[01:26:41] - Error: Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
Edit: I just pulled new work from this server, all is well
Re: 169.230.26.30
169.230.26.30 is in REJECT status.
169.230.26.30 classic fahserver1 vvoelz full Reject 0.76 0 0 0 686 122 11 21.86 24743 24550 197991 - - - - 0
169.230.26.30 classic fahserver1 vvoelz full Reject 0.76 0 0 0 686 122 11 21.86 24743 24550 197991 - - - - 0
Code: Select all
[22:11:23] Folding@home Core Shutdown: FINISHED_UNIT
[22:11:26] CoreStatus = 64 (100)
[22:11:26] Sending work to server
[22:11:26] Project: 4613 (Run 37, Clone 102, Gen 28)
[22:11:26] + Attempting to send results [March 14 22:11:26 UTC]
[22:11:27] - Couldn't send HTTP request to server
[22:11:27] + Could not connect to Work Server (results)
[22:11:27] (169.230.26.30:8080)
[22:11:27] + Retrying using alternative port
[22:11:28] - Couldn't send HTTP request to server
[22:11:28] + Could not connect to Work Server (results)
[22:11:28] (169.230.26.30:80)
[22:11:28] - Error: Could not transmit unit 02 (completed March 14) to work server.
[22:11:28] Keeping unit 02 in queue.
[22:11:28] Project: 4613 (Run 37, Clone 102, Gen 28)
[22:11:28] + Attempting to send results [March 14 22:11:28 UTC]
[22:11:29] - Couldn't send HTTP request to server
[22:11:29] + Could not connect to Work Server (results)
[22:11:29] (169.230.26.30:8080)
[22:11:29] + Retrying using alternative port
[22:11:30] - Couldn't send HTTP request to server
[22:11:30] + Could not connect to Work Server (results)
[22:11:30] (169.230.26.30:80)
[22:11:30] - Error: Could not transmit unit 02 (completed March 14) to work server.
[22:11:30] + Attempting to send results [March 14 22:11:30 UTC]
[22:11:51] - Couldn't send HTTP request to server
[22:11:51] + Could not connect to Work Server (results)
[22:11:51] (171.65.103.100:8080)
[22:11:51] + Retrying using alternative port
[22:12:12] - Couldn't send HTTP request to server
[22:12:12] + Could not connect to Work Server (results)
[22:12:12] (171.65.103.100:80)
[22:12:12] Could not transmit unit 02 to Collection server; keeping in queue.
-
- Posts: 1024
- Joined: Sun Dec 02, 2007 12:43 pm
Re: 169.230.26.30
AgrFan wrote:169.230.26.30 is in REJECT status.
Most likely this will remain off-line until tomorrow morning.
-
- Posts: 131
- Joined: Sun Dec 02, 2007 6:29 am
- Hardware configuration: 1. C2Q 8200@2880 / W7Pro64 / SMP2 / 2 GPU - GTS250/GTS450
2. C2D 6300@3600 / XPsp3 / SMP2 / 1 GPU - GT240 - Location: Florida
Re: 169.230.26.30
Yep!
The main problem is the dumb AS keeps assigning it.
So you can't get any work at all.
Restarted several times, removed advmethods, restarted several times, same old thing.
Great system.
The main problem is the dumb AS keeps assigning it.
So you can't get any work at all.
Restarted several times, removed advmethods, restarted several times, same old thing.
Great system.
Re: 169.230.26.30
I guess this server is less important than other ones as it would explain why I have at least 4 units that cannot return work to this server, the CS is not interested either & no surprises there, I removed advmethods & got at least one work unit, lucky me or not?
Teddy
Teddy
-
- Posts: 128
- Joined: Mon Dec 03, 2007 9:38 pm
- Hardware configuration: CPU folding on only one machine a laptop
GPU Hardware..
3 x 460
1 X 260
4 X 250
+ 1 X 9800GT (3 days a week) - Location: Chester U.K
Re: 169.230.26.30
Looks like it was fixed and I got/sent some work. Didn't last for long though, its gone into reject mode again..
Pete
Pete