Ground Stations #33 & #328 not happy after upgrade

1

Both #33 and #328 were updated yesteday and both are returning purple waterfalls whereas before they seemed to be ok.

Ouptut from journalctl -u satnogs-client.service

    Dec 29 11:42:19 SatNOGSVHF systemd[1]: Started SatNOGS client.
    Dec 29 11:59:12 SatNOGSVHF satnogs-client[317]: 2019-12-29 11:59:12,554 - apscheduler.executors.default - ERROR - Job "get_jobs (trigger: interval[0:01:00], next run at: 2019-12-29 11:59:27 UTC)" raised an exception
Dec 29 11:59:12 SatNOGSVHF satnogs-client[317]: Traceback (most recent call last):
Dec 29 11:59:12 SatNOGSVHF satnogs-client[317]:   File "/usr/lib/python2.7/dist-packages/apscheduler/executors/base.py", line 125, in run_job
Dec 29 11:59:12 SatNOGSVHF satnogs-client[317]:     retval = job.func(*job.args, **job.kwargs)
Dec 29 11:59:12 SatNOGSVHF satnogs-client[317]:   File "/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/scheduler/tasks.py", line 164, in get_jobs
Dec 29 11:59:12 SatNOGSVHF satnogs-client[317]:     timeout=45)
Dec 29 11:59:12 SatNOGSVHF satnogs-client[317]:   File "/usr/lib/python2.7/dist-packages/requests/api.py", line 75, in get
Dec 29 11:59:12 SatNOGSVHF satnogs-client[317]:     return request('get', url, params=params, **kwargs)
Dec 29 11:59:12 SatNOGSVHF satnogs-client[317]:   File "/usr/lib/python2.7/dist-packages/requests/api.py", line 60, in request
Dec 29 11:59:12 SatNOGSVHF satnogs-client[317]:     return session.request(method=method, url=url, **kwargs)
Dec 29 11:59:12 SatNOGSVHF satnogs-client[317]:   File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 533, in request
Dec 29 11:59:12 SatNOGSVHF satnogs-client[317]:     resp = self.send(prep, **send_kwargs)
Dec 29 11:59:12 SatNOGSVHF satnogs-client[317]:   File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 646, in send
Dec 29 11:59:12 SatNOGSVHF satnogs-client[317]:     r = adapter.send(request, **kwargs)
Dec 29 11:59:12 SatNOGSVHF satnogs-client[317]:   File "/usr/lib/python2.7/dist-packages/requests/adapters.py", line 529, in send
Dec 29 11:59:12 SatNOGSVHF satnogs-client[317]:     raise ReadTimeout(e, request=request)
Dec 29 11:59:12 SatNOGSVHF satnogs-client[317]: ReadTimeout: HTTPSConnectionPool(host='network.satnogs.org', port=443): Read timed out. (read timeout=45)
Dec 29 12:06:54 SatNOGSVHF satnogs-client[317]: 2019-12-29 12:06:54,054 - satnogsclient.observer.commsocket - ERROR - Cannot connect to socket 127.0.0.1:4533
Dec 29 12:06:54 SatNOGSVHF satnogs-client[317]: 2019-12-29 12:06:54,060 - satnogsclient.observer.commsocket - ERROR - Cannot connect to socket 127.0.0.1:4533
Dec 29 12:06:54 SatNOGSVHF satnogs-client[317]: 2019-12-29 12:06:54,061 - satnogsclient.observer.commsocket - ERROR - Cannot send to socket 127.0.0.1:4533
Dec 29 12:06:54 SatNOGSVHF satnogs-client[317]: Exception in thread Thread-1:
Dec 29 12:06:54 SatNOGSVHF satnogs-client[317]: Traceback (most recent call last):
Dec 29 12:06:54 SatNOGSVHF satnogs-client[317]:   File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
Dec 29 12:06:54 SatNOGSVHF satnogs-client[317]:     self.run()
Dec 29 12:06:54 SatNOGSVHF satnogs-client[317]:   File "/usr/lib/python2.7/threading.py", line 754, in run
Dec 29 12:06:54 SatNOGSVHF satnogs-client[317]:     self.__target(*self.__args, **self.__kwargs)
Dec 29 12:06:54 SatNOGSVHF satnogs-client[317]:   File "/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/observer/worker.py", line 112, in _communicate_tracking_info
Dec 29 12:06:54 SatNOGSVHF satnogs-client[317]:     self.send_to_socket(pin, sock)
Dec 29 12:06:54 SatNOGSVHF satnogs-client[317]:   File "/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/observer/worker.py", line 198, in send_to_socket
Dec 29 12:06:54 SatNOGSVHF satnogs-client[317]:     position = sock.send("p\n").split('\n')
Dec 29 12:06:54 SatNOGSVHF satnogs-client[317]:   File "/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/observer/commsocket.py", line 81, in send
Dec 29 12:06:54 SatNOGSVHF satnogs-client[317]:     response = self.sock.recv(self._tasks_buffer_size).decode('ascii')
Dec 29 12:06:54 SatNOGSVHF satnogs-client[317]: error: [Errno 107] Transport endpoint is not connected
Dec 29 12:06:59 SatNOGSVHF satnogs-client[317]: gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.13.4
Dec 29 12:06:59 SatNOGSVHF satnogs-client[317]: built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri hackrf bladerf rfspace airspy airspyhf soapy redpitaya freesrp
Dec 29 12:06:59 SatNOGSVHF satnogs-client[317]: FATAL: Failed to open AirSpy device (-5) AIRSPY_ERROR_NOT_FOUND
Dec 29 12:06:59 SatNOGSVHF satnogs-client[317]: Trying to fill up 1 missing channel(s) with null source(s).
Dec 29 12:06:59 SatNOGSVHF satnogs-client[317]: This is being done to prevent the application from crashing
Dec 29 12:06:59 SatNOGSVHF satnogs-client[317]: due to gnuradio bug #528.

Any clues?

2

This looks like the main problem:

It isn’t finding your SDR.

3

I agree with Jebba, this problem is consistent with purple waterfalls.

If your AirSpy is plugged in, as I suspect, it may be a permission problem.
You can use airspy_info from the airspy package. If it works only with the root user, it is a permission issue. You’ll have to see in /etc/group file and in /etc/udev/rules.d to fix this.

4

Trouble is I get the the same purple waterfall with an rtl_sdr station (328) that doesn’t have the same error message. Both of these were working prior to upgrade I’m guessing that these issues are common.

5

The purple waterfalls often happen when there is a problem with the connection between the SDR and the computer (SDR not recognized) . I do not know the details of how it happens (upgrade or any), it is often difficult to know as it can depend on the complete history.

6

I’ve gone with a reset in satnogs-setup and start agin with the config. If that fails then I’ll reflash the sd cards and start afresh

7

What error message does the other one give? Does airspy_info and other similar applications work when running as user pi (e.g. not as root)?