You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently retired my old server which was running my ADSB system, I had Radarbox running without any issue (had multiple instances for different receivers). Now when I try to build config on the new system, it constantly gives segmentation faults and as a result doesn't load up.
I tried again on another system and ran into the same problem, I even spun up another docker with the latest pull of docker-radarbox on the original server and it works fine, but the two new servers I constantly get the segmentation faults and no data is ever processed.
Old server was an E3 Xeon, new servers are E5 and E7 Xeons, not sure if that has anything to do with it.
I don't run mikenye/readsb-protobuf, but never did with the old setup either. Tried with a new config and reusing old config with same result.
Thanks Mike, this indeed solves the issue. I am bit perplexed as to why the original system did not have this fix implemented and had no problem.
Because I have multiple containers for the same websites (IE: 4x receivers) I created a volume with the segment fix and mounted on all of them, seems to be working now.
Hi Mike,
I recently retired my old server which was running my ADSB system, I had Radarbox running without any issue (had multiple instances for different receivers). Now when I try to build config on the new system, it constantly gives segmentation faults and as a result doesn't load up.
I tried again on another system and ran into the same problem, I even spun up another docker with the latest pull of docker-radarbox on the original server and it works fine, but the two new servers I constantly get the segmentation faults and no data is ever processed.
Old server was an E3 Xeon, new servers are E5 and E7 Xeons, not sure if that has anything to do with it.
I don't run mikenye/readsb-protobuf, but never did with the old setup either. Tried with a new config and reusing old config with same result.
The text was updated successfully, but these errors were encountered: