SatNOGS DB Release : 1.76

SatNOGS Software
1

We have a new release for SatNOGS DB, which will be deployed in the next minutes. Notable changes can be found in this thread: Upcoming SatNOGS DB release (1.76) - 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-db · GitLab

More details and release notes can be found in:

3 Likes
2

failed loads in DB.

I am sending data to db.satnogs.org, and it arrives intermittently, some arrive, others do not, I send with skyroof like lw2dyb/gs since I cannot put the same token as the satnogs 1861 station, and I write here because I cannot open a topic new, I don’t know why.

3

Thanks for reporting, let me take a look.

4

I am sure that you are aware but the network is down (error 500 in browser and docker log). Can go back and find when it died if you like.

5

you are right. same here..

live stream from here :

zoom, an notice 500 server error

image
image1053×835 102 KB

image
image623×260 13.7 KB

finally i found real use case for this live streaming over asciinema.. poke @mhuebner

3 Likes
SatNOGS station monitor
6

Glad you find it useful. When we started at www.dk0tu.de with streaming the station roughly one year ago, we did it mainly for publicity. The stream is embedded in our website too:

The stream was also a nice exhibition piece for our presence at the German Chaos Communications Congress, showing guests the actual operation of a satnogs-based satellite ground station.

I became co-maintainer of satnogs-monitor too. If you have patches for the software, feel free to send them in (no AI-slop please).

2 Likes
7

I continue sending to DB as station LW2DYB/GS and not all of them impact the DB, only some, I don’t know if they are lost or rejected for some reason or if they remain on the stack and are old but it does not reflect what I sent. Thank you in advance, very good job

Julio

LW2DYB (1861) and LW2DYB/GS with SKYROOF

1 Like
8

@LW2DYB

I can see that some (~40%) of the requests you send fail with 400 error code.

Usually this error code is returned in one of these cases:

  • Invalid NORAD ID (currently without the Alpha-5 support, sent NORAD ID should be a number, you can use the temporary NORAD ID for now until we release the Alpha-5 support)
  • Missing parameters, like missing latitude or longitude
  • Invalid station coordinates
  • Timestamp is in the future

Given that some request succeed, I tend to believe that the error comes either from using and Alpha-5 NORAD ID (the ones with letters) or from a timestamp that it is in the future.

Are there any logs from SKYROOF that we can see what is error is returned or the parameters of the request? That would be very useful to debug the issue.

9

wow! that soooo cool

1 Like