Raspbian SatNOGS client image issues

[Jferns]

@fredy

sudo journalctl -u satnogs-client.service | less

That will allow you to get all the file from start and move to the end by pressing down arrow or page down. Press Q to exit.

sudo journalctl -u satnogs-client.service | grep rror

This will print only the rows with errors. Yes it misses the e in order to catch both Error and error as grep is case sensitive. if you need to check some rows above (Before) or bellow (After) that row use -A and/or -B . for example:

sudo journalctl -u satnogs-client.service | grep rror -A 2 -B 2

It will show 2 lines before and after the matched row.

Finally journalctl allows you to filter logs with some time parameters… you need to check this in its manual.

If you are able to watch live one of the observations then you can use:

sudo journalctl -f -u satnogs-client.service

This is useful information that could be added to WIKI

[Zathras]

Observation 7091 & 7092 - Falconsat-3 FSK9k6
Waterfall, audio and data uploaded to dev-network ok, after removing RX-Gain from .env

Log shows:
Oct 05 21:27:32 satnogs-uhf bash[4669]: [WARNING] /home/satnogs/gr-satnogs/lib/ax25_decoder_bm_impl.cc:379: Wrong crc
About every minute for the duration of both observations.

/tmp directory is full of files, end time changes:
fsk9600_crc_failed_2017-10-05T13-27-06.hex
fsk9600_crc_failed_2017-10-05T13-27-06.txt

After 2 observations there is approx 2000 files in /tmp

[Jferns]

@fredy

For rasbian, these are the instructions but for fedora we have removed them without moving them to wiki.

For now we can find the fedora process here.

I think we should move it back either on wiki or docs repo until all issues with the new rasbian image are solved and it is stable like the fedora one.

Request to revert commit so documentation for fedora is available. Lots of documentation links are broken.

[comzeradd]

I moved the Fedora installation instructions on the wiki. It needs some editing to fix formatting issues and convert rst sytnax to md, but it’s readable.

If you have found broken links on documentation please list them here to be fixed.

[Zathras]

Hmm, my UHF station is broken

Noticed it had been down for almost a day. Pings ok but no satnogs running. Reboot, no difference. Tried satnogs-setup and end up with the below:

  Oct 26 16:50:24 satnogs-uhf systemd[1]: Dependency failed for SatNOGS client.
  Oct 26 16:50:24 satnogs-uhf systemd[1]: satnogs-client.service: Job satnogs-client.service/start failed with result 'dependency'.

fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "Unable to start service satnogs-client: A dependency job for satnogs-client.service failed. See 'journalctl -xe' for details.\n"}

 journalctl -xe
Oct 26 17:29:11 satnogs-uhf systemd[1]: Failed to start Advanced key-value store.
-- Subject: Unit redis-server.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit redis-server.service has failed.
--
-- The result is failed.
Oct 26 17:29:11 satnogs-uhf systemd[1]: redis-server.service: Unit entered failed state.
Oct 26 17:29:11 satnogs-uhf systemd[1]: redis-server.service: Failed with result 'exit-code'.
Oct 26 17:29:11 satnogs-uhf systemd[1]: redis-server.service: Service hold-off time over, scheduling restart.
Oct 26 17:29:11 satnogs-uhf systemd[1]: Stopped Advanced key-value store.
-- Subject: Unit redis-server.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit redis-server.service has finished shutting down.
Oct 26 17:29:11 satnogs-uhf systemd[1]: redis-server.service: Start request repeated too quickly.
Oct 26 17:29:11 satnogs-uhf systemd[1]: Failed to start Advanced key-value store.
-- Subject: Unit redis-server.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit redis-server.service has failed.
--
-- The result is failed.
Oct 26 17:29:11 satnogs-uhf systemd[1]: redis-server.service: Unit entered failed state.
Oct 26 17:29:11 satnogs-uhf systemd[1]: redis-server.service: Failed with result 'exit-code'.
Oct 26 17:30:06 satnogs-uhf sudo[952]: pam_unix(sudo:session): session closed for user root
lines 1845-1873/1873 (END)

I guess a re-image is in order ???