Improve handling of confusing log output "vmcircbuf_default_factory: No such file or directory" on first observation
On a fresh SatNOGS (RF, stable) installation, satnogs-client outputs the following message:
/var/lib/satnogs/.gnuradio/prefs/vmcircbuf_default_factory: No such file or directory
vmcircbuf_createfilemapping: createfilemapping is not available
gr::vmcircbuf_sysv_shm: shmat (2): Invalid argument
gr::vmcircbuf_sysv_shm: shmat (2): Invalid argument
gr::vmcircbuf_sysv_shm: shmat (2): Invalid argument
The file .gnuradio/prefs/vmcircbuf_default_factory
is created the first time GNURadio gets executed (source), so this is normal and not an error.
Unfortunately the fact that this is normal is not conveyed by the message. Thus it is a prime candidate to be confused with unrelated errors. This happened multiple times in the past:
- 2020-04-03: https://community.libre.space/t/initial-rtl-sdr-setup-issues/5903/8
"Seems there is something screwy. The /home/pi/.gnuradio/prefs does contain the file???"
- 2020-05-20: https://community.libre.space/t/demodulate-lrpt-from-satnogs-iq-file/6167/25
Seems I can ignore the first couple as warnings; not sure about the remainder but they do seem to stop and don’t recur on next run so I assume it’s to do with setting stuff up.
- 2019-12-22: https://community.libre.space/t/its-time-to-upgrade-the-software-of-your-stations/2019/44
After an reception this message turns up
Full log output:
pi@station132:~ $ sudo systemctl --no-pager status satnogs-client
● satnogs-client.service - SatNOGS client
Loaded: loaded (/etc/systemd/system/satnogs-client.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2023-03-22 15:40:14 GMT; 13min ago
Main PID: 14074 (satnogs-client)
Tasks: 50 (limit: 4915)
CPU: 2min 32.648s
CGroup: /system.slice/satnogs-client.service
├─14074 /var/lib/satnogs/bin/python /var/lib/satnogs/bin/satnogs-client
└─14239 /usr/bin/python3 /usr/bin/satnogs_fsk.py --soapy-rx-device=driver=rtlsdr --samp-rate-rx=2.048e6 --rx-freq=435950000 --file-path=/tmp/.satnogs/data/receiving_satnogs_731…
Mar 22 15:51:14 station132 satnogs-client[14239]: [INFO] Opening Generic RTL2832U OEM :: 00000001...
Mar 22 15:51:15 station132 satnogs-client[14239]: Found Rafael Micro R820T tuner
Mar 22 15:51:15 station132 satnogs-client[14239]: [R82XX] PLL not locked!
Mar 22 15:51:15 station132 satnogs-client[14239]: [INFO] Using format CF32.
Mar 22 15:51:37 station132 satnogs-client[14239]: /var/lib/satnogs/.gnuradio/prefs/vmcircbuf_default_factory: No such file or directory
Mar 22 15:51:37 station132 satnogs-client[14239]: vmcircbuf_createfilemapping: createfilemapping is not available
Mar 22 15:51:37 station132 satnogs-client[14239]: gr::vmcircbuf_sysv_shm: shmat (2): Invalid argument
Mar 22 15:51:37 station132 satnogs-client[14239]: gr::vmcircbuf_sysv_shm: shmat (2): Invalid argument
Mar 22 15:51:37 station132 satnogs-client[14239]: gr::vmcircbuf_sysv_shm: shmat (2): Invalid argument
Mar 22 15:51:37 station132 satnogs-client[14239]: Allocating 15 zero-copy buffers
Change the log format to show the log message severity. The gnuradio output could be logged with severity "INFO" so that it's clear that those message are normal and do not correspond to an error.
Related Issues
- #378: Superfluous rtlsdr driver & hamlib output circumvents the python logger