Bug 711781

Hi ! 

Some of my friends using BOINC related this to me. 

I've watched the page about installing BOINC on Debian system : 

The problem is : 
The user is not added to the boinc group. 

Just edit the file /etc/group 
Find the line that contain "boinc:x:{number}:"
At the end, just add your user account. 
Save the file and reboot 

Then after lauching the manager, you'll be asked for attaching to a project or an account manager. 

This had to be done during the installation of boinc-client and boinc-manager.

Thanks a lot. 

Alexandre

Hi Alexandre.

Thanks for the tip. 
I've tried that, but it doesn't work.

Anyway ... if I download the client from the WCG homepage, then it works without any group settings, etc.
I simply expect the same behavior without changing anything.

Jaromír,

did you start the boinc-client service?

(Follow: https://fedoraproject.org/wiki/User:Mjakubicek/HowToUseBoinc)

Ahoj Miloši.

Yes, the service is started.

I just discovered, that it's somehow related to user rights.
It works well, when executed from the root account ...

Please, let me know if You need more info.

Thanks,
Jaromir.

Ahhh .... sorry ...

It was a combination of both (running service and group settings) and I forgot to relogin after the group change ... that's why it didn't work.

But ... I have to say, that the current behavior doesn't match the behavior of the precompiled BOINC client ... I'm perfectly ok with that as long as the client displays any ERROR message to the user! Otherwise the behavior is wrong!

The user needs to be informed, that he can't attach to project, because he's missing in the boinc group and that the boinc-client service is not running.

I have installed BOINC today, but I *can't* run it:

$ sudo yum install boinc-client boinc-manager

and then added my user name to the boinc group:

$ su -c '/usr/sbin/usermod -G boinc -a german'

Then I enabled and started the service:

$ sudo systemctl enable boinc-client.service 
boinc-client.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig boinc-client on
Warning: unit files do not carry install information. No operation executed.

$ sudo systemctl start boinc-client.service

and it is running as you can see:

$ systemctl status boinc-client.service 
boinc-client.service - LSB: This script monitors the BOINC client.
	  Loaded: loaded (/etc/rc.d/init.d/boinc-client)
	  Active: active (running) since Wed, 21 Dec 2011 04:06:33 -0200; 16s ago
	 Process: 13038 ExecStart=/etc/rc.d/init.d/boinc-client start (code=exited, status=0/SUCCESS)
	  CGroup: name=systemd:/system/boinc-client.service
		  └ 13054 /usr/bin/boinc_client --dir /var/lib/boinc

Then I started the GUI:

$ boincmgr

and then I set up the account as explained here http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Fedora#Set_up_your_accounts, I mean:

Advanced -> Select computer -> Host name: localhost, Password: content of/var/lib/boinc/gui_rpc_auth.cfg

...but *no luck*...

A window appears, saying:

"The BOINC client has exited unexpectedly 3 times within the last 2 minutes. Would you like to restart it again?"

and I say yes, but then in the status bar I see "Connecting to localhost" followed by "Disconnected".

What am I missing? Please help me! :(

(In reply to comment #6)
> I have installed BOINC today, but I *can't* run it:
> $ sudo yum install boinc-client boinc-manager
> and then added my user name to the boinc group:
> $ su -c '/usr/sbin/usermod -G boinc -a german'
> 
> Then I enabled and started the service:
> and it is running as you can see:
> Then I started the GUI:
> $ boincmgr
> 
> What am I missing? Please help me! :(

Hello German,
Did you logoff and logon before starting the gui ? You need it to update your groups

Hi GuL:

Ohh...now it works!! Thanks very much!! hehe...sorry for so much noise, it was so easy...

Germán.

You're welcome !

If you want to use your graphic card for crunching maybe can you have a look there : https://bugzilla.redhat.com/show_bug.cgi?id=754600

Merry christas

I think there should be more feedback from the program to the user. I got it running, but only because Jarda instructed me how. Please, be so kind so to:

1) Add some more concise error messages

2) Update manual

Thank you very much. It's a pity this worthy project is held back by such minor issues.

I have updated the manual and even patched the manager so that it now shows an error dialog with pointer to the documentation for Fedora in case it cannot connect to the client. I'm not very happy with the patch since I can't really hope it will get upstreamed (in this way, or another, more configurable), so it is quite a burden for the future. But I agree that 90 % of all bugreports to boinc-client related to this issue, so...let's try.

You can have a look at a preliminary version here:

http://koji.fedoraproject.org/koji/taskinfo?taskID=4196528

Ahoj Miloši.

If the patch is generic enough to be suitable for other distributions, then I see no reason for rejection by the boinc upstream. Anyway, it's really good you fixed that.

Regards,
Jaromir.

This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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 to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

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.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping