Questions and Answers :
Unix/Linux :
Cant boinccmd --project http://setiathome.berkeley.edu update -> after cc_config.xml created??
Message board moderation
Author | Message |
---|---|
DanHansen@Denmark Send message Joined: 14 Nov 12 Posts: 194 Credit: 5,881,465 RAC: 0 |
Hi, Ubuntu Server 12.04/12.10 All CLI environment Using the command line tool boinccmd, I usually use this command to update and attach. Suddenly I get an error! What am I doing wrong?? Facts: System uses cc_config.xml to use multiple GPU's System uses /etc/boinc-client to allow remote control "BOINC_OPTS="--allow_remote_gui_rpc" System set with password for remote control in "gui_rpc_auth.cfg" boinc-clients are currently being controlled/used by BoincTasks to show results of a test I'm doing. Can this be it?? No, right?? Errors: # boinccmd --project http://setiathome.berkeley.edu update Error -155: authentication error # boinccmd --project_attach http://setiathome.berkeley.edu 4................8 Error -155: authentication error I don't understand it. Because the --host --passwd (commands/flags?) we use when remotely controlling the computer from another computer!?!? But I tried it anyway! I CAN use boinccmd --get_tasks and it works just fine. Just can't contact SETI/Asteroids using the --project command!?!? FAQ: boinccmd [--host hostname] [--passwd passwd] command If the client uses a non-default GUI RPC port, you can specify it as hostname:port Tried these alternatives: boinccmd --project http://asteroidsathome.net/boinc/ update boinccmd --passwd mypassword --project http://asteroidsathome.net/boinc/ update boinccmd --host 192.168.0.50 --passwd mypassword --project http://asteroidsathome.net/boinc/ update boinccmd --host 192.168.0.50:31416 --passwd mypassword --project http://asteroidsathome.net/boinc/ update Content of cc_config.xml: <cc_config> <log_flags> <task>1</task> <file_xfer>1</file_xfer> <sched_ops>1</sched_ops> </log_flags> <options> <use_all_gpus>1</use_all_gpus> </options> </cc_config> Content of /etc/default/boinc-client: # This file is /etc/default/boinc-client, it is a configuration file for the # /etc/init.d/boinc-client init script. # Set this to 1 to enable and to 0 to disable the init script. ENABLED="1" # Set this to 1 to enable advanced scheduling of the BOINC core client and # all its sub-processes (reduces the impact of BOINC on the system's # performance). SCHEDULE="1" # The BOINC core client will be started with the permissions of this user. BOINC_USER="boinc" # This is the data directory of the BOINC core client. BOINC_DIR="/var/lib/boinc-client" # This is the location of the BOINC core client, that the init script uses. # If you do not want to use the client program provided by the boinc-client # package, you can specify here an alternative client program. #BOINC_CLIENT="/usr/local/bin/boinc" BOINC_CLIENT="/usr/bin/boinc" # Here you can specify additional options to pass to the BOINC core client. # Type 'boinc --help' or 'man boinc' for a full summary of allowed options. #BOINC_OPTS="--allow_remote_gui_rpc" BOINC_OPTS="--allow_remote_gui_rpc" Content of /etc/boinc-client/gui_rpc_auth.cfg: mypassword I'm sure its a little thing which I should be able to solve, but I just cant see it!?!?!? Help a sorry soul here :o . Project Headless CLI Linux Multiple GPU Boinc Servers Ubuntu Server 14.04.1 64bit Kernel 3.13.0-32-generic CPU's i5-4690K GPU's GT640/GTX750TI Nvidia v.340.29 BOINC v.7.2.42 |
William Send message Joined: 14 Feb 13 Posts: 2037 Credit: 17,689,662 RAC: 0 |
I know the problem from Windows, when you run without registry entries. Authentication problem is more like the boinccmd doesn;t have the right credentials to tell the client anything. on 32 bit Windows my workaround was to have a copy of boinccmd in the boinc data folder and use that copy to issue commands. under 64 bit not even that helped Apart from that you can try ans ask your question on the NC forum a lot of the people there don;t check Q&A and there might be a few more with the highly specialised knowledge you need. A person who won't read has no advantage over one who can't read. (Mark Twain) |
DanHansen@Denmark Send message Joined: 14 Nov 12 Posts: 194 Credit: 5,881,465 RAC: 0 |
Hi William, Thanks for getting back to me ;) I'll do that. I'll try to post it there. I just thought it was me who didn't know how to set the commands in the right place (--paswd --get_ / --get_ --passwd). Or maybe it was because I'm using the cc_config.xml file now, and some flags where to blame. Maybe there's a place to lookup "Error -155" to see what it means!? Thanks for the help ;) . Project Headless CLI Linux Multiple GPU Boinc Servers Ubuntu Server 14.04.1 64bit Kernel 3.13.0-32-generic CPU's i5-4690K GPU's GT640/GTX750TI Nvidia v.340.29 BOINC v.7.2.42 |
BilBg Send message Joined: 27 May 07 Posts: 3720 Credit: 9,385,827 RAC: 0 |
Errors: 1) I think the URL have to have "/" at the end: boinccmd --project http://setiathome.berkeley.edu/ update 2) I don't understand why you still insist on only using CLI when you now have BoincTasks Just right-click on task or project and ... Â - ALF - "Find out what you don't do well ..... then don't do it!" :) Â |
DanHansen@Denmark Send message Joined: 14 Nov 12 Posts: 194 Credit: 5,881,465 RAC: 0 |
Hi BilBg ;) I think the URL have to have "/" at the end: I'll try it right away ;) I don't understand why you still insist on only using CLI when you now have BoincTasks Just right-click on task or project and ... I know ;) But for all the other stuff I'm doing, shell scripts, temp watchdogs, fan-controls etc, I need the command line. And because usually I use SSH to remotely control the clients. I'm only using BoincTasks on my desktop to see results of a couple of tests I've done, and because it's nice to see it all lined up this way of course ;) All Boinc crunchers are going to be equipped several scripts which in case of some kind of hardware failure, will shut down automatically. I'm not going to "check" the crunchers on a daily basis when done here. They are going to crunch, day in and day out taking care of themselves. No need for control. They will tell me, when and if something is wrong ;) I'm installing a hardware fan/temp. control though, which will run in parallel to the temp. control scripts and hardware monitoring scripts. Then, if something is wrong and I'm not anywhere near my phone to be warned by email, the alarm will go off. It is what I'm trying to do. Build a semi professional system, which will run 24/7/365. Without the need for daily handling and management. This is why e.g. the PSU is a industrial PSU and not an everyday peace of hardware. Like the CPU cooler, this too is an industrial peace of hardware. And 4 large fans is built in the case. It's built to work 24/7. "No stopping and stretching legs" ;) Regarding the error -155: I checked the key log entry, and I wrote "...--password." Instead of "...--passwd." Moran!! boinccmd --project http://asteroidsathome.net/boinc/ update boinccmd --passwd mypassword --project http://asteroidsathome.net/boinc/ update boinccmd --host 192.168.0.50 --passwd mypassword --project http://asteroidsathome.net/boinc/ update boinccmd --host 192.168.0.50:31416 --passwd mypassword --project http://asteroidsathome.net/boinc/ update And there was a maintenance going on at the same time, so whenever I did anything right, nothing happened ;) Can't update to server!? Needs to get rid of units which is done, before installing new OS ;) Yes. Maintenance. . Project Headless CLI Linux Multiple GPU Boinc Servers Ubuntu Server 14.04.1 64bit Kernel 3.13.0-32-generic CPU's i5-4690K GPU's GT640/GTX750TI Nvidia v.340.29 BOINC v.7.2.42 |
©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.