171.64.65.102 Reject

Moderators: Site Moderators, FAHC Science Team

RAH
Posts: 131
Joined: Sun Dec 02, 2007 6:29 am
Hardware configuration: 1. C2Q 8200@2880 / W7Pro64 / SMP2 / 2 GPU - GTS250/GTS450
2. C2D 6300@3600 / XPsp3 / SMP2 / 1 GPU - GT240
Location: Florida

171.64.65.102 Reject

Post by RAH »

171.64.65.102
Server is in reject mode.

Could a mod pass the info to correct peoples.
Thanks you
Image
baz657
Posts: 55
Joined: Thu Nov 12, 2009 1:40 pm
Hardware configuration: Win 7 Ultimate x64, 2 X Nvidia Fermi cards, one 2 Core CPU and one quad and one very old laptop
Location: Chesterfield, UK
Contact:

Re: 171.64.65.102 Reject

Post by baz657 »

+1
Bobcat
Posts: 24
Joined: Fri Dec 10, 2010 12:08 am
Hardware configuration: i7-860 2.8 GHz, 4 GB RAM, 1 TB HD, Win7 64-bit
Sapphire (ATI) 5670 825 MHz, 1 GB DDR5 RAM
Location: New Jersey
Contact:

Re: 171.64.65.102 Reject

Post by Bobcat »

Chronic problems continue with 171.64.65.102. It seems that half the time, the server is rejecting connections. Can anyone see what's going on and fix this? It's used with the ATI GPU WUs.

Code: Select all

[12:53:10] Folding@home Core Shutdown: FINISHED_UNIT
[12:53:12] CoreStatus = 64 (100)
[12:53:12] Sending work to server
[12:53:12] Project: 5737 (Run 2, Clone 630, Gen 67)
[12:53:12] + Attempting to send results [December 15 12:53:12 UTC]
[12:53:12] Gpu type=1 species=4.
[12:53:13] - Couldn't send HTTP request to server
[12:53:13] + Could not connect to Work Server (results)
[12:53:13] (171.64.65.102:8080)
[12:53:13] + Retrying using alternative port
[12:53:15] - Couldn't send HTTP request to server
[12:53:15] + Could not connect to Work Server (results)
[12:53:15] (171.64.65.102:80)
[12:53:15] - Error: Could not transmit unit 06 (completed December 15) to work server.
[12:53:15] Keeping unit 06 in queue.
[12:53:15] Project: 5737 (Run 2, Clone 630, Gen 67)
[12:53:15] + Attempting to send results [December 15 12:53:15 UTC]
[12:53:15] Gpu type=1 species=4.
[12:53:16] - Couldn't send HTTP request to server
[12:53:16] + Could not connect to Work Server (results)
[12:53:16] (171.64.65.102:8080)
[12:53:16] + Retrying using alternative port
[12:53:17] - Couldn't send HTTP request to server
[12:53:17] + Could not connect to Work Server (results)
[12:53:17] (171.64.65.102:80)
[12:53:17] - Error: Could not transmit unit 06 (completed December 15) to work server.
[12:53:17] + Attempting to send results [December 15 12:53:17 UTC]
[12:53:17] Gpu type=1 species=4.
[12:53:18] - Couldn't send HTTP request to server
[12:53:18] (Got status 503)
[12:53:18] + Could not connect to Work Server (results)
[12:53:18] (171.67.108.17:8080)
[12:53:18] + Retrying using alternative port
[12:53:18] - Couldn't send HTTP request to server
[12:53:18] (Got status 503)
[12:53:18] + Could not connect to Work Server (results)
[12:53:18] (171.67.108.17:80)
[12:53:18] Could not transmit unit 06 to Collection server; keeping in queue.
[12:53:18] - Preparing to get new work unit...
[12:53:18] Cleaning up work directory
[12:53:18] + Attempting to get work packet
[12:53:18] Passkey found
[12:53:18] Gpu type=1 species=4.
[12:53:18] - Connecting to assignment server
[12:53:19] + No appropriate work server was available; will try again in a bit.
[12:53:19] + Couldn't get work instructions.
[12:53:19] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[12:53:27] + Attempting to get work packet
[12:53:27] Passkey found
[12:53:27] Gpu type=1 species=4.
[12:53:27] - Connecting to assignment server
[12:53:28] + No appropriate work server was available; will try again in a bit.
[12:53:28] + Couldn't get work instructions.
[12:53:28] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[12:53:40] + Attempting to get work packet
[12:53:40] Passkey found
[12:53:40] Gpu type=1 species=4.
[12:53:40] - Connecting to assignment server
[12:53:41] + No appropriate work server was available; will try again in a bit.
[12:53:41] + Couldn't get work instructions.
[12:53:41] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[12:54:08] + Attempting to get work packet
[12:54:08] Passkey found
[12:54:08] Gpu type=1 species=4.
[12:54:08] - Connecting to assignment server
[12:54:09] + No appropriate work server was available; will try again in a bit.
[12:54:09] + Couldn't get work instructions.
[12:54:09] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[12:54:52] + Attempting to get work packet
[12:54:52] Passkey found
[12:54:52] Gpu type=1 species=4.
[12:54:52] - Connecting to assignment server
[12:54:53] + No appropriate work server was available; will try again in a bit.
[12:54:53] + Couldn't get work instructions.
[12:54:53] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[12:56:26] + Attempting to get work packet
[12:56:26] Passkey found
[12:56:26] Gpu type=1 species=4.
[12:56:26] - Connecting to assignment server
[12:56:27] + No appropriate work server was available; will try again in a bit.
[12:56:27] + Couldn't get work instructions.
[12:56:27] - Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[12:59:16] + Attempting to get work packet
[12:59:16] Passkey found
[12:59:16] Gpu type=1 species=4.
[12:59:16] - Connecting to assignment server
[12:59:17] + No appropriate work server was available; will try again in a bit.
[12:59:17] + Couldn't get work instructions.
[12:59:17] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
drougnor
Posts: 147
Joined: Tue Dec 29, 2009 2:21 am

