Journalctl not working

I have flashed a new card with the latest version of Satnogs client (I think) and the journalctl does not show the typical get jobs every 60 seconds or show the frequencies during an observation like my previous SD card (older version) did. But my system still seems to be doing observations. It is not connected to the antenna at this time because that requires going onto the roof, and I want to make sure everything is working properly (like the doppler correction) before I climb up there. I’m sure I downloaded the latest version of Satnogs (2023) but it still comes up satnogs-client-ansible-202209101521. Don’t understand this either.

Journalctl NOT during an observation shows this:
– Journal begins at Tue 2023-11-14 15:44:27 CST. –
Feb 27 12:46:26 raspberrypi satnogs-client[3872]: network_open: hoststr=127.0.0.1, portstr=4532
Feb 27 12:46:30 raspberrypi satnogs-client[4098]: Found Rafael Micro R820T tuner
Feb 27 12:46:30 raspberrypi satnogs-client[4098]: [INFO] Opening Generic RTL2832U OEM :: 00000001…
Feb 27 12:46:30 raspberrypi satnogs-client[4098]: Found Rafael Micro R820T tuner
Feb 27 12:46:30 raspberrypi satnogs-client[4098]: [R82XX] PLL not locked!
Feb 27 12:46:31 raspberrypi satnogs-client[4098]: [INFO] Using format CF32.
Feb 27 12:46:52 raspberrypi satnogs-client[4098]: /var/lib/satnogs/.gnuradio/prefs/vmcircbuf_default_factory: No such file or directory
Feb 27 12:46:52 raspberrypi satnogs-client[4098]: vmcircbuf_createfilemapping: createfilemapping is not available
Feb 27 12:46:52 raspberrypi satnogs-client[4098]: Allocating 15 zero-copy buffers
Feb 27 12:54:19 raspberrypi satnogs-client[3872]: netrigctl_close: done status=Command completed successfully

Any help would be appreciated. -AV

Here is support report:
Generating support report. Please wait…
------------[ copy here ]------------
{
“versions”: {
“satnogs-client”: “1.8.1”,
“satnogs-client-ansible”: “202209101521”,
“satnogs-flowgraphs”: “1.4-1”,
“gr-satnogs”: “2.3.5.0-1”,
“gr-soapy”: “2.1.3.1-1”,
“gnuradio”: “3.8.2.0-14”,
“satnogs-config”: “0.13.2”
},
“state”: {
“is-applied”: false,
“pending-tags”: [
“satnogs_client_config”
]
},
“system”: {
“date”: “2024-02-28T21:38:10.440612+00:00”,
“distribution”: {
“DESCRIPTION”: “Raspbian GNU/Linux 11 (bullseye)”,
“RELEASE”: “11”,
“CODENAME”: “bullseye”,
“ID”: “Raspbian”
},
“pending-updates”: false,
“platform”: {
“system”: “Linux”,
“node”: “raspberrypi”,
“release”: “6.1.21-v8+”,
“version”: “#1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023”,
“machine”: “aarch64”
},
“memory”: {
“total”: 3978645504,
“available”: 3724578816,
“percent”: 6.4,
“used”: 174145536,
“free”: 2707152896,
“active”: 278388736,
“inactive”: 858890240,
“buffers”: 38584320,
“cached”: 1058762752,
“shared”: 847872,
“slab”: 95424512
},
“disk”: {
“total”: 31073529856,
“used”: 3889139712,
“free”: 25867595776,
“percent”: 13.1
}
},
“configuration”: {
“satnogs_antenna”: “RX”,
“satnogs_api_token”: “[redacted]”,
“satnogs_rf_gain”: “12”,
“satnogs_rx_samp_rate”: “2.048e6”,
“satnogs_soapy_rx_device”: “driver=rtlsdr”,
“satnogs_station_elev”: “77”,
“satnogs_station_id”: “2303”,
“satnogs_station_lat”: “35.118”,
“satnogs_station_lon”: “-89.971”,
“sentry_enabled”: true
}
}

Hi @viano

My guess is that the DEBUG level isn’t enough to show you all the details. Try to raise it to DEBUG by following this guide.

Worked. Many thanks!

1 Like