Questions and Answers :
Unix/Linux :
boincmgr: The password you have provided is incorrect, please try again
Message board moderation
Author | Message |
---|---|
Martin A. Boegelund Send message Joined: 4 Jul 00 Posts: 292 Credit: 387,485 RAC: 1 |
After converting to a new boinc client, Boinc Manager gives me the message "The password you have provided is incorrect, please try again" upon startup. I have my client and manager on the same machine in the same boinc directory. I have worked through several posts, bug lists etc, and found that it might have something to do with gui rpc. So I have experimented with the files gui_rpc_auth.cfg and remote_hosts.cfg, but nothing works, and I'm getting quite frustrated. What am I doing wrong? "Are you suggesting coconuts migrate?" |
5 and a half of 13 Send message Joined: 21 Jan 02 Posts: 240 Credit: 21,261 RAC: 0 |
Unless you plan on control BOINC from another computer, don't place a password in gui_rpc_auth.cfg Likewise all you should need in remote_hosts.cfg is 127.0.0.1 (the loopback address) unless you plan to control BIONC from another computer. You can also use hostnames instead of addresses The BOINC-Wiki! discusses this in greater detail. Edit: clarified Need help? Check out the excellent Unofficial BOINC-Wiki! 'We are the BOINC. Prepare to be assimilated.' |
Martin A. Boegelund Send message Joined: 4 Jul 00 Posts: 292 Credit: 387,485 RAC: 1 |
Thank you for replying to my question. I have tried several things including putting 127.0.0.1 in remote_hosts.cfg, with and without having the gui_rpc_auth.cfg file, other hostnames in remote_hosts.cfg, etc., but nothing helps. I have also updated a bug report on the problem in BoincZilla. Now I plan to create a brand new BOINC directory with only the needed executables (no xml files and stuff) once my current work units are calculated and sent. But I still welcome any help and suggestions :) "Are you suggesting coconuts migrate?" |
Martin A. Boegelund Send message Joined: 4 Jul 00 Posts: 292 Credit: 387,485 RAC: 1 |
Update to the above... It didn't work out to make a new Boinc directory with only the executables didn't help - boincmgr still fails attaching to my running Boinc client. So I've downloaded boincgui instead. And it works! It's a bit simple, but it works. "Are you suggesting coconuts migrate?" |
5 and a half of 13 Send message Joined: 21 Jan 02 Posts: 240 Credit: 21,261 RAC: 0 |
Should have thought of that. BOINC Manager can be a pain sometimes :/ Another handy program is KBOINCSpy (don't have the url). Need help? Check out the excellent Unofficial BOINC-Wiki! 'We are the BOINC. Prepare to be assimilated.' |
Trane Francks Send message Joined: 18 Jun 99 Posts: 221 Credit: 122,319 RAC: 0 |
So I've downloaded boincgui instead. And it works! It's a bit simple, but it works.It only shows the correct states with BOINC 3.x clients. It does not work correctly with 4.x clients. |
ADS4 Send message Joined: 8 Feb 00 Posts: 1 Credit: 5,646 RAC: 0 |
I had this problem also. I run BOINC 5.2.13 on Linux (FC4) as a daemon under the account boinc, per the instructions. After only an hour of banging my head against the wall, I found this works (YMMV because I didn't debug the application, I just threw guesses at it): $ su - [enter root password] # su boinc $ cd /var/lib/boinc $ /usr/local/BOINC/boincmgr Switching to root first is necessary because the boinc account has no password. Of course, if you installed BOINC in a directory other than /usr/local, change the path in the last command to your installation directory. |
Trane Francks Send message Joined: 18 Jun 99 Posts: 221 Credit: 122,319 RAC: 0 |
It occurs to me that you may not have set the working directory for the BOINC Manager. The newest Manager needs to run from the install dir; otherwise, it can't read the password. Not intuitive, but that's what I needed to do to fix this problem here. |
Dotsch Send message Joined: 9 Jun 99 Posts: 2422 Credit: 919,393 RAC: 0 |
Scarecrow has posted a solution for your problem : http://setiathome.berkeley.edu/forum_thread.php?id=23845#202309 |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.