"My app isn't working, now what?"

Troubleshooting
1

Hi everyone,

If you’re experiencing issues with your unit, here are some steps to help troubleshoot. First thing’s first, go to your unit and find the IP address that’s on the screen on front of the unit, this is required for every link below:

  • Access System Logs:
    Even if the unit seems unresponsive, you can still reach the system logs through a separate service. Navigate to http://{Device IP}:19531/entries to view them. If you’re unable to access the logs, this may point to a hardware or network issue. You can save these logs to a text file and send them to the support@micro-nova.com to help us begin to troubleshoot your issue.
  • Reach the Updater:
    To update your unit, go to http://{Device IP}:5001/update and click the update button. If your unit failed after an update, updating again can sometimes solve this. You can find the device’s IP on the front screen of the unit.
  • Request a Support Tunnel:
    If you need assistance, you can set up a support tunnel by visiting http://{Device IP}:5001. From there, click on the Support Tunnel tab. Send the credentials and some background information on your issues to support@micro-nova.com, and we’ll be happy to help.
2

Quick question; where are the log entries stored on the AmpliPi? The ones viewable at :19531/entries.

I have a NodeRED flow that queries the AmpliPi API every 5s, to keep track of changes and send updates to some DIY wall panels I have around the house for controlling my music.

Querying /entries returns a LOT of data;

Sep 12 22:23:33 amplipi authbind[813]: INFO:     192.168.10.23:58512 - "GET /api HTTP/1.1" 200 OK
Sep 12 22:23:34 amplipi authbind[813]: INFO:     192.168.10.25:49576 - "GET /api/ HTTP/1.1" 200 OK
Sep 12 22:23:34 amplipi authbind[813]: INFO:     192.168.10.25:49576 - "GET /api/ HTTP/1.1" 200 OK
Sep 12 22:23:34 amplipi authbind[813]: INFO:     192.168.10.25:49576 - "GET /api/ HTTP/1.1" 200 OK
Sep 12 22:23:34 amplipi authbind[813]: INFO:     192.168.10.25:49576 - "GET /api/ HTTP/1.1" 200 OK
Sep 12 22:23:35 amplipi authbind[813]: INFO:     192.168.10.25:49576 - "GET /api/ HTTP/1.1" 200 OK

I just want to ensure these are not being written to the Pi storage and wearing it out!

3

We’re aware of the limited read/write cycles that a pi’s EMMC is capable of surviving, we’ve anticipated this and have set logs to store to memory rather than to disc by default.

We are anticipating a near future where logs can optionally be stored to disc should they be needed for troubleshooting post-reboot, if you have that setting selected (again, once that update is released) they’ll be stored at /var/logs/journal/.

4

Yep cool, that is what I thought, as I poked around /var/logs and couldn’t see any syslog or the like. Just wanted to confirm that my high rate polling wasn’t causing issues.

5

Just for a data point, my upgrade to 0.4.4 went very sideways. Tried more than once to update and the first “copying software” step would error out with a message that the return code from the “cp” command was failing.

I figured something might be just stuck somewhere, so I went into the interface and issued a reboot. Then the web interface didn’t start at all. Rebooted again, same thing. Followed the above directions to load port 5001 and /update to get the update going again and from there was successful.

Interesting side note, all my internet radio stations that vanished with the 0.4.x upgrade came back.

1 Like