Re: 171.64.65.102 Reject

Post by drougnor »

This has been happening for me as well, all morning long.
VijayPande
Pande Group Member
Posts: 2058
Joined: Fri Nov 30, 2007 6:25 am
Location: Stanford

Re: 171.64.65.102 Reject

Post by VijayPande »

Thanks. We're looking into it.
Prof. Vijay Pande, PhD
Departments of Chemistry, Structural Biology, and Computer Science
Chair, Biophysics
Director, Folding@home Distributed Computing Project
Stanford University
Bobcat
Posts: 24
Joined: Fri Dec 10, 2010 12:08 am
Hardware configuration: i7-860 2.8 GHz, 4 GB RAM, 1 TB HD, Win7 64-bit
Sapphire (ATI) 5670 825 MHz, 1 GB DDR5 RAM
Location: New Jersey
Contact:

Re: 171.64.65.102 Reject

Post by Bobcat »

Looks like we're alive again.

I realize that there will be problems from time to time, but it seems to me that 171.64.65.102 is in 'reject' mode way too often.
drougnor
Posts: 147
Joined: Tue Dec 29, 2009 2:21 am

Re: 171.64.65.102 Reject

Post by drougnor »

The server is in reject once again, as of Fri Jan 7 11:10:10 PST 2011
GreyWhiskers
Posts: 660
Joined: Mon Oct 25, 2010 5:57 am
Hardware configuration: a) Main unit
Sandybridge in HAF922 w/200 mm side fan
--i7 2600K@4.2 GHz
--ASUS P8P67 DeluxeB3
--4GB ADATA 1600 RAM
--750W Corsair PS
--2Seagate Hyb 750&500 GB--WD Caviar Black 1TB
--EVGA 660GTX-Ti FTW - Signature 2 GPU@ 1241 Boost
--MSI GTX560Ti @900MHz
--Win7Home64; FAH V7.3.2; 327.23 drivers

b) 2004 HP a475c desktop, 1 core Pent 4 HT@3.2 GHz; Mem 2GB;HDD 160 GB;Zotac GT430PCI@900 MHz
WinXP SP3-32 FAH v7.3.6 301.42 drivers - GPU slot only

c) 2005 Toshiba M45-S551 laptop w/2 GB mem, 160GB HDD;Pent M 740 CPU @ 1.73 GHz
WinXP SP3-32 FAH v7.3.6 [Receiving Core A4 work units]
d) 2011 lappy-15.6"-1920x1080;i7-2860QM,2.5;IC Diamond Thermal Compound;GTX 560M 1,536MB u/c@700;16GB-1333MHz RAM;HDD:500GBHyb w/ 4GB SSD;Win7HomePrem64;320.18 drivers FAH 7.4.2ß
Location: Saratoga, California USA

Re: 171.64.65.102 Reject

Post by GreyWhiskers »

Down again.


From Stanford Server Stats:
Folding@home server status
Report initiated on Sat Jan 15 19:15:10 PST 2011.
171.64.65.102 GPU vspg2v2 vvoelz full Reject

