Description of problem: Yesterday, I had boinc client and manager v7.0.65... Today, after a yum update, I have 7.2.33 and the manager cannot connect to the client. There is no more dialog box to report this. When there was, it was bogus. Now that there is no dialog box, it actually cannot connect to the client. Version-Release number of selected component (if applicable): 7.2.33 How reproducible: I've rebooted several times now and it doesn't work. Steps to Reproduce: 1. Install 7.2.33 2. Try to run boinc manager 3. Actual results: BOINC manager cannot connect to the client Expected results: BOINC manager should connect to the client Additional info: BTW, I cannot file this against boinc-manager because bugzilla says no such fedora component exists, but it clearly does. That's not right.
Can you please open a shell as root and report here outputs of the commands: 'systemctl status --full boinc-client.service' and 'systemctl start --full boinc-client.service' There's no component 'boinc-manager' in bugzilla because it's a subpackage of 'boinc-client', so that's no error.
> sudo systemctl status --full boinc-client.service boinc-client.service - Berkeley Open Infrastructure Network Computing Client Loaded: loaded (/usr/lib/systemd/system/boinc-client.service; enabled) Active: active (running) since Sat 2014-01-04 17:27:23 PST; 8h ago Process: 8985 ExecStopPost=/bin/rm -f /var/lib/boinc/lockfile (code=exited, status=0/SUCCESS) Process: 9106 ExecStartPre=/usr/bin/chown boinc:boinc /var/log/boinc.log /var/log/boincerr.log (code=exited, status=0/SUCCESS) Process: 9104 ExecStartPre=/usr/bin/touch /var/log/boinc.log /var/log/boincerr.log (code=exited, status=0/SUCCESS) Process: 9101 ExecStartPre=/bin/sleep 1 (code=exited, status=0/SUCCESS) Main PID: 9109 (boinc) CGroup: name=systemd:/system/boinc-client.service ├─2102 ../../projects/setiathome.berkeley.edu/astropulse_6.03_x86_64-pc-linux-gnu ├─2245 ../../projects/setiathome.berkeley.edu/setiathome_7.01_x86_64-pc-linux-gnu ├─4282 ../../projects/setiathome.berkeley.edu/setiathome_7.01_x86_64-pc-linux-gnu ├─4379 ../../projects/setiathome.berkeley.edu/setiathome_7.04_x86_64-pc-linux-gnu__opencl_ati_linux --device 0 ├─9109 /bin/bash /usr/bin/boinc --dir /var/lib/boinc ├─9112 /usr/bin/boinc_client --allow_multiple_clients --dir /var/lib/boinc └─9120 ../../projects/setiathome.berkeley.edu/astropulse_6.01_i686-pc-linux-gnu Jan 04 17:27:22 <hostname-redacted> systemd[1]: Starting Berkeley Open Infrastructure Network Computing Client... Jan 04 17:27:23 <hostname-redacted> systemd[1]: Started Berkeley Open Infrastructure Network Computing Client. > sudo systemctl start --full boinc-client.service > sudo systemctl status --full boinc-client.service boinc-client.service - Berkeley Open Infrastructure Network Computing Client Loaded: loaded (/usr/lib/systemd/system/boinc-client.service; enabled) Active: active (running) since Sat 2014-01-04 17:27:23 PST; 8h ago Process: 8985 ExecStopPost=/bin/rm -f /var/lib/boinc/lockfile (code=exited, status=0/SUCCESS) Process: 9106 ExecStartPre=/usr/bin/chown boinc:boinc /var/log/boinc.log /var/log/boincerr.log (code=exited, status=0/SUCCESS) Process: 9104 ExecStartPre=/usr/bin/touch /var/log/boinc.log /var/log/boincerr.log (code=exited, status=0/SUCCESS) Process: 9101 ExecStartPre=/bin/sleep 1 (code=exited, status=0/SUCCESS) Main PID: 9109 (boinc) CGroup: name=systemd:/system/boinc-client.service ├─2102 ../../projects/setiathome.berkeley.edu/astropulse_6.03_x86_64-pc-linux-gnu ├─2245 ../../projects/setiathome.berkeley.edu/setiathome_7.01_x86_64-pc-linux-gnu ├─4282 ../../projects/setiathome.berkeley.edu/setiathome_7.01_x86_64-pc-linux-gnu ├─4379 ../../projects/setiathome.berkeley.edu/setiathome_7.04_x86_64-pc-linux-gnu__opencl_ati_linux --device 0 ├─9109 /bin/bash /usr/bin/boinc --dir /var/lib/boinc ├─9112 /usr/bin/boinc_client --allow_multiple_clients --dir /var/lib/boinc └─9120 ../../projects/setiathome.berkeley.edu/astropulse_6.01_i686-pc-linux-gnu Jan 04 17:27:22 <hostname-redacted> systemd[1]: Starting Berkeley Open Infrastructure Network Computing Client... Jan 04 17:27:23 <hostname-redacted> systemd[1]: Started Berkeley Open Infrastructure Network Computing Client. Jan 05 01:39:30 <hostname-redacted> systemd[1]: Started Berkeley Open Infrastructure Network Computing Client.
Have you linked the 'gui_rpc_auth.cfg' file to your home directory? What's the output of 'ls -l /var/lib/boinc/gui_rpc_auth.cfg' and 'ls -l ~/gui_rpc_auth.cfg' ? Is your user a member of 'boinc' group? See it with command 'groups'
No, I don't have that file anywhere in my home directory. I haven't touched it since installing boinc-client RPM. My user is in the 'boinc' group. ...Okay, thanks. I linked it the other way, just to test, and it worked. Another detail that somehow I never learned and that never mattered until recently. The instructions I read said to go to Advanced > Select computer and then use the passphrase in that file. I didn't need that before, but I tried it this time. Is that supposed to work?
Yes, it's the recommended procedure stated at http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Fedora#Set_up_your_accounts However it's weird that it can't connect typing the password. I tried myself and I found that if you type 'localhost' and the password it doesn't connect, but if you type '127.0.0.1' and the password it connects! I will investigate this. Meanwhile I'm glad your problem is solved in some way...
Damn, I read that page many times. I'm sorry, mea cupla. So, I noticed this a while ago, but didn't have any indication that it caused a problem. But you found one! try getent hosts localhost...it doesn't find the IP4 addr, only the IP6. I remember when IP6 localhost showed up in my /etc/hosts. I don't think it is strictly legal for the same name to map to two different IP addrs; at least getent doesn't like it. Wait, didn't getent used to returned more than one result. I can't remember for sure. But, either way, it sounds like the default /etc/hosts is not correct. Anyway, that's why localhost doesn't work.
I don't think it's that problem: boinc 7.0.65 works, boinc 7.2.33 does not. And the getent output is always the same. I've opened a request on Boinc forums to see if other users have the same problem on other distributions: http://boinc.berkeley.edu/dev/forum_thread.php?id=8828
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.