128.143.231.201 is not working (solved)

Moderators: Site Moderators, FAHC Science Team

Post Reply
-alias-
Posts: 121
Joined: Sun Feb 22, 2009 1:20 pm

128.143.231.201 is not working (solved)

Post by -alias- »

BA server 128.143.231.201 does not seem to be operational?

Mod edit: marked as solved
bollix47
Posts: 2982
Joined: Sun Dec 02, 2007 5:04 am
Location: Canada

Re: 128.143.231.201 is not working

Post by bollix47 »

Thank you for your report. I'm not seeing a problem at this time but that doesn't mean there isn't one.

Please post a section of your log showing the problem you're experiencing.
Image
Jesse_V
Site Moderator
Posts: 2850
Joined: Mon Jul 18, 2011 4:44 am
Hardware configuration: OS: Windows 10, Kubuntu 19.04
CPU: i7-6700k
GPU: GTX 970, GTX 1080 TI
RAM: 24 GB DDR4
Location: Western Washington

Re: 128.143.231.201 is not working

Post by Jesse_V »

I can ping it, but I get "401 HTTP UNAUTHORIZED /" on ports 80 and 8080 when I connect to the server through my browser.
F@h is now the top computing platform on the planet and nothing unites people like a dedicated fight against a common enemy. This virus affects all of us. Lets end it together.
-alias-
Posts: 121
Joined: Sun Feb 22, 2009 1:20 pm

Re: 128.143.231.201 is not working

Post by -alias- »

Below is the log from the event:

Code: Select all

[08:49:28] Completed 247500 out of 250000 steps  (99%)
[09:00:38] Completed 250000 out of 250000 steps  (100%)
[09:00:51] DynamicWrapper: Finished Work Unit: sleep=10000
[09:01:01] 
[09:01:01] Finished Work Unit:
[09:01:01] - Reading up to 64340496 from "work/wudata_00.trr": Read 64340496
[09:01:01] trr file hash check passed.
[09:01:01] - Reading up to 31675796 from "work/wudata_00.xtc": Read 31675796
[09:01:02] xtc file hash check passed.
[09:01:02] edr file hash check passed.
[09:01:02] logfile size: 212181
[09:01:02] Leaving Run
[09:01:04] - Writing 96389349 bytes of core data to disk...
[09:01:27] Done: 96388837 -> 91617440 (compressed to 5.9 percent)
[09:01:27]   ... Done.
[09:01:32] - Shutting down core
[09:01:32] 
[09:01:32] Folding@home Core Shutdown: FINISHED_UNIT
[09:01:32] CoreStatus = 64 (100)
[09:01:32] Unit 0 finished with 80 percent of time to deadline remaining.
[09:01:32] Updated performance fraction: 0.819317
[09:01:32] Sending work to server
[09:01:32] Project: 8101 (Run 0, Clone 8, Gen 379)


[09:01:32] + Attempting to send results [January 22 09:01:32 UTC]
[09:01:32] - Reading file work/wuresults_00.dat from core
[09:01:32]   (Read 91617952 bytes from disk)
[09:01:32] Connecting to http://128.143.231.201:8080/
[09:04:42] - Couldn't send HTTP request to server
[09:04:42] + Could not connect to Work Server (results)
[09:04:42]     (128.143.231.201:8080)
[09:04:42] + Retrying using alternative port
[09:04:42] Connecting to http://128.143.231.201:80/
[09:14:05] - Couldn't send HTTP request to server
[09:14:05] + Could not connect to Work Server (results)
[09:14:05]     (128.143.231.201:80)
[09:14:05] - Error: Could not transmit unit 00 (completed January 22) to work server.
[09:14:05] - 1 failed uploads of this unit.
[09:14:05]   Keeping unit 00 in queue.
[09:14:05] Trying to send all finished work units
[09:14:05] Project: 8101 (Run 0, Clone 8, Gen 379)
[09:14:05] + Attempting to send results [January 22 09:14:05 UTC]
[09:14:05] - Reading file work/wuresults_00.dat from core
[09:14:05]   (Read 91617952 bytes from disk)
[09:14:05] Connecting to http://128.143.231.201:8080/
[09:16:42] Posted data.
But just minutes after this one of my other servers finished his WU and everything went normal, so I reset the problem server and then it started again. So thank you, as it seems to have worked out!
Post Reply