Page 1 of 1

171.67.108.11 and 25

Posted: Wed Dec 23, 2009 5:34 pm
by theo343
[14:43:16] + Attempting to send results [December 23 14:43:16 UTC]
[14:43:17] - Couldn't send HTTP request to server
[14:43:17] + Could not connect to Work Server (results)
[14:43:17] (171.67.108.11:8080)
[14:43:17] + Retrying using alternative port
[14:43:19] - Couldn't send HTTP request to server
[14:43:19] + Could not connect to Work Server (results)
[14:43:19] (171.67.108.11:80)
[14:43:19] - Error: Could not transmit unit 08 (completed December 23) to work server.
[14:43:19] - Read packet limit of 540015616... Set to 524286976.

[14:43:19] + Attempting to send results [December 23 14:43:19 UTC]
[14:43:21] - Couldn't send HTTP request to server
[14:43:21] + Could not connect to Work Server (results)
[14:43:21] (171.67.108.25:8080)
[14:43:21] + Retrying using alternative port
[14:43:23] - Couldn't send HTTP request to server
[14:43:23] + Could not connect to Work Server (results)
[14:43:23] (171.67.108.25:80)
[14:43:23] Could not transmit unit 08 to Collection server; keeping in queue.

Re: 171.67.108.11 and 25

Posted: Wed Dec 23, 2009 7:03 pm
by bruce
I can open all four of http://171.67.108.11 and http://171.67.108.11:8080 and http://171.67.108.25:8080/ and http://171.67.108.25/from here.

171.67.108.11 is rather busy, but it seems to be working normally. Go on to running the next WU and the client will keep trying until it gets through.

Re: 171.67.108.11 and 25

Posted: Wed Dec 23, 2009 9:04 pm
by theo343
:)

Re: 171.67.108.11 and 25

Posted: Thu Dec 24, 2009 12:06 am
by Cajun_Don
I have been having the same problem with the last 5 or more wu's uploading, since yesterday, but they do eventually upload in time before the preferred deadline.

Happy Holidays everyone

Re: 171.67.108.11 and 25

Posted: Tue Dec 29, 2009 9:48 pm
by tobor
I've got 5 clients not sending.... 171.67.108.25-11

Re: 171.67.108.11 and 25

Posted: Wed Dec 30, 2009 4:36 am
by bruce
171.67.108.25 is indeed not accepting connections, but it's a collection server which is only called into service when the primary work server has problems. I will report it, of course, but it's a secondary consideration.

The primary consideration is server 171.67.108.11. That server was down from about 11:00 to about 13:45 PST and you posted at 13:48 PST so I'll assume that the problem was fixed about the same time you posted unless I hear from you again. It seems to have been accepting a lot of results since then, as well as distributing a lot of new WUs.

Re: 171.67.108.11 and 25

Posted: Mon Jan 18, 2010 7:50 pm
by bollix47
171.67.108.11 in REJECT