Satnogs-client.service not found

[SA2KNG]

journal is a systemd thing, not docker.
here’s a few threads where we have touched some of this:

Install and run on RPI4 and SDRPlay RSP1a

If you switch to the new stack, most of the software is located inside the docker images and not on the host. Which means that you should jump in to a shell inside the container and run it there instead of on the host. sudo docker exec -it satnogs_satnogs-client bash then inside that shell that should look something like: satnogs-client@00e0894cb01c:/usr/src$ you can run SoapySDRUtil, this will also test that is is reachable from the container as well. Checking the logs with sudo docker logs …

Need help debugging my setup

Welcome @frank_schirpke ! This is a misleading message in the SatNOGS web service and should be ignored. (@sfou: Can we hide the “Configuration” tab until this feature is finished, to avoid confusion?) It is not related to the problem of your station, as @Acinonyx suggested already too. Debugging: Current status satnogs-client is fetching jobs and is uploading observation metadata successfully, e.g. most recently in 11000114. no waterfall image is produced or uploaded, nor any audio file o…

All the documentation and troubleshooting is slowly catching up to the new stack. SatNOGS Setup - SatNOGS Wiki