Regarding Observation 2882121 …
I noticed the metadata field is no longer displaying on some recent observations. Is this a system change or is something wrong with my station?
The above observation is one example.
That’s strange, can you post here the “Advanced” —> “Support” result from satnogs-setup.
Also do you see anything strange in logs, if you run journalctl -f -u satnogs-client.service?
Here are the results from my other, more accessible station 1440. Same missing metadata. See observation https://network.satnogs.org/observations/2883923/
Note the journal shows this observation failed to upload.
SUPPORT Results:
Generating support report. Please wait…
Generating support report. Please wait…
------------[ copy here ]------------
{
“versions”: {
“satnogs-client”: “1.3.4”,
“satnogs-client-ansible”: “202007160921”,
“satnogs-flowgraphs”: “1.2.2-1”,
“gr-satnogs”: “2.1.2.1-1”,
“gr-soapy”: “2.1.3-1”,
“gnuradio”: “3.8.1.0~rc1-2”,
“satnogs-config”: “0.10.2”
},
“state”: {
“is-applied”: true,
“pending-tags”: null
},
“system”: {
“date”: “2020-09-23T17:59:23.601366+00:00”,
“distribution”: {
“DESCRIPTION”: “Raspbian GNU/Linux 10 (buster)”,
“RELEASE”: “10”,
“CODENAME”: “buster”,
“ID”: “Raspbian”
},
“pending-updates”: true,
“platform”: {
“system”: “Linux”,
“node”: “SatNOGSLJ”,
“release”: “5.4.51-v7+”,
“version”: “#1333 SMP Mon Aug 10 16:45:19 BST 2020”,
“machine”: “armv7l”,
“processor”: “”
},
“memory”: {
“total”: 970825728,
“available”: 495288320,
“percent”: 49.0,
“used”: 379510784,
“free”: 196755456,
“active”: 538296320,
“inactive”: 171868160,
“buffers”: 42070016,
“cached”: 352489472,
“shared”: 34672640,
“slab”: 44953600
},
“disk”: {
“total”: 31090814976,
“used”: 3787415552,
“free”: 25992941568,
“percent”: 12.7
}
},
“configuration”: {
“satnogs_antenna”: “RX”,
“satnogs_api_token”: “[redacted]”,
“satnogs_pre_observation_script”: “/home/pi/rtl_biast/build/src/rtl_biast -b 1”,
“satnogs_rf_gain”: “49.6”,
“satnogs_rx_samp_rate”: “2.048e6”,
“satnogs_soapy_rx_device”: “driver=rtlsdr”,
“satnogs_station_elev”: “100”,
“satnogs_station_id”: “1440”,
“satnogs_station_lat”: “32.883”,
“satnogs_station_lon”: “-117.235”
}
}
------------[ copy end ]-------------
JOURNALCTL Results:
pi@SatNOGSLJ:~ $ journalctl -f -u satnogs-client.service
– Logs begin at Thu 2019-02-14 10:11:59 UTC. –
Sep 23 16:50:10 SatNOGSLJ satnogs-client[9572]: work_item.run()
Sep 23 16:50:10 SatNOGSLJ satnogs-client[9572]: File “/usr/lib/python3.7/concurrent/futures/thread.py”, line 57, in run
Sep 23 16:50:10 SatNOGSLJ satnogs-client[9572]: result = self.fn(*self.args, **self.kwargs)
Sep 23 16:50:10 SatNOGSLJ satnogs-client[9572]: File “/usr/lib/python3/dist-packages/apscheduler/executors/base.py”, line 125, in run_job
Sep 23 16:50:10 SatNOGSLJ satnogs-client[9572]: retval = job.func(*job.args, **job.kwargs)
Sep 23 16:50:10 SatNOGSLJ satnogs-client[9572]: File “/var/lib/satnogs/lib/python3.7/site-packages/satnogsclient/scheduler/tasks.py”, line 136, in post_data
Sep 23 16:50:10 SatNOGSLJ satnogs-client[9572]: ‘response status code: %s’, fil, observation_id, response.status_code)
Sep 23 16:50:10 SatNOGSLJ satnogs-client[9572]: Message: ‘Upload of %s for observation %i failed, response status code: %s’
Sep 23 16:50:10 SatNOGSLJ satnogs-client[9572]: Arguments: (‘data_2883923_2020-09-23T15-34-40’, ‘2883923’, 502)
Sep 23 16:50:10 SatNOGSLJ satnogs-client[9572]: satnogsclient.scheduler.tasks - ERROR - 502 Server Error: Bad Gateway for url: https://network.satnogs.org/api/jobs/?ground_station=1440&lat=32.883&lon=-117.235&alt=100
All observations fail also for me with an up-to-date and rebooted station. Seems to concern many or all stations looking at the recent observation results on the network.
The error i get:
Sep 23 21:44:43 satpi satnogs-client[332]: apscheduler.executors.default - ERROR - Job "spawn_observer (trigger: date[2020-09-23 20:44:43 UTC], next run at: 2020-09-23 20:44:43 UTC)" raised an exception
Sep 23 21:44:43 satpi satnogs-client[332]: Traceback (most recent call last):
Sep 23 21:44:43 satpi satnogs-client[332]: File "/usr/lib/python3/dist-packages/apscheduler/executors/base.py", line 125, in run_job
Sep 23 21:44:43 satpi satnogs-client[332]: retval = job.func(*job.args, **job.kwargs)
Sep 23 21:44:43 satpi satnogs-client[332]: File "/var/lib/satnogs/lib/python3.7/site-packages/satnogsclient/scheduler/tasks.py", line 26, in spawn_observer
Sep 23 21:44:43 satpi satnogs-client[332]: tle = {'tle0': obj['tle0'], 'tle1': obj['tle1'], 'tle2': obj['tle2']}
Sep 23 21:44:43 satpi satnogs-client[332]: KeyError: 'tle0'
Might be on the server response the tle[0-2] fields have been renamed tle_line_[0-2] ?
Sep 23 22:29:30 satpi satnogs-client[332]: satnogsclient.scheduler.tasks - DEBUG - Observation obj: {'id': 2881129, 'start': '2020-09-23T21:31:47Z', 'end': '2020-09-23T21:37:31Z', 'ground_station': 1207, 'tle_line_0': '0 AISTECHSAT-3', 'tle_line_1': '1 44103U 19018AB 20267.45394285 .00000494 00000-0 23773-4 0 9991', 'tle_line_2': '2 44103 97.3983 327.3305 0012785 196.2725 290.0558 15.23301986 82356', 'frequency': 436730000, 'mode': 'FSK AX.100 Mode 5', 'transmitter': 'TGP8nqLVquNWuYYytpbQ7A', 'baud': 9600.0}
1 Like
That’s normal. Unfortunately, there is no retry logic yet when uploading metadata.