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: 5
|
![]() |
Author |
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2131 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Since a few months I've been seeing empty wcgrid_*_x86_64-pc-linux-gnu* program files in my boinc's 'projects' directory for WCG:
# (cd ~boinc/projects/www.worldcommunitygrid.org/ && ll wcgrid_*_x86_64-pc-linux-gnu*) When looking at what caused this, my system log is showing this: 21-Jun-2022 15:50:49 [---] Checking presence of 148 project files So, next there is a download starting for these files (according to the system log) and while downloading, this happens: 2022-06-21T15:50:55.744507+02:00 boinc[6739]: 21-Jun-2022 15:50:55 [World Community Grid] Incomplete read of 1773.000000 < 5KB for wcgrid_opng_autodockgpu_7.28_x86_64-pc-linux-gnu__opencl_nvidia_102 - truncating and so on ... ending up again with zero size files, everytime I restart BOINC. Is this a bug or is it a glitch because BOINC hasn't been started on your side? Adri |
||
|
TPCBF
Master Cruncher USA Joined: Jan 2, 2011 Post Count: 1937 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
In case you missed it, but the project has been shut down for 4 month, with NO data being send/updated from the projects web site.
----------------------------------------And so far, only the forum and project web site has been reactivated so far, even the personal stats page is likely to be taken with a grain of salt until all databases of the actual project WUs is reactivated as well, which then will result in actually receiving valid WUs. Everything else may receive in the meantime isn't likely to be taken serious up to them... Ralf ![]() |
||
|
PMH_UK
Veteran Cruncher UK Joined: Apr 26, 2007 Post Count: 766 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Adri,
----------------------------------------I suspect the zero length files relate to use of a CDN but with the host site down and no (few) requests the contents have timed out leaving just ghosts. Paul.
Paul.
|
||
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2131 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Thank you, Paul.
Ralf, I'm just worried if there will be an issue with the downloading of program files, after the restart. The program files (all matching wcgrid_*_x86_64-pc-linux-gnu) are all 'destroyed', as they all have a zero size now and they have only non-executable bits, as I showed. What would happen after the restart? Will the executables be restored first and will they get their executable bits back, the bits that they definitely need, after the restart, before any task will be started? If there will be tasks starting before the executables are restored, then those tasks will fail with messages like 'cannot execute program' or 'permission denied' and my computer will probably be restricted receiving new tasks. On a recreational fun note: a zero length program can replicate itself and it is the shortest computer program that one could write replicating itself. ![]() So, thinking about this issue, my advice to the admins would be to make sure that the destroyed, zero length executables are restored first, before any tasks are sent out, after the restart. |
||
|
TPCBF
Master Cruncher USA Joined: Jan 2, 2011 Post Count: 1937 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Thank you, Paul. I have done pretty much the same when I switched to another project for the duration of the WCG shutdown. And the same happened when I deslected/reselected WCG projects in the past. Also not different from when the project applications themselves are being updated...Ralf, I'm just worried if there will be an issue with the downloading of program files, after the restart. The program files (all matching wcgrid_*_x86_64-pc-linux-gnu) are all 'destroyed', as they all have a zero size now and they have only non-executable bits, as I showed. What would happen after the restart? Will the executables be restored first and will they get their executable bits back, the bits that they definitely need, after the restart, before any task will be started? If there will be tasks starting before the executables are restored, then those tasks will fail with messages like 'cannot execute program' or 'permission denied' and my computer will probably be restricted receiving new tasks. On a recreational fun note: a zero length program can replicate itself and it is the shortest computer program that one could write replicating itself. ![]() So, thinking about this issue, my advice to the admins would be to make sure that the destroyed, zero length executables are restored first, before any tasks are sent out, after the restart. BOINC is just re-downloading what it needs, it is pretty resilient in that regard... Ralf ![]() [Edit 1 times, last edit by TPCBF at Jun 22, 2022 11:35:05 PM] |
||
|
|
![]() |