System wont update , now in testing mode

SatNOGS Software
1

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

2

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

3

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

4

“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

5

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
6

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

7

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

8

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

Rafael