Can't connect to 171.65.103.100

Moderators: Site Moderators, FAHC Science Team

Post Reply
diegonix
Posts: 4
Joined: Wed Apr 07, 2010 12:52 pm

Can't connect to 171.65.103.100

Post by diegonix »

Hey folks,

I can't send my results to this specific server:

Tests:
[root@localhost ~]# telnet 171.65.103.100 8080
Trying 171.65.103.100...
telnet: connect to address 171.65.103.100: Connection timed out
telnet: Unable to connect to remote host: Connection timed out


[root@localhost ~]# tracert -n -I 171.65.103.100
traceroute to 171.65.103.100 (171.65.103.100), 30 hops max, 40 byte packets
1 189.115.178.145 0.665 ms 0.759 ms 0.968 ms
2 189.115.179.229 1.473 ms 1.609 ms 1.902 ms
3 189.59.248.193 1.068 ms 1.063 ms 1.050 ms
4 64.208.26.5 1.834 ms 1.870 ms 1.862 ms
5 154.54.12.69 109.348 ms 109.342 ms 109.400 ms
6 154.54.28.245 109.516 ms 108.920 ms 108.943 ms
7 154.54.24.197 140.344 ms 140.152 ms 140.203 ms
8 154.54.0.253 168.518 ms 168.859 ms 168.721 ms
9 154.54.3.134 185.883 ms 185.835 ms 186.142 ms
10 154.54.28.82 182.996 ms * *
11 66.250.7.138 182.569 ms 182.509 ms 182.782 ms
12 68.65.168.33 183.331 ms 183.093 ms 182.885 ms
13 * * *
14 * * *
...


FAHlog:

[12:02:22] + Attempting to send results [April 7 12:02:22 UTC]
[12:02:43] - Couldn't send HTTP request to server
[12:02:43] + Could not connect to Work Server (results)
[12:02:43] (171.65.103.100:8080)
[12:02:43] + Retrying using alternative port
[12:03:04] - Couldn't send HTTP request to server
[12:03:04] + Could not connect to Work Server (results)
[12:03:04] (171.65.103.100:80)
[12:03:04] Could not transmit unit 08 to Collection server; keeping in queue.
[12:03:04] Project: 4606 (Run 7, Clone 96, Gen 87)
[12:03:04] - Read packet limit of 540015616... Set to 524286976.


[12:03:04] + Attempting to send results [April 7 12:03:04 UTC]
[12:03:08] - Unknown packet returned from server, expected ACK for results
[12:03:08] - Error: Could not transmit unit 09 (completed April 7) to work server.
[12:03:08] - Read packet limit of 540015616... Set to 524286976.


[12:03:08] + Attempting to send results [April 7 12:03:08 UTC]
[12:03:29] - Couldn't send HTTP request to server
[12:03:29] + Could not connect to Work Server (results)
[12:03:29] (171.65.103.100:8080)
[12:03:29] + Retrying using alternative port
[12:03:51] - Couldn't send HTTP request to server
[12:03:51] + Could not connect to Work Server (results)
[12:03:51] (171.65.103.100:80)
[12:03:51] Could not transmit unit 09 to Collection server; keeping in queue.
toTOW
Site Moderator
Posts: 6349
Joined: Sun Dec 02, 2007 10:38 am
Location: Bordeaux, France
Contact:

Re: Can't connect to 171.65.103.100

Post by toTOW »

Code: Select all

171.65.103.100	-	VSPMF33	-	CS 1	DOWN
But it's a collection server ... so you have to look earlier in your log to find the work server that doesn't answer ...
Image

Folding@Home beta tester since 2002. Folding Forum moderator since July 2008.
diegonix
Posts: 4
Joined: Wed Apr 07, 2010 12:52 pm

Re: Can't connect to 171.65.103.100

Post by diegonix »

Correct, I can't send my finished WUs to the collection server.
The server is down since march 25, what will happen with my finished WUs?
toTOW
Site Moderator
Posts: 6349
Joined: Sun Dec 02, 2007 10:38 am
Location: Bordeaux, France
Contact:

Re: Can't connect to 171.65.103.100

Post by toTOW »

So what is the server (work server) that issued the WU ?
Image

