| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Boinc client shuts down SuSE 10.0 |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 15
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hmph! Not good news this morning, I'm afraid.
I switched on and booted up, then checked that the boinc client was running. Yup. Everything is fine: peter@linux:~> ps -eaf | grep boinc_client boinc 6817 1 0 08:35 ? 00:00:02 /usr/local/bin/boinc_client --daemon Then I tried to start boincmgr, just as I did yesterday. No chance. It comes up with the Authorization Failed error message again. Worse than that, it doesn't matter which directory I'm in (i.e. whether it has the password file in it or not) or what user I run boincmgr under (my own user, the boinc user, or root). Nor will it accept me typing in 'localhost' and the 'password' from Advanced --> Select Computer. So I've re-read the help and re-read the article that contained the script, but I've not found anything to explain this or give any clues. Everything assumes that at the very worst I should be able to give boincmgr the machine name and password and that all will be well. And I've checked the password file to make sure it still has the '\n' in it. It (or rather they, since I've made a copy in my home directory) has. Sorry to be a pain, but I'm way out of my depth on this one. Cheers Peter |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Can you try actually putting in a password in gui_rpc_auth.cfg? I don't know what that would make a difference, but it's something to try.
If you're interested Eric (the same person who wrote up those install instructions you've been using) has packaged up BOINC into a rpm. It sounds like you've already got boinc's home directory in /var/lib/boinc so all you would have to do is remove the executables and then install the rpm. Details here http://pirates.spy-hill.net/help/linux-rpm.html And if you do decide to try the rpm, can you make an account on Pirates and report your findings in this thread? http://pirates.spy-hill.net/forum_thread.php?id=872 |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi Kathryn. Thanks for the response.
I have, actually, always had a password in that file. Yesterday I tried with a password of my own devising, which didn't work: but then I got it working using the random password chosen by the installer. I've never been able to get it to work by entering the machine name and password in the gui: and yesterday it worked just fine without that - just by having the password file in the same directory as the one from which I invoked boincmgr. I think I did try it once without a password, but without success. I was, however trying to connect via the gui IIRC and I've never succeeded in doing that. It always says the password is incorrect - even if I've copied and pasted it from the file, and even when it appears to infill the password itself. I can't understand why it should have worked yesterday, but not today. The only difference is that the daemon started on reboot this time rather than from me starting it from within the YaST control centre (effectively issuing the boinc_client start command, which is - as far as I know - exactly what happens at startup). So why on earth could the manager connect to the running client yesterday, but not today? I'll check out the rpm and see if that helps. Cheers Peter |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The RPM package won't install. YaST reports a conflict, saying I need libc.so.6 and that it isn't available even though it's installed on my system:
peter@linux:~> locate libc.so /lib/i686/libc.so.6 /lib/libc.so.6 /lib/tls/libc.so.6 /lib64/klibc/lib/libc.so /lib64/libc.so.6 /lib64/tls/libc.so.6 /usr/lib64/libc.so /usr/lib64/nptl/libc.so peter@linux:~> I guess the RPM expects it somewhere else, so unless anyone has any more ideas, it looks as though I'm stuck. I'm really grateful for the time everyone has taken to try to help, and I'd be delighted to try any other ideas if anyone has any: but I confess to have reached the limit of my abilities in this area (some time ago, actually). Thanks again. Peter |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The RPM worked (version 5.10.21-18). Had me going for a bit until I found the executables had been shifted to /usr/bin from usr/local/bin.
It even survived a reboot - despite saying that starting the daemon had failed. When I checked, I found it hadn't failed, and boincmgr started and connected just fine. For ease of use I've added boincmgr to the SuSE menu giving it /usr/bin/boincmgr as the command and /var/lib/boinc as the "Work path". This works OK, too. Thanks for all the help (and patience) Cheers Peter |
||
|
|
|