Posts by YAG

1) Message boards : Number crunching : Expired SSL Certificate (Message 1752) Posted 29 May 2022 by YAG Post: Just to mention this: The project server quchempedia.univ-angers.fr occasionally presents an SSL certificate that has expired at Tue, 26 Apr 2022 18:01:10 UTC. A 2nd certificate used as an option will soon expire at Sun, 26 Jun 2022 07:54:29 UTC. In addition the server does only support TLS v1.2. It would be good to switch to TLS v1.3 as preferred protocol. +1 You will prevent new volunteers from crunching for getting the code needed to subscribe in Boinc.
2) Questions and Answers : Unix/Linux : BOINC 7.18.1 causes invalids (Message 1683) Posted 28 Feb 2022 by YAG Post: I do not know. I am a Debian 11 user. I am afraid future linux distributions will use the strict mode and will expect that the several projects will update their apps for using only authorized paths.
3) Questions and Answers : Unix/Linux : BOINC 7.18.1 causes invalids (Message 1681) Posted 24 Feb 2022 by YAG Post: Hey, Jim1348! Nice to meet you. We was talking five months ago about, I think, the same issue. Sebastien provided a solution and now I think we know the root cause. I copy/paste here what I think important: To fix this issue, I edited the file /lib/systemd/system/boinc-client.service and replaced ProtectSystem=strict by ProtectSystem=full systemctl stop boinc-client sed -i 's/ProtectSystem=strict/ProtectSystem=full/g' /lib/systemd/system/boinc-client.service systemctl daemon-reload systemctl start boinc-client Reading the systemd.exec man page I saw it is recommended, due to security measures, to use the strict parameter, and also that that parameter was introduced in 2016. The distinct Linux distributions are incorporating the recomendations, and if the project of Boinc you want to run tries to store data in a path not authorized by the "strict" parameter, the app fails. So the issue finally depends on the systemd version, the Boinc version and the project you are executing.
4) Questions and Answers : Unix/Linux : Workunits failure after upgrading Debian to 11 (bullseye) (Message 1624) Posted 9 Jan 2022 by YAG Post: {AF>WildWildWest}Sebastien wrote: Look at this post It could fix your problem. You rocked it, Sebastien! I am going to crunch again for QuChemPedia. Reading the systemd.exec man page I saw it is recommended, due to security measures, to use the strict parameter, and also that that parameter was introduced in 2016. Because now it is the recommended (and most secure) option, I think the best thing to do here is to update the QuChemPedIA executable for not writing but in the allowed directories. Again, most of users will not check in the forums for the solution. Nevertheless, I will keep computing for QuChemPedIA even while the app is not upgraded. Thanks a lot!
5) Questions and Answers : Unix/Linux : Workunits failure after upgrading Debian to 11 (bullseye) (Message 1620) Posted 9 Jan 2022 by YAG Post: Thank you anyway, it is always good to know that is failing in a new OS. It is sad to say that all Debian 10 devices and other devices went out of the top computers. As long as devices are being upgrade, they end working for QuChemPedIA. The actual workaround (a Virtual Machine, with Virtual Box or others) is a hard workaround for a basic user, and most of the ones will not look at the forum for knowing why the tasks were not working. As I said on 1 Sep 2021, 20:20:00 UTC , I still will keeping an eye on this project, I love it. And as soon as I receive a notification in this thread about it is solved and the project is still having software maintenance I will start computing for it and sharing the good new in the forums I am participating.
6) Questions and Answers : Unix/Linux : Workunits failure after upgrading Debian to 11 (bullseye) (Message 1475) Posted 12 Sep 2021 by YAG Post: I finally created a Virtual Machine with VirtualBox, with Debian 9 (Linux 4.9.0-16-amd64, Boinc 7.6.33), and I could execute successfully a test task (200 credit). I am sure Debian 10 will work too, as I was using Debian 10. Virtualization is a valid workaround. When using virtualization, I prefer to run projects that were created with it in mind from the start, as Cosmology. I will still keeping an eye on further developments of this QuChemPedIA, because it is a good idea. I love to support basic research, and quantic is an uncharted territory. I hope the project will find the resources for keeping it alive. Thank you all for your contributions to this thread, and thanks to the QuChemPedIA team for this amazing project. I wish you the best.
7) Questions and Answers : Unix/Linux : Workunits failure after upgrading Debian to 11 (bullseye) (Message 1467) Posted 4 Sep 2021 by YAG Post: It would be nice to know if your computer with the i9-10900F CPU is able to end a task successfully. I saw in the LHC forum the following message: (...) After upgrading this machine to Linux kernel 5.4.0-58 (from 5.4.0-52) I started getting failures, so I had to abort them. (...) There is something strange about that upgrade. It is causing problems for me on QuChemPedIA also on two machines, a Ryzen 3900X and the i7-9700. (Both are on Ubuntu 18.04.5).
8) Questions and Answers : Unix/Linux : Workunits failure after upgrading Debian to 11 (bullseye) (Message 1463) Posted 3 Sep 2021 by YAG Post: Jim1348, your new machine has the same Ubuntu version but a newer Linux kernel: 5.11.0-27. It could be the kernel version, as Tullio said... And, very important think, the issue is affecting to several Linux distributions, not only Debian.
9) Questions and Answers : Unix/Linux : Workunits failure after upgrading Debian to 11 (bullseye) (Message 1461) Posted 1 Sep 2021 by YAG Post: Interesting, Jim1348. I do not know the reason, Tullio, and there are other relevant changes in the Debian upgrade. Damotbe told the generator of the project is EvoMol. It was developed on Ubuntu 18.04+ and it is written in Python. Several packages built with Python 2 were removed in Debian 11 (bullseye): «Python 2 is already beyond its End Of Life, and will receive no security updates. It is not supported for running applications, and packages relying on it have either been switched to Python 3 or removed. However, Debian bullseye does still include a version of Python 2.7, as well as a small number of Python 2 build tools such as python-setuptools. These are present only because they are required for a few application build processes that have not yet been converted to Python 3.» I am sure this incident will be solved soon, because 15 of the 20 top computers in average credit are using Debian 10 (Buster).
10) Questions and Answers : Unix/Linux : Workunits failure after upgrading Debian to 11 (bullseye) (Message 1458) Posted 31 Aug 2021 by YAG Post: I am a Debian user with three computers (two P.C. and a laptop). I executed successfully tasks in the three computers. Recently, I upgraded Debian from 10 (buster) to 11 (bullseye). When upgrading, the boinc client and other projects (Rosetta & Einstein) are working as expected, but not QuChemPedIA. I tried to detach and attach again the project, and the issue persists. Now, the details. This is my laptop. All the tasks have "invalid" as output, and all of them last no more than 1s of CPU time. I will mention some examples. I could not see an easy way to fix it in the stderr logs of the tasks: * 7617565 * 7617848 * 7618125