Page 1 of 1
171.67.108.11 - can not get work
Posted: Thu Jul 15, 2010 10:11 pm
by Flathead74
It seems there is a problem with 171.67.108.11
Work is not being accepted nor handed out.
Also, the server stats and psummary pages won't load.
Code: Select all
[21:28:46] + Attempting to send results [July 15 21:28:46 UTC]
[21:28:46] - Reading file work/wuresults_05.dat from core
[21:28:46] (Read 99815 bytes from disk)
[21:28:46] Connecting to http://171.67.108.11:8080/
[21:28:46] - Couldn't send HTTP request to server
[21:28:46] (Got status 503)
[21:28:46] + Could not connect to Work Server (results)
[21:28:46] (171.67.108.11:8080)
[21:28:46] + Retrying using alternative port
[21:28:46] Connecting to http://171.67.108.11:80/
[21:28:46] - Couldn't send HTTP request to server
[21:28:46] (Got status 503)
[21:28:46] + Could not connect to Work Server (results)
[21:28:46] (171.67.108.11:80)
[21:28:46] - Error: Could not transmit unit 05 (completed July 15) to work server.
[21:28:46] - 1 failed uploads of this unit.
[21:28:46] Keeping unit 05 in queue.
[21:28:46] Trying to send all finished work units
[21:28:46] Project: 5769 (Run 0, Clone 335, Gen 86)
[21:28:46] - Read packet limit of 540015616... Set to 524286976.
Ping results show a 50% packet loss.
Code: Select all
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\xxxxxxx>ping 171.67.108.11
Pinging 171.67.108.11 with 32 bytes of data:
Reply from 171.67.108.11: bytes=32 time=236ms TTL=51
Request timed out.
Reply from 171.67.108.11: bytes=32 time=217ms TTL=51
Request timed out.
Ping statistics for 171.67.108.11:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 217ms, Maximum = 236ms, Average = 226ms
Re: 171.67.108.11 - can not get work
Posted: Thu Jul 15, 2010 10:14 pm
by rickoic
Think Stanford may be down as I'm having the same problem with 171.64.65.61.
Fold on
Rick
EDIT: Home page won't load as well.
Re: 171.67.108.11 - can not get work
Posted: Thu Jul 15, 2010 10:17 pm
by TheWolf
I wouldn't delete core_11 for it to download a new one anytime soon.
Under new topic you can see my other post. I think they maybe trying to clean up a virus.
Re: 171.67.108.11 - can not get work
Posted: Thu Jul 15, 2010 10:22 pm
by SantaFe
Whoops, didn't see this post, as I'm having the same problem with 171.65.103.160. At least now I can stop trying to fix my connection!
Re: 171.67.108.11 - can not get work
Posted: Thu Jul 15, 2010 10:23 pm
by Macaholic
Dr. Pande has been notified. Thank you.
Re: 171.67.108.11 - can not get work
Posted: Thu Jul 15, 2010 10:25 pm
by VijayPande
Thanks. We're looking into it.
Re: 171.67.108.11 - can not get work
Posted: Thu Jul 15, 2010 10:55 pm
by VijayPande
We are seeing some strange behavior in the Stanford net. I've notified the network IT staff.
Re: 171.67.108.11 - can not get work
Posted: Thu Jul 15, 2010 11:02 pm
by RAH
Seems to be fixed for me. Thanks
Got work again.
Of course everything is going to get slammed for awhile.
440 on AS right now.
Re: 171.67.108.11 - can not get work
Posted: Thu Jul 15, 2010 11:02 pm
by Blasphemous Cannibal
It looks like the servers are starting to assign work again. Three of my four cards are now folding.
Re: 171.67.108.11 - can not get work
Posted: Thu Jul 15, 2010 11:49 pm
by VijayPande
PS Some updates:
IT Services is receiving complaints of slow network connections to
off-campus sites, as well as general slowness. Some external callers have
indicated an inability to reach Stanford. Network engineers are now
investigating.
--------------------
Resolution
----------
The CPU utilization one of the campus boundary routers was extremely
high, causing the router to drop packets. No unusual traffic or other
obvious cause was discovered, so an emergency reboot of the router
was scheduled. Traffic and CPU are now back to normal levels and the
networking team will continue to investigate the root cause of this
issue.
Re: 171.67.108.11 - can not get work
Posted: Fri Jul 16, 2010 6:35 am
by 7im
VijayPande wrote:
Resolution
----------
The CPU utilization one of the campus boundary routers was extremely
high, causing the router to drop packets. No unusual traffic or other
obvious cause was discovered, so an emergency reboot of the router
was scheduled. Traffic and CPU are now back to normal levels and the
networking team will continue to investigate the root cause of this
issue.
So I take it that no viruses were found? That no one else reported anything in the nature of an infection? And any claims to that nature are completely unfounded?
Re: 171.67.108.11 - can not get work
Posted: Fri Jul 16, 2010 10:56 am
by SantaFe
7im wrote:
So I take it that no viruses were found? That no one else reported anything in the nature of an infection? And any claims to that nature are completely unfounded?
Well, I *DO* have the sniffles!
Re: 171.67.108.11 - can not get work
Posted: Fri Jul 16, 2010 3:34 pm
by Zagen30
SantaFe wrote:7im wrote:
So I take it that no viruses were found? That no one else reported anything in the nature of an infection? And any claims to that nature are completely unfounded?
Well, I *DO* have the sniffles!
Well, obviously the Pande Group
must have given it to you. I mean where else could you catch a cold?