| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 8
|
|
| Author |
|
|
wujj123456
Cruncher Joined: Jun 9, 2010 Post Count: 38 Status: Offline Project Badges:
|
I just assembled my EPYC 7401P server yesterday and for most of part, it's working fine. (Except AMD false-advertised their all-core boost, which comes far far behind 2.8GHz. That's a separate topic if anyone interested, but doesn't belong here.)
----------------------------------------However, I am getting "Download Error" on MIP1, and MIP1 only. The error all looks same: <core_client_version>7.9.2</core_client_version> <![CDATA[ <message> WU download error: couldn't get input files: <file_xfer_error> <file_name>mip1.MIP1_databasev2.zip</file_name> <error_code>-224 (permanent HTTP error)</error_code> <error_message>permanent HTTP error</error_message> </file_xfer_error> </message> ]]> The server has gone through a few hours of memtest, and it churns out valid results for all other projects. Just MIP1, it consistently fails due to this. Any idea if this is really a "download" error, or it's something potentially with my hardware? Is the mip1.MIP1_databasev2.zip a single file shared across WUs or downloaded per WU? Edit: Going into client, the only currently active unit is indeed stuck in "downloading" state. There is plenty of disk space available though. boinc-client log show a flood of these messages, but didn't associate with any WCG project. (WCG is the only project I added for now.) Mar 11 09:06:19 S8026 boinc[1421]: No protocol specified Mar 11 09:06:20 S8026 boinc[1421]: No protocol specified Mar 11 09:06:21 S8026 boinc[1421]: No protocol specified [Edit 1 times, last edit by wujj123456 at Mar 11, 2018 4:13:40 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I have the same problem with database download
|
||
|
|
wujj123456
Cruncher Joined: Jun 9, 2010 Post Count: 38 Status: Offline Project Badges:
|
I have the same problem with database download Thanks for reporting. Do you also happen to setup the client yesterday? I am asking because I do have other hosts running MIP1 just fine in between all the failures on my new server. So I am suspecting it's either something with my client, server, or maybe this file is part of initial setup that's not downloadable for now. Hopefully it's the latter... |
||
|
|
Dayle Diamond
Senior Cruncher Joined: Jan 31, 2013 Post Count: 452 Status: Offline Project Badges:
|
Yes, please post on the hardware forum if you're not getting an all-core boost on your 48 thread system.
Would hate to see that crunching power go to waste. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
> Do you also happen to setup the client yesterday?
no, i was crunching for a week. btw issue is resolved for my now |
||
|
|
wujj123456
Cruncher Joined: Jun 9, 2010 Post Count: 38 Status: Offline Project Badges:
|
My download started to succeed since 3am GMT today and no error ever since. I guess maybe it's just out of work.
|
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges:
|
We are working to have a permanent fix for this at the moment.
Details: There is a file that we call sticky, which means it is used between batches. This is that database file with download error. The input file deleter which helps clean up the backend of our system was deleting this file. Meanwhile the backend process that creates work was trying to access or copy that file into place. This caused errors in multiple places. We have paused the file input deleter which allows things to run as normal, but it causes files to stay around and fill up our file system. Thus a permanent fix is in the works to prevent the input deleter from deleting our sticky files. Thanks, -Uplinger |
||
|
|
wujj123456
Cruncher Joined: Jun 9, 2010 Post Count: 38 Status: Offline Project Badges:
|
Thank you very much for the details!
|
||
|
|
|