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

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?

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

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

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 :-)

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!

---

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

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

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

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.

---

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.

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

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

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

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

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

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

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.

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.

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