New Pi setup, "no such process", check_observation_end_reached


#1

Hi folks. I’ve seen the “no such process” error with check_observation_end_reached in older issues like this one where rx-gain fails and this one that has no workaround other than reinstalling. However I don’t see anything that is current. Here’s the error during an observation, more details afterwards.

Feb  2 23:11:20 raspberrypi satnogs-client[529]: 2019-02-02 23:11:20,860 - apscheduler.executors.default - INFO - Job "post_data (trigger: interval[0:02:00], next run at: 2019-02-02 23:13:20 UTC)" executed successfully
Feb  2 23:11:22 raspberrypi satnogs-client[529]: 2019-02-02 23:11:22,138 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2019-02-02 23:12:20 UTC)" executed successfully
Feb  2 23:11:40 raspberrypi satnogs-client[529]: Exception in thread Thread-661:
Feb  2 23:11:40 raspberrypi satnogs-client[529]: Traceback (most recent call last):
Feb  2 23:11:40 raspberrypi satnogs-client[529]:   File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
Feb  2 23:11:40 raspberrypi satnogs-client[529]:     self.run()
Feb  2 23:11:40 raspberrypi satnogs-client[529]:   File "/usr/lib/python2.7/threading.py", line 754, in run
Feb  2 23:11:40 raspberrypi satnogs-client[529]:     self.__target(*self.__args, **self.__kwargs)
Feb  2 23:11:40 raspberrypi satnogs-client[529]:   File "/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/observer/worker.py", line 123, in _communicate_tracking_info
Feb  2 23:11:40 raspberrypi satnogs-client[529]:     self.check_observation_end_reached()
Feb  2 23:11:40 raspberrypi satnogs-client[529]:   File "/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/observer/worker.py", line 168, in check_observation_end_reached
Feb  2 23:11:40 raspberrypi satnogs-client[529]:     self.trackstop()
Feb  2 23:11:40 raspberrypi satnogs-client[529]:   File "/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/observer/worker.py", line 164, in trackstop
Feb  2 23:11:40 raspberrypi satnogs-client[529]:     os.killpg(os.getpgid(self._gnu_proc.pid), signal.SIGINT)
Feb  2 23:11:40 raspberrypi satnogs-client[529]: OSError: [Errno 3] No such process
Feb  2 23:12:20 raspberrypi satnogs-client[529]: 2019-02-02 23:12:20,827 - apscheduler.executors.default - INFO - Running job "get_jobs (trigger: interval[0:01:00], next run at: 2019-02-02 23:13:20 UTC)" (scheduled at 2019-02-02 23:12:20.756297+00:00)

My setup is an RTL-SDR on a Pi3. I’ve set it up in the past 48 hours using fresh images. My config seems reasonable. The tmp directory is nearly empty:

$ find /tmp/.satnogs/ -type f
/tmp/.satnogs/jobs.sqlite
/tmp/.satnogs/data/receiving_waterfall_445722_2019-02-02T23-02-19.dat
$ ls -l /tmp/.satnogs/data/receiving_waterfall_445722_2019-02-02T23-02-19.dat
-rw-r--r-- 1 satnogs satnogs 4100 Feb  2 23:02 /tmp/.satnogs/data/receiving_waterfall_445722_2019-02-02T23-02-19.dat

Finally, I ran satnogs_fm_demod.py, it successfully creates an ogg file of white noise. The audio uploaded of the observation (to network) was 4.2k, which I assume is only ogg headers.

For fun I did “apply” in the satnogs-setup again and rebooted, so we’ll see if any successive observations succeed. I just don’t know what to troubleshoot other than this.


#2

woot, I got some more errors.

