Message boards : Puzzles and science : MNEMOSYNE
Message board moderation
Previous · 1 · 2 · 3 · 4 · Next
| Author | Message |
|---|---|
Henk Haneveld72 years old Send message Joined: 28 Sep 26 Posts: 31 Credit: 3,560,476 RAC: 84,073 |
In reply to entity's message of 25 Oct 2026: Is the download happening inside the container? What should I look for and where is it stored? |
|
25 years old Send message Joined: 27 Sep 26 Posts: 349 Credit: 5,210,013 RAC: 137,017 |
There is nothing special to do; you just need to let it run. Make sure your internet connection is unlimited.
|
|
Send message Joined: 1 Oct 26 Posts: 35 Credit: 86,317,024 RAC: 555,648 |
I had 5 instances running on Ubuntu 26.04.1 Linux systems. All 5 ran for 4 hours and ended but then were marked as invalid. |
|
25 years old Send message Joined: 27 Sep 26 Posts: 349 Credit: 5,210,013 RAC: 137,017 |
Yes, because they haven’t accomplished any work; they’ve simply wasted time. I fixed this problem.
|
[SG]KidDosCrunchSend message Joined: 8 Oct 26 Posts: 29 Credit: 87,709,633 RAC: 1,721,339 |
Installed Docker Per User Installed BUDA Restart Laptop and Restart Boinc. 26.10.2026 08:42:55 | | Docker detection in docker-desktop: 26.10.2026 08:42:55 | | - cmd: podman --version 26.10.2026 08:42:55 | | - output: /bin/sh: podman: not found 26.10.2026 08:42:55 | | Docker detection in docker-desktop: 26.10.2026 08:42:55 | | - cmd: docker --version 26.10.2026 08:42:55 | | - output: It looks like you have tried to invoke the docker CLI from the docker-desktop WSL2 distribution. This is not supported.Please invoke the docker CLI from the Windows Command Prompt, PowerShell, or other compatible terminals.If you wish to interact with Docker Desktop from a third-party WSL2 distribution, such as Ubuntu, please enable the Docker Desktop WSL2 integration for it. See: https://docs.docker.com/desktop/wsl/#enabling-docker-support-in-wsl-2-distros 26.10.2026 08:42:55 | | Windows processor group 0: 32 processors 26.10.2026 08:42:55 | | Computer name: HW0101C001 26.10.2026 08:42:55 | | Processor: 32 GenuineIntel 13th Gen Intel(R) Core(TM) i9-13900HX [Family 6 Model 183 Stepping 1] 26.10.2026 08:42:55 | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush acpi mmx fxsr sse sse2 ss htt tm pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 movebe popcnt aes f16c rdrandsyscall nx lm avx avx2 adx gfni vaes vpclmulqdq tm2 pbe fsgsbase bmi1 smep bmi2 26.10.2026 08:42:55 | | OS: Microsoft Windows 11: Professional x64 Edition, (10.00.26300.00) 26.10.2026 08:42:55 | | Memory: 63.71 GB physical, 67.71 GB virtual 26.10.2026 08:42:55 | | Disk: 3.64 TB total, 1.48 TB free 26.10.2026 08:42:55 | | Local time is UTC +1 hours 26.10.2026 08:42:55 | | Usable WSL distros: 26.10.2026 08:42:55 | | - docker-desktop (WSL 2) (default) 26.10.2026 08:42:55 | | - OS: Linux (Docker Desktop) 26.10.2026 08:42:55 | | Some projects require Docker; we recommend that you install it. 26.10.2026 08:42:55 | PrimeGrid | Found app_config.xml What is wrong? |
[SG]KidDosCrunchSend message Joined: 8 Oct 26 Posts: 29 Credit: 87,709,633 RAC: 1,721,339 |
with installed BUDA, I meant https://github.com/BOINC/boinc-buda-runner-wsl |
[SG]KidDosCrunchSend message Joined: 8 Oct 26 Posts: 29 Credit: 87,709,633 RAC: 1,721,339 |
I also followed https://docs.docker.com/desktop/wsl/#enabling-docker-support-in-wsl-2-distros without success. Still the same error messages. |
Stony666Send message Joined: 30 Sep 26 Posts: 62 Credit: 337,396,796 RAC: 9,119,508 |
Hi, i run some instaces of boinc on the same host. Each on a different port. But all ended up with an error Do we need an app_config.xml with a port definition? There are many more of the bold line... what filesystem is read only for the app? =========== ... /app/run.sh: 25: cannot create /app/fraction_done: Read-only file system /app/run.sh: 25: cannot create /app/fraction_done: Read-only file system /app/run.sh: 25: cannot create /app/fraction_done: Read-only file system 2026-10-26 07:46:05,685 - seesaw.warrior - DEBUG - Update warrior hq. 2026-10-26 07:46:05,686 - seesaw.warrior - DEBUG - Warrior ID ''. 2026-10-26 07:46:05,695 - seesaw.warrior - DEBUG - Update project. 2026-10-26 07:46:05,695 - seesaw.warrior - DEBUG - Check project has update telegram 2026-10-26 07:46:05,708 - seesaw.warrior - DEBUG - git fetch 2026-10-26 07:46:05,806 - seesaw.warrior - DEBUG - Select project telegram 2026-10-26 07:46:06,260 - seesaw.warrior - DEBUG - False 2026-10-26 07:56:05,685 - seesaw.warrior - DEBUG - Update warrior hq. 2026-10-26 07:56:05,686 - seesaw.warrior - DEBUG - Warrior ID ''. 2026-10-26 07:56:05,802 - seesaw.warrior - DEBUG - Select project telegram /app/run.sh: 35: cannot create /project/mnemosyne_1792986006_1_0_r916432147_0: Read-only file system /app/run.sh: 36: cannot create /app/fraction_done: Read-only file system stderr end running docker command: container rm boinc__bitboinc.athena.org.tr__mnemosyne_1792986006_1_0 program: podman command output: time="2026-10-26T09:01:13+01:00" level=warning msg="The cgroupv2 manager is set to systemd but there is no systemd user session available" time="2026-10-26T09:01:13+01:00" level=warning msg="For using systemd, you may need to log in using a user session" time="2026-10-26T09:01:13+01:00" level=warning msg="Alternatively, you can enable lingering with: `loginctl enable-linger 128` (possibly as root)" time="2026-10-26T09:01:13+01:00" level=warning msg="Falling back to --cgroup-manager=cgroupfs" time="2026-10-26T09:01:13+01:00" level=warning msg="The cgroupv2 manager is set to systemd but there is no systemd user session available" time="2026-10-26T09:01:13+01:00" level=warning msg="For using systemd, you may need to log in using a user session" time="2026-10-26T09:01:13+01:00" level=warning msg="Alternatively, you can enable lingering with: `loginctl enable-linger 128` (possibly as root)" time="2026-10-26T09:01:13+01:00" level=warning msg="Falling back to --cgroup-manager=cgroupfs" boinc__bitboinc.athena.org.tr__mnemosyne_1792986006_1_0 2026-10-26 09:01:13 (362030): called boinc_finish(0) </stderr_txt> <message> upload failure: <file_xfer_error> <file_name>mnemosyne_1792986006_1_0_r916432147_0</file_name> <error_code>-161 (not found)</error_code> </file_xfer_error> </message> |
Stony666Send message Joined: 30 Sep 26 Posts: 62 Credit: 337,396,796 RAC: 9,119,508 |
Please have a look on my post above. |
Henk Haneveld72 years old Send message Joined: 28 Sep 26 Posts: 31 Credit: 3,560,476 RAC: 84,073 |
In the project info it says that a result can be suspended and resumed. I do not think this is working as it should. Take a look at: https://bitboinc.athena.org.tr/result.php?resultid=8443236 It did resume but then ended long before it reached the 4 hours mark but on the project stats page it shows the run time plus the time is was suspended There are also a lot of debug messages in the result file. Is that correct or is there also something wrong with the processing. It did valid . |
|
25 years old Send message Joined: 27 Sep 26 Posts: 349 Credit: 5,210,013 RAC: 137,017 |
Fixed.
|
|
Send message Joined: 1 Oct 26 Posts: 35 Credit: 86,317,024 RAC: 555,648 |
In reply to Alperen Yavuz's message of 26 Oct 2026: Yes, because they haven’t accomplished any work; they’ve simply wasted time. I ran 6 more and they all ended with validate errors. Why won't they validate? |
|
25 years old Send message Joined: 27 Sep 26 Posts: 349 Credit: 5,210,013 RAC: 137,017 |
You need to upload more than 2 MB per session; otherwise, it will be marked as invalid. ArchiveTeam probably banned you for a few hours because you were running multiple tasks on the same IP address.
|
|
Send message Joined: 1 Oct 26 Posts: 35 Credit: 86,317,024 RAC: 555,648 |
I'm assuming then that if one has multiple machines you can only run one instance of the program per site, not one per machine. Is that correct? Is there anyway we can get some diagnostic information out of this program to help us diagnose issues? |
|
25 years old Send message Joined: 27 Sep 26 Posts: 349 Credit: 5,210,013 RAC: 137,017 |
Yes, as far as I can tell the limits that matter here are per public IP address, not per computer. The Archive Team’s servers and the sites being saved rate-limit by IP, so several machines behind one connection share the same limit. Our server only allows one session per computer, it does not look at the IP. A sensible setup for now is one or two sessions per internet connection. Diagnostics: open the result page of a finished task (the “Stderr output” part). Since version 5 it shows a line starting with mnemosyne diag (whether the container’s folders are writable), and since version 6 also the last lines of the Warrior’s own log and a summary line with the running time, the time spent suspended and the bytes received and sent. If a session is invalid, the summary line tells you why: it needs at least 2 MB of traffic and enough running time. Please post such a result link if something looks wrong.
|
|
Send message Joined: 1 Oct 26 Posts: 35 Credit: 86,317,024 RAC: 555,648 |
Thank you so much for the information. That is information we can work with. I couldn't see any of the information you described because all the invalid work units were the .04 version. I will limit it to one per IP and maybe expand by one session later. Once again, thank you for information |
rilianSend message Joined: 28 Sep 26 Posts: 261 Credit: 43,482,494 RAC: 474,864 |
|
|
25 years old Send message Joined: 27 Sep 26 Posts: 349 Credit: 5,210,013 RAC: 137,017 |
Done. Thx.
|
rilianSend message Joined: 28 Sep 26 Posts: 261 Credit: 43,482,494 RAC: 474,864 |
BitBoinc Mnemosyne on macOS 27 / Apple Silicon: Solved with Podman I got BitBoinc’s Mnemosyne (web archiving, ArchiveTeam Warrior) tasks working on my Apple Silicon MacBook Pro M4 Pro running macOS 27. Here’s what I did. My setup []Hardware: MacBook Pro M4 Pro, 24 GB RAM []OS: macOS 27.0 []BOINC: 8.2.11 (ARM64) []Docker Desktop: Installed and working under my regular user account []VirtualBox: 7.1.8 []Project: BitBoinc — Mnemosyne
Message from server: Docker not present Docker worked normally in my user account, but BOINC runs as the separate macOS service account [font=Courier]boinc_master[/font]. Testing Docker from that account confirmed it couldn’t access Docker Desktop’s API socket: permission denied while trying to connect to the Docker API The socket [font=Courier]/var/run/docker.sock[/font] was a symlink to Docker Desktop’s per-user socket under [font=Courier]~/.docker/run/docker.sock[/font]. The solution: Install Podman I installed Podman using the BOINC Podman instructions for macOS. Initially, I manually ran: podman machine init podman machine start Podman started successfully but warned that another process was already listening on the default Docker API socket because Docker Desktop was running. BOINC has its own Podman integration and manages its own VM. Afterward, BOINC initialized its Podman environment. Successful result The BOINC Event Log showed: 12:09:20 | Podman VM initialized 12:09:46 | bitboinc | Scheduler request completed: got 1 new tasks 12:09:48 | bitboinc | Started download of mnemosyne_docker_wrapper_1_arm64-apple-darwin 12:09:52 | bitboinc | Finished download of mnemosyne_docker_wrapper_1_arm64-apple-darwin 12:09:53 | bitboinc | Starting task mnemosyne_1793030106_4_0 Previously, the scheduler rejected the computer with [font=Courier]Docker not present[/font]. After Podman initialized, the scheduler granted a task and BOINC downloaded the required Mnemosyne files. Final result: BOINC detected Podman, initialized its Podman VM, and successfully received and started a Mnemosyne task. Takeaways
[]Docker Desktop working in your regular macOS account doesn’t necessarily mean BOINC’s service account can access its Docker API socket. []Podman provides a Docker-compatible interface that BOINC can detect. []BOINC’s Podman integration can initialize its own VM. []The initial [font=Courier]Docker not present[/font] message was followed by successful task allocation after Podman initialized.
I crunch for Ukraine
|
NichanSend message Joined: 6 Oct 26 Posts: 16 Credit: 2,177,741 RAC: 56,607 |
Si c'etait une tache en nci , ce serait nettement mieux, je trouve ca dommage de monopoliser un coeur cpu pour cela |