Joined: 28 Jun 10
Got this when I started the manager yesterday after the machine had been shut down while mains was off for some work. Using BOINC 7.19.0 compiled about three weeks ago from source on Git-Hub. Ubuntu 21.10.
I found three threads about this relating to Windows but none seemed particularly informative with respect to a Linux system. This repeated several times till I exited the manager, ran
~$ sudo systemctl start boinc-clientI then ran top which told me that the tasks had continued to run without the manager. Restarted the manager and everything ran normally.
Not a major problem and will do some more extensive log perusing if it happens again. Nothing that leaps out at me so far.
Joined: 27 Jun 08
One of the problems I have with Linux is looking for informative error messages. About all I can do is grep for "boinc" in the var/log folder and then grep for "error". Usually the files are so large I need to delete them and reboot to be able to spot a problem the next time it happens.
Not anywhere as clean as looking in the windows event viewer and spotting "memory resource" warnings and finding I had too many apps running to leave suspended apps in ram.
AFAICT there are no linux apps that break logs into "apps" and "system" and then organize the results into critical, error, warning, and "info" like windows does.
I run about 10 systems and monitor the boinc event log using boinctasks. There are so many meaningless messages from all systems that I did a mod of boinc to filter out the worst ones. I have no need to be told 500 times that I can get CPU tasks but that I chose not to. Those push real error messages off the bottom of the log file before I can read them.
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.