Feb  3 03:10:35 raspberrypi satnogs-client[513]: Using device #0 Realtek RTL2838UHIDIR SN: 00000001
Feb  3 03:10:35 raspberrypi satnogs-client[513]: Using 32 buffers of size 16384.
Feb  3 03:10:35 raspberrypi satnogs-client[513]: Found Rafael Micro R820T tuner
Feb  3 03:10:36 raspberrypi satnogs-client[513]: [R82XX] PLL not locked!
Feb  3 03:10:36 raspberrypi satnogs-client[513]: Exact sample rate is: 1000000.026491 Hz
Feb  3 03:10:36 raspberrypi satnogs-client[513]: [R82XX] PLL not locked!
Feb  3 03:10:36 raspberrypi satnogs-client[513]: Traceback (most recent call last):
Feb  3 03:10:36 raspberrypi satnogs-client[513]:   File "/usr/bin/satnogs_bpsk_ax25.py", line 434, in <module>
Feb  3 03:10:36 raspberrypi satnogs-client[513]:     main()
Feb  3 03:10:36 raspberrypi satnogs-client[513]:   File "/usr/bin/satnogs_bpsk_ax25.py", line 428, in main
Feb  3 03:10:36 raspberrypi satnogs-client[513]:     tb = top_block_cls(antenna=options.antenna, baudrate=options.baudrate, bb_gain=options.bb_gain, decoded_data_file_path=options.decoded_data_file_path, dev_args=options.dev_args, doppler_correction_per_sec=options.doppler_correction_per_sec, enable_iq_dump=options.enable_iq_dump, file_path=options.file_path, if_gain=options.if_gain, iq_file_path=options.iq_file_path, lo_offset=options.lo_offset, ppm=options.ppm, rf_gain=options.rf_gain, rigctl_port=options.rigctl_port, rx_freq=options.rx_freq, rx_sdr_device=options.rx_sdr_device, samp_rate_rx=options.samp_rate_rx, udp_IP=options.udp_IP, udp_port=options.udp_port, waterfall_file_path=options.waterfall_file_path, excess_bw=options.excess_bw, max_cfo=options.max_cfo)
Feb  3 03:10:36 raspberrypi satnogs-client[513]:   File "/usr/bin/satnogs_bpsk_ax25.py", line 109, in __init__
Feb  3 03:10:36 raspberrypi satnogs-client[513]:     1, sps*baudrate, ((1.0 + excess_bw) * baudrate/2.0) + max_cfo, baudrate / 16.0, firdes.WIN_HAMMING, 6.76))
Feb  3 03:10:36 raspberrypi satnogs-client[513]:   File "/usr/lib/python2.7/dist-packages/gnuradio/filter/filter_swig.py", line 146, in low_pass
Feb  3 03:10:36 raspberrypi satnogs-client[513]:     return _filter_swig.firdes_low_pass(*args, **kwargs)
Feb  3 03:10:36 raspberrypi satnogs-client[513]: RuntimeError: firdes check failed: 0 < fa <= sampling_freq / 2
Feb  3 03:11:01 raspberrypi satnogs-client[513]: 2019-02-03 03:11:01,234 - apscheduler.executors.default - ERROR - Job "spawn_observer (trigger: date[2019-02-03 03:10:31 UTC], next run at: 2019-02-03 03:10:31 UTC)" raised an exception
Feb  3 03:11:01 raspberrypi satnogs-client[513]: Traceback (most recent call last):
Feb  3 03:11:01 raspberrypi satnogs-client[513]:   File "/usr/lib/python2.7/dist-packages/apscheduler/executors/base.py", line 125, in run_job
Feb  3 03:11:01 raspberrypi satnogs-client[513]:     retval = job.func(*job.args, **job.kwargs)
Feb  3 03:11:01 raspberrypi satnogs-client[513]:   File "/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/scheduler/tasks.py", line 108, in spawn_observer
Feb  3 03:11:01 raspberrypi satnogs-client[513]:     observer.observe()
Feb  3 03:11:01 raspberrypi satnogs-client[513]:   File "/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/observer/observer.py", line 301, in observe
Feb  3 03:11:01 raspberrypi satnogs-client[513]:     self.plot_waterfall()
Feb  3 03:11:01 raspberrypi satnogs-client[513]:   File "/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/observer/observer.py", line 392, in plot_waterfall
Feb  3 03:11:01 raspberrypi satnogs-client[513]:     tmin, tmax = np.min(t_idx), np.max(t_idx)
Feb  3 03:11:01 raspberrypi satnogs-client[513]:   File "/usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py", line 2352, in amin
Feb  3 03:11:01 raspberrypi satnogs-client[513]:     out=out, **kwargs)
Feb  3 03:11:01 raspberrypi satnogs-client[513]:   File "/usr/lib/python2.7/dist-packages/numpy/core/_methods.py", line 29, in _amin
Feb  3 03:11:01 raspberrypi satnogs-client[513]:     return umr_minimum(a, axis, None, out, keepdims)
Feb  3 03:11:01 raspberrypi satnogs-client[513]: ValueError: zero-size array to reduction operation minimum which has no identity
Feb  3 03:11:26 raspberrypi satnogs-client[513]: 2019-02-03 03:11:26,297 - apscheduler.executors.default - INFO - Running job "get_jobs (trigger: interval[0:01:00], next run at: 2019-02-03 03:12:26 UTC)" (scheduled at 2019-02-03 03:11:26.220770+00:00)

...

Feb  3 03:13:19 raspberrypi satnogs-client[513]: Exception in thread Thread-16:
Feb  3 03:13:19 raspberrypi satnogs-client[513]: Traceback (most recent call last):
Feb  3 03:13:19 raspberrypi satnogs-client[513]:   File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
Feb  3 03:13:19 raspberrypi satnogs-client[513]:     self.run()
Feb  3 03:13:19 raspberrypi satnogs-client[513]:   File "/usr/lib/python2.7/threading.py", line 754, in run
Feb  3 03:13:19 raspberrypi satnogs-client[513]:     self.__target(*self.__args, **self.__kwargs)
Feb  3 03:13:19 raspberrypi satnogs-client[513]:   File "/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/observer/worker.py", line 123, in _communicate_tracking_info
Feb  3 03:13:19 raspberrypi satnogs-client[513]:     self.check_observation_end_reached()
Feb  3 03:13:19 raspberrypi satnogs-client[513]:   File "/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/observer/worker.py", line 168, in check_observation_end_reached
Feb  3 03:13:19 raspberrypi satnogs-client[513]:     self.trackstop()
Feb  3 03:13:19 raspberrypi satnogs-client[513]:   File "/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/observer/worker.py", line 164, in trackstop
Feb  3 03:13:19 raspberrypi satnogs-client[513]:     os.killpg(os.getpgid(self._gnu_proc.pid), signal.SIGINT)
Feb  3 03:13:19 raspberrypi satnogs-client[513]: OSError: [Errno 3] No such process
Feb  3 03:13:26 raspberrypi satnogs-client[513]: 2019-02-03 03:13:26,245 - apscheduler.executors.default - INFO - Running job "get_jobs (trigger: interval[0:01:00], next run at: 2019-02-03 03:14:26 UTC)" (scheduled at 2019-02-03 03:13:26.220770+00:00)

Perhaps the “firdes check failed” is relevant? I found a related ticket, linking it here to complete the loop.


#3

Hello @tedder

Welcome to SatNOGS!

Indeed you hit the BPSK bug, which is solved but not released yet.

Probably in a couple of days the new release will be available.

I’ve seen that in your station you have added only the UHF Eggbeater with the range 460MHz - 470MHz. This allows you to schedule passes only for few BPSK transmitters/satellites which hit the bug.

Maybe you would like to add one more UHF antenna that will allow you to schedule observations to another frequency range.


#4

Is there a ticket for that bug?

My antenna actually covers 400-470, is there someone I should contact to get it added? There’s a helical and a turnstile that are 430-470, I’m tempted to use one of them.


#5

I used a 430-470 antenna and pulled up other observations. I think they look good example, example, though they aren’t producing anything in the ‘data’ tab.


#6

The ticket for bpsk issue is https://gitlab.com/librespacefoundation/satnogs/gr-satnogs/issues/139

About the antenna, I’m going to add one for your case, until then please keep using 430-470 one.


#7

Try one of the satellites that are known to well produce data, like FALCONSAT-3, UNISAT-6, the AMSAT FOX satellites (-1B and -1D are good!) to check your performance. Try to avoid the CW transmitters for that as there are some known issues with auto-vetting etc.


#8

I’ll keep an eye on these. UNISAT has a pass coming up. I got actual decoded data from BUGSAT, and at least the email string is human-readable.

Thanks. I see the fix, where can I monitor the satnogs releases? e.g., to know when I can simply upgrade?


#9

That BUGSAT observation looks good! To see the decoded telemetry you can just watch the dashboard for :wink:

New satnogs-client and gr-satnogs releases (as they are depending on each other) are announced on the forums! Watch @fredy’s posts!