Message boards : Questions and problems : boinc-client crash and reboot my machine
Message board moderation
Author | Message |
---|---|
Send message Joined: 2 Feb 21 Posts: 30 |
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 |
Send message Joined: 31 Dec 18 Posts: 293 |
Hi, How’s the cooling on your machine? Do you have a monitor to show you the CPU temperature? |
Send message Joined: 2 Feb 21 Posts: 30 |
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 |
Send message Joined: 2 Feb 21 Posts: 30 |
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 |
Send message Joined: 31 Dec 18 Posts: 293 |
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 :-) |
Send message Joined: 17 Nov 16 Posts: 888 |
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! |
Send message Joined: 2 Feb 21 Posts: 30 |
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 |
Send message Joined: 5 Oct 06 Posts: 5123 |
The log history for Linux systemd installations is kept in the system journal. |
Send message Joined: 2 Feb 21 Posts: 30 |
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 |
Send message Joined: 17 Nov 16 Posts: 888 |
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. |
Send message Joined: 5 Oct 06 Posts: 5123 |
Richard,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;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. |
Send message Joined: 2 Feb 21 Posts: 30 |
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 |
Send message Joined: 2 Feb 21 Posts: 30 |
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 |
Send message Joined: 2 Feb 21 Posts: 30 |
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 |
Send message Joined: 2 Feb 21 Posts: 30 |
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 |
Send message Joined: 5 Mar 08 Posts: 272 |
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 |
Send message Joined: 2 Feb 21 Posts: 30 |
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. 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 |
Send message Joined: 2 Feb 22 Posts: 81 |
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. |
Send message Joined: 28 Jun 10 Posts: 2662 |
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. |
Send message Joined: 2 Feb 21 Posts: 30 |
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. 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 |
Copyright © 2024 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.