| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: BETA-tasks erroring out |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 52
|
|
| Author |
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2361 Status: Offline Project Badges: 
|
Spotted this task: BETA_BETA30_9900032_8577_0; notice the "version GLIBC_.... not found" error.
Logfile: <core_client_version>7.0.27</core_client_version> <message> process exited with code 1 (0x1, -255) </message> <stderr_txt> ../../projects/worldcommunitygrid.org/wcgrid_beta30_map_7.07_x86_64-pc-linux-gnu__mt: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by ../../projects/worldcommunitygrid.org/wcgrid_beta30_map_7.07_x86_64-pc-linux-gnu__mt) ../../projects/worldcommunitygrid.org/wcgrid_beta30_map_7.07_x86_64-pc-linux-gnu__mt: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.23' not found (required by ../../projects/worldcommunitygrid.org/wcgrid_beta30_map_7.07_x86_64-pc-linux-gnu__mt) ../../projects/worldcommunitygrid.org/wcgrid_beta30_map_7.07_x86_64-pc-linux-gnu__mt: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by ../../projects/worldcommunitygrid.org/wcgrid_beta30_map_7.07_x86_64-pc-linux-gnu__mt) ../../projects/worldcommunitygrid.org/wcgrid_beta30_map_7.07_x86_64-pc-linux-gnu__mt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.16' not found (required by ../../projects/worldcommunitygrid.org/wcgrid_beta30_map_7.07_x86_64-pc-linux-gnu__mt) ../../projects/worldcommunitygrid.org/wcgrid_beta30_map_7.07_x86_64-pc-linux-gnu__mt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by ../../projects/worldcommunitygrid.org/wcgrid_beta30_map_7.07_x86_64-pc-linux-gnu__mt) ../../projects/worldcommunitygrid.org/wcgrid_beta30_map_7.07_x86_64-pc-linux-gnu__mt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.18' not found (required by ../../projects/worldcommunitygrid.org/wcgrid_beta30_map_7.07_x86_64-pc-linux-gnu__mt) ../../projects/worldcommunitygrid.org/wcgrid_beta30_map_7.07_x86_64-pc-linux-gnu__mt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.17' not found (required by ../../projects/worldcommunitygrid.org/wcgrid_beta30_map_7.07_x86_64-pc-linux-gnu__mt) ../../projects/worldcommunitygrid.org/wcgrid_beta30_map_7.07_x86_64-pc-linux-gnu__mt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by ../../projects/worldcommunitygrid.org/wcgrid_beta30_map_7.07_x86_64-pc-linux-gnu__mt) </stderr_txt> Adri PS Had to insert an empty tagpair between two dots to overcome the Forbidden problem |
||
|
|
alanb1951
Veteran Cruncher Joined: Jan 20, 2006 Post Count: 1341 Status: Offline Project Badges: 
|
Those Beta tasks from 2025-12-17 and 2025-12-18 were fairly small and (I suspect) unlikely to find any nasty [or unexpected] problems. The 47 errors I saw amongst the wingmen on the 2,279 tasks I processed involved 16 out of 194 systems (assuming each system name was only used by one machine somewhere!)
31 missing library errors of the type you've reported above were spread across 13 systems (usually only complaining about one version of GLIBC!) and 16 SIGILL aborts spread across 5 systems (sometimes reported as signal 4 rather than SIGILL...) -- nothing else, not even a download error! 9 of the "missing library" cases had such similar system names that I suspect they had common ownership and configuration, so perhaps only 5 users had that problem... Both those types were likely to show up, though I think they'd have hoped for a lower proportion of clients showing the issues. The original information WCG posted about the new MAM1 version pointed out that it needed a non-ancient version of libc  , and there was always a risk of there being some hardware too old to cope (so no surprise about the odd SIGILL).Whether that proportion of likely-to-fail systems is reflective of the main Linux population is, of course, an unknown. Last time around (late July 2025) I did some experimenting with MCM1 wingmen data and came to the conclusion that [based on my sample] if the limit was "above version 2.29" perhaps 5% of MCM1 systems would fail - that is quite an old library version . (Partial write-up in a different thread in this forum.) It may be possible to avoid sending work to systems with old O/S versions or libraries, and similarly it should be possible to avoid sending work to systems that are missing critical hardware capabilities. However, that depends on the client reporting enough detail and the server being able to dig out what it needs to know , so I guess such errors will continue...Cheers - Al. |
||
|
|
|