I get the above message whenever I start boincmgr. I know this question has been asked before, but none of the responses seem to work for me so far, so I have some additional info...

The standard response to this is to edit the gui_rpc_auth.cfg file in the installation directory. Well, that file doesn't exist on my machine - anywhere. Restart boinc, they tell me - still no file. So, I gave up and created it myself. I set the password to blank and it still gives me the same message.

Please help - it's getting late (gone 1.30 am here) and I'm quite tired of trying to fix this now :-(

---

Do you have some strange messages from the boinc_client ? - Can you please post the messages from the startup of the boinc client, please.
Which OS and which boinc client do you use ?

---

Do you have some strange messages from the boinc_client ? - Can you please post the messages from the startup of the boinc client, please.
Which OS and which boinc client do you use ?

Um, I'm afraid I'm quite new to all this and don't really know what I'm doing! :-s

I'm running on Linux (SuSE 10, specifically) and I'm running the latest BOINC from the home page. As for the messages, all I can get out of it is 'BOINC is already running'

I'm sorry if this is too little information, but I don't know how to get at any logs, etc.

---

I'm running on Linux (SuSE 10, specifically) and I'm running the latest BOINC from the home page. As for the messages, all I can get out of it is 'BOINC is already running'

Did the boinc client startup automaticly at boot ? - If yes, it could be, that the startup script redirect the messages in the files stderrdae.txt and stdoutdae.txt.
These are of interest.

Restart boinc, they tell me - still no file.

What do you mean ? - Do you have stoped the boinc client and restarted again after editing the file ?

Who do you connect from the boinc manager ? - Do you get some dialogbox, which asks for hostname and a password ? - Normaly you should only click to OK.

---

Did the boinc client startup automaticly at boot ? - If yes, it could be, that the startup script redirect the messages in the files stderrdae.txt and stdoutdae.txt.
These are of interest.

I think the boinc client would start automatically at boot, as when I installed it, I set up a user called boinc, as per the instructions I stumbled across via google. I can't say for sure because this machine almost never gets rebooted (running for just under 3 months now).

I'll check for the files you mentioned and repost.

Restart boinc, they tell me - still no file.

What do you mean ? - Do you have stoped the boinc client and restarted again after editing the file ?

I was told boinc creates the file when it starts, so I restarted it, but the file was still not created. Therefore, I created it manually, edited it, then restarted boinc again.

Who do you connect from the boinc manager ? - Do you get some dialogbox, which asks for hostname and a password ? - Normaly you should only click to OK.

I get no dialogue box initially, other than the error. I can click 'file > select computer...' to get the box you suggest. I enter 'localhost' as the server and leave the password field blank (as it is in my file). I still get the same message about the password, though.

---

Did the boinc client startup automaticly at boot ? - If yes, it could be, that the startup script redirect the messages in the files stderrdae.txt and stdoutdae.txt.
These are of interest.

The text files you specify don't exist on my system. I searched for std*.txt and got 0 files found. I'm starting to wonder if it's even installed properly!

---

Make sure you 'cd' into your BOINC installation directory before you start up the Manager. It doesn't like running outside of the install dir.

---

Make sure you 'cd' into your BOINC installation directory before you start up the Manager. It doesn't like running outside of the install dir.

Still no joy, I'm afraid. The boinc installation directory must be in my path variable, as I can run any of the executables from any location just by typing their name.

---

I think, it is the best to make some logging....
Can you please stop the boinc client, open a terminal window, cd to your boinc directory and start the boinc client from here.
Now the boinc client produces some messages. Can you please post it here.
Open a other terminal window and start the boinc manager there. - Are there some messages from the boinc client ?
Have the file gui_rpc_auth.cfg permitions to read for the user under which the boinc client runs ?
Btw. a empty file means no password. You could try this, too. But you have got to stop the client, change the file "> gui_rpc_auth.cfg" and start the boinc client again.

---

I think, it is the best to make some logging....
Can you please stop the boinc client, open a terminal window, cd to your boinc directory and start the boinc client from here.
Now the boinc client produces some messages. Can you please post it here.
Open a other terminal window and start the boinc manager there. - Are there some messages from the boinc client ?
Have the file gui_rpc_auth.cfg permitions to read for the user under which the boinc client runs ?
Btw. a empty file means no password. You could try this, too. But you have got to stop the client, change the file "> gui_rpc_auth.cfg" and start the boinc client again.

Herein lies a problem - I've fallen at the first hurdle. I cannot stop the boinc client. Issuing "boinc_cmd --quit" returns "Authorization failure: -155"
My gui_rpc_auth.cfg file is blank (with a carriage return for good measure). I'm sure I've been able to do this before...

Can anyone remember how to get the PID of everything that's running so I can kill it and start again?

---

Herein lies a problem - I've fallen at the first hurdle. I cannot stop the boinc client. Issuing "boinc_cmd --quit" returns "Authorization failure: -155"
My gui_rpc_auth.cfg file is blank (with a carriage return for good measure). I'm sure I've been able to do this before...

Can anyone remember how to get the PID of everything that's running so I can kill it and start again?

There is no PID file. You have got to kill it : "ps -eaf|grep boinc" -> second line is the PID. Then do a "kill $PID" <- PID is the process PID, you have seen from the ps command.
I am not shure, if the carriage return in the gui_rpc_auth.cfg is OK, or it sould be empty (a 0 byte file).

---

It appears I had multiple versions of boinc installed. I'm not sure how, but it must have happened when I upgraded.
For now, I have removed everything I can find and I will attempt to reinstall at some point in the future.
Thanks for your help, guys.

---