Server 171.64.65.56 with problems ?

[Fernando_Celio]

Gentlemen.

A team mate, nickname fernandol, team 13802 is experimenting problems to get a WU from this server.

He is using Ubuntu 8.04 under VMWare. Until last week he had no problem with this scheme.

Following is what we have done :

Open a browser and digit IP's server receives an OK back.

Send a ping to the server the results look like this :

Code: Select all

PING 171.64.65.56 (171.64.65.56) 56(84) bytes of data.
64 bytes [url]from [/url]171.64.65.56: icmp_seq=1 ttl=128 time=246 ms
64 bytes from 171.64.65.56: icmp_seq=2 ttl=128 time=255 ms
64 bytes from 171.64.65.56: icmp_seq=3 ttl=128 time=245 ms
64 bytes from 171.64.65.56: icmp_seq=4 ttl=128 time=244 ms
64 bytes from 171.64.65.56: icmp_seq=5 ttl=128 time=243 ms
64 bytes from 171.64.65.56: icmp_seq=6 ttl=128 time=244 ms
64 bytes from 171.64.65.56: icmp_seq=7 ttl=128 time=227 ms

--- 171.64.65.56 ping statistics ---
8 packets transmitted, 7 received, 12% packet loss, time 7018ms
rtt min/avg/max/mdev = 227.350/243.726/255.760/7.777 ms

Traceroute results :

Code: Select all

Tracing route to vspg4.Stanford.EDU [171.64.65.56]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  LINUX2 [10.0.0.1]
  2     1 ms    <1 ms    <1 ms  201-27-5-1.dsl.telesp.net.br [201.27.5.1]
  3     *        *        *     Request timed out.
  4    45 ms    72 ms    43 ms  200-207-234-9.dial-up.telesp.net.br [200.207.234.9]
  5    44 ms    45 ms    43 ms  200.204.27.25
  6    46 ms    44 ms    45 ms  200-100-3-233.dsl.telesp.net.br [200.100.3.233]
  7    46 ms    43 ms    45 ms  201-63-253-162.customer.tdatabrasil.net.br[201.63.253.162]
  8   101 ms    45 ms   110 ms  Xe0-2-0-0-grtsanem2.red.telefonica-wholesale.net
 [84.16.11.193]
  9   160 ms   159 ms   160 ms  xe10-2-0-0-grtmiabr5.red.telefonica-wholesale.net [84.16.15.10]
 10   196 ms   191 ms   196 ms  Xe11-0-0-0-grtdaleq1.red.telefonica-wholesale.net [213.140.38.125]
 11   195 ms   195 ms   192 ms  te4-4.ccr02.dfw03.atlas.cogentco.com [154.54.13.225]
 12   196 ms   198 ms   196 ms  te8-2.ccr02.dfw01.atlas.cogentco.com [154.54.6.97]
 13   205 ms   205 ms   204 ms  te3-2.ccr02.mci01.atlas.cogentco.com [154.54.5.170]
 14   241 ms   243 ms   239 ms  te2-4.ccr02.sfo01.atlas.cogentco.com [154.54.24.109]
 15   242 ms   353 ms   239 ms  te9-1.mpd01.sjc04.atlas.cogentco.com [154.54.0.178]
 16   242 ms   245 ms   243 ms  Stanford_University2.demarc.cogentco.com [66.250.7.138]
 17   240 ms   239 ms   239 ms  bbra-rtr.Stanford.EDU [171.64.1.151]
 18     *        *        *     Request timed out.
 19   246 ms   243 ms   243 ms  vspg4.Stanford.EDU [171.64.65.56]

Trace complete.

And, at least the FAHlog :

Code: Select all

--- Opening Log file [June 4 16:53:58 UTC] 


# Linux SMP Console Edition ###################################################
###############################################################################

                       Folding@Home Client Version 6.24beta

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: /home/fernando/fah2
Executable: ./fah6
Arguments: -smp -verbosity 9 -advmethods -forceasm 

[16:53:58] - Ask before connecting: No
[16:53:58] - User name: fernandol (Team 13802)
[16:53:58] - User ID not found locally
[16:53:58] + Requesting User ID from server
[16:53:58] - Getting ID from AS: 
[16:53:58] Connecting to http://assign.stanford.edu:8080/
[16:54:00] Posted data.
[16:54:00] Initial: B473; - Received User ID = 73B47C877D50181D
[16:54:00] - Machine ID: 2
[16:54:00] 
[16:54:00] Work directory not found. Creating...
[16:54:00] Could not open work queue, generating new queue...
[16:54:00] - Autosending finished units... [June 4 16:54:00 UTC]
[16:54:00] Trying to send all finished work units
[16:54:00] + No unsent completed units remaining.
[16:54:00] - Autosend completed
[16:54:00] - Preparing to get new work unit...
[16:54:00] + Attempting to get work packet
[16:54:00] - Will indicate memory of 450 MB
[16:54:00] - Connecting to assignment server
[16:54:00] Connecting to http://assign.stanford.edu:8080/
[16:54:01] Posted data.
[16:54:01] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[16:54:01] + News From Folding@Home: Welcome to Folding@Home
[16:54:01] Loaded queue successfully.
[16:54:01] Connecting to http://171.64.65.56:8080/
[16:54:07] Posted data.
[17:17:09] ***** Got an Activate signal (2)
[17:17:09] Killing all core threads

Folding@Home Client Shutdown.

He checked with his Internet Provider and the people there did not find anything wrong.

After the message
"[16:54:01] Connecting to http://171.64.65.56:8080/"
he did wait for 23 minutes before stop the program.

Any help will be appreciated.

Best Regards, Fernando.

[kasson]

The server is successfully assigning and accepting work units. SMP work units can often be large in size; if your colleague has low bandwidth or the ISP is doing bandwidth throttling transmission time may be rather long.

[Fernando_Celio]

kasson,

Thank you for your answer.

Now we have a problem and I don't know how to solve it. fernandol told me that the computers that are in trouble were in his work, which has a link with 1.5 MB of download and a 0.5 MB of upload. He has no problems to send WU's, even with this rate of upload. The problem is to download a WU, and, until last week, it did not exist. We know that some change has been implemented by Stanford, the problem with GPU's AS and servers are still fresh in my memory. He has several servers running Linux and Windows with Linux under VMWare. The Windows clients can get WU's easily, the Linux clients do not. Since he did everything that I knew to test the path to this server, and made a several tests with his ISP (that just say that there is no problem by his side), so, do you have any suggestion in what to do next ?

Thank you once more.

Best Regards, Fernando.

[kasson]

Actually, I have one suggestion:
Is he using an up-to-date client? Some of the older client versions time out after 20 minutes of transfer.
Otherwise, maybe someone else on the forum has ideas. This particular server did not have any networking changes in the past year or so, so nothing's different here. Other people are uploading and downloading successfully. So there's nothing we know of that might have changed here.

[314159]

His log is showing "Folding@Home Client Version 6.24beta", so he is appears Ok there.

ISP's lie all the time!!!
I suspect that his bandwidth is considerably less than what he thinks, i.e. that 23 minutes did not suffice, possibly due to packet loss issues. (see below)
I also note that this was a new install but appears to be a successful one.
Let the darned thing try for an hour or so and see what happens.
If bandwidth is not as advertised, gig the ISP again.
Try to get transferred to their "technical area" vs. "customer service" or ask to talk to the Supervisor of the Department.

I have a file with my ISP that must weigh 10 pounds.
It includes numerous service complaints, tons of contacts with customer service, their maintenance department, their security department and even their legal area.
I have had no real problems with them in MANY months.

Can he try a site such as http://www.numion.com/ to verify that he has what his ISP claims that they are providing?
Multiple uses of this site will create a history file that is readily accessible and very useful.

I assume that you DID notice this:

Code: Select all

--- 171.64.65.56 ping statistics ---
8 packets transmitted, 7 received, 12% packet loss, time 7018ms

Is he wireless or cabled?

I use 171.64.65.56:8080 daily with quite a few WUs going up & coming down.
Xfer rates for me are fine with this server - both ways.

Example shows what I typically get on ALL machines unless two or three are sending concurrently and sharing the bandwidth - could that be his problem? i.e. another machine on the network (folding or not) that is effectively killing shared bandwidth.....
Maybe a router or Modem in need of replacement?

Code: Select all

[08:24:45] Project: 2677 (Run 19, Clone 81, Gen 12)


[08:24:45] + Attempting to send results [June 6 08:24:45 UTC]
[08:24:45] - Reading file work/wuresults_06.dat from core
[08:24:45]   (Read 49179554 bytes from disk)
[08:24:45] Connecting to http://171.64.65.56:8080/
[08:29:23] Posted data.
[08:29:23] Initial: 0000; - Uploaded at ~166 kB/s
[08:29:33] - Averaged speed for that direction ~149 kB/s
[08:29:33] + Results successfully sent
[08:29:33] Thank you for your contribution to Folding@Home.
[08:29:33] + Number of Units Completed: 883

[08:29:34] - Warning: Could not delete all work unit files (6): Core file absent
[08:29:34] Trying to send all finished work units
[08:29:34] + No unsent completed units remaining.
[08:29:34] - Preparing to get new work unit...
[08:29:34] + Attempting to get work packet
[08:29:34] - Will indicate memory of 1000 MB
[08:29:34] - Connecting to assignment server
[08:29:34] Connecting to http://assign.stanford.edu:8080/
[08:29:35] Posted data.
[08:29:35] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[08:29:35] + News From Folding@Home: Welcome to Folding@Home
[08:29:35] Loaded queue successfully.
[08:29:35] Connecting to http://171.64.65.56:8080/
[08:29:40] Posted data.
[08:29:40] Initial: 0000; - Receiving payload (expected size: 4833746)
[08:29:44] - Downloaded at ~1180 kB/s
[08:29:44] - Averaged speed for that direction ~1125 kB/s

Good luck!!

[Fernando_Celio]

Thank you for all help, gentlemen.

fernandol confirms that this week everything is back to normal and newspapers said that Telefonica, the fernandol's ISP, was under attack last week.

This is interesting. He has other clients running, include GPUs clients, but only Linux clients were affected.

Thanks once more.

Best Regards, Fernando.