Questions and Answers :
Windows :
BOINCCMD fail to detach error -1
Message board moderation
Author | Message |
---|---|
anon.4300 Send message Joined: 19 Jul 16 Posts: 5 Credit: 86,188 RAC: 0 |
ver 7.6.33 attempting to execute boinccmd http://bearnol.is-a-geek.com/wanless2/ detach returns operation failed error -1 |
anon.4300 Send message Joined: 19 Jul 16 Posts: 5 Credit: 86,188 RAC: 0 |
correction, :> boinccmd --project http://bearnol.is-a-geek.com/wanless2/ detached operation fails error -1 how can this be resolved ? |
Darrell Wilcox ![]() Send message Joined: 11 Nov 99 Posts: 303 Credit: 180,954,940 RAC: 118 ![]() ![]() |
@ anon.4300: I don't know what the error code means, but confirm you have the correct URL by running this: boinccmd --get_project_urls |
anon.4300 Send message Joined: 19 Jul 16 Posts: 5 Credit: 86,188 RAC: 0 |
confirmed... |
![]() Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 ![]() |
From http://boinc.berkeley.edu/wiki/Boinccmd_tool The usage of boinccmd is: So if you just run the command from a command line, and not from the BOINC programs directory, the command in this case needs to be: boinccmd --host localhost --passwd {the password from the gui_rpc_auth.cfg file in the BOINC data directory} bearnol.is-a-geek.com/wanless2/ detach You can also exit the BOINC client, and restart it using: boinc --detach_project bearnol.is-a-geek.com/wanless2/ This will only work if no other client is running. Ref startup options. The URLs of the project don't need http:// or https:// in front. Oh, by the way, why post that at the Windows forum of Seti@Home, and not at the BOINC forums (https://boinc.berkeley.edu/dev/)? (I guess you don't want to post it at the WEP-M+2 project forums because it seems a lottle dead there.) |
anon.4300 Send message Joined: 19 Jul 16 Posts: 5 Credit: 86,188 RAC: 0 |
results are the same, failure. -1 |
![]() Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 ![]() |
I see I made a mistake. The command is: boinccmd --host localhost --passwd password --project bearnol.is-a-geek.com/wanless2/ detach I just tested doing it from the BOINC programs directory, for me it works with the project I tested with and my BOINC no longer has Eon2 added. |
anon.4300 Send message Joined: 19 Jul 16 Posts: 5 Credit: 86,188 RAC: 0 |
weird, executed the exact same thing, and still error -1 funny thing is -1 is an ole IBM Series One compile status meaning compile was error FREE... |
![]() Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 ![]() |
The "error -1" is a message of no permission, or path not found. What could be is that I have the paths to my BOINC programs and -data directory stored in the Windows Environment, so anything of BOINC I can execute from anywhere else and it'll find things about itself. You won't have that. What happens here is that BOINCCMD tries to read the contents of the gui_rpc_auth.cfg against the password you've given. It's possible that it won't be able to, because when you start BOINCCMD from the BOINC Programs directory, it'll expect to read this from that directory. The gui_rpc_auth.cfg file is however in the data directory. You could start BOINCCMD from the data directory. It's also possible you have no rights to do what you want, that you try to do this with an account that didn't install BOINC, or is allowed to control BOINC. Or that you mistyped the password from the gui_rpc_auth.cfg file, if it's still the original random 32 character hexadecimal number. Or that you changed the password in this file to one of your own and added an End of Line (Return/Enter). The password in this file requires it to be on one line only, no EoL character at the end. But most mystifying, since you post this in the Windows forum, why not do this via BOINC Manager? Why the specific need to do it via BOINCCMD? |
©2023 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.