System wont update , now in testing mode

Hi my system has been placed in testing mode after looking to have gone deaf

sudo apt update finds 6 updates
sudo apt upgrade 6 updates run in follwed by reboot
update of satnogs client runs but gets the error
Failed to lock directory /var/lib/apt/lists/: E:Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)

running the update get the error

ERROR! couldn’t resolve module/action ‘ansible.posix.mount’. This often indicate s a misspelling, missing collection, or incorrect module path.

The error appears to be in ‘/root/.satnogs/ansible/roles/satnogs_client/tasks/ma in.yml’: line 138, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

- Restart satnogs-client service
  • name: Use tmpfs for state directory
    ^ here

Is anyone able to help?
Cheers
Max

what station and what version is the client and os now ?

This looks like you didn’t run the satnogs client command using sudo.

“versions”: {
“satnogs-client”: “1.6”,
“satnogs-client-ansible”: “202209101521”,
“satnogs-flowgraphs”: “1.4-1”,
“gr-satnogs”: “2.3.3.0-1”,
“gr-soapy”: “2.1.3.1-1”,
“gnuradio”: “3.8.2.0-14satnogs2”,
“satnogs-config”: “0.12”
},
“state”: {
“is-applied”: false,
“pending-tags”: null
},
“system”: {
“date”: “2023-03-06T06:56:27.905181+00:00”,
“distribution”: {
“DESCRIPTION”: “Raspbian GNU/Linux 10 (buster)”,
“RELEASE”: “10”,
“CODENAME”: “buster”,
“ID”: “Raspbian”
},
“pending-updates”: false,
“platform”: {
“system”: “Linux”,
“node”: “satnogs”,
“release”: “5.15.52-v7+”,
“version”: “#1570 SMP Mon Jul 4 13:29:14 BST 2022”,
“machine”: “armv7l”,
“processor”: “”

is this info any use ?

system overview

all plots being generated are signal free, usualy ISS shows voice traffic ( this may be off at the minute but this has been 3 weeks ) , nothing has changed in the setup, I have tested the rtl sdr and it works on the usual signals using sdr#, rtl_test returns expected results, I have a tinygs and ADSB on the same discone and all get a signal, this set up hasn’t changed, anything else I could try? thanks for your help

using sudo to run the update, the applying update gives

ERROR! couldn’t resolve module/action ‘ansible.posix.mount’. This often indicates a misspelling, missing collection, or incorrect module path.

The error appears to be in ‘/root/.satnogs/ansible/roles/satnogs_client/tasks/main.yml’: line 138, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

- Restart satnogs-client service
  • name: Use tmpfs for state directory
    ^ here

update of satnogs client runs but gets the error
“CODENAME”: “buster”,
“ID”: “Raspbian”

@blueskies

I seem to recall hosing my RPi buster (10) satnogs-client image a few months ago when trying to update the satnogs-client - I don’t recall the exact error it produced but it cratered. The developer team should be able to confirm if the buster Rpi image is no longer supported (breaks when an update is run ) and updating to bullseye (11) is the resolution. Or I could be totally off here. One or the other :slight_smile:

Scott

Just tried rebuildng the station, is raspberry pi 3 still supported ? I have read that bullseye doesn’t run on a 3 only on a 4 ? Does the pi have to be on bullseye now ?
Cheers

Max

Raspi 3B running here with client 1.8.1 since 6 months ago and no problems. Regularly updates but no upgrades yet.

Rafael

Any Raspberry Pi which is supported by Raspberry Pi OS (previously “Raspbian”) is also supported by the SatNOGS Image, including the Pi 3.

Yes, the SatNOGS Image is based on bullseye (announcement in this post).

Raspbian Buster is no longer supported by SatNOGS Client Software. Unfortunately it was not possible to implement an upgrade for “old” SatNOGS Stations (based on Raspbian buster) to bullseye. Thus, to update an “old” SatNOGS station (as identified by “DESCRIPTION”: “Raspbian GNU/Linux 10 (buster)” in the Support Information), flashing a fresh image is required (docs).

Hi all
have managed to get the system up but all my tests have failed , the future passes take a long time to build. Any advice? below is one of the passes metadata

{

  • radio: {
    • name: “gr-satnogs”,
    • version: “v2.3-compat-xxx-v2.3.4.0”,
    • parameters: {
      • soapy-rx-device: “driver=rtlsdr”,
      • samp-rate-rx: “2.048e6”,
      • rx-freq: “137912500”,
      • file-path: “/tmp/.satnogs/data/receiving_satnogs_7381106_2023-04-07T09-10-18.out”,
      • waterfall-file-path: “/tmp/.satnogs/data/receiving_waterfall_7381106_2023-04-07T09-10-18.dat”,
      • decoded-data-file-path: “/tmp/.satnogs/data/receiving_data_7381106_2023-04-07T09-10-18.png”,
      • doppler-correction-per-sec: null,
      • lo-offset: null,
      • ppm: null,
      • rigctl-port: “4532”,
      • gain-mode: “Overall”,
      • gain: “32.8”,
      • antenna: "Discone ",
      • dev-args: null,
      • stream-args: null,
      • tune-args: null,
      • other-settings: null,
      • dc-removal: null,
      • bb-freq: null,
      • bw: null,
      • enable-iq-dump: “0”,
      • iq-file-path: null,
      • udp-dump-host: null,
      • udp-dump-port: 57356,
      • wpm: null,
      • baudrate: null,
      • framing: null}},
  • latitude: -40.95972,
  • longitude: 175.6575,
  • elevation: 150,
  • frequency: 137912500

}

This is not the antenna description, rather the antenna port on the SDR. It’s usually RX on the rtl-sdr’s.
This should be visible in the log, as the flowgraph fails to run when it doesn’t get the correct sdr settings.

1 Like

You can only use SDR values that are present in Soapy.

So for a RTLSDR this is:

SoapySDRUtil --probe="driver=rtlsdr"

######################################################
##     Soapy SDR -- the SDR abstraction library     ##
######################################################

Probe device driver=rtlsdr
Found Rafael Micro R820T/2 tuner
[INFO] Opening Generic RTL2832U OEM :: 00001985...
Found Rafael Micro R820T/2 tuner

----------------------------------------------------
-- Device identification
----------------------------------------------------
  driver=RTLSDR
  hardware=R820T
  index=0
  origin=https://github.com/pothosware/SoapyRTLSDR

----------------------------------------------------
-- Peripheral summary
----------------------------------------------------
  Channels: 1 Rx, 0 Tx
  Timestamps: YES
  Time sources: sw_ticks
  Other Settings:
     * Direct Sampling - RTL-SDR Direct Sampling Mode
       [key=direct_samp, default=0, type=string, options=(0, 1, 2)]
     * Offset Tune - RTL-SDR Offset Tuning Mode
       [key=offset_tune, default=false, type=bool]
     * I/Q Swap - RTL-SDR I/Q Swap Mode
       [key=iq_swap, default=false, type=bool]
     * Digital AGC - RTL-SDR digital AGC Mode
       [key=digital_agc, default=false, type=bool]
     * Bias Tee - RTL-SDR Blog V.3 Bias-Tee Mode
       [key=biastee, default=false, type=bool]

----------------------------------------------------
-- RX Channel 0
----------------------------------------------------
  Full-duplex: NO
  Supports AGC: YES
  Stream formats: CS8, CS16, CF32
  Native format: CS8 [full-scale=128]
  Stream args:
     * Buffer Size - Number of bytes per buffer, multiples of 512 only.
       [key=bufflen, units=bytes, default=262144, type=int]
     * Ring buffers - Number of buffers in the ring.
       [key=buffers, units=buffers, default=15, type=int]
     * Async buffers - Number of async usb buffers (advanced).
       [key=asyncBuffs, units=buffers, default=0, type=int]
  Antennas: RX
  Full gain range: [0, 49.6] dB
    TUNER gain range: [0, 49.6] dB
  Full freq range: [23.999, 1764] MHz
    RF freq range: [24, 1764] MHz
    CORR freq range: [-0.001, 0.001] MHz
  Sample rates: [0.225001, 0.3], [0.900001, 3.2] MSps
  Filter bandwidths: [0, 8] MHz

As you can see for Antennas: there is only the RX option, so this should be changed in you config.

Thank you will investigate this tommorow. Ill let you know how it goes

Many thanks for the help , system back online and out of testing
cheers
Max

1 Like