Satnogs-flowgraphs fails with radio_config_pb2

SatNOGS Software
1

Dear Community,

the last Debian Update of satnogs-flowgraphs killed my installtion. I tried to fix it and was not successful. I even installed it by hand from gitlab and not via apt install. Always the same problem at the end…

Traceback (most recent call last):
  File "/usr/local/bin/flowgraph_dispatcher", line 11, in <module>
    import radio_config_pb2
ModuleNotFoundError: No module named 'radio_config_pb2'

Any idea how I could fix this issue? I don’t find the radio config and it is not generated anywhere.

Debian is 12.15

All the best and thanks a lot!

2 Likes
2

Hello,

I saw your post about the satnogs-flowgraphs issue. I am currently running on Debian 12 (bookworm) as well, and it seems to be working fine for now.

I know how frustrating these updates can be. I just wanted to share that it is stable on my system, in case it helps you narrow down the cause. I hope you find a fix for it soon!

1 Like
3

Thanks for your kind words @jp7dvx! I actually used Debian 12 for this Project because it was recommended on every Wiki.

The satnogs-flowgraphs update has been installed 5 days ago - then this error came up. Before it was stable for month.

I hope someone can help me with this issue…

1 Like
4

I checked my system and realized that satnogs-flowgraphs isn’t installed via apt on my machine (it seems I installed it manually).

Since you mentioned you installed it via apt, perhaps there was a recent change in the Debian repository package that broke the dependency chain for radio_config_pb2. My manual installation might be using a different version or build method, which is why it’s still working for me.

This might be a useful clue for others who are also using the apt version.

5

I also tried to install it manually. But I ended up with the same error. It seems like the radio_config_pb2 is not generated in my case.

Do you know what version you are using?

1 Like
6

I have confirmed the reason why my setup is working while yours is having trouble! It turns out my entire installation is running inside Docker containers, managed via satnogs-ansible.

Here is the output of sudo docker ps on my machine:

CONTAINER ID   IMAGE                          COMMAND                  CREATED      STATUS      PORTS           NAMES
59d6e5d639b6   librespace/satnogs-client:2.1.2   "satnogs-client"         5 days ago   Up 5 days               satnogs_satnogs-client
ac1b73a4128b   librespace/hamlib:4.5.4           "/docker-entrypoint.…"   5 days ago   Up 5 days               satnogs_rigctld
40e3cc3b77a1   librespace/satnogs-config:1.1     "/bin/sh -c 'trap : …"   5 days ago   Up 5 days               ansible_satnogs-config
2795602c70a6   librespace/ansible:9.13.0         "/bin/sh -c 'trap : …"   5 days ago   Up 5 days               ansible_ansible

My environment is isolated, which explains why it remains unaffected by host-level Debian updates. It seems that your issues likely stem from running the software directly on the host OS, where system updates can easily break Python dependencies like radio_config_pb2.

I hope sharing this structural difference helps you and the developers find a solution!

7

I just found out about satnogs-proto. I try to go this route first, but I’ll check if all my customizations could run with the dockerized version.

1 Like
8

That sounds like a great plan! Transitioning to satnogs-proto or a containerized setup is definitely the way to go for better stability. I’m glad my findings helped point you in the right direction. Good luck with the migration!

9

Hello. satnogs-proto is currently developed to be used in later versions of satnogs-flowgraphs but right now cannot replace the funcionality already exists.

You are correct that the error comes from the code we have in the workings for new versions. That being said you should see such error unless you have not checked out to the master branch or I have pushed something wrong to the master branch that needs to be fixed immediately.

1 Like
10

Until now I used the deb provided here:

Maybe I have to switch to something else? The manual build via git clone has not worked on Debian 12.

1 Like
11

Thanks for the clarification, @sdoukos! It’s great to have a Core Contributor involved. I’ll just follow the discussion as I continue to run my stable containerized setup. Hopefully, the master branch gets fixed soon for everyone else!

12

Good afternoon,

SatNOGS client 1.8.x was the last official supported legacy (apt/anisble method) client all higher version use by default the docker environment.

So if you where running the legacy client and where able to install a 2.x client you setup will indeed break because this isn’t supported.

SatNOGS updating Wiki pages.

Jan | PE0SAT

13

Which one do you download. The satnogs-flowgraphs_2.5.2-1_all.deb should work correctly, satnogs-flowgraphs_2.5.2+16+gac12b779-1_all.deb has the code that needs satnogs-proto but it is not ready to work out of the box or be released.

Also check satnogs2 repository not unstable.

14

The switch to satnogs2 repos solved it. I now got 2.5.2-1 and it is working again.

As far as I understood the docs and wiki recommend to use Debian 12 for stability reasons.

1 Like