Hello Resin.io gurus,
I’m having issues rebooting my Raspberry Pi 3 Resin.io app. It loads fine and runs initially after a fresh disk burn. After hitting the reboot button in the dashboard, it gets stuck in “stopping” status.
For troubleshooting purposes, I created a leaner version of the app as a repository that has the same issues for me. I’m hoping that you are able to reproduce this issue? My thought currently is that I’m doing something incorrect with the docker file as was likely the case in this forum post. However, the issue has returned and seems reproducible. I can’t seem to pinpoint the issue just yet.
Support access is enabled. It’s ok to do as you wish with the device including reboots and other tasks as needed. The device url is:
https://dashboard.resin.io/devices/e144aba2f8baaf1e0700d71773dc895f/summary (updated)
How to reproduce the rebooting issue:
Setup a Raspberry Pi 3 application in resin.io.
Add a v2.7.8+rev1 device (I added wifi settings) and download the image.
Burn to disk (I used Etcher on PC, update: now using my Mac).
Clone troubleshooting project (I used a Mac, High Sierra).
git clone https://github.com/owntheweb/resin-io-temporary-troubleshooting.git
cd resin-io-temporary-troubleshooting
Add resin.io remote.
git remote add resin USERNAME@git.resin.io:USERNAME/PROJECTNAME.git
Push to resin.
git push resin master
Wait for the awesome unicorn of success.
Insert burned disk to Pi and power on.
Wait for the application to download to the Pi and launch. “Hello!” should be seen in the resin.io device logs showing that app.js has run successfully.
Choose “Reboot” in the resin.io dashboard device page.
After a last message of “Rebooting” is seen in the logs, the device partially reboots, stuck on the “Stopping” status. I can login to the host OS via the dashboard, but not the app container.
update: I’m seeing any blinking LEDs on the Pi. When plugged into HDMI, I’m seeing the Resin.io ASCII art with “Booted - Check your resin.io dashbard.”
Shots In the Dark
I burned this with a PC and made updates from a Mac. Could there be a character encoding issue happening somehow? (I have a new mac that requires an adapter for USB-C -> USB yeesh, should go buy one to see if using Mac all the way through helps) (went and bought and adapter, burned with Mac, same results)
If I sync with local copy or login to the dev image to run npm install commands, I was getting errors about characters not being recognized e.g. npm install promise after ssh’ing in was resulting in these errors.
Thank you!
Thanks for taking a look in advance! Please let me know if there is any additional information I can provide.
Kind regards,
Chris
