Setting up BOINC on a Raspberry Pi

Update 2016-01-29

nn

Replaced [email protected] project with [email protected] solution for Authorization failure error.

nn

Install the BOINC package.

nn

<code>$ sudo apt-get updaten$ sudo apt-get install boincn</code>n

nn

Start the BOINC daemon

nn

<code>$ sudo /etc/init.d/boinc-client startn</code>n

nn

Acquire your account key

nn

<code>$ boinccmd --lookup_account http://asteroidsathome.net/boinc/ your-email your-passwordn</code>n

nn

Attach the project

nn

<code>$ boinccmd --project_attach http://asteroidsathome.net/boinc/ your-account-keyn</code>n

nn

Shortly, your Pi should start downloading and computing a work unit. To verify, run $ boinccmd --get_tasks. The active task list will be displayed on your terminal. You should see the [email protected] task listed under project_url and the current action of the project under active_task_state.

nn

Other Handy Commands

nn

To stop the BOINC daemon: $ sudo /etc/init.d/boinc-client stop

nn

To restart/bounce the BOINC daemon: $ sudo /etc/init.d/boinc-client restart

nn

To check the status of the daemon: $ sudo /etc/init.d/boinc-client status

nn

To view diagnostic and error messages: $ boinccmd --get_messages

nn

Troubleshooting

nn

Receive error Authorization failure: -155 when executing boinccmd

nn

boinccmd is a command line management tool for managing the boinc client, which actually computes the work units. boinccmd communicates via boinc using GUI RPC (Graphical User Interface Remote Procedure Call). A single boinccmd tool can manage multiple boinc clients on multple machines, both local and remote. A password is used to authenticate requests between a tool/manager and the boinc client. More details available here.

nn

The password is stored in a file called gui_rpc_auth.cfg. Copies of this file are stored in three locations:

n

    n

  1. /var/lib/boinc-client/gui_rpc_auth.cfg
  2. n

  3. /etc/boinc-client/gui_rpc_auth.cfg
  4. n

  5. /~/gui_rpc_auth.cfg
  6. n

nn

The password in the file in the user’s home directory is compared to the copy in the /var and /etc directories. Assuming you aren’t interested in securing this program, or only plan on running and administering boinc locally, the simplest resolution to this issue is just the delete all three copies. Once I did this, I no longer received this error message.

nn

A workaround is to execute all boinccmd commands from the BOINC data directory (/var/lib/boinc-client).

Leave a Reply

Your email address will not be published. Required fields are marked *