1) Message boards : Sixtrack Application : EXIT_DISK_LIMIT_EXCEEDED (Message 43290)
Posted 28 Aug 2020 by pvh
Post:
I am getting those too. Plenty of room on the disk, so that is not the problem... One example is w-c0.004_0.000_job.B2_2012_rerun_c0.004_0.000.4415__48__s__64.282_59.312__4.1_6.1__6__4.94505_1_sixvf_boinc15045_0
2) Message boards : Number crunching : Tasks exceeding disk limit (Message 26793)
Posted 3 Oct 2014 by pvh
Post:
I have racked up 240 failed tasks now due to "Maximum disk usage exceeded"... I am temporarily disabling this project until this is fixed. Too many resources wasted here...
3) Message boards : Number crunching : 13 jan 2014 -- Error while computing (Message 26121)
Posted 13 Jan 2014 by pvh
Post:
Looks like all the wsuper_nuebb010 units crash. At least do they for me.
4) Message boards : Number crunching : Big problem: work units running with negative time. (Message 25797)
Posted 7 Sep 2013 by pvh
Post:
Yet get Test4Theory@home to work? I very quickly gave up on that when I noticed that around 50% of WUs were failing. This virtualbox system seems to be very flaky.
5) Message boards : Number crunching : Big problem: work units running with negative time. (Message 25794)
Posted 7 Sep 2013 by pvh
Post:
I run BOINC 7.0.65 on openSUSE 12.3. It runs just fine. Did you install the correct libraries? You need these:

libwx_baseu-2_8-0-wxcontainer-2.8.12-17.1.1.x86_64
libwx_baseu_net-2_8-0-wxcontainer-2.8.12-17.1.1.x86_64
libwx_gtk2u_adv-2_8-0-wxcontainer-2.8.12-17.1.1.x86_64
libwx_gtk2u_core-2_8-0-wxcontainer-2.8.12-17.1.1.x86_64
libwx_gtk2u_html-2_8-0-wxcontainer-2.8.12-17.1.1.x86_64
wxWidgets-wxcontainer-compat-lib-config-2.8.12-17.1.1.x86_64
6) Message boards : Number crunching : Big problem: work units running with negative time. (Message 25791)
Posted 7 Sep 2013 by pvh
Post:
Thanks for all the (detailed) feedback. Looks like a Linux problem on
"some" Linux systems. We tested on basically RedHat 6.


I assume you mean RHEL 6 here? They tend to have very conservative software choices in their stack (meaning very old software). Most users will not be running that. May I suggest putting some more cutting edge Linux distros in your testbed (at least part of it)? Fedora core, Ubuntu, or openSUSE could be good choices... They would be closer to what your users are using.
7) Message boards : Number crunching : Big problem: work units running with negative time. (Message 25755)
Posted 4 Sep 2013 by pvh
Post:
I got more WUs that all show the same problem. This is in the logs (repeated a zillion times):

2013-09-04T21:01:57 CEST | LHC@home 1.0 | Restarting task sd_sixt5_890_1.6_4D_err__26__s__62.31_60.32__8_10__6__15_1_sixvf_boinc2180_0 using sixtrack version 44603 (pni) in slot 30
2013-09-04T21:01:59 CEST | LHC@home 1.0 | Task sd_sixt5_890_1.6_4D_err__26__s__62.31_60.32__2_4__6__65_1_sixvf_boinc2139_0 exited with zero status but no 'finished' file
2013-09-04T21:01:59 CEST | LHC@home 1.0 | If this happens repeatedly you may need to reset the project.


Each WU crashes as soon as it starts and then gets restarted indefinitely (I have never seen anything good come out of that policy, especially the indefinite part, but that is a different discussion...). This problem is 100% reproducible. Needless to say that resetting the project didn't help (does it ever?). I am disabling this project until I see a message here that this is solved or that we have reverted to a different client.
8) Message boards : Number crunching : Big problem: work units running with negative time. (Message 25749)
Posted 4 Sep 2013 by pvh
Post:
I too had 4 WUs thoroughly stuck at 0% for over 10 hours. They were consuming 0% CPU despite the fact that BOINC claimed that they were running. I aborted these units. There definitely is a problem with the new client. I successfully ran sixtrack units before. This is on openSUSE 12.3 with BOINC 7.0.65.



©2024 CERN