boinc-client crash and reboot my machine

Message boards : Questions and problems : boinc-client crash and reboot my machine
Message board moderation

To post messages, you must log in.

1 · 2 · Next

AuthorMessage
sprzyswa

Send message
Joined: 2 Feb 21
Posts: 30
France
Message 107616 - Posted: 28 Mar 2022, 21:51:57 UTC

Hi,
For a few days my boinc-client application installed on Ubuntu 20.04 (5.4.0-105-generic) after a few minutes crash and reboot my machine although it had been working perfectly for a year, does anyone have an explanation ?
Sam.
Powered by Debian & Ubuntu 20.04 LTS
Boinc version 7.16.6 x86_64-pc-linux-gnu
ID: 107616 · Report as offensive
Bryn Mawr
Help desk expert

Send message
Joined: 31 Dec 18
Posts: 235
United Kingdom
Message 107617 - Posted: 28 Mar 2022, 22:04:20 UTC - in response to Message 107616.  

Hi,
For a few days my boinc-client application installed on Ubuntu 20.04 (5.4.0-105-generic) after a few minutes crash and reboot my machine although it had been working perfectly for a year, does anyone have an explanation ?
Sam.


How’s the cooling on your machine?

Do you have a monitor to show you the CPU temperature?
ID: 107617 · Report as offensive
sprzyswa

Send message
Joined: 2 Feb 21
Posts: 30
France
Message 107618 - Posted: 28 Mar 2022, 22:31:05 UTC - in response to Message 107617.  

Hi,

I use liquid cooling, CPU temperature is +/- 50° Celsius and CPU temperature is permanently displayed on the desktop.

I've checked memory, disks and swap status, I'm at about 50% memory usage (32Gb) I've tested running ONLY boinc-client to be sure it doesn't did not come from another application.

Sam.
Powered by Debian & Ubuntu 20.04 LTS
Boinc version 7.16.6 x86_64-pc-linux-gnu
ID: 107618 · Report as offensive
sprzyswa

Send message
Joined: 2 Feb 21
Posts: 30
France
Message 107619 - Posted: 28 Mar 2022, 22:42:06 UTC - in response to Message 107617.  

I also uninstalled and deleted the /var/lib/boinc-client directory and reinstalled boinc-client but it's still the same
Powered by Debian & Ubuntu 20.04 LTS
Boinc version 7.16.6 x86_64-pc-linux-gnu
ID: 107619 · Report as offensive
Bryn Mawr
Help desk expert

Send message
Joined: 31 Dec 18
Posts: 235
United Kingdom
Message 107629 - Posted: 29 Mar 2022, 15:12:48 UTC - in response to Message 107619.  

I also uninstalled and deleted the /var/lib/boinc-client directory and reinstalled boinc-client but it's still the same


Then it will be a case of looking at the logs but I’m struggling to work out how to allow Boinc to start normally for the test but stopping it from running and overwriting the log on restart.

I’ll think about that and hope someone else will jump in with the answer :-)
ID: 107629 · Report as offensive
Profile Keith Myers
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 17 Nov 16
Posts: 720
United States
Message 107630 - Posted: 29 Mar 2022, 17:29:55 UTC - in response to Message 107629.  
Last modified: 29 Mar 2022, 17:31:32 UTC

You should have the Log backup file stdoutdae.old in your /var/lib/boinc-client directory. That contains the backup sessions of the stdoutdae.txt which is the name of the current Event Log.
Mine goes back two weeks. I don't know how far back you need to look for older sessions. The file is size limited by cc_config.xml parameter default of 2MB. I have mine at 32MB.

<max_stdout_file_size>N</max_stdout_file_size>
Specify the maximum size of the standard out log file (stdoutdae.txt); default is 2 MB.
Sample: <max_stdout_file_size>3145728</max_stdout_file_size> equals 3 MB.
NB: A Client restart may be needed to have changes take effect!


ID: 107630 · Report as offensive
sprzyswa

Send message
Joined: 2 Feb 21
Posts: 30
France
Message 107634 - Posted: 29 Mar 2022, 20:02:02 UTC - in response to Message 107630.  

You should have the Log backup file stdoutdae.old in your /var/lib/boinc-client directory

No I have not stdoutdae.old file in my /var/lib/boinc-client directory !?

Sam.
Powered by Debian & Ubuntu 20.04 LTS
Boinc version 7.16.6 x86_64-pc-linux-gnu
ID: 107634 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 4874
United Kingdom
Message 107635 - Posted: 29 Mar 2022, 20:44:32 UTC - in response to Message 107634.  

The log history for Linux systemd installations is kept in the system journal.
ID: 107635 · Report as offensive
sprzyswa

Send message
Joined: 2 Feb 21
Posts: 30
France
Message 107637 - Posted: 29 Mar 2022, 22:33:10 UTC - in response to Message 107635.  

