Message boards : Questions and problems : boinc won't start after reboot for any reason
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 10 Jan 21 Posts: 20 |
Boinc won't start after reboot. If I completely reinstall Mint Linux and then reinstall boinc it starts with no problem and runs einstein@home perfectly..until I reboot for any reason. Then boinc won't start. Everything else runs...Firefox, Thunderbird, etc just not boinc -------------------------- Dell Optiplex 9010 running Linux Mint 22.3 Zena \n \l --------------------------- steve@skynet:~$ lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 36 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Vendor ID: GenuineIntel Model name: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz CPU family: 6 Model: 58 -------------------------------------------- steve@skynet:~$ sudo dmidecode -t memory | grep -i size [sudo] password for steve: Size: 4 GB Size: 8 GB Size: 4 GB Size: 8 GB ----------------------------------------------- steve@skynet:~$ tail -f /var/log/syslog 2026-05-03T15:12:19.974577-05:00 skynet systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. 2026-05-03T15:12:19.974959-05:00 skynet systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. 2026-05-03T15:13:06.131786-05:00 skynet PackageKit: daemon quit 2026-05-03T15:13:06.137322-05:00 skynet systemd[1]: packagekit.service: Deactivated successfully. 2026-05-03T15:14:45.530596-05:00 skynet systemd[1603]: gnome-terminal-server.service: Consumed 1.665s CPU time. 2026-05-03T15:14:49.634270-05:00 skynet dbus-daemon[1624]: [session uid=1000 pid=1624] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.124' (uid=1000 pid=4171 comm="/usr/bin/gnome-terminal.real" label="unconfined") 2026-05-03T15:14:49.650872-05:00 skynet systemd[1603]: Starting gnome-terminal-server.service - GNOME Terminal Server... 2026-05-03T15:14:49.864605-05:00 skynet dbus-daemon[1624]: [session uid=1000 pid=1624] Successfully activated service 'org.gnome.Terminal' 2026-05-03T15:14:49.865073-05:00 skynet systemd[1603]: Started gnome-terminal-server.service - GNOME Terminal Server. 2026-05-03T15:14:49.942366-05:00 skynet systemd[1603]: Started vte-spawn-ecd17bc9-399e-45b2-a97e-335620eb3de0.scope - VTE child process 4187 launched by gnome-terminal-server process 4177. 2026-05-03T15:15:15.280630-05:00 skynet systemd[1]: Started [email protected] - Process Core Dump (PID 4205/UID 0). 2026-05-03T15:15:15.431865-05:00 skynet systemd-coredump[4206]: Process 4201 (boincmgr) of user 1000 dumped core.#012#012Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2build1.1.amd64#012Module libsystemd.so.0 from deb systemd-255.4-1ubuntu8.15.amd64#012Module libgcc_s.so.1 from deb gcc-14-14.2.0-4ubuntu2~24.04.1.amd64#012Module libatomic.so.1 from deb gcc-14-14.2.0-4ubuntu2~24.04.1.amd64#012Module libstdc++.so.6 from deb gcc-14-14.2.0-4ubuntu2~24.04.1.amd64#012Stack trace of thread 4201:#012#0 0x0000738b1549eb2c __pthread_kill_implementation (libc.so.6 + 0x9eb2c)#012#1 0x0000738b1544527e __GI_raise (libc.so.6 + 0x4527e)#012#2 0x0000738b154288ff __GI_abort (libc.so.6 + 0x288ff)#012#3 0x00006153cf538930 n/a (boincmgr + 0x4ac930)#012#4 0x00006153d055c12e g_log_writer_default (boincmgr + 0x14d012e)#012#5 0x00006153d05598e7 g_log_structured_array (boincmgr + 0x14cd8e7)#012#6 0x00006153d055a6bf g_log_structured_standard (boincmgr + 0x14ce6bf)#012#7 0x00006153cfe630fb n/a (boincmgr + 0xdd70fb)#012#8 0x00006153d04fc119 g_type_create_instance (boincmgr + 0x1470119)#012#9 0x00006153d04dcc90 g_object_new_with_properties (boincmgr + 0x1450c90)#012#10 0x00006153d04de5d1 g_object_new (boincmgr + 0x14525d1)#012#11 0x00006153cfe63e82 _gdk_wayland_display_open (boincmgr + 0xdd7e82)#012#12 0x00006153cfea1080 gdk_display_manager_open_display (boincmgr + 0xe15080)#012#13 0x00006153cfb9836a gtk_init_check (boincmgr + 0xb0c36a)#012#14 0x00006153cf844cf9 n/a (boincmgr + 0x7b8cf9)#012#15 0x00006153cf9f00c0 n/a (boincmgr + 0x9640c0)#012#16 0x00006153cf9f0a8b n/a (boincmgr + 0x964a8b)#012#17 0x00006153cf545982 main (boincmgr + 0x4b9982)#012#18 0x0000738b1542a1ca __libc_start_call_main (libc.so.6 + 0x2a1ca)#012#19 0x0000738b1542a28b __libc_start_main_impl (libc.so.6 + 0x2a28b)#012#20 0x00006153cf561e1a _start (boincmgr + 0x4d5e1a)#012#012Stack trace of thread 4204:#012#0 0x0000738b154ed937 __GI___getdents64 (libc.so.6 + 0xed937)#012#1 0x0000738b154ed9c7 __GI___readdir64 (libc.so.6 + 0xed9c7)#012#2 0x00006153d0237c41 n/a (boincmgr + 0x11abc41)#012#3 0x00006153d0239b5f n/a (boincmgr + 0x11adb5f)#012#4 0x00006153d0885c25 n/a (boincmgr + 0x17f9c25)#012#5 0x00006153d0886e19 n/a (boincmgr + 0x17fae19)#012#6 0x00006153d0888476 n/a (boincmgr + 0x17fc476)#012#7 0x00006153d08896df n/a (boincmgr + 0x17fd6df)#012#8 0x00006153d0878f0f n/a (boincmgr + 0x17ecf0f)#012#9 0x00006153d088134f n/a (boincmgr + 0x17f534f)#012#10 0x00006153d02377b3 n/a (boincmgr + 0x11ab7b3)#012#11 0x00006153d0237df9 n/a (boincmgr + 0x11abdf9)#012#12 0x00006153d0228938 n/a (boincmgr + 0x119c938)#012#13 0x00006153d0228c78 FcInitLoadConfigAndFonts (boincmgr + 0x119cc78)#012#14 0x00006153d021842e n/a (boincmgr + 0x118c42e)#012#15 0x00006153cffb5c45 n/a (boincmgr + 0xf29c45)#012#16 0x00006153d0589999 n/a (boincmgr + 0x14fd999)#012#17 0x0000738b1549caa4 start_thread (libc.so.6 + 0x9caa4)#012#18 0x0000738b15529c6c __clone3 (libc.so.6 + 0x129c6c)#012ELF object binary architecture: AMD x86-64 2026-05-03T15:15:15.435338-05:00 skynet systemd[1]: [email protected]: Deactivated successfully. Stephen Hawkins 73 49 111 01001001 |
DaveSend message Joined: 28 Jun 10 Posts: 3289
|
Boinc won't start after reboot. I recently tried mint22.3 in a VM and didn't see this problem. It is possible I avoided this by compiling the latest master of 8.3.0 from source. Did you reboot with BOINC running? In your home directory is there a file BOINC MANAGER-steve There may be an underscore or hyphen between boinc and manager and hyphen after manager may be an underscore, I can't remember. If such a file exists, deleting it will let BOINC start normally. I won't check to see what the exact filename is at the moment because I don't want to risk losing the work that is running. |
|
Send message Joined: 10 Jan 21 Posts: 20 |
Boinc and einstein@home were running fine on this computer and had been for quite some time. I had some updates one of which was a new kernel. I installed the updates successfully. Afterwards boinc would no longer start. That was the beginning of this problem. I have rebooted, redone the update the problem still existed. I finally in desperation reinstalled mint linux. Then reinstalled boinc. Everything worked fine and I restated einstein@home. Everything worked fine until I did a reboot then I was back to the original problem boinc would no longer start. Stephen Hawkins 73 49 111 01001001 |
Vitalii KoshuraSend message Joined: 29 Mar 17 Posts: 209
|
Have you tried installing BOINC from here? BOINC maintainer. For any insight, check my BOINC Development Blog. |
Copyright © 2026 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.