Troubleshooting guide

General

Before doing any investigation, it is good practice to check the log. It is available in journald.

Get the last 200 log entries:

journalctl -u r2cloud -n 200

Get errors:

journalctl -u r2cloud -p 3

Common errors

1. The most common error is a disk space. Check current disk space:

df -h

There are different ways to solve:

• Buy bigger SD card
• Use SSD instead/alongside of SD card
• Disable uninterested satellites. This could be done in r2cloud ui. Click on "Satellites" link at the top and de-select satellite.
• Run second Rpi in parallel. Configure satellites transmitting on 13x Mhz, 14x Mhz on one Rpi and 43x Mhz on second Rpi.
• Configure retention policy for old observations.

2. usb_claim_interface error

This normally happen if something else is using rtl. Check if no other software installed is using rtl.

ps aux|grep rtl_

r2cloud errors

1. Integration with Satnogs configured, but i'm not seeing any data there.

• Satnogs adds grid square to your callsign while saving observation. Make sure you're using it while quering their API. For example: https://db.satnogs.org/api/telemetry/?satellite=&app_source=&observer=M7RED-LO33sr&transmitter=&start=&end=
• Only telemetry uploaded to Satnogs via SiDS protocol. Weather satellites are not supported

2. I'm seeing observations in r2cloud, but not in r2server.ru

• Check logs for specific satellite. Grep using Norad id. For example:

journalctl -u r2cloud -n 500 |grep 44387

• They should contain "uploading observation"
• Check filesystem. r2cloud doesn't support /tmp on a separate filesystem. If "/tmp" and "/home/pi/r2cloud" are on different filesystems (mounts), then configure tmp directory in ~/.r2cloud to be:

server.tmp.directory=/home/pi/r2cloud/tmp