Observation 5697268: XW-2C (40906)

Satellites & Observations Observations
1

Regarding Observation 5697268 I got the following error after it in the journal:

Mar 29 06:45:41 raspberrypi satnogs-client[370]: IR processing successful!
Mar 29 06:45:41 raspberrypi satnogs-client[370]: gr-satellites: Observation: 5697267, Norad: 40069, Name: 0_METEOR_M2, Script: satnogs_lrpt_demod.py
Mar 29 06:45:55 raspberrypi satnogs-client[370]: gr-satellites: Observation: 5697268, Norad: 40906, Name: XW-2C, Script: satnogs_cw_decoder.py
Mar 29 06:45:55 raspberrypi satnogs-client[370]: gr-satellites: Starting observation 5697268
Mar 29 06:45:57 raspberrypi satnogs-client[370]: gr-satellites: running at 48000 sps
Mar 29 06:46:00 raspberrypi satnogs-client[370]: Traceback (most recent call last):
Mar 29 06:46:00 raspberrypi satnogs-client[370]:   File "/usr/bin/satnogs_cw_decoder.py", line 27, in <module>
Mar 29 06:46:00 raspberrypi satnogs-client[370]:     from distutils import util
Mar 29 06:46:00 raspberrypi satnogs-client[370]:   File "<frozen importlib._bootstrap>", line 983, in _find_and_load
Mar 29 06:46:00 raspberrypi satnogs-client[370]:   File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
Mar 29 06:46:00 raspberrypi satnogs-client[370]:   File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
Mar 29 06:46:00 raspberrypi satnogs-client[370]:   File "<frozen importlib._bootstrap_external>", line 724, in exec_module
Mar 29 06:46:00 raspberrypi satnogs-client[370]:   File "<frozen importlib._bootstrap_external>", line 857, in get_code
Mar 29 06:46:00 raspberrypi satnogs-client[370]:   File "<frozen importlib._bootstrap_external>", line 525, in _compile_bytecode
Mar 29 06:46:00 raspberrypi satnogs-client[370]: KeyboardInterrupt
Mar 29 06:46:03 raspberrypi satnogs-client[370]: POST OBSERVATION SCRIPT RUNNING
Mar 29 06:46:03 raspberrypi satnogs-client[370]: gr-satellites: Observation: 5697268, Norad: 40906, Name: XW-2C, Script: satnogs_cw_decoder.py
Mar 29 06:46:04 raspberrypi satnogs-client[370]: gr-satellites: Stopping observation 5697268
Mar 29 06:46:04 raspberrypi satnogs-client[370]: satnogsclient.observer.observer - ERROR - No waterfall data file found
Mar 29 06:46:06 raspberrypi satnogs-client[370]: apscheduler.executors.default - ERROR - Job "spawn_observer (trigger: date[2022-03-29 06:42:09 UTC], next run at: 2022-03-29 06:42:09 UTC)" raised an exception
Mar 29 06:46:06 raspberrypi satnogs-client[370]: Traceback (most recent call last):
Mar 29 06:46:06 raspberrypi satnogs-client[370]:   File "/var/lib/satnogs/lib/python3.7/site-packages/apscheduler/executors/base.py", line 125, in run_job
Mar 29 06:46:06 raspberrypi satnogs-client[370]:     retval = job.func(*job.args, **job.kwargs)
Mar 29 06:46:06 raspberrypi satnogs-client[370]:   File "/var/lib/satnogs/lib/python3.7/site-packages/satnogsclient/scheduler/tasks.py", line 65, in spawn_observer
Mar 29 06:46:06 raspberrypi satnogs-client[370]:     observer.observe()
Mar 29 06:46:06 raspberrypi satnogs-client[370]:   File "/var/lib/satnogs/lib/python3.7/site-packages/satnogsclient/observer/observer.py", line 261, in observe
Mar 29 06:46:06 raspberrypi satnogs-client[370]:     artifact = Artifacts(waterfall, metadata)
Mar 29 06:46:06 raspberrypi satnogs-client[370]:   File "/var/lib/satnogs/lib/python3.7/site-packages/satnogsclient/artifacts.py", line 30, in __init__
Mar 29 06:46:06 raspberrypi satnogs-client[370]:     self._waterfall_data = waterfall.data
Mar 29 06:46:06 raspberrypi satnogs-client[370]: AttributeError: 'NoneType' object has no attribute 'data'

May this be related to the fact that previous observation was METEOR M2 (SatNOGS Network - Observation 5697267) ?

image
image1141×263 11.1 KB

2

Looks like you’re already back online with good observation since.

It’s odd that there is a KeyboardInterrupt message in the log as if the satnogs-client responded to a Ctrl-C input. Was the satnogs-client not running as a daemon? Not even sure that’s a possibility.

Anyways, how’d you resolve it?

Scott (MAUSyagi)

3

Restarting seems to help, but other than that it seems that sometime after decoding Meteor M-2 it just gets stuck.

1 Like
4

Speculation on my part but it might be a Rpi resource issue (CPU/RAM, ?swap space?, ?temps?), which in turn bogs down the satnogs-client.

1 Like
5

that seems possible as meteor decoding requires some computation, but the images are so worth it

2 Likes