Cannot Access rs.local or Web Interface Despite Device Showing on Network

Technical Support
1

I cannot access rs.local
I checked the IP from my router/app and confirmed the Raspberry Shake is connected to the network. When I enter that IP in a browser, the page is completely blank.
I can connect to the device via FileZilla (SFTP) using the same IP, but SWARM cannot connect to it.

What should I do next?

2

hi pakkapong,

since SFTP is working, i assume ssh will also work as well. using whichever method you prefer, i would appreciate it if you would download the log files for me and post them here.

  1. via SFTP, download the folder /opt/log, bundle accordingly, and post the file here
  2. via ssh, after logging in to the Shake, the following commands:
    > cd /opt
    > tar cf /tmp/logs.tar log
    > bzip2 /tmp/logs.tar
  1. use SFTP to download the compressed file /tmp/logs.tar.bz2, and post it here

with log files in hand, i will be able to investigate the issue and propose a solution for you.

thanks in advance,
richard

3

logs.tar.bz2 (212.2 KB)
Hi Richard,
Here is the file logs.tar.bz2 you requested.
Please let me know if you need anything else.

Thanks!

4

hi,
the issue has been diagnosed and a solution identified. i will post again tomorrow the details once it has been finalized and packaged.

cheers,
richard

5

hello,

A program is attached below that solves the issue you are having with the upgrade.

Problem Description
Part of the upgrade involves downloading a new docker image and installing it on the Shake-Pi computer. If, in the middle of this download, the command is unexpectedly stopped, (e.g., system is rebooted), it is possible that the docker directories involved can become corrupt.

Resolution
The attached program addresses this situation:

  1. Saves all current docker images to a tar file
  2. Recreates the docker directories
  3. Restores all docker images saved in step 1
  4. Confirms download of new image is now successful

Instructions

  1. Download the attached program to your local computer
  2. Copy the program to the Shake needing to be healed, using scp or any FTP transfer program
    2.1. Copy to directory /tmp
  3. Log in to the Shake using ssh:
    3.1. > ssh [email protected] # default pw: shakeme
  4. Issue the following command:
    4.1. > /tmp/docker-rebuild

A Success or Failure message will be output once the program completes its work:

  1. On Success, reboot the Shake-Pi to complete the upgrade.
  2. On Failure, file system remains in a corrupted state and will require an SD card re-burn in order to proceed.

Please report back any other issues you may come across, we are always very interested in knowing about all the situations which may occur across all the units installed all over the world.

regards,
richard

docker-rebuild (58.4 KB)

6

I am having the exact same problem. I can see my shake (R16F7) on StationView and it is showing current activity; however, I can’t access it on either rs.local or using the shake IP address. I suspect the SD card might be corrupt because the shake has been rebooted a few times because it lost power (it is solar powered with a backup battery but several cloudy days in a row drained the battery resulting in the shake being shut down). Is an SD card re-burn my only option?
Bill

7

hi bill,

before re-burning, you should try to apply the program provided in the response above to correct corruption in the file system.

only when this does not succeed should you have to resort to a re-burn of the SD card.

if possible, please report back whether or not the program worked to correct your problem.

thanks in advance,
richard

8

Hello,

I was able to copy docker-rebuild to the pi and run it. It completed successfully and I rebooted. However, browsing to rs.local or to the IP address still does not work. As before, the pi is online and sending current data but I cannot access it like I had before. Not sure how to proceed.

9

hi,
sorry to hear that.

Can you send me the log files using these instructions:?

thanks,
richard

10

Hello again,

Here is my log file:
logs.tar.bz2 (231.8 KB)

Bill

11

I am having the same problem.

I had to make the file executable before it worked.

Waited 20 minutes and never got a success or failure message, after rebooting I get a wave form in Swarm but no webpage.

I tried to run the command again, same results as before. I am getting a waveform in Swarm and in Station View, but no local webpage.

12

hi bill,

thank you for the logs, they are pointing to a different issue than the docker download failure. i am looking into the problem and will report back once i have identified a solution.

thanks for your patience and apologies for the inconvenience.

cheers,
richard

13

hi bill,

the updater has been modified to generate more log file output than before, to expose the part of the installation that is not succeeding as it should. can you reboot your unit, and after it is back up, send me just this one file from the log directory:

  • /opt/log/upgrade.log

once i have this in hand i will be able to identify the exact issue so that the proper solution can be identified and applied.

thanks in advance,
richard

14

Hello Richard, My upgrade.log is attached.
Bill
upgrade.log (270.4 KB)

15

thanks, exactly what i need. stay tuned…

richard

16

Hi Richard, here is mine as well, if you wish to take a look at it.

upgrade.log (335.3 KB)

17

FYI:

  1. the problem is identified and understood
  2. a solution has been defined and will be prepared
  3. a new updater will be issued later today that will address this issue; a version bump will not be needed

thank you to everybody for the quick turnaround with the log files and overall cooperation, it is invaluable in situations like these.

cheers,
richard

18

Update:

  1. the V21 updater has been updated to solve the issue of python dependencies failing install

please reboot your unit, confirm problem is resolved or not (FE-config should work), and report back the results. in the case where any update issue remains, this or any other, kindly forward the log files for further inspection.

and thanks again for the quick turnaround and feedback, it is invaluable.

cheers,
richard

1 Like
19

Thanks. My shake is up and working correctly.

2 Likes
20

Thanks, Richard,
I rebooted and was able to see the new interface for the first time. Thanks for all your help!
Bill

2 Likes