130.237.232.140 Not Accepting
Moderators: Site Moderators, FAHC Science Team
-
- Posts: 30
- Joined: Tue Feb 12, 2008 1:53 am
130.237.232.140 Not Accepting
I have 2x SMP bonus units sitting here that I would really like to upload for the science. I do see that the remaining available WU's on this server is very low.
Any chance of at least accepting units crunched?
Any chance of at least accepting units crunched?
Last edited by Mitsimonsta on Tue Sep 07, 2010 10:50 am, edited 1 time in total.
Re: 130.237.232.140 Not Accepting
We'll do our best, but this server may be down for a little while.
-
- Posts: 30
- Joined: Tue Feb 12, 2008 1:53 am
Re: 130.237.232.140 Not Accepting
Thanks for the speedy reply Peter. Even getting the WU details to the collection/results server would be nice.
It is slightly disappointing when the processing is done and you can't get the results sent back, and more so when it is multiple units.
I hope it is up and running again soon.
It is slightly disappointing when the processing is done and you can't get the results sent back, and more so when it is multiple units.
I hope it is up and running again soon.
Re: 130.237.232.140 Not Accepting
When you say little while, do you mean hours or days? Since it's already been over 7 hours since it was reported hours doesn't seem very likely. What happens to the WU's we have waiting to upload if it isn't fixed by the preferred deadline?
Re: 130.237.232.140 Not Accepting
Well, it's been 12 hours since it was first reported. Any updates as to when this is going to be fixed?
-
- Posts: 30
- Joined: Tue Feb 12, 2008 1:53 am
Re: 130.237.232.140 Not Accepting
I am sure they will have a fix in place as soon as possible. From Dr. Kasson's message it appears that the issue is not with the server instance or waiting for new WU's to generate, but possibly the underlying hardware (RAID volume failure, NIC failure possibly... who knows).
You lose it, it will expire and auto-delete from the queue when it passes final deadline. Too bad, so sad.MrNovi wrote:What happens to the WU's we have waiting to upload if it isn't fixed by the preferred deadline?
Re: 130.237.232.140 Not Accepting
Mitsimonsta wrote:I am sure they will have a fix in place as soon as possible. From Dr. Kasson's message it appears that the issue is not with the server instance or waiting for new WU's to generate, but possibly the underlying hardware (RAID volume failure, NIC failure possibly... who knows).
I can understand that there may be more to it than just reboot the server, but there should be redundancies in place for that occasion.
MrNovi wrote:What happens to the WU's we have waiting to upload if it isn't fixed by the preferred deadline?
Mitsimonsta wrote:You lose it, it will expire and auto-delete from the queue when it passes final deadline. Too bad, so sad.
That part I find unacceptable. If the completed WU's can't be uploaded they should NOT be distributing them to be worked on.
-
- Posts: 10179
- Joined: Thu Nov 29, 2007 4:30 pm
- Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
- Location: Arizona
- Contact:
Re: 130.237.232.140 Not Accepting
Mitsimonsta isn't know for his diplomatic skills, but is technically correct.
FAH does have redundancies. First, the completed WU is cached at the client level, and the client moves on to new work to keep the client productive. Next, the fah client will automatically try to upload the completed WU every 6 hours. And most WS (work servers) have a back up CS (collection server) so that when the WS goes offline, the CS can accept the stranded work units.
The Server Status page (link on toolbar at top of page) shows the CS is 130.237.165.141 for WS 130.237.165.140. Does your fahlog show the client attempting to upload to the CS as well as the WS?
FAH does have redundancies. First, the completed WU is cached at the client level, and the client moves on to new work to keep the client productive. Next, the fah client will automatically try to upload the completed WU every 6 hours. And most WS (work servers) have a back up CS (collection server) so that when the WS goes offline, the CS can accept the stranded work units.
The Server Status page (link on toolbar at top of page) shows the CS is 130.237.165.141 for WS 130.237.165.140. Does your fahlog show the client attempting to upload to the CS as well as the WS?
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Tell me and I forget. Teach me and I remember. Involve me and I learn.
-
- Posts: 11
- Joined: Thu Jun 24, 2010 2:47 am
- Hardware configuration: case - Cooler Master ATCS-840
psu - Corsair 750TX 750 watt
mobo - Gigabyte X58A-UDR
cpu - Intel i7-950 w/ OC to 3.8GHz
cooler - Cooler Master Hyper 212+ w/ 2nd fan
ram - G.Skill DDR3 PC-1066 6Gb (3 x 2Gb) 9/9/9/20 timings
gpu - EVGA GTX-460 768Mb Superclocked Edition, 763MHz core, 1526MHz shaders
hdd - Samsung Spinpoint F3 1Tb
ups - APC XS-1500
Re: 130.237.232.140 Not Accepting
My HFM log shows the client attempting both of those servers for over 16 hours now. I am about 2 hours away from another retry, but as I write this the work server is still listed as not accepting. Maybe I am overlooking it, but I do not see the collection server listed on the status page.7im wrote:The Server Status page (link on toolbar at top of page) shows the CS is 130.237.165.141 for WS 130.237.165.140. Does your fahlog show the client attempting to upload to the CS as well as the WS?
Re: 130.237.232.140 Not Accepting
No, it tries 130.237.232.140:8080 first then goes to 130.237.165.141:8080. At no time does it try to go to 130.237.165.140. 130.267.165.140 isn't even on your server status list at http://fah-web.stanford.edu/serverstat.html
Re: 130.237.232.140 Not Accepting
Code: Select all
[22:41:07] - Autosending finished units... [September 7 22:41:07 UTC]
[22:41:07] Trying to send all finished work units
[22:41:07] Project: 6015 (Run 1, Clone 63, Gen 282)
[22:41:07] + Attempting to send results [September 7 22:41:07 UTC]
[22:41:07] - Reading file work/wuresults_03.dat from core
[22:41:07] (Read 20542514 bytes from disk)
[22:41:07] Connecting to http://130.237.232.140:8080/
[22:41:08] - Couldn't send HTTP request to server
[22:41:08] + Could not connect to Work Server (results)
[22:41:08] (130.237.232.140:8080)
[22:41:08] + Retrying using alternative port
[22:41:08] Connecting to http://130.237.232.140:80/
[22:41:10] - Couldn't send HTTP request to server
[22:41:10] + Could not connect to Work Server (results)
[22:41:10] (130.237.232.140:80)
[22:41:10] - Error: Could not transmit unit 03 (completed September 7) to work server.
[22:41:10] - 6 failed uploads of this unit.
[22:41:10] + Attempting to send results [September 7 22:41:10 UTC]
[22:41:10] - Reading file work/wuresults_03.dat from core
[22:41:10] (Read 20542514 bytes from disk)
[22:41:10] Connecting to http://130.237.165.141:8080/
[22:41:31] - Couldn't send HTTP request to server
[22:41:31] + Could not connect to Work Server (results)
[22:41:31] (130.237.165.141:8080)
[22:41:31] + Retrying using alternative port
[22:41:31] Connecting to http://130.237.165.141:80/
[22:41:52] - Couldn't send HTTP request to server
[22:41:52] + Could not connect to Work Server (results)
[22:41:52] (130.237.165.141:80)
[22:41:52] Could not transmit unit 03 to Collection server; keeping in queue.
[22:41:52] + Sent 0 of 1 completed units to the server
[22:41:52] - Autosend completed
Re: 130.237.232.140 Not Accepting
And as for the redundancies, if they are in place why they heck aren't the WU's uploading to them? It's obvious that they either don't actually have any redundancies, or they are so misconfigured as to be non-functional.
So now, when are they going to fix this this so we can upload our finished Work Units?
So now, when are they going to fix this this so we can upload our finished Work Units?
-
- Site Moderator
- Posts: 6986
- Joined: Wed Dec 23, 2009 9:33 am
- Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB
Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400 - Location: Land Of The Long White Cloud
- Contact:
Re: 130.237.232.140 Not Accepting
The good news is that there will be more SMP Servers soon: http://folding.typepad.com/news/2010/08 ... -line.html
The "unknown" news is that there isn't any ETA.
The "unknown" news is that there isn't any ETA.
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Re: 130.237.232.140 Not Accepting
Dear MrNovi,
If everything was perfect all the time, my mother would not have Alzheimer's. Please be patient. If I lose a WU it is the end of the world as I know it, not.
If everything was perfect all the time, my mother would not have Alzheimer's. Please be patient. If I lose a WU it is the end of the world as I know it, not.
-
- Posts: 450
- Joined: Tue Dec 04, 2007 8:36 pm
Re: 130.237.232.140 Not Accepting
MrNovi wrote:What happens to the WU's we have waiting to upload if it isn't fixed by the preferred deadline?
Actually, you get base points with no bonus when it doesn't upload by the preferred deadline. The WU will auto-delete from the queue at the final deadline.Mitsimonsta wrote:You lose it, it will expire and auto-delete from the queue when it passes final deadline. Too bad, so sad.
You can call it "unacceptable" if you want, but we certainly have been warned. None of us like it, but but we have to accept that risk when we choose to run SMP units with the bonus plan, and it's really a rather rare phenomenon.MrNovi wrote:That part I find unacceptable. If the completed WU's can't be uploaded they should NOT be distributing them to be worked on.
source: Subject: new release: extra-large work unitskasson wrote:Important: The bonus scheme is based on the time that returned work units are received by our servers. We make every effort to keep these servers available to receive work, but there will inevitably be congestion or downtimes. We do not guarantee server availability. If for some reason you do not receive the expected bonus please do let us know, but unlike base points, we will generally not give recredits for bonuses. Bonuses are not guaranteed. Similar policies apply for unexpected loss of work units, etc. The bonus program has some "slack" calculated in to allow for such unexpected events.