BOINC Manager - Connection Issue - The password you have provided is incorrect, please try again

[dbareis]

I'm on Windows 10 x64 with latest updates and latest BOINC (the about box doesn't let me copy anything so I assume you won't want it).

Apart from the bug itself, dialogs such as this one (picture attached) are pretty much useless as it doesn't even say what passwords don't match, is it BOINCSTATS BAM? Is it one of the projects? I know BOINCSTATS is correct, and since I have recently changed the password I just went and checked all of them by making sure I could logon with the current password. One or two were wrong.

Now I can't even find out where the password is as I can't find any place in the BOINC app that takes one.

The thing is everything was working fine, then it died, and would display the dialog, to recover I tried stopping all processes and restarting. What Worked was removing BOINCSTATS and adding it again.

It was then working for a day or so and now has a similar issue but this time the manager has been automatically removed and the "use account manager" (add) option is displaying the error! Rebooting definitely doesn't help. Both times the "project" tab went crazy adding many blank lines, the first time I had to kill it the second it eventually settled down.

I think wherever BOINC keeps the password has been corrupted. The BOINC tasks are still running.

If I try to connect to my computer (localhost) after disconnecting it, then it prefills the password entry field with something like (modified slightly by me for security): "7ef13dea46415d2a2e02d48d5ffa4ac1" (starred so not normally visible). I also tried my BOINCSTATS/Project password, both fail (same dialog).

If BOINSTATS is covered by this project as well then I have to say I was surprised that the extremely obvious CPU work preferences bugs and others still exist from when I last used BOINC many, many moons ago...

[dbareis]

After failing to connect to local host, I tried from a "File->new boinc manager window" which also failed. I then shutdown both managers and opened up a new one, it connected, no problems. I HAVE NOT CHANGED ANY PASSWORDS ANYWHERE. I do have to reconnect BAM!

Spoke too soon, my projects were back. Once I connected BAM! I've got the password error dialog again. I just tried successfully logoff and logon with same credentials at "https://www.boincstats.com/". It looks like it might have connected as my host name is now duplicated at "https://www.boincstats.com/"...

[davidpanderson]

That message is misleading; it refers to a random string generated by the client to authorize requests from the Manager. It's stored in a file "gui_rpc_auth.cfg" in the data directory. If you start a manager in a different directory, you'll get that error.

The next version of the client replaces this with a clearer message.

[dbareis]

Thanks for the update. I hope the bug gets fixed also.

I'm not sure what you mean by start in a different directory, I'm starting the manager with the shortcut the installer created (both when it does & doesn't work). Directory (current?) always the same and presumably correct.

So the server (localhost) and the client both have their own memory of what the "password" is?

"gui_rpc_auth.cfg" contains the same hash that gets prepopulated as the localhost password. I did move the data directory during install but the working directory of "C:\Program Files\BOINC\boincmgr.exe" is the correct (my location) data directory.

Will anything go to the event log or any other logs?

Its currently working, and connected to local host, it fails if I try to add the account manager (BAM!).

Basically, how do I fix this?

[AenBleidd]

@dbareis, try to run regedit and go to HKEY_LOCAL_MACHINE\SOFTWARE\Space Sciences Laboratory, U.C. Berkeley\BOINC Setup and change DATADIR value with the correct path to your DATA directory

[RichardHaselgrove]

I'm not fully convinced by the arguments on this issue. The 'bad password' alert complained of has plagued us intermittently for years, and is NOT usually triggered by actual changes in the GUI_RPC_AUTH string. The alert is generated at

https://github.com/BOINC/boinc/blob/client_release/7/7.14/clientgui/BOINCBaseFrame.cpp#L517

where it is the final 'else' case in a sequence of tests - shown by default when something unexpected happens.

The replacement code from #3709 can be studied at

https://github.com/BOINC/boinc/blob/client_release/7/7.16/clientgui/BOINCBaseFrame.cpp#L503

(although we currently still have a mis-match between release branch code and the latest release) Again, the new wording ("Invalid client RPC password") is used in an 'else' case handler - I'm suspicious of this. I would prefer that the 'else' case wording was distinct, so that future debugging attempts have better data to start from: otherwise, the !bUsedDefaultPassword outcome cannot be uniquely distinguished. There is a (rare) problem here that we haven't got to the bottom of yet.

[Ageless93]

"gui_rpc_auth.cfg" contains the same hash that gets prepopulated as the localhost password. I did move the data directory during install but the working directory of "C:\Program Files\BOINC\boincmgr.exe" is the correct (my location) data directory.

Hold on, are you saying that you moved your data directory to C:\Program Files\BOINC\ ?? Because that is a Windows protected directory that Windows does not allow much (writing) in. If you did move the data directory to this directory, you have no other choice than to move it elsewhere again. Or better yet, uninstall, remove that directory, install BOINC and install it with the default path values.

[dbareis]

@AenBleidd Nothing at HKLM, it's at HKCU (I don't have a service). "DATADIR" doesn't exist anywhere in that tree as far as I can see. I also search the complete registry for my data directory and it wasn't found.

@RichardHaselgrove Even that message is too cryptic, and why not include a link to a page where the message is discussed, including solutions, perhaps the problem record or a WIKI page specific to the error message. Shouldn't make it hard for users to get help on errors (or for developers to get more info).

@Ageless93 That is in the installation directory, I would never try to move data there and if I did it wouldn't work and everything is working on and off and at this stage, my theory is BOICSTATS BAM syncing is causing this issue. What I said was "the working directory of "C:\Program Files\BOINC\boincmgr.exe" is correct" (my data directory which is obviously how it knows where the data is).

[Ageless93]

Since you don't know where your data directory is and you cannot find its path in the registry, it is best to uninstall BOINC and reinstall it, then in the third screen of the installer click Advanced, then check the path to the data directory there (second entry from the top) and if that's empty, put a path in it. Default path is C:/Programdata/BOINC/

If it turns out the path is empty, we'll need sanity checks in place to see if these entries aren't empty or not existing (like path to a drive letter that doesn't exist).

[dbareis]

@ Ageless93 I'm not sure what gave you the impression that I don't know where the data is or that boinc doesn't know as I'd confirmed that the EXE working directory was pointing to the data directory.

I'm guessing the value you mentioned is only used if you select a BOINC service which as I've said I haven't. I also said its been working which it can't do unless it doesn't know where the data is.

During install, I CHOSE the data directory I wanted and all evidence says that it was happy with that and it's being used.

The cause is adding BOINCSTATS as a manager, I had it working all day today before stupidly trying to add the manager again. BAM! sync is the cause of the issue.

I have created a video of BOINC starting up. It only does the process once before displaying the dialog. If I connect to localhost it will do the whole thing TWICE before displaying the dialog. Boinc Manager Startup Video.mp4.mp4.zip

How it resolves itself I'm unsure.

[RichardHaselgrove]

@dbareis Unfortunately, Jord is right: whatever you're seeing on your system, a normal installation will create both HKLM and HKCU entries in the registry. This is an extract from one I saved some years ago, but it's still current and accurate:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Space Sciences Laboratory, U.C. Berkeley\BOINC Setup]
"UpgradingTo"="7.6.22"
"INSTALLDIR"="D:\\BOINC\\"
"DATADIR"="D:\\BOINCdata\\"

Whether you install as a service or as a user (I install as a user, too), the installer will (?should) create those entries. As you can see, my chosen locations are non-standard, chosen and created through the advanced options page in the installer.

It is essential that the DATADIR key is both present and accurate for password discovery to work as intended.

[dbareis]

@RichardHaselgrove

OK, I executed "boinc_7.16.7_windows_x86_64.exe" and tried a repair, no HKLM created (if it should be then there is a bug in the MSI). Program still fails.

Uninstalled BOINC, "setup" key removed from HKCU registry. Reinstalled "boinc_7.16.7_windows_x86_64.exe", data directory correctly detected from unknown location (as the DLL doesn't log it, why not native MSI functionality?):

Action start 8:35:56: CARestoreSetupState.
MSI (c) (A0:04) [08:35:56:027]: Invoking remote custom action. DLL: C:\Users\Dennis\AppData\Local\Temp\MSI65A.tmp, Entrypoint: RestoreSetupState
...
Action 8:35:56: CARestoreSetupState. Restore the previous setups saved parameters.
Custom Message : Action Name: CARestoreSetupState Description: Successfully retrieved registry value 'DATADIR' with a value of 'D:\TMP\[DATA]\BOINC\' Error Code: 0 

Setup creates or uses "HKEY_LOCAL_MACHINE\SOFTWARE\Space Sciences Laboratory, U.C. Berkeley\BOINC Setup" and "DATADIR" is there. Not sure when that got created but a registry search now finds it and didn't before and in any case, I browsed to it and it wasn't there yesterday (actually used RegJump from sysinternals).

Same issue exists.

[dbareis]

@RichardHaselgrove

I executed "boinc_7.16.7_windows_x86_64.exe" and tried a repair, no HKLM created (if it should be then there is a bug in the MSI). Program still fails.

Uninstalled BOINC, "setup" key removed from HKCU registry. Reinstalled "boinc_7.16.7_windows_x86_64.exe", data directory correctly detected from unknown location (as the DLL doesn't log it, why not native MSI functionality or at least log location?):

Action start 8:35:56: CARestoreSetupState.
MSI (c) (A0:04) [08:35:56:027]: Invoking remote custom action. DLL: C:\Users\Dennis\AppData\Local\Temp\MSI65A.tmp, Entrypoint: RestoreSetupState
...
Action 8:35:56: CARestoreSetupState. Restore the previous setups saved parameters.
Custom Message : Action Name: CARestoreSetupState Description: Successfully retrieved registry value 'DATADIR' with a value of 'D:\TMP\[DATA]\BOINC\' Error Code: 0 

Setup creates or uses "HKEY_LOCAL_MACHINE\SOFTWARE\Space Sciences Laboratory, U.C. Berkeley\BOINC Setup" and "DATADIR" is there. Not sure when that got created but a registry search now finds it and didn't before and in any case, I browsed to it and it wasn't there yesterday (actually used RegJump from sysinternals).

Rebooted, same issue exists.

Another boinc bug are the "Don't show this dialog again" checkboxes, unless it is MEANT to say "Don't show this dialog again (this session)"

[AenBleidd]

@dbareis,

Another boinc bug are the "Don't show this dialog again" checkboxes, unless it is MEANT to say "Don't show this dialog again (this session)"

it is a registry value saved. If you set this option and safely close BOINC Manager (without killing it in some way) this value hould be saved

[AenBleidd]

HKEY_CURRENT_USER\Software\Space Sciences Laboratory, U.C. Berkeley\BOINC Manager -> DisplayShutdownClientDialog 1 - Dialog will be shown 0 - Dialog will not be shown

[dbareis]

I deleted all the data and all the jobs, successfully added BAM, it's now working. Pity BOINC doesn't log.

[dbareis]

@AenBleidd I always close it from the task bar, right-click->Exit

Thanks for the information, that will allow me to investigate this later

[Ageless93]

Pity BOINC doesn't log.

CTRL+SHIFT+E will open the event log. Else view, advanced view, tools, event log will do that. CTRL+SHIFT+F will open the debug options menu for the event log. Don't enable all at once. See https://boinc.berkeley.edu/wiki/Client_configuration#Logging_flags for logging flags options.

BOINC logs quite a bit.

[RichardHaselgrove]

CTRL+SHIFT+E will show the log for the current session (from last BOINC restart) only.

Older logs are available in the files stdoutdae.txt and stdoutdae.old in the BOINC data directory.

[dbareis]

Thanks for the logging info, pity no one mentioned this earlier (before I deleted the data)

Update: I realised the files were probably in the recycle bin, The attached file is with default logging options. It seems this is what the error looks like in the log:

18-Jul-2020 17:43:30 [---] [gui_rpc] GUI RPC reply: '<boinc_gui_rpc_reply>
<unauthorized/>
</boinc_gui_rpc_reply>

stdoutdae (2).zip

[Ageless93]

Thanks for the logging info, pity no one mentioned this earlier (before I deleted the data)

You don't ask. You guess and assume a lot. You give confusing information. When given information on how to fix it, you ignore it and first do things your own way. To then post that that doesn't work and complain about that. To then follow the advice given and that works. And then hastily do things again that were unnecessary.

See https://boinc.berkeley.edu/wiki/User_manual for the user manual. Since it's now working, there's no need to continue this thread. There's as far as I see no bug here. See you at the https://boinc.berkeley.edu/forum_index.php for the BOINC forums for future help.

[dbareis]

@Ageless93

I'm helping YOU. I'm helping all the other people who have been ignored (or at least not helped) after reporting this bug.

While I would like this fixed, if it doesn't I'll just stop using BOINC, as I did many moons ago.

I'm providing this information so YOU or a DEVELOPER can fix BOINC, If a bug forum is not the correct place to report this then please point me to the correct location.

I provided a log, I got no comments. I chose extra flags at random because no one suggested which ones I should use. I will provide a log for my current issue.

You don't ask.

I did

You guess and assume a lot.

I guess where I need to

You give confusing information.

I gave a lot of information, all detailed, if you can't read it fine.

When given information on how to fix it, you ignore it and first do things your own way.

I can't remember ignoring any information. I followed all advice provided

To then post that that doesn't work and complain about that.

I'm posting information/facts, in the US these are unwanted, here in Australia we like facts, they help us solve problems,

To then follow the advice given and that works.

And yet it didn't, the issue come back

And then hastily do things again that were unnecessary.

Well I do want it working. I've also seen people in forums mentioning this problem going back yonks, almost be beginning of time.

[dbareis]

The issue has come back on it's own, I got prompted to add an unknown BOINC project called "mip1_00311774_2988_0", I said no. The password dialog appear shortly after, this is the 3rd time I've had that dialog but I don't think that has come up every time I've had the password issue. But as I've said before the issue it definitely seems BOICSTATS related.

I captured an image of the request yesterday:

[AenBleidd]

mip1_00311774_2988_0 is not a project, it' a task name. Could you please attach next files:

• stdoutdae.txt
• stdoutdae.old
• stderrdae.txt
• stderrdae.old

[dbareis]

@AenBleidd Thanks, I realised it was probably a task, but the dialog specifically says it's a project :-)

If you need the rest let me know but the error (+task name) is included in the attached log. If I need to add extra logging, please suggest which flags: [Uploading stdoutdae - More logging - mip1_00311774_2988_0 dialog.zip…]()

I wanted to take a picture of the flags but the ones I set are no longer set so I don't know if there was extra login in the attached.

Settings not being persisted might be a symptom of this problem. I will look at the dialog case mentioned above.

[AenBleidd]

Unfortunately, there are no logs attached

[AenBleidd]

I wanted to take a picture of the flags but the ones I set are no longer set so I don't know if there was extra login in the attached.

All flags are saved in cc_config.xml file. So you can just send us a piece of the configuration and there is no need to make a screenshot

[dbareis]

HKEY_CURRENT_USER\Software\Space Sciences Laboratory, U.C. Berkeley\BOINC Manager -> DisplayShutdownClientDialog

@AenBleidd It's "DisplayShutdownConnectedClientDialog" which was just restored even though I've ticked that a million times. I'll have to try this again when boinc is "working" again. The exit confirmation has never been an issue (I did tick stop running tasks if that means anything).

Does BOINC correctly handle shutdown events? That is close itself?

[dbareis]

[BUG] "DisplayShutdownConnectedClientDialog" registry has gone back to 1. I think It's if you don't go ahead with the connecting to computer (show computer/password dialog and cancel).

[AenBleidd]

It's all looks very strange. And I have feeling that something constantly breaks data on your PC.

• Do you run any antivirus?
• Do you run any application that makes any clean-up of your PC?

[dbareis]

@AenBleidd

• Do you run any antivirus?

AVAST FREE

• Do you run any application that makes any clean-up of your PC?

NO

I also have no evidence of data issues on any of the many other programs running on my computer.

The dialog one is definitely a BOINC bug (I've added details you may not have seen).

I think the "flags" is also a bug, as it shows defaults in the dialog even when they aren't the flags that are set (were these flags used in the previously attached log?, if not it's not just a visual issue):

    <log_flags>
        <file_xfer>1</file_xfer>
        <sched_ops>1</sched_ops>
        <task>1</task>
        <app_msg_receive>1</app_msg_receive>
        <app_msg_send>0</app_msg_send>
        <async_file_debug>0</async_file_debug>
        <benchmark_debug>0</benchmark_debug>
        <checkpoint_debug>0</checkpoint_debug>
        <coproc_debug>0</coproc_debug>
        <cpu_sched>0</cpu_sched>
        <cpu_sched_debug>0</cpu_sched_debug>
        <cpu_sched_status>0</cpu_sched_status>
        <dcf_debug>0</dcf_debug>
        <disk_usage_debug>0</disk_usage_debug>
        <file_xfer_debug>0</file_xfer_debug>
        <gui_rpc_debug>1</gui_rpc_debug>
        <heartbeat_debug>0</heartbeat_debug>
        <http_debug>1</http_debug>
        <http_xfer_debug>1</http_xfer_debug>
        <idle_detection_debug>0</idle_detection_debug>
        <mem_usage_debug>0</mem_usage_debug>
        <network_status_debug>0</network_status_debug>
        <notice_debug>0</notice_debug>
        <poll_debug>0</poll_debug>
        <priority_debug>0</priority_debug>
        <proxy_debug>0</proxy_debug>
        <rr_simulation>0</rr_simulation>
        <rrsim_detail>0</rrsim_detail>
        <sched_op_debug>0</sched_op_debug>
        <scrsave_debug>0</scrsave_debug>
        <slot_debug>0</slot_debug>
        <state_debug>1</state_debug>
        <statefile_debug>0</statefile_debug>
        <suspend_debug>0</suspend_debug>
        <task_debug>0</task_debug>
        <time_debug>0</time_debug>
        <trickle_debug>0</trickle_debug>
        <unparsed_xml>0</unparsed_xml>
        <work_fetch_debug>0</work_fetch_debug>
    </log_flags>

[AenBleidd]

@dbareis,

The dialog one is definitely a BOINC bug

Ok, I see the issue here. I'll file it and take a look at it

I think the "flags" is also a bug, as it shows defaults in the dialog even when they aren't the flags that are set (were these flags used in the previously attached log?, if not it's not just a visual issue)

Default flags are shown when BOINC Manager is not connected to any client. I assume it's should be shown in this case. I'll file this too.

And I still see no logs from you to investigate your main issue

[dbareis]

@AenBleidd

The latest log is on: https://github.com/BOINC/boinc/issues/3925#issuecomment-660731123

[AenBleidd]

@dbareis, the link doesn't work

[dbareis]

@AenBleidd

@dbareis, the link doesn't work

Weird, will try again here (it's a zip file, I just tested that it works in preview):

[LOG] stdoutdae - More logging - mip1_00311774_2988_0 dialog.zip

[AenBleidd]

Now it works. Thanks. I'll check and let you know

[dbareis]

@AenBleidd

Stopping boinc, deleting "cc_config.xml" ("BAD" COPY ATTACHED) and restarting BOINC has fixed the password problem. I was hoping to compare with good but BOINC hasn't recreated the file.

The contents of the file all looks good. I decided to add debugging to recreate the file, that gave me a good and I see no differences of any significance. As it appeared to be the presence of the file that kills me, I created an almost empty one, that worked, so I have to work through the options....

This is the only option that causes the password issue (1), its not it's presence but its value of 1:

<cc_config>
    <log_flags>
    <gui_rpc_debug>1</gui_rpc_debug>
    </log_flags>
    <options>
    </options>
</cc_config>

I can't remember changing debug before the first issue but maybe that gets written when other options are selected. Maybe that PLUS BAM! causes the problem?

cc_config.xml [deleting this file resolves the password issue].zip

[CharlieFenton]

@AenBleidd - @dbareis edited the last comment with potentially important info after the email with the comment was sent. Be sure to look at the updated comment.

[davidpanderson]

The option generates a huge amount of messages and it crashes the client after a while. I never got around to figuring this out.

[dbareis]

The option generates a huge amount of messages and it crashes the client after a while. I never got around to figuring this out.

It causes my problem immediately after start BOINC (30 or so seconds). It appears (to me) to be doing something that corrupts memory (specifically where that key thing is kept)

[dbareis]

The "gui_rpc_debug" flag issue probably doesn't explain my original issue. I do however remember seeing the debug flags dialog along the way, but as far as I can see there is no UI to that dialog (why not? If it's there its well hidden) and you have to press SHIFT+CTRL+F to get there which I wouldn't have known about. If that came up because of the crash it's possible I set some flags.

The "gui_rpc_debug" flag caused the password issue with or without BAM! whereas my original problem seems to have been created when I added BAM!

But unless I or someone else reports the same issue without that flag we are probably done here?

[dbareis]

@AenBleidd

The password issue came back this morning :-(

2020-07-24 - Was working earlier this morning - BOINC.zip

[dbareis]

@AenBleidd Restarting BOINC server + client fixed it, logs attached to prev comment

[bobbonomo]

I have not digested the whole thread yet but let me add something. The password on a Windows 10 PC is stored in %SYSTEMDRIVE%\ProgramData\Boinc\gui_rpc_auth.cfg and it's a hash like mentioned here. All local data is stashed in the same directory also.

I only use World Community Grid and the client supplied there. 3 Xubuntu and 1 Windows 10 crunching away. All up to date.

I too was experimenting and struggling with boincmgr and here is what I found.

The machines running boinc don't care about the remote_hosts.cfg and gui_rpc_auth.cfg and just need 1 in options in the cc_config.xml file.

The IP I am using to connect to my remotes is not even in the remote_hosts.cfg. All four are left blank or with just comments. Two PCs (1 win and 1 Xubuntu) have a a clear text password in gui_rpc_auth.cfg.

Using boincmgr, I just fill in a remote IP and a blank field for password. As a matter of fact, when I put in the password from the gui_rpc_auth.cfg on the remote, it says it is incorrect.

OK! It may not be what the documentation states but everything works.

Here is a link to WCG where I have a thread going: https [:] //www [.] worldcommunitygrid [.] org/forums/wcg/viewthread_thread,42703

[AenBleidd]

If I recall correctly, remote_hosts.cfg are needed when you need to limit to limit incoming connections, and not outcomming as you are describing

ср, 5 авг. 2020 г. в 21:46, bobbonomo notifications@github.com:

I have not read the whole thread yet but let me add something. The password on a Windows 10 PC is stored in %SYSTEMDRIVE%\ProgramData\Boinc\gui_rpc_auth.cfg and it's a hash like mentioned here. All local data is stashed in the same directory also.

I only use World Community Grid and the client supplied there. 3 Xubuntu and 1 Windows 10 crunching away. All up to date.

I too was experimenting and struggling with boincmgr and here is what I found.

The machines running boinc don't care about the remote_hosts.cfg and gui_rpc_auth.cfg and just need

1 in in the cc_config.xml file. The IP I am using to connect to my remotes is not even in the remote_hosts.cfg. All four are left blank or with just comments. Two PCs (1 win and 1 Xubuntu) have a a clear text password in gui_rpc_auth.cfg. Using boincmgr, I just fill in a remote IP and a blank field for password. As a matter of fact, when I put in the password from the gui_rpc_auth.cfg on the remote, it says it is incorrect. OK! It may not be what the documentation states but everything works. Here is a link to WCG where I have a thread going: https [:] //www [.] worldcommunitygrid [.] org/forums/wcg/viewthread_thread,42703 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub , or unsubscribe . -- Best regards, Vitalii Koshura

Sent via iPhone

[davidpanderson]

Documentation is here: https://boinc.berkeley.edu/wiki/Controlling_BOINC_remotely

[bobbonomo]

AenBleidd: I have no idea what you are talking about outcoming. I was describing the remote machine and limiting incoming connection for RPC. When I said "running boinc" I meant the client running the work units. Maybe in this forum it is the wrong term. I'm guessing here boinc means everything which is installed.

davidpanderson: Yep read that and it is ambiguous. I based everything on that.

Read the thread I gave above from World Community Grid where I gave my full explanation. Not sure if I can drop a link here so here it is: https://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,42703