![]() When the core client starts one of these apps, it becomes unresponsive for a few seconds, until whatever heavy work the app has to do is finished, and it has settled into normal crunching (in the Einstein case, the workload seems to be loading and possibly decompressing several large binary data files). Einstein gravity wave and CPDN seem to be particular cases in point. My working assumption is: based on other observations, some project applications go through a heavy start-up phase when called upon by the BOINC client. Try again a few seconds later, and it works. I think, on Windows, I've occasionally seen a 'wrong password' popup dialog when there's actually nothing wrong with the installation, configuration or anything. That's why I put it in front of the developers. Until you said something about it in a previous post, I didn't even know that you needed to do that. Would be nice if you cut the quote down to the part where you answer, but alas.īut to answer you, uhm, I cannot explain it. Remove the password again by editing the file, restart BOINC and the BM connects without a wrong password warning.Ĭoelum Non Animum Mutant, Qui Trans Mare Currunt So, can you run boinccmd after you did boinc -no_gui_rpc?Įxplain to me why I've never been able to run the BM when there is a password in the gui_rpc_auth.cfg. ![]() Not just between boinc and boincmgr, but also between boinc and boinccmd. ![]() This GUI RPC port is used by BOINC to communicate between its parts. You just told BOINC to not use the GUI RPC port. Hold on, did you do the lsof command after running boinc -no_gui_rpc? As then it's normal that port 31416 isn't used. Port 31416 is not in use, "lsof -i:31416" returns empty. If you can, of course.Īlso I can use "boinc -no_gui_rpc" to start boinc. I don't say I don't want to help you, or can't help you (even though my knowledge of Linux is limited, I must admit), but you best ask the Debian package maintainers as well. You're not running Berkeley BOINC, but a BOINC compiled by the package maintainer of Debian. Will have to ask the developers about that, but I also need to stress that this is done by the package maintainers. I'm not too sure anymore if there needs to be something in the gui_rpc_auth.cfg file for Linux. The "gui_rpc_auth.cfg" is empty, it seems this file should contains password? I put a string in it and run "boinccmd -host localhost -passwd -get_state" this time I get "Authorization failure: -102"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |