Yes, it was the Raspbian image. That step not included.
I believe the images uses systemd.
Some cleanup would be handy and increase /tmp/.satnogs. Did find that can fill rather quick. Some waterfall files have been >50Mb
Interesting how .ogg files virtually always get uploaded, not so for waterfall. The latter helps to adjust gain.
As a trial, I’ve gone back to a manual build, but upgraded to latest gr-satnogs and satnogs-client.
It is possibly the same issue with the missing cleanup of completed jobs in the client. It could be that the system ran out of memory and started killing processes randomly. In the first case it may be rotctld and in the second GNU Radio.
This issue will be fixed with the release of SatNOGS client version 0.5 hopefully in a few days.
More Information regarding above logs: I have also tried building satnogs-client 0 branch locally, with similar results. Tried Fedora and Rasbian on raspberry pi 3. Regarding cleanup, the logs were on fresh system. I have tried this with multiple observations. I do-not have any rotor so did not set any related settings in the BASIC or ADVANCED settings page for them.
About SATNOGS_COMPLETE_OUTPUT_PATH, it is changed on v0.5 to be blank as the new default behaviour is after successful uploading to delete files (ogg, waterfall and data) and not moving them into the complete directory.
Edit: The rest seems to be compatibility issues between client and gr-satnogs.
I’ve changed the SATNOGS_COMPLETE_OUTPUT_PATH to blank.
Never knew about the Compatiblity page. Ok, so I need the latest gr-satnogs.
Now, not being a linux guru, how do I make sure I download and install the correct version? How do I check what version I have installed currently?
I tried git clone https://github.com/satnogs/gr-satnogs.git and recompile, but still not getting any data. Where is the data stored while and after processing. Couldn’t find ogg or waterfall files anywhere?
Sample of the log just after a METEOR-M 2 pass:
Oct 04 10:15:20 satnogs-vhf bash: 2017-10-04 10:15:20,846 - satnogsclient - DEBUG - Sending message: F 137897423
Oct 04 10:15:20 satnogs-vhf bash: 2017-10-04 10:15:20,849 - satnogsclient - DEBUG - Received message: RPRT 0
Oct 04 10:15:20 satnogs-vhf bash: 2017-10-04 10:15:20,973 - satnogsclient - DEBUG - Sending message: F 137897422
Oct 04 10:15:20 satnogs-vhf bash: 2017-10-04 10:15:20,978 - satnogsclient - DEBUG - Received message: RPRT 0
Oct 04 10:15:21 satnogs-vhf bash: Exception in thread Thread-101:
Oct 04 10:15:21 satnogs-vhf bash: Traceback (most recent call last):
Oct 04 10:15:21 satnogs-vhf bash: File “/usr/lib/python2.7/threading.py”, line 801, in __bootstrap_inner
Oct 04 10:15:21 satnogs-vhf bash: self.run()
Oct 04 10:15:21 satnogs-vhf bash: File “/usr/lib/python2.7/threading.py”, line 754, in run
Oct 04 10:15:21 satnogs-vhf bash: self.__target(*self.__args, **self.__kwargs)
Oct 04 10:15:21 satnogs-vhf bash: File “/usr/local/lib/python2.7/dist-packages/satnogsclient/observer/worker.py”, line 127, in _communicate_tracking_info
Oct 04 10:15:21 satnogs-vhf bash: self.check_observation_end_reached()
Oct 04 10:15:21 satnogs-vhf bash: File “/usr/local/lib/python2.7/dist-packages/satnogsclient/observer/worker.py”, line 175, in check_observation_end_reached
Oct 04 10:15:21 satnogs-vhf bash: self.trackstop()
Oct 04 10:15:21 satnogs-vhf bash: File “/usr/local/lib/python2.7/dist-packages/satnogsclient/observer/worker.py”, line 168, in trackstop
Oct 04 10:15:21 satnogs-vhf bash: os.killpg(os.getpgid(self._gnu_proc.pid), signal.SIGKILL)
Oct 04 10:15:21 satnogs-vhf bash: OSError: [Errno 3] No such process
Oct 04 10:15:33 satnogs-vhf bash: 2017-10-04 10:15:33,989 - apscheduler.executors.default - INFO - Running job “get_jobs (trigger: interval[0:01:00], next run at: 2017-10-04 02:16:33 UTC)” (scheduled at 2017-10-04 02:15:33.964267+00:00)
Oct 04 10:15:36 satnogs-vhf bash: 2017-10-04 10:15:36,019 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Hi @Zathras – I’m new to SatNOGS, but since you mentioned having the Raspbian image up above:
You can check which version of gr-satnogs is present by running dpkg -l gr-satnogs:
pi@raspberrypi:~/.ssh $ dpkg -l gr-satnogs
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
ii gr-satnogs 20171001.ae1e331-1 armhf SatNOGS GNU Radio Out-Of-Tree Module
Here, you can see that my version is “20171001.ae1e331-1” – meaning it was built October 1 2017, and it’s about a week old (looking for “ae1e331” on that page, you can see I’m a couple of updates behind.)
I’d assume that re-running the sudo satnogs-setup -n script is intended to take care of updating components.
Nope, that did not work for me. I’m not using the SatNOGS Raspbian image, just what created myself. The instructions no longer exist though Which is a pity because I did refer to them all the time.
I had several issues with the SatNOGS Raspbian image, which is why I went back to my version.
@Zathras If you have the rasbian image you used can you check if rotctld process was running? ps -ax or check if port 4533 is listening with netstat -nap
I got the same error on the fresh raspbian image and I think satnogs-client requires rotctld process running, which does not happen if HAMLIB_UTILS_ROT_ENABLED is set to False(No in the configuration screen). As @Acinonyx pointed above if there is no rotator then below setting are required.
I had to set the above setting to get rid of the above error. Correct me if I am wrong. The raspbian wiki might need to be updated or satnogs-client fixed.
Another issue. Also yesterday night I was testing raspbian image again and got lot of TLS certificate errors and PI stopped responding to ssh commands and communicating with website. This started just when a CW observation started. I could not even log back in to PI. I could reproduce it three times. So frustrating.