Page 1 of 1

169.230.26.30

Posted: Tue Oct 13, 2009 10:09 pm
by autogrog
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.

Re: 169.230.26.30

Posted: Wed Oct 14, 2009 3:48 am
by Leoslocks
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

Re: 169.230.26.30

Posted: Fri Oct 16, 2009 4:59 pm
by Tynat
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".

Re: 169.230.26.30

Posted: Fri Oct 16, 2009 5:46 pm
by Pette Broad
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

Re: 169.230.26.30

Posted: Fri Oct 16, 2009 6:11 pm
by toTOW

Re: 169.230.26.30

Posted: Fri Oct 16, 2009 6:21 pm
by Pette Broad
O.K, That's good news :)

Pete

Re: 169.230.26.30

Posted: Fri Oct 16, 2009 10:07 pm
by codysluder
I can open http://169.230.26.30:8080/ but not http://169.230.26.30:80/
Does that agree with your observations?

Re: 169.230.26.30

Posted: Fri Oct 16, 2009 10:11 pm
by toTOW
Yes, this server doesn't seem to be able to assign on port 80 ...

But standard 8080 port is working.

Re: 169.230.26.30

Posted: Fri Dec 18, 2009 1:35 am
by AgrFan
169.230.26.30 is unavailable ...

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.
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 :)

Re: 169.230.26.30

Posted: Mon Mar 15, 2010 1:30 am
by AgrFan
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

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.

Re: 169.230.26.30

Posted: Mon Mar 15, 2010 2:08 am
by codysluder
AgrFan wrote:169.230.26.30 is in REJECT status.

Most likely this will remain off-line until tomorrow morning.

Re: 169.230.26.30

Posted: Mon Mar 15, 2010 3:01 am
by RAH
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.

Re: 169.230.26.30

Posted: Mon Mar 15, 2010 7:41 am
by Teddy
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

Re: 169.230.26.30

Posted: Mon Mar 15, 2010 6:11 pm
by Pette Broad
Looks like it was fixed and I got/sent some work. Didn't last for long though, its gone into reject mode again..


Pete