SatNOGS Network Release: 1.128, 1.129, 1.130, 1.131, 1.132

We have a new release for SatNOGS Network, which will be deployed in the next minutes. Notable changes can be found in this thread: Upcoming SatNOGS Network release (1.128) - Breaking and Notable Changes.

If you notice anything unexpected, let us know either by posting here or opening a new issue in Issues · librespacefoundation / SatNOGS / satnogs-network · GitLab

More details and release notes can be found in:

4 Likes

It may take a little time due to some migrations performed in the database. Thank you for your patience!

There was a performance issue, we are fixing it and deploying it in the next minutes. Thank you for your patience.

The performance issue seems to be solved now, if you notice any strange behavior, let us know.

1 Like

It seems the auto scheduler (librespacefoundation / SatNOGS / satnogs-auto-scheduler · GitLab) is either broken, or was hit by the outage. Expected/known? Or what’s the status with that?

1 Like

image

just waiting this red sign, go to green :smiley:

source

There is an update merged for auto-scheduler, so if you run the latest version and you have any trouble, please report them either here or in issues in the project repository in order to be fixed.

2 Likes

latest auto scheduler is work. thank you @fredy

pip install satnogs-predict  
pip install git+https://gitlab.com/librespacefoundation/satnogs/satnogs-auto-scheduler.git
1 Like

Hello!

Since the upgrade, my SIDS upload attempts are returning:

HTTP/1.1 400 Bad Req

Thanks for reporting, I’m going to check this and I’ll come back, probably in pm to solve it.

1 Like

For future reference, we managed to find the root cause, there is an introduced check on the timestamp when a frame is SiDS submitted, if the timestamp is in the future (usually due to syncing or timezone issues), the request fails with 400 code.

2 Likes

Hi, just now HTTP 500 when trying to access a station page.
Any ongoing work at the moment?

1 Like

There is an ongoing DDoS attack on both Network and DB, we are working on mitigate it.

Hopefully in the next minutes things will be back to normal.

5 Likes

Oh that’s sad that we have a DDoS attack… Thanks for info.

1 Like

Would this fix the sudden on/offline that’s been happening to my station since the updates seem to be taking place? I try to pride myself on keeping my Groundstation online but it seems to register every time the network goes on and offline making it look like it’s my end. Does this affect the usage of my groundstation by ‘rating’ in any way?

1 Like

OK we are fully back up as of the last 20 mins or so

Down again

Both Network and DB services seems to be stabilized for now! Kudos to @Acinonyx!

Maybe we should have split it in another thread as it wasn’t related with the releases but big ddos attack.

If you still face issues, please reply here or send me a pm.

6 Likes

Thanks for holding the fort!

Hi fredy,

A big thank you to you and the team for steering the ship through rough waters over the last couple of days. Handling unexpected “big storms” is never a walk in the park, but it’s wonderful to see everything back on track.

Thanks for your tireless efforts behind the scenes to keep our orbital window open and stable!

2 Likes

I have installed the new auto-scheduler

jim@gs-satnogs:~$ /home/jim/auto-scheduler/.venv/bin/python /home/jim/auto-scheduler/.venv/bin/schedule_single_station --version
satnogs-auto-scheduler 0.4

When I run:

/home/jim/auto-scheduler/.venv/bin/python /home/jim/auto-scheduler/.venv/bin/schedule_single_station -s 3020 -n

I get this Error:

jim@gs-satnogs:\~$ /home/jim/auto-scheduler/.venv/bin/python /home/jim/auto-scheduler/.venv/bin/schedule_single_station -s 3020 -n
Using cached satellites, transmitters and TLEs.
Using cached transmitter statistics.
Filter transmitters based on ground station capability.
Search passes for 0 satellites:
0it \[00:00, ?it/s\]
Download list of scheduled passes from SatNOGS Network...
Found 1 scheduled passes between 2026-09-01 01:19:35 and 2026-09-01 02:19:35 on ground station 3020.
1 passes selected out of 0, 215 s out of 215 s at 100.000% efficiency
GS | Sch | NORAD | Start time          | End time            | Duration | AzR El AzS | Priority | Transmitter UUID       | Mode        | Freq   | Satellite name
| misuse |
Traceback (most recent call last):
File "/home/jim/auto-scheduler/.venv/bin/schedule_single_station", line 8, in 
sys.exit(main())
File "/home/jim/auto-scheduler/.venv/lib/python3.9/site-packages/auto_scheduler/cli/schedule_single_station.py", line 334, in main
schedule_single_station(
File "/home/jim/auto-scheduler/.venv/lib/python3.9/site-packages/auto_scheduler/cli/schedule_single_station.py", line 505, in schedule_single_station
print_scheduledpass_summary(
File "/home/jim/auto-scheduler/.venv/lib/python3.9/site-packages/auto_scheduler/utils.py", line 164, in print_scheduledpass_summary
sat_entry = satellites_catalog\[int(satpass\["satellite"\]\["id"\])\]
KeyError: 60246

Thank you

Jim