Message boards : Puzzles and science : MNEMOSYNE
Message board moderation
Previous · 1 · 2 · 3 · 4
| Author | Message |
|---|---|
|
25 years old Send message Joined: 27 Sep 26 Posts: 349 Credit: 5,210,013 RAC: 137,017 |
Emulation needs to be enabled in Docker/Podman settings.
|
|
51 years old Send message Joined: 28 Sep 26 Posts: 67 Credit: 45,860,229 RAC: 928,524 |
Ok. And how do I do that? |
|
25 years old Send message Joined: 27 Sep 26 Posts: 349 Credit: 5,210,013 RAC: 137,017 |
Check your Docker settings; you'll see it there.
|
|
51 years old Send message Joined: 28 Sep 26 Posts: 67 Credit: 45,860,229 RAC: 928,524 |
Ok I will have to ask ChatGPT how to do that with Podman when I get home in a couple of days. Until then I'm happy to see that the Linux for x86 version is back. My Laptop started a task... |
rilianSend message Joined: 28 Sep 26 Posts: 261 Credit: 43,482,494 RAC: 474,864 |
In reply to Drago75's message of 2 Nov 2026: Ok I will have to ask ChatGPT how to do that with Podman when I get home in a couple of days. Until then I'm happy to see that the Linux for x86 version is back. My Laptop started a task... it's really good idea. i had weird issues with docker and tried to solve that with chatgpt, but eventually it suggested to try podman and it worked like a charm! I crunch for Ukraine
|
rilianSend message Joined: 28 Sep 26 Posts: 261 Credit: 43,482,494 RAC: 474,864 |
In reply to Drago75's message of 2 Nov 2026: Ok I will have to ask ChatGPT how to do that with Podman when I get home in a couple of days. Until then I'm happy to see that the Linux for x86 version is back. My Laptop started a task... Hey not sure if helps but on one my computer with boinc 8.2.10 even when i installed Podman it did not show up Only after i updated boinc to latest 8.2.11 it detected podman Mon 2 Nov 21:28:06 2026 | | Docker: version 6.1.4 (podman) Mon 2 Nov 21:29:02 2026 | | Podman VM initialized I crunch for Ukraine
|
Tamagoch47 years old Send message Joined: 29 Sep 26 Posts: 68 Credit: 14,373,389 RAC: 423,227 |
|
|
25 years old Send message Joined: 27 Sep 26 Posts: 349 Credit: 5,210,013 RAC: 137,017 |
This project is allocated 1 core and 1.5 gb of RAM. It performs download parsing and compression, so we might encounter problems if it's marked as an NCI file.
|
Tamagoch47 years old Send message Joined: 29 Sep 26 Posts: 68 Credit: 14,373,389 RAC: 423,227 |
In reply to Alperen Yavuz's message of 4 Nov 2026: This project is allocated 1 core and 1.5 gb of RAM. It performs download parsing and compression, so we might encounter problems if it's marked as an NCI file. Can I do it on my side to test? I suppose the constant pausing could be more harmful (I hope I am wrong). Just took a look at the process: got 1.5 GB allocated but CPU load jumps between 0.2% and 1.2% I am always leaving 1 core free on machines doing similar jobs - MJ-12, residental proxies, VPN server etc. That's why I think Mnemosyne could easily fit within that core. Is it posiible to test that and make an option in device profiles to run Mnemosyne as NCI?
|
|
51 years old Send message Joined: 28 Sep 26 Posts: 67 Credit: 45,860,229 RAC: 928,524 |
Over the recent week I kept checking on the archiving activity of my Mnemosyne tasks but I couldn't find one that was actually doing anything other than waiting for work to be assigned to it. Also the pausing doesn't work. It starts over and runs for another 4:15h. So if repeatedly interrupted before reaching the end the task will run infinitely. Here is a report from today: **Mnemosyne v0.07: no observable archiving activity and pause/resume failures** I monitored Mnemosyne on Linux using BOINC 8.3.0 and rootless Podman 4.9.3. **Fresh, uninterrupted task: Result 10241829, host 192** Task: `mnemosyne_1794639903_1_0` The task ran for 4 h 15 min without suspension and validated successfully, receiving 25,000 credits. All 253 monitoring samples succeeded, but no download/upload worker processes or recently modified `wget.log` files were observed. Warrior selected `uploaderjp` and repeatedly performed HQ and Git update checks. No completed archiving items were documented. **Previously suspended task: Result 9759700, host 347** Task: `mnemosyne_1794142203_0_0` The wrapper repeatedly logged `pause command failed: -1`. On resumption, it restarted the container, including an explicit kill/start sequence after detecting `Up 2 hours`. Total reported runtime reached 10 h 2 min, although the configured session duration was four hours plus a 15-minute shutdown allowance. This task nevertheless validated successfully and received 25,000 credits. **Earlier validation failure: Result 9877741, host 192** Task: `mnemosyne_1794259503_0_0` This task also showed a failed pause and container restart. It finished locally with exit code 0, but the server reported a validation error. The validator’s rejection reason was not included in the available log. Could you investigate the pause/resume handling and check whether the archiving pipeline actually processes items? The uninterrupted test shows that the lack of observable archiving activity is not limited to previously suspended tasks. Full logs are available.
|
Tamagoch47 years old Send message Joined: 29 Sep 26 Posts: 68 Credit: 14,373,389 RAC: 423,227 |
How could it be possible to keep Mnemosyne runnig 24/7 if it gives up the allocated core to other projects on the host? ( I see the only way to set it to less than 1 CPU otherwise BOINC client is free to allocate that core elsewhere, as there is no special priority to Mnemosyne. How are you guys managing that? I was able to run it 24/7 only if there weren't any other CPU tasks active except Wuprop.
|
|
51 years old Send message Joined: 28 Sep 26 Posts: 67 Credit: 45,860,229 RAC: 928,524 |
I tried different setups as well. What I am doing at the moment is limiting the max concurrent tasks of let's say Potamos to max threads minus one so that there is always one available for Mnemosyne. This needs to go into the app_config.xml of BitBoinc or of the other project you are supporting together with Mnemosysne: <app> <name>potamos</name> <max_concurrent>11</max_concurrent> </app> |
|
Send message Joined: 7 Oct 26 Posts: 11 Credit: 6,000 RAC: 17 |
Try changing the Computing Preferences option "Switch between tasks every _____ minutes" to something like 999999 so that BOINC never stops a task for another. |
Henk Haneveld72 years old Send message Joined: 28 Sep 26 Posts: 31 Credit: 3,560,476 RAC: 84,073 |
In reply to signore2's message of 15 Nov 2026: Try changing the Computing Preferences option "Switch between tasks every _____ minutes" to something like 999999 so that BOINC never stops a task for another. That works except when you have work that is close to its deadline and needs to run to finish on time. Than the setting is ignored. However if you also set the Preferences option "Leave non-GPU tasks in memory while suspended" to enabled then the suspended work should resume from where it stopped. |