Page 2 of 5
Re: (171.67.108.11:8080) and (171.67.108.25:80)
Posted: Fri Jun 12, 2009 10:21 pm
by Teddy
Yep a few unsent units here as well.. always seems to happen on weekends (well Sat morn here in Aus)
Teddy
Re: (171.67.108.11:8080) and (171.67.108.25:80)
Posted: Fri Jun 12, 2009 11:46 pm
by ei57
It's still Friday at Stanford, but 171.67.108.11 seems to have been in reject all day according to this log:
http://fah-web.stanford.edu/logs/171.67.108.11.log.html
Starting: Fri Jun 12 08:25:10 PDT 2009 171.67.108.11 GPU vsp07v vvoelz full Reject
Last record: Fri Jun 12 16:35:10 PDT 2009 171.67.108.11 GPU vsp07v vvoelz full Reject
That's more than 8 hours without any heat issues!
Re: (171.67.108.11:8080) and (171.67.108.25:80)
Posted: Sat Jun 13, 2009 4:02 am
by Hyperlife
Vince just posted
this notice in the NVIDIA forum about 171.67.108.11.
Re: (171.67.108.11:8080) and (171.67.108.25:80)
Posted: Sat Jun 13, 2009 4:22 am
by boscoj
what's up with .25?
Re: (171.67.108.11:8080) and (171.67.108.25:80)
Posted: Sat Jun 13, 2009 10:50 am
by Grandpa_01
In Reject again
Re: (171.67.108.11:8080) and (171.67.108.25:80)
Posted: Sat Jun 13, 2009 9:26 pm
by codysluder
They're finally going to fix it for real:
viewtopic.php?f=52&t=10355
Re: (171.67.108.11:8080) and (171.67.108.25:80)
Posted: Sun Jun 14, 2009 4:09 am
by duvie23
By the time they get around fixing it I likely will get a past deadline and no points for the unit....
No offense, but for the guys that dont do the work and get all of the work done by us they have very little they need to do...one is keep their nettwork and servers up....I can tell you from experience over the last 3 years they haven't been doing a good job of this....
This issue, plus buggy software, bad units, etc are generally the reasons I stop folding now and then.
Re: (171.67.108.11:8080) and (171.67.108.25:80)
Posted: Sun Jun 14, 2009 4:50 am
by boscoj
dude . . wtf . . . chill . . .
duvie23 wrote:By the time they get around fixing it I likely will get a past deadline and no points for the unit....
No offense, but for the guys that dont do the work and get all of the work done by us they have very little they need to do...one is keep their nettwork and servers up....I can tell you from experience over the last 3 years they haven't been doing a good job of this....
This issue, plus buggy software, bad units, etc are generally the reasons I stop folding now and then.
Re: (171.67.108.11:8080) and (171.67.108.25:80)
Posted: Sun Jun 14, 2009 6:36 pm
by Leoslocks
codysluder wrote:They're finally going to fix it for real:
viewtopic.php?f=52&t=10355
It seems that the Stanford IT department can not handle the situation. From the News page May 25, 2009, " If this cannot be resolved in a timely manner (24-36 hours) by the IT dept, we will start taking more aggressive measures ourselves." I suspect that the 'new code' comes at a price to the F@H department as well as a penalty to the GPU folders worrying about the server status.
Perhaps we should send money dedicated to the F@H department instead of complaints. It is not like we are not throwing money at graphics cards.
Re: (171.67.108.11:8080) and (171.67.108.25:80)
Posted: Sun Jun 14, 2009 11:18 pm
by duvie23
boscoj wrote:dude . . wtf . . . chill . . .
duvie23 wrote:By the time they get around fixing it I likely will get a past deadline and no points for the unit....
No offense, but for the guys that dont do the work and get all of the work done by us they have very little they need to do...one is keep their nettwork and servers up....I can tell you from experience over the last 3 years they haven't been doing a good job of this....
This issue, plus buggy software, bad units, etc are generally the reasons I stop folding now and then.
Excuse me ! Sorry I am not as chicken-shit as you to question the almighty pande group....I am calling them like I see them. Especially for a group that is so fortunauate to have such a large group of VOLUNTEERS with VOLUNTEER computing power at a HUGE monetary cost to that VOLUNTEER doing the real work for them. All we ask is that they give and retrive our units...
Re: (171.67.108.11:8080) and (171.67.108.25:80)
Posted: Mon Jun 15, 2009 3:53 am
by boscoj
I'd love to know how much it costs to run this thing . . .
This is not an NPO is it?
Re: (171.67.108.11:8080) and (171.67.108.25:80)
Posted: Mon Jun 15, 2009 5:15 am
by Teddy
Server is down again...
Teddy
Re: (171.67.108.11:8080) and (171.67.108.25:80)
Posted: Mon Jun 15, 2009 5:27 am
by BrokenWolf
Yep. I have the same problem on a WU.
Code: Select all
[05:09:47] + Attempting to send results [June 15 05:09:47 UTC]
[05:09:47] - Reading file work/wuresults_07.dat from core
[05:09:47] (Read 155457 bytes from disk)
[05:09:47] Connecting to http://171.67.108.25:8080/
[05:09:49] - Couldn't send HTTP request to server
[05:09:49] (Got status 503)
[05:09:49] + Could not connect to Work Server (results)
[05:09:49] (171.67.108.25:8080)
[05:09:49] + Retrying using alternative port
[05:09:49] Connecting to http://171.67.108.25:80/
[05:09:51] - Couldn't send HTTP request to server
[05:09:51] (Got status 503)
[05:09:51] + Could not connect to Work Server (results)
[05:09:51] (171.67.108.25:80)
[05:09:51] Could not transmit unit 07 to Collection server; keeping in queue.
[05:09:51] + Sent 0 of 1 completed units to the server
[05:09:51] - Autosend completed
When I try to go to the web interface,
http://171.67.108.25:80 or port 8080, firefox says it can not connect to the site.
Broken
Re: 171.67.108.11 and 171.67.108.25
Posted: Wed Jun 17, 2009 7:27 pm
by ei57
Just checked one of my GPU-clients and found it folding something coming from an other server than 171.67.108.11. Next, I checked the server status page and as expected, 171.67.108.11 was in reject, as we've seen every other day the last couple of weeks.
I won't speculate in what's causing trouble, but my GPU's are delighted about the change.
Re: 171.67.108.11 and 171.67.108.25
Posted: Wed Jun 17, 2009 8:17 pm
by bruce
171.67.108.11 was working until about two hours ago -- 11:20:10 PDT -- though I don't know what happened then. (You probably got your next assignment from 171.64.122.70 which has been down for a while and finally completed the fsck.)