From my Log:
[02:58:30] + Attempting to send results [January 16 02:58:30 UTC]
[02:58:30] - Reading file work/wuresults_04.dat from core
[02:58:30] (Read 264899 bytes from disk)
[02:58:30] Gpu type=1 species=3.
[02:58:30] Connecting to http://171.64.65.102:8080/
[02:58:31] - Couldn't send HTTP request to server
[02:58:31] + Could not connect to Work Server (results)
[02:58:31] (171.64.65.102:8080)
[02:58:31] + Retrying using alternative port
[02:58:31] Connecting to http://171.64.65.102:80/
[02:58:32] - Couldn't send HTTP request to server
[02:58:32] + Could not connect to Work Server (results)
[02:58:32] (171.64.65.102:80)
[02:58:32] - Error: Could not transmit unit 04 (completed January 16) to work server.
GreyWhiskers
Posts: 660
Joined: Mon Oct 25, 2010 5:57 am
Hardware configuration: a) Main unit
Sandybridge in HAF922 w/200 mm side fan
--i7 2600K@4.2 GHz
--ASUS P8P67 DeluxeB3
--4GB ADATA 1600 RAM
--750W Corsair PS
--2Seagate Hyb 750&500 GB--WD Caviar Black 1TB
--EVGA 660GTX-Ti FTW - Signature 2 GPU@ 1241 Boost
--MSI GTX560Ti @900MHz
--Win7Home64; FAH V7.3.2; 327.23 drivers

b) 2004 HP a475c desktop, 1 core Pent 4 HT@3.2 GHz; Mem 2GB;HDD 160 GB;Zotac GT430PCI@900 MHz
WinXP SP3-32 FAH v7.3.6 301.42 drivers - GPU slot only

c) 2005 Toshiba M45-S551 laptop w/2 GB mem, 160GB HDD;Pent M 740 CPU @ 1.73 GHz
WinXP SP3-32 FAH v7.3.6 [Receiving Core A4 work units]
d) 2011 lappy-15.6"-1920x1080;i7-2860QM,2.5;IC Diamond Thermal Compound;GTX 560M 1,536MB u/c@700;16GB-1333MHz RAM;HDD:500GBHyb w/ 4GB SSD;Win7HomePrem64;320.18 drivers FAH 7.4.2ß
Location: Saratoga, California USA

Re: 171.64.65.102 Reject

Post by GreyWhiskers »

Looks like it's back up. The Server stats aren't updated yet, though.


[03:42:17] + Attempting to get work packet
[03:42:17] Passkey found
[03:42:17] - Will indicate memory of 2047 MB
[03:42:17] Gpu type=1 species=3.
[03:42:17] - Connecting to assignment server
[03:42:17] Connecting to http://assign-GPU.stanford.edu:8080/
[03:42:17] Posted data.
[03:42:17] Initial: 40AB; - Successful: assigned to (171.64.65.102).
[03:42:17] + News From Folding@Home: Welcome to Folding@Home
[03:42:17] Loaded queue successfully.
[03:42:17] Gpu type=1 species=3.
[03:42:17] Sent data
[03:42:17] Connecting to http://171.64.65.102:8080/
[03:42:18] Posted data.
[03:42:18] Initial: 0000; - Receiving payload (expected size: 97207)
[03:42:18] Conversation time very short, giving reduced weight in bandwidth avg
[03:42:18] - Downloaded at ~189 kB/s
[03:42:18] - Averaged speed for that direction ~183 kB/s
[03:42:18] + Received work.
[03:42:18] Trying to send all finished work units
[03:42:18] Project: 5738 (Run 2, Clone 636, Gen 107)
[03:42:18] - Read packet limit of 540015616... Set to 524286976.
GreyWhiskers
Posts: 660
Joined: Mon Oct 25, 2010 5:57 am
Hardware configuration: a) Main unit
Sandybridge in HAF922 w/200 mm side fan
--i7 2600K@4.2 GHz
--ASUS P8P67 DeluxeB3
--4GB ADATA 1600 RAM
--750W Corsair PS
--2Seagate Hyb 750&500 GB--WD Caviar Black 1TB
--EVGA 660GTX-Ti FTW - Signature 2 GPU@ 1241 Boost
--MSI GTX560Ti @900MHz
--Win7Home64; FAH V7.3.2; 327.23 drivers

b) 2004 HP a475c desktop, 1 core Pent 4 HT@3.2 GHz; Mem 2GB;HDD 160 GB;Zotac GT430PCI@900 MHz
WinXP SP3-32 FAH v7.3.6 301.42 drivers - GPU slot only

c) 2005 Toshiba M45-S551 laptop w/2 GB mem, 160GB HDD;Pent M 740 CPU @ 1.73 GHz
WinXP SP3-32 FAH v7.3.6 [Receiving Core A4 work units]
d) 2011 lappy-15.6"-1920x1080;i7-2860QM,2.5;IC Diamond Thermal Compound;GTX 560M 1,536MB u/c@700;16GB-1333MHz RAM;HDD:500GBHyb w/ 4GB SSD;Win7HomePrem64;320.18 drivers FAH 7.4.2ß
Location: Saratoga, California USA

Re: 171.64.65.102 Reject

Post by GreyWhiskers »

It's down again - the 171.64.65.102 server log (http://fah-web.stanford.edu/logs/171.64.65.102.log.html) has been showing the status of REJECT since 1700 Stanford local time.

This is the main server for my class of ATI GPUs - and has been down a LOT.

GW.

BACK UP AT ~1820 - Downloaded new WU after trying for about 1 hr 20 minutes.

GW.
Bobcat
Posts: 24
Joined: Fri Dec 10, 2010 12:08 am
Hardware configuration: i7-860 2.8 GHz, 4 GB RAM, 1 TB HD, Win7 64-bit
Sapphire (ATI) 5670 825 MHz, 1 GB DDR5 RAM
Location: New Jersey
Contact:

Re: How to fix Systray client.cfg file?

Post by Bobcat »

Here we go again:

[09:39:18] + Attempting to send results [January 21 09:39:18 UTC]
[09:39:18] Gpu type=1 species=4.
[09:39:19] - Couldn't send HTTP request to server
[09:39:19] + Could not connect to Work Server (results)
[09:39:19] (171.64.65.102:8080)
[09:39:19] + Retrying using alternative port
[09:39:20] - Couldn't send HTTP request to server
[09:39:20] + Could not connect to Work Server (results)
[09:39:20] (171.64.65.102:80)
[09:39:20] - Error: Could not transmit unit 01 (completed January 21) to work server.

Pain in the #$%! I'm trying to see if I fixed everything and if I'll get the points. This is how the trouble started in the first place!

But I have to switch users, so I have to shut down the GPU client without the results being sent. It's unlikely I'll be able to turn it back on before the deadline. So PG doesn't get the results in time. Their loss, not mine.

Pain in the #$%! I think I'll just give up on the GPU client because they can't keep the servers working properly. I'm sick of this *^%$.
Bobcat
Posts: 24
Joined: Fri Dec 10, 2010 12:08 am
Hardware configuration: i7-860 2.8 GHz, 4 GB RAM, 1 TB HD, Win7 64-bit
Sapphire (ATI) 5670 825 MHz, 1 GB DDR5 RAM
Location: New Jersey
Contact:

Re: 171.64.65.102 Reject

Post by Bobcat »

It's dead again. Dead again. Dead again. Dead again. Dead again. Dead again. Dead again. Dead again. Dead again. Dead again.

Someone put it out of its misery, please. Is there euthanasia for servers?

http://fah-web.stanford.edu/localinfo/contact.GPU.html
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 171.64.65.102 Reject

Post by bruce »

Dead from 01:10 PST to 03:50 PST. Either it's set to automatically recover or somebody was working very strange hours at Stanford.

Yes, there is euthanasia for servers, but Stanford tends to keeps them on hospice care until the have the capacity to replace it.
Bobcat
Posts: 24
Joined: Fri Dec 10, 2010 12:08 am
Hardware configuration: i7-860 2.8 GHz, 4 GB RAM, 1 TB HD, Win7 64-bit
Sapphire (ATI) 5670 825 MHz, 1 GB DDR5 RAM
Location: New Jersey
Contact:

Re: 171.64.65.102 Reject

Post by Bobcat »

Note that this thread was started 3 months ago, and there are other threads about this server going back for well over a year(!), so 171.64.65.102 has been sick for a long time. I'm just going to give up on GPU folding. Between the problems of switching users with the GPU client and dealing with this screwed-up server, it's not worth the hassle.

If Stanford can't be bothered to keep their servers running, why should we bother to run-up our electric bills to do their work?
Bobcat
Posts: 24
Joined: Fri Dec 10, 2010 12:08 am
Hardware configuration: i7-860 2.8 GHz, 4 GB RAM, 1 TB HD, Win7 64-bit
Sapphire (ATI) 5670 825 MHz, 1 GB DDR5 RAM
Location: New Jersey
Contact:

Re: 171.64.65.102 Reject

Post by Bobcat »

171.64.65.102 is in reject mode again: http://fah-web.stanford.edu/localinfo/contact.GPU.html
Post Reply