Folding@Home beta tester since 2002. Folding Forum moderator since July 2008.
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Can't connect to 171.65.103.100

Post by bruce »

diegonix wrote:Correct, I can't send my finished WUs to the collection server.
The server is down since march 25, what will happen with my finished WUs?
Welcome to the foldingforum.org, diegonix.

The primary upload path should always be to the Work Server. Since you didn't mention that server, it's difficult to help you. What we're trying to tell you is that the Collection Server is a backup path which is only needed in case the primary path fails.

Please check the Server Status page before you try telnet and/or opening the default web page.
diegonix
Posts: 4
Joined: Wed Apr 07, 2010 12:52 pm

Re: Can't connect to 171.65.103.100

Post by diegonix »

Hey Bruce, thank you!
I understand the point and sorry for the dummie question, but where do I find what Work Server I'm using?
diegonix
Posts: 4
Joined: Wed Apr 07, 2010 12:52 pm

Re: Can't connect to 171.65.103.100

Post by diegonix »

Sorry, I forgot to set verbosity!

Here is the log with verbosity 9:

Code: Select all

[20:27:39] + Attempting to send results [April 7 20:27:39 UTC]
[20:27:39] - Reading file work/wuresults_00.dat from core
[20:27:39]   (Read 213884 bytes from disk)
[20:27:39] Connecting to http://169.230.26.30:8080/
[20:27:39] Working on queue slot 02 [April 7 20:27:39 UTC]
[20:27:39] + Working ...
[20:27:39] - Calling '.\FahCore_78.exe -dir work/ -suffix 02 -checkpoint 15 -service -verbose -lifeline 4632 -version 623'

[20:27:39] 
[20:27:39] *------------------------------*
[20:27:39] Folding@Home Gromacs Core
[20:27:39] Version 1.90 (March 8, 2006)
[20:27:39] 
[20:27:39] Preparing to commence simulation
[20:27:39] - Looking at optimizations...
[20:27:39] - Files status OK
[20:27:42] - Expanded 2991984 -> 15120201 (decompressed 505.3 percent)
[20:27:42] 
[20:27:42] Project: 2485 (Run 266, Clone 18, Gen 17)
[20:27:42] 
[20:27:42] Assembly optimizations on if available.
[20:27:42] Entering M.D.
[20:27:46] Posted data.
[20:27:46] Initial: 7254; - Uploaded at ~29 kB/s
[20:27:46] - Averaged speed for that direction ~40 kB/s
[20:27:46] - Unknown packet returned from server, expected ACK for results
[20:27:46] - Error: Could not transmit unit 00 (completed April 7) to work server.
[20:27:46] - 8 failed uploads of this unit.
[20:27:46] - Read packet limit of 540015616... Set to 524286976.


[20:27:46] + Attempting to send results [April 7 20:27:46 UTC]
[20:27:46] - Reading file work/wuresults_00.dat from core
[20:27:46]   (Read 213884 bytes from disk)
[20:27:46] Connecting to http://171.65.103.100:8080/
[20:28:03] (Starting from checkpoint)
[20:28:03] Protein: system
[20:28:03] 
[20:28:03] Writing local files
[20:28:03] Completed 48859 out of 250000 steps  (20%)
[20:28:05] Extra SSE boost OK.
[20:28:07] - Couldn't send HTTP request to server
[20:28:07] + Could not connect to Work Server (results)
[20:28:07]     (171.65.103.100:8080)
[20:28:07] + Retrying using alternative port
[20:28:07] Connecting to http://171.65.103.100:80/
endrik
Posts: 34
Joined: Mon Dec 10, 2007 10:41 pm
Location: Wroclaw, Poland
Contact:

Re: Can't connect to 171.65.103.100

Post by endrik »

One answer, in FAHlog.txt file (take in look in your FAH folder). On the beginning of current Wu you willl find something like
[10:45:16] + Attempting to get work packet
[10:45:16] - Connecting to assignment server
[10:45:17] - Successful: assigned to (171.64.65.111)

If it was some older Wu, try FAHlog-prev.txt

Or simply visit http://fah-web.stanford.edu/psummary.html and under your Wu's number you'll find the server responsible.
yours,
endrik

*Bookworms will rule the world
(after we finish the background reading).
Post Reply