Posts by [AF>Le_Pommier] Jerome_C2005

Mersenneplustwo home page
log in
1) Message boards : News : New server (Message 537)
Posted 83 days ago by Profile [AF>Le_Pommier] Jerome_C2005
I suppose you mean "66k" ? it was -60k for me :(

I assume we must "Always look on the bright side of life" : using a 13 years old laptop as a server, we could have lost hundreds thousands of credits since the beginning of the project :)
2) Message boards : Number crunching : All taks failing on linux host (Message 424)
Posted 555 days ago by Profile [AF>Le_Pommier] Jerome_C2005
Welcome :)

It seems the same issue happened on other project (WCG, ibercivis, for those I'm aware) with debian 10 hosts.

I *think* that for the other host of mine I mentioned above where "it was working fine" I had already and precisely applied that same fix, found in the ibercivis forum, so that's why it was already working with your project.

The forum topic is here (it includes a link to a WCG topic where the initial solution was given).

I reported there that it was working, and then it stopped working again but the errors were completely different so I think it was another issue with their app.
3) Message boards : Number crunching : All taks failing on linux host (Message 422)
Posted 556 days ago by Profile [AF>Le_Pommier] Jerome_C2005
For information this was fixed by

1. sudo nano /etc/default/grub
2. change the row
GRUB_CMDLINE_LINUX_DEFAULT="<existing text>"
by
GRUB_CMDLINE_LINUX_DEFAULT="<existing text> vsyscall=emulate"
3. save
4. sudo update-grub
5. sudo reboot
4) Message boards : Number crunching : All taks failing on linux host (Message 421)
Posted 561 days ago by Profile [AF>Le_Pommier] Jerome_C2005
Hi

I have a linux debian 10 host with 2 Intel Xeon CPU E5645 @ 2.40GHz + 20 GB RAM where *all the tasks* (more than 250) are failing after a few seconds :

<core_client_version>7.16.6</core_client_version>
<![CDATA[
<message>
process got signal 11</message>
<stderr_txt>
SIGSEGV: segmentation violation
SIGABRT: abort called
SIGABRT: abort called
SIGABRT: abort called
SIGABRT: abort called
SIGABRT: abort called
SIGABRT: abort called

(repeated many time)

I have another linux debian 10 host with a slightly better CPU (2 Intel Xeon CPU X5650 @ 2.67GHz with only 8 GB RAM) where it works fine !

Any idea of what may happen ?
5) Message boards : News : Project stopped (hopefully temporarily) (Message 401)
Posted 695 days ago by Profile [AF>Le_Pommier] Jerome_C2005
Hi

I have a modest 50 terminated tasked in "ready to validate" status (uploaded already) 6 days overdue that are just "staying there", I have to abandon them ? but I also have some "automatically abandoned tasks" that are also "staying there" and not removed from my boinc when it connects to the project...

I'm pretty sure the boinc server software has options to limit the workload in different ways, why don't you try your luck with the boinc_projects list ?

https://boinc.berkeley.edu/trac/wiki/EmailLists




Return to WEP-M+2 Project main page


Copyright © 2021 M+2 Group