Advanced search

Message boards : Number crunching : BOINC Manager doesn't open

Post to thread Subscribe Sort
Author Message
Profile ServicEnginIC
Avatar
Send message
Joined: 24 Sep 10
Posts: 581
Credit: 9,815,362,024
RAC: 20,602,106
Level
Tyr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 55902 - Posted: 8 Dec 2020 | 19:50:01 UTC

BOINC Manager doesn't open.

It's been driving me crazy a random problem at the moment of opening BOINC Manager application.
Details:
- OS: Ubuntu Linux 20.04.1 LTS
- BOINC version: 7.16.x (x64)
- Problem: BOINC client running, BOINC Manager doesn't open when clicking its symlink
- On host: Same problem in eight, different, varied hosts

Firstly, I thought it was a random problem, solved sometimes after rebooting system.
Afterwards, I discovered that there was a narrow window at very first after rebooting, at what BOINC Manager was able to open.
After missing this window, BOINC Manager wasn't able to open when clicking its symlink.
As a bypass, I found that BOINC Manager could be opened anyway by means of a Terminal window.
Command:

sudo boincmgr

But sometimes, when closing Terminal parent window, also hanging BOINC Manager window closed.

Recently, I tried a solution that has worked for me on those eight mentioned hosts:

- Open a Terminal window
- Command:
sudo gedit /etc/rc.local

- Copy and paste the following contents if file is blank, or add the remarked two lines in it:
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
sleep 10
/usr/bin/boincmgr
exit 0

- Save changes at edited rc.local file
- Command:
sudo chmod +x /etc/rc.local

- Reboot system

After that, symlink for opening BOINC Manager is working as expected.

Known issue:
If I close BOINC Manager window, it won't open again.
For eviting this, I prefer to leave BOINC Manager window minimized.
But even then, this other remedy can be applied (no rebooting needed):

- Open a Terminal window
- Command:
sudo killall boincmgr

And BOINC Manager will open again by means of its symlink.

ID: 55902 | Rating: 0 | rate: Rate + / Rate - Report as offensive    Reply Quote
Richard Haselgrove
Send message
Joined: 11 Jul 09
Posts: 1620
Credit: 8,880,316,535
RAC: 19,979,876
Level
Tyr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 55903 - Posted: 8 Dec 2020 | 20:51:45 UTC - in response to Message 55902.

Check for a lockfile BOINC Manager-richard [your own username there] in your home folder. If present, delete it.

The lockfile will usually be there all the time the Manager is open, and is usually deleted when you close it. But sometimes - especially if the Event Log window is also open - the lockfile is left behind. Bug. Causes the symptoms you describe.

ID: 55903 | Rating: 0 | rate: Rate + / Rate - Report as offensive    Reply Quote
biodoc
Send message
Joined: 26 Aug 08
Posts: 183
Credit: 10,085,929,375
RAC: 1,709,448
Level
Trp
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 55904 - Posted: 8 Dec 2020 | 20:59:24 UTC
Last modified: 8 Dec 2020 | 21:01:59 UTC

I've found these steps from the Arch linux boinc wiki to be useful when setting up a new boinc installation on Ubuntu or Mint. https://wiki.archlinux.org/index.php/BOINC

"You will also need to add yourself to the boinc group in order for the manager to connect:"

# sudo usermod -a -G boinc $(whoami)


"By default, a password is created in /var/lib/boinc/gui_rpc_auth.cfg for connecting to the daemon. To simplify connection of the GUI to the daemon, cd to your home directory, create a link to the file, and change permissions to allow read access to boinc group members."

$ cd ~/
$ ln -s /var/lib/boinc/gui_rpc_auth.cfg gui_rpc_auth.cfg
# sudo chmod 640 gui_rpc_auth.cfg

ID: 55904 | Rating: 0 | rate: Rate + / Rate - Report as offensive    Reply Quote
Profile ServicEnginIC
Avatar
Send message
Joined: 24 Sep 10
Posts: 581
Credit: 9,815,362,024
RAC: 20,602,106
Level
Tyr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 55906 - Posted: 8 Dec 2020 | 22:49:05 UTC

Check for a lockfile BOINC Manager-richard [your own username there] in your home folder. If present, delete it.

The lockfile will usually be there all the time the Manager is open, and is usually deleted when you close it. But sometimes - especially if the Event Log window is also open - the lockfile is left behind. Bug. Causes the symptoms you describe.

Thank you Richard, I've effectively chacked that if mentioned "BOINC Manager-user" file is present at home folder, it prevents for BOINC Manager to open. I take note.
I usually maintain opened Event Log in a second window...

biodoc, thank you for your kind indications, I've followed them also.

ID: 55906 | Rating: 0 | rate: Rate + / Rate - Report as offensive    Reply Quote
Profile ServicEnginIC
Avatar
Send message
Joined: 24 Sep 10
Posts: 581
Credit: 9,815,362,024
RAC: 20,602,106
Level
Tyr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 55915 - Posted: 9 Dec 2020 | 10:57:14 UTC

Thank you Richard, I've effectively chacked that if mentioned "BOINC Manager-user" file is present at home folder, it prevents for BOINC Manager to open...

Anyway, I've also checked that when executing previously mentioned command:
sudo killall boincmgr

BOINC Manager will open even if "BOINC Manager-user" file is present

ID: 55915 | Rating: 0 | rate: Rate + / Rate - Report as offensive    Reply Quote
Richard Haselgrove
Send message
Joined: 11 Jul 09
Posts: 1620
Credit: 8,880,316,535
RAC: 19,979,876
Level
Tyr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 55916 - Posted: 9 Dec 2020 | 13:46:30 UTC - in response to Message 55915.

Even if committing mass genocide is an effective workround, I submit that deleting a file is a less drastic solution!

I think that this problem points to a difference between 'Close window' and 'Exit BOINC [Manager]' - and your workround rather confirms this.

It is the decision of the Linux repo package maintainers to remove the 'Exit BOINC' option from the File menu in BOINC Manager. The code remains in the BOINC sources, and you may find a self-compiled replacement suits your needs better.

The package maintainers think in corporate terms, where the daily user of the computer is not the owner or sysadmin. They live in a world where sudo and root login are not available to mere mortals: in this world, the systemctl commands for controlling the BOINC client aren't available either. The maintainers are worried that the option 'Stop running tasks when exiting the BOINC Manager' will stop all scientific research until a sysadmin can intervene.

I think that your 'killall' mimics 'Exit', whereas 'Close window' leaves some of it running.

ID: 55916 | Rating: 0 | rate: Rate + / Rate - Report as offensive    Reply Quote
Profile ServicEnginIC
Avatar
Send message
Joined: 24 Sep 10
Posts: 581
Credit: 9,815,362,024
RAC: 20,602,106
Level
Tyr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 55921 - Posted: 9 Dec 2020 | 20:14:07 UTC - in response to Message 55916.
Last modified: 9 Dec 2020 | 20:15:24 UTC

I submit that deleting a file is a less drastic solution!

Guided by your kind advice, I've changed my habits to this other command:
rm 'BOINC Manager-user'

Where user is the affected host's username
It solves my problem fine, and, as you say, it is less drastical.
Thank you very much again.
Hopefully it may help to other users in the same situation.

ID: 55921 | Rating: 0 | rate: Rate + / Rate - Report as offensive    Reply Quote
Post to thread

Message boards : Number crunching : BOINC Manager doesn't open

//