128.252.203.2:8080: Server did not like results, dumping

Moderators: Site Moderators, FAHC Science Team

Post Reply
CPTK
Posts: 2
Joined: Thu Mar 19, 2020 10:00 am

128.252.203.2:8080: Server did not like results, dumping

Post by CPTK »

Code: Select all

09:18:39:WU01:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64)
09:18:39:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:14533 run:0 clone:5844 gen:0 core:0x22 unit:0x0000000080fccb025e72f24ac77d2ce3
09:18:39:WU01:FS01:Uploading 49.92MiB to 128.252.203.2
09:18:39:WU01:FS01:Connecting to 128.252.203.2:8080
09:18:45:WU01:FS01:Upload 78.50%
09:18:46:WU01:FS01:Upload complete
09:18:46:WU01:FS01:Server responded WORK_QUIT (404)
09:18:46:WARNING:WU01:FS01:Server did not like results, dumping
09:18:46:WU01:FS01:Cleaning up
Server: "Sorry, it's not you, it's me. Actually no, I just don't like you."
Results: /sadnoises :(

No overheating, no errors on my GPU as far as I can tell. Not going to run Folding anymore till I know what's the problem. While I want to help, I don't want to waste hours of electricity for nothing.
Jesse_V
Site Moderator
Posts: 2851
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.252.203.2:8080: Server did not like results, dumping

Post by Jesse_V »

Folding@home performs sanity checks on the workunits to verify that all the numbers and formatting looks good. It's possible that it was caught in the filter because something happened or by accident. That's my guess. Another possibility is that the servers are overwhelmed by the flood of new users, which causes errors in the processing.

The workunit is likely marked as failed or corrupt and it will get reassigned to try again. I'd recommend that you keep the software running as the other workunits should proceed properly.
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.
bruce
Posts: 20910
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 128.252.203.2:8080: Server did not like results, dumping

Post by bruce »

Are you running an antivirus program that scans your computer for malware periodically?

If so, it may have found a false positive.

FAH's work files contain a lot of semi-random values and occasionally those sequences match up with a "known virus pattern" so it quarantinesl the suspected virus, corrupting the WU.

Reconfigure your AV program to avoid scanning FAH's work files.
MrFrizzy
Posts: 123
Joined: Fri Feb 14, 2020 4:48 am

Re: 128.252.203.2:8080: Server did not like results, dumping

Post by MrFrizzy »

I too got the same result on the p14533 project. The whole thing processed just fine and then spit out that "Server did not like results, dumping" message.

Code: Select all

06:59:21:WU00:FS01:0x22:Folding@home Core Shutdown: FINISHED_UNIT
06:59:22:WU00:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64)
06:59:22:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:14533 run:0 clone:1056 gen:0 core:0x22 unit:0x0000000080fccb025e72f1f2cd42c3b7
06:59:22:WU00:FS01:Uploading 49.92MiB to 128.252.203.2
06:59:22:WU00:FS01:Connecting to 128.252.203.2:8080
06:59:28:WU00:FS01:Upload 17.15%
06:59:34:WU00:FS01:Upload 39.94%
06:59:40:WU00:FS01:Upload 60.35%
06:59:46:WU00:FS01:Upload 82.76%
06:59:51:WU00:FS01:Upload complete
06:59:51:WU00:FS01:Server responded WORK_QUIT (404)
06:59:51:WARNING:WU00:FS01:Server did not like results, dumping
06:59:51:WU00:FS01:Cleaning up
S1: AMD R5 3600 & Sapphire RX 5700 XT Reference @2.1GHz under water
S2: Intel Xeon E5-2620v3 & MSI GTX 1650

RX 5700 XT Project & PPD Tracking Spreadsheet

Image
CPTK
Posts: 2
Joined: Thu Mar 19, 2020 10:00 am

Re: 128.252.203.2:8080: Server did not like results, dumping

Post by CPTK »

A few hours after I posted this yesterday, I went to check server status, and yeah, the server at 128.252.203.2 was out of disk space. This may have been the problem. The server status page now shows it has 19+ TiB.

The logs have to be more specific about these errors.
Post Reply