Trouble downloading work to Raspberry Pi 3

Questions and Answers : Unix/Linux : Trouble downloading work to Raspberry Pi 3
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile FindingTribbles
Avatar

Send message
Joined: 18 Jan 14
Posts: 3
Credit: 19,873
RAC: 0
Portugal
Message 1811129 - Posted: 21 Aug 2016, 21:29:39 UTC

I'm having trouble downloading work units to my Raspberry Pi 3 (first time setup). Specifically, I continue to get a "communications differed" message in the advanced view panel. The account is recognized and the project loaded, however. Any ideas would be kindly appreciated.
ID: 1811129 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 1811310 - Posted: 22 Aug 2016, 10:20:50 UTC - in response to Message 1811129.  

You get "Communication deferred" messages when BOINC doesn't recognize something in your setup, like the operating system used, or the CPU. The project has got
Seti v8 applications for ARM CPUs, but it needs to be specific.

What you best can do now is post your startup messages, all the way from Starting BOINC client version 7.4.23 for *** till you've put a message from the project in. The messages will tell what's wrong. They can be reached through the Event Log (Tools->Event Log or CTRL+SHIFT+E).
ID: 1811310 · Report as offensive
Profile FindingTribbles
Avatar

Send message
Joined: 18 Jan 14
Posts: 3
Credit: 19,873
RAC: 0
Portugal
Message 1813315 - Posted: 29 Aug 2016, 1:34:31 UTC - in response to Message 1811310.  

Thank you Ageless and sorry for the delay - I've been traveling. Just taking a quick peek at this now and it looks like I've not the correct version installed....

28-Aug-2016 19:12:02 [---] Starting BOINC client version 7.4.23 for arm-unknown
...

28-Aug-2016 19:50:59 [SETI@home] No tasks are available for SETI@home v8
28-Aug-2016 19:50:59 [SETI@home] Your app_info.xml file doesn't have a usable version of SETI@home v8.
...

28-Aug-2016 20:57:51 [SETI@home] Sending scheduler request: To fetch work.
28-Aug-2016 20:57:51 [SETI@home] Requesting new tasks for CPU
28-Aug-2016 20:57:54 [SETI@home] Scheduler request completed: got 0 new tasks
28-Aug-2016 20:57:54 [SETI@home] No tasks sent
28-Aug-2016 20:57:54 [SETI@home] No tasks are available for SETI@home v7
28-Aug-2016 20:57:54 [SETI@home] No tasks are available for AstroPulse v7
28-Aug-2016 20:57:54 [SETI@home] No tasks are available for SETI@home v8
...

28-Aug-2016 20:57:54 [SETI@home] Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them



How I can go about fixing this through an SSH session? Must I first uninstall the version 7?

Thanks!
ID: 1813315 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 1813511 - Posted: 29 Aug 2016, 17:58:19 UTC - in response to Message 1813315.  

28-Aug-2016 19:50:59 [SETI@home] Your app_info.xml file doesn't have a usable version of SETI@home v8.

If you truly have that line in your log, then that will explain why.

Using the anonymous platform applications means that you have to tell BOINC which applications to use, and when the project updates its application, you have to manually update yours to get work again.

Easiest fix? Remove the app_info.xml file from the data directory/projects/setiathome.berkeley.edu/ and then reset the project.

Otherwise tell BOINC which applications to use, updated to Seti version 8.

Oh, BOINC is version 7, Seti is version 8, they've got nothing to do with each other for version numbering.
ID: 1813511 · Report as offensive
Profile FindingTribbles
Avatar

Send message
Joined: 18 Jan 14
Posts: 3
Credit: 19,873
RAC: 0
Portugal
Message 1813666 - Posted: 30 Aug 2016, 1:46:36 UTC - in response to Message 1813511.  

Thanks again, but something else (strange) seems to be going on... I checked and for some reason /home/pi directory is now missing. Is there a step by step guide to setting this up via the shell? Going it alone did not work all that well for me :-\

29-Aug-2016 21:25:30 dir_open: Could not open directory 'slots' from '/home/pi'.
29-Aug-2016 21:25:31 [---] GUI RPC bind to port 31416 failed: 98
29-Aug-2016 21:26:01 gstate.init() failed
Error Code: -180

ID: 1813666 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 1813741 - Posted: 30 Aug 2016, 8:35:37 UTC - in response to Message 1813666.  

'/home/pi' would assume you used Berkeley BOINC to install, because most package built versions install in /var/lib/ and such like directories.

You should be able to tell which path it is using, as BOINC will tell you in the start-up messages. There will be a line called Data directory with a path behind it.

And if the GUI RPC problem you have is with BOINC Manager, you can check those same messages in the data directory, stdoutdae.txt file. Or with the BOINCCMD tool in the terminal. Run boinccmd -h for help on that.
ID: 1813741 · Report as offensive

Questions and Answers : Unix/Linux : Trouble downloading work to Raspberry Pi 3


 
©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.