The log history for Linux systemd installations is kept in the system journal.

Ok, thanks but nothing wrong on syslog just this:

Mar 30 00:00:48 jupiter boinc[11481]: dir_open: Could not open directory 'locale' from '/var/lib/boinc-client'.

Sam.
Powered by Debian & Ubuntu 20.04 LTS
Boinc version 7.16.6 x86_64-pc-linux-gnu
ID: 107637 · Report as offensive
Profile Keith Myers
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 17 Nov 16
Posts: 720
United States
Message 107638 - Posted: 30 Mar 2022, 0:01:33 UTC - in response to Message 107635.  

The log history for Linux systemd installations is kept in the system journal.

Richard,
Any idea why my stdoutdae.txt and .old files are in my /var/lib/boinc-client in my RPi3 running Rasbian 32bit Bullseye OS. I believe it to be a standard systemd installation.


ID: 107638 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 4874
United Kingdom
Message 107639 - Posted: 30 Mar 2022, 7:12:37 UTC - in response to Message 107638.  

Richard,
Any idea why my stdoutdae.txt and .old files are in my /var/lib/boinc-client in my RPi3 running Rasbian 32bit Bullseye OS. I believe it to be a standard systemd installation.
I don't really know. I'm still very much a newbie on Linux, and I only have personal experience of the Debian / Ubuntu / Mint family of distros. My guess would be that it depends on the distro and the precise version of BOINC in use.

There's a note in the sources from February 2018:

Both Fedora and Debian have their own systemd units for boinc;
this is based on elements of both so we stop duplicating effort.

This also adds minimal confinement to protect the home directories.
There were a number of systemd changes around that time, which roughly equates to v7.10.xx of BOINC (which I had a hand in releasing). It probably depends on how closely the Rasbian maintainers followed those changes.
ID: 107639 · Report as offensive
sprzyswa

Send message
Joined: 2 Feb 21
Posts: 30
France
Message 107659 - Posted: 30 Mar 2022, 17:26:11 UTC

Hi,

I'm going to have to abandon the Boinc project because as soon as I launch boinc-client the machine reboot, no crash but a clean reboot...

Sam.
Powered by Debian & Ubuntu 20.04 LTS
Boinc version 7.16.6 x86_64-pc-linux-gnu
ID: 107659 · Report as offensive
sprzyswa

Send message
Joined: 2 Feb 21
Posts: 30
France
Message 107661 - Posted: 30 Mar 2022, 21:03:55 UTC

Hi,

The problem is solved, my home directory was corrupted, I put all my directory back with my username and group, restarted the machine and everything is OK.

Thanks for your help.

Sam.
Powered by Debian & Ubuntu 20.04 LTS
Boinc version 7.16.6 x86_64-pc-linux-gnu
ID: 107661 · Report as offensive
sprzyswa

Send message
Joined: 2 Feb 21
Posts: 30
France
Message 107679 - Posted: 1 Apr 2022, 12:02:55 UTC - in response to Message 107661.  

Sorry but the problem came back and seems to come from VirtualBox...

Sam.
Powered by Debian & Ubuntu 20.04 LTS
Boinc version 7.16.6 x86_64-pc-linux-gnu
ID: 107679 · Report as offensive
sprzyswa

Send message
Joined: 2 Feb 21
Posts: 30
France
Message 107689 - Posted: 3 Apr 2022, 0:09:15 UTC

Hi,

There seems to be a problem running boinc-client on Ubuntu 20.04 I think I will abandon this project...

Sam.
Powered by Debian & Ubuntu 20.04 LTS
Boinc version 7.16.6 x86_64-pc-linux-gnu
ID: 107689 · Report as offensive
MarkJ
Volunteer tester
Help desk expert

Send message
Joined: 5 Mar 08
Posts: 272
Australia
Message 107690 - Posted: 3 Apr 2022, 0:38:36 UTC
Last modified: 3 Apr 2022, 1:04:41 UTC

You know you can run BOINC without VirtualBox. Its only needed if the project in question only have that type of work unit. I'm still crunching for Rosetta although they have a "rosetta python projects" which uses vbox. I'm running their normal CPU work units only. VirtualBox allows you to run virtual machines. In the case of the various BOINC projects they supply work units which are a VM image.

The Linux versions of BOINC don't keep an old version of stdoutdae around. They use the standard Linux way of doing things. You can view the log by doing a "sudo journalctl --unit=boinc-client" command in a terminal or ssh session. The journal entries can go back quite some time (I have some from Sept 2021 on one machine).

As for directory naming on Raspberry Pi OS, they are following the Debian standard. Debian used to use /var/lib/boinc-client and other Linux distros use /var/lib/boinc. The later BOINC releases have both folders and a symlink from /var/lib/boinc to /var/lib/boinc-client so they are basically the same directory.
MarkJ
ID: 107690 · Report as offensive
sprzyswa

Send message
Joined: 2 Feb 21
Posts: 30
France
Message 107692 - Posted: 3 Apr 2022, 10:52:11 UTC - in response to Message 107690.  

You know you can run BOINC without VirtualBox. Its only needed if the project in question only have that type of work unit. I'm still crunching for Rosetta although they have a "rosetta python projects" which uses vbox. I'm running their normal CPU work units only. VirtualBox allows you to run virtual machines. In the case of the various BOINC projects they supply work units which are a VM image.

The Linux versions of BOINC don't keep an old version of stdoutdae around. They use the standard Linux way of doing things. You can view the log by doing a "sudo journalctl --unit=boinc-client" command in a terminal or ssh session. The journal entries can go back quite some time (I have some from Sept 2021 on one machine).

As for directory naming on Raspberry Pi OS, they are following the Debian standard. Debian used to use /var/lib/boinc-client and other Linux distros use /var/lib/boinc. The later BOINC releases have both folders and a symlink from /var/lib/boinc to /var/lib/boinc-client so they are basically the same directory.


Yes I know all that, I installed boinc-client on Debian 9.13 without problems but my machine is installed in Ubuntu 20.04 and even without installing VirtualBox the machine reboots after launching boinc-client...

Sam.
Powered by Debian & Ubuntu 20.04 LTS
Boinc version 7.16.6 x86_64-pc-linux-gnu
ID: 107692 · Report as offensive
computezrmle

Send message
Joined: 2 Feb 22
Posts: 43
Germany
Message 107693 - Posted: 3 Apr 2022, 11:29:05 UTC - in response to Message 107692.  

A (very long) while ago I had a power outage due to a heavy thunderstorm.
After that all my machines rebooted and seemed to work fine for a couple of weeks.
Then, as of a sudden, 1 machine crashed (rebooted) every time BOINC started a GPU task.

I finally could trace the error down to a corrupted filesystem (multiple sector allocation on the harddisk).
The solution was to
- backup all data
- reformat the disk
- restore all data
- force a reinstall of the OS, drivers and all applications

Since then the machine runs fine again.
ID: 107693 · Report as offensive
Profile Dave
Help desk expert

Send message
Joined: 28 Jun 10
Posts: 1924
United Kingdom
Message 107694 - Posted: 3 Apr 2022, 15:55:10 UTC - in response to Message 107692.  

Yes I know all that, I installed boinc-client on Debian 9.13 without problems but my machine is installed in Ubuntu 20.04 and even without installing VirtualBox the machine reboots after launching boinc-client...


I would agree that a clean re-install is the thing most likely to clear the problem. (Assuming it isn't caused by dodgy memory.) Whatever it is almost certain that the problem is not BOINC itself but that BOINC is exposing that the problem is there. Over the years, I have found more than once a clean re-install has sorted things out. I have for many years now always made a point to keep the OS on a separate hard disk to my data. I still back up before doing a clean install but since I started doing that, have not had to use the backup.
ID: 107694 · Report as offensive
sprzyswa

Send message
Joined: 2 Feb 21
Posts: 30
France
Message 107695 - Posted: 3 Apr 2022, 17:34:45 UTC - in response to Message 107690.  
Last modified: 3 Apr 2022, 17:39:57 UTC

You know you can run BOINC without VirtualBox. Its only needed if the project in question only have that type of work unit. I'm still crunching for Rosetta although they have a "rosetta python projects" which uses vbox. I'm running their normal CPU work units only. VirtualBox allows you to run virtual machines. In the case of the various BOINC projects they supply work units which are a VM image.

The Linux versions of BOINC don't keep an old version of stdoutdae around. They use the standard Linux way of doing things. You can view the log by doing a "sudo journalctl --unit=boinc-client" command in a terminal or ssh session. The journal entries can go back quite some time (I have some from Sept 2021 on one machine).

As for directory naming on Raspberry Pi OS, they are following the Debian standard. Debian used to use /var/lib/boinc-client and other Linux distros use /var/lib/boinc. The later BOINC releases have both folders and a symlink from /var/lib/boinc to /var/lib/boinc-client so they are basically the same directory.


I even reinstalled my machine to have a clean system but after installing boinc-client I still have the same thing, a clean REBOOT and that broke my RAID-1 I have a disk in resynchronization...

Sam.
Powered by Debian & Ubuntu 20.04 LTS
Boinc version 7.16.6 x86_64-pc-linux-gnu
ID: 107695 · Report as offensive
1 · 2 · Next

Message boards : Questions and problems : boinc-client crash and reboot my machine

Copyright © 2022 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.