I encountered the same issue. As a temporary workaround, I enabled the “Experimental” setting (“Install latest versions of all software”) in the Software Package Settings using satnogs-setup. That seems to have resulted in a functioning system again.
Once the “stable” releases are again truly stable, I intend to switch this back.
Should have checked this thread before updating my system 
Same failure here!
I used the experimental version but a test job failed. I will wait offline for info about a fix.
Have in mind that currently returning back to stable from experimental is only possible by flashing sd-card from scratch with the stable image.
Same failure on my side…
The issue should be fixed for new updates but unfortunately it won’t recover stations which are already in this state.
To recover you need to manually run:
sudo apt-get purge libgnuradio-satnogs gr-satnogs
and then do a normal Update through satnogs-setup.
still the same issue. I´ll run my alternative SD Card again
@dl4eec or anyone else, could you provide logs after running sudo apt-get purge libgnuradio-satnogs gr-satnogs?
I´ll try later the day/night. Maybe others could be faster
What is the easiest way of determining what the most current stable released version of the client is? Is it checking the branch dropdown at gitlab?
For each project you can check the tags in gitlab:
satnogs-client: https://gitlab.com/librespacefoundation/satnogs/satnogs-client/-/tags
gr-satnogs: https://gitlab.com/librespacefoundation/satnogs/gr-satnogs/-/tags
satnogs-flowgraphs: https://gitlab.com/librespacefoundation/satnogs/satnogs-flowgraphs/-/tags
I create a new image on a micro SD card. First time same issue. After running sudo apt-get purge libgnuradio-satnogs gr-satnogs a second time I could update and apply. I can´t find the issue, but it´s running now
This seems to work for me. Job https://network.satnogs.org/observations/3246655/ done, just waiting for audio file. EDIT: Audio file upload ok.
Thanks for the command to get the station back on track. My station has had 150 failed observations after it broke. Hopefully it will be back to normal operational state now. I’ll let it run overnight and report back.
Yup, my station seems to be fine again.
Thank you @Acinonyx - with your advice, update went through.
But now my station is experiencing another error. It seems to occur after some 4 hours after the last reboot of the Pi, but not sure if this is just coincidence.
This is from the syslog:
Dec 7 13:08:00 satnogs satnogs-client[336]: — Logging error —
Dec 7 13:08:00 satnogs satnogs-client[336]: Traceback (most recent call last):
Dec 7 13:08:00 satnogs satnogs-client[336]: File “/var/lib/satnogs/lib/python3.7/site-packages/satnogsclient/scheduler/tasks.py”, line 124, in post_data
Dec 7 13:08:00 satnogs satnogs-client[336]: response.raise_for_status()
Dec 7 13:08:00 satnogs satnogs-client[336]: File “/var/lib/satnogs/lib/python3.7/site-packages/requests/models.py”, line 941, in raise_for_status
Dec 7 13:08:00 satnogs satnogs-client[336]: raise HTTPError(http_error_msg, response=self)
Dec 7 13:08:00 satnogs satnogs-client[336]: requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://network.satnogs.org/api/observations/3255525/
Dec 7 13:08:00 satnogs satnogs-client[336]: During handling of the above exception, another exception occurred:
Dec 7 13:08:00 satnogs satnogs-client[336]: Traceback (most recent call last):
Dec 7 13:08:00 satnogs satnogs-client[336]: File “/usr/lib/python3.7/logging/init.py”, line 1034, in emit
Dec 7 13:08:00 satnogs satnogs-client[336]: msg = self.format(record)
Dec 7 13:08:00 satnogs satnogs-client[336]: File “/usr/lib/python3.7/logging/init.py”, line 880, in format
Dec 7 13:08:00 satnogs satnogs-client[336]: return fmt.format(record)
Dec 7 13:08:00 satnogs satnogs-client[336]: File “/usr/lib/python3.7/logging/init.py”, line 619, in format
Dec 7 13:08:00 satnogs satnogs-client[336]: record.message = record.getMessage()
Dec 7 13:08:00 satnogs satnogs-client[336]: File “/usr/lib/python3.7/logging/init.py”, line 380, in getMessage
Dec 7 13:08:00 satnogs satnogs-client[336]: msg = msg % self.args
Dec 7 13:08:00 satnogs satnogs-client[336]: TypeError: %i format: a number is required, not str
Dec 7 13:08:00 satnogs satnogs-client[336]: Call stack:
Dec 7 13:08:00 satnogs satnogs-client[336]: File “/usr/lib/python3.7/threading.py”, line 885, in _bootstrap
Dec 7 13:08:00 satnogs satnogs-client[336]: self._bootstrap_inner()
Dec 7 13:08:00 satnogs satnogs-client[336]: File “/usr/lib/python3.7/threading.py”, line 917, in _bootstrap_inner
Dec 7 13:08:00 satnogs satnogs-client[336]: self.run()
Dec 7 13:08:00 satnogs satnogs-client[336]: File “/usr/lib/python3.7/threading.py”, line 865, in run
Dec 7 13:08:00 satnogs satnogs-client[336]: self._target(*self._args, **self._kwargs)
Dec 7 13:08:00 satnogs satnogs-client[336]: File “/usr/lib/python3.7/concurrent/futures/thread.py”, line 80, in _worker
Dec 7 13:08:00 satnogs satnogs-client[336]: work_item.run()
Dec 7 13:08:00 satnogs satnogs-client[336]: File “/usr/lib/python3.7/concurrent/futures/thread.py”, line 57, in run
Dec 7 13:08:00 satnogs satnogs-client[336]: result = self.fn(*self.args, **self.kwargs)
Dec 7 13:08:00 satnogs satnogs-client[336]: File “/var/lib/satnogs/lib/python3.7/site-packages/apscheduler/executors/base.py”, line 125, in run_job
Dec 7 13:08:00 satnogs satnogs-client[336]: retval = job.func(*job.args, **job.kwargs)
Dec 7 13:08:00 satnogs satnogs-client[336]: File “/var/lib/satnogs/lib/python3.7/site-packages/satnogsclient/scheduler/tasks.py”, line 147, in post_data
Dec 7 13:08:00 satnogs satnogs-client[336]: ‘response status code: %s’, fil, observation_id, response.status_code)
Dec 7 13:08:00 satnogs satnogs-client[336]: Message: ‘Upload of %s for observation %i failed, response status code: %s’
Dec 7 13:08:00 satnogs satnogs-client[336]: Arguments: (‘waterfall_3255525_2020-12-07T11-23-52.png’, ‘3255525’, 400)
Dec 7 13:08:00 satnogs satnogs-client[336]: satnogsclient.scheduler.tasks - ERROR - 502 Server Error: Bad Gateway for url: https://network.satnogs.org/api/jobs/?ground_station=376&lat=48.833&lon=8.839&alt=460
Currently, it seems to be working, thank you!
Time to upgrade your stations!
A new release of SatNOGS Client Ansible (202012231828) is available!
Q: How can I upgrade my SatNOGS software?
A: You can find detailed instructions on how to update your system in SatNOGS Client Setup wiki page
Q: I’ve found a bug. Where can I report it?
A: You can file any issues you find in GitLab
SatNOGS Software Manifest