Menu
▾
▴
#87 CRC Error with Satellite Database Update
With my new slackware-current install, satellite updates do not work. If I try to do a manual update I get the following errors. I am guessing that a library update has caused this issue. Not sure where to go from there tho.
satupdat amsat.txt /n /s
Update of F6FBB's BBS satellite data base orbital parameters
Version 1.89 - February 2015 - Bernard Pidoux, f6bvp@amsat.org
Reading NASA format with CRC-10
Update keeping only satellites being in the input file
deleting data older than 100 days.
reading file satel.dat
1 data less than 100 days
Reading file: amsat.txt
1 : AO-07 ok
UO-11 CRC error !
AO-16 CRC error !
LO-19 CRC error !
AO-27 CRC error !
IO-26 CRC error !
FO-29 CRC error !
NOAA-15 CRC error !
GO-32 CRC error !
ISS CRC error !
NO-44 CRC error !
SO-50 CRC error !
CO-55 CRC error !
CO-57 CRC error !
RS-22 CRC error !
NOAA-18 CRC error !
CO-58 CRC error !
CO-65 CRC error !
AAUSAT2 CRC error !
CO-66 CRC error !
RS-30 CRC error !
PRISM CRC error !
NOAA-19 CRC error !
SRMSAT CRC error !
HRBE CRC error !
RS-40 CRC error !
ZACUBE-1 CRC error !
Delfi-N3xt CRC error !
GOMX-1 CRC error !
LO-74 CRC error !
AO-73 CRC error !
SPROUT CRC error !
DTUSAT-2 CRC error !
EO-80 CRC error !
HODOYOSHI-1 CRC error !
XW-2C CRC error !
XW-2D CRC error !
LILACSAT-2 CRC error !
XW-2B CRC error !
IO-86 CRC error !
ChubuSat-2 CRC error !
ChubuSat-3 CRC error !
Horyu-4 CRC error !
Lapan A3 CRC error !
Pratham CRC error !
CAS-2T CRC error !
CAS-4B CRC error !
CAS-4A CRC error !
Aalto 1 CRC error !
URSA MAIOR CRC error !
Max Valier Sat CRC error !
D-SAT CRC error !
TechnoSat CRC error !
AO-91 CRC error !
TianYi 2 CRC error !
Zhou Enlai CRC error !
TianYi 6 CRC error !
S-Net D CRC error !
S-Net B CRC error !
S-Net A CRC error !
S-Net C CRC error !
Ten-Koh CRC error !
PO-101 CRC error !
QO-100 CRC error !
MinXSS-2 CRC error !
AO-95 CRC error !
RANGE-B CRC error !
RANGE-A CRC error !
MOVE-II CRC error !
SNUSat 2 CRC error !
SnugLite CRC error !
ITASat 1 CRC error !
EAGLET 1 CRC error !
ESEO CRC error !
CSIM CRC error !
JO-97 CRC error !
Suomi 100 CRC error !
ISAT CRC error !
UWE-4 CRC error !
Sparrow CRC error !
AISat 1 CRC error !
Prox-1 CRC error !
SONATE CRC error !
BeeSat 9 CRC error !
JAISAT-1 CRC error !
Taurus 1 CRC error !
Duchifat 3 CRC error !
OPS-SAT CRC error !
TO-108 CRC error !
FloripaSat 1 CRC error !
RS-44 CRC error !
BY70-2 CRC error !
UPMSat 2 CRC error !
AmicalSat CRC error !
SALSAT CRC error !
UVSQ-SAT CRC error !
YUSAT 1 CRC error !
SOMP 2b CRC error !
IDEASSat CRC error !
CubeSX-Sirius-HSE CRC error !
CubeSX-HSE CRC error !
KSU-Cubesat CRC error !
GRBAlpha CRC error !
Orbicraft-Zorkiy CRC error !
STECCO CRC error !
MO-110 CRC error !
TUBIN CRC error !
LEDSAT CRC error !
CUTE CRC error !
TeikyoSat 4 CRC error !
Z-Sat CRC error !
KOSEN 1 CRC error !
HO-113 CRC error !
Tevel-3 CRC error !
Tevel-8 CRC error !
Tevel-5 CRC error !
Tevel-6 CRC error !
Tevel-1 CRC error !
IRIS-A CRC error !
Tevel-7 CRC error !
Tevel-4 CRC error !
Tevel-2 CRC error !
SO-115 CRC error !
SO-114 CRC error !
OreSat0 CRC error !
Planetum 1 CRC error !
Foresail-1 CRC error !
SNUGLITE 2 CRC error !
IO-117 CRC error !
SelfieSat CRC error !
FO-118 CRC error !
SSS-2B CRC error !
CIRBE CRC error !
INSPIRE-Sat 7 CRC error !
RoseyCubesat 1 CRC error !
SO-120 CRC error !
MRC-100 CRC error !
UmKA 1 (RS40S) CRC error !
CubeBel-2 (EU11S) CRC error !
VERONIKA CRC error !
KAFASAT CRC error !
ENSO CRC error !
EIRSAT-1 CRC error !
SO-121 CRC error !
SONATE-2 CRC error !
KASHIWA CRC error !
sorting by catalog number(1)
looking for duplicate(1)
sorting by name(1)
Data of 1 satellites over 1 have been updated on 20/05/24 at 02:25:49
Are you sure your input file isn't corrupted / wrong?
The satupdat source only relies on some standard C libraries. Unfortunately I haven't got a Slackware-current install / VM running (yet) to test.
With testing on Debian 11 + 12 and Ubuntu 22.04 + 24.04 I haven't noticed any issues with parsing a NASA formatted amsat file and CRC calculation. Used the one from this location:
https://www.amsat.org/tle/current/nasabare.txt
Update of F6FBB's BBS satellite data base orbital parameters
Version 1.89 - February 2015 - Bernard Pidoux, f6bvp@amsat.org
Reading NASA format with CRC-10
Update keeping only satellites being in the input file
deleting data older than 100 days.
file satel.dat not found - new data base created !
reading file satel.dat
0 data less than 100 days
Reading file: amsat.txt
1 : AO-07 ok
2 : UO-11 ok
3 : AO-16 ok
4 : LO-19 ok
5 : AO-27 ok
6 : IO-26 ok
7 : FO-29 ok
8 : NOAA-15 ok
9 : GO-32 ok
10 : ISS ok
11 : NO-44 ok
12 : SO-50 ok
13 : CO-55 ok
14 : CO-57 ok
15 : RS-22 ok
16 : NOAA-18 ok
17 : CO-58 ok
18 : CO-65 ok
19 : AAUSAT2 ok
20 : CO-66 ok
21 : RS-30 ok
22 : PRISM ok
23 : NOAA-19 ok
24 : SRMSAT ok
25 : HRBE ok
26 : RS-40 ok
27 : ZACUBE-1 ok
28 : Delfi-N3xt ok
29 : GOMX-1 ok
30 : LO-74 ok
31 : AO-73 ok
32 : SPROUT ok
33 : DTUSAT-2 ok
34 : EO-80 ok
35 : HODOYOSHI-1 ok
36 : XW-2C ok
37 : XW-2D ok
38 : LILACSAT-2 ok
39 : XW-2B ok
40 : IO-86 ok
41 : ChubuSat-2 ok
42 : ChubuSat-3 ok
43 : Horyu-4 ok
44 : Lapan A3 ok
45 : Pratham ok
46 : CAS-2T ok
47 : CAS-4B ok
48 : CAS-4A ok
49 : Aalto 1 ok
50 : URSA MAIOR ok
51 : Max Valier Sat ok
52 : D-SAT ok
53 : TechnoSat ok
54 : AO-91 ok
55 : TianYi 2 ok
56 : Zhou Enlai ok
57 : TianYi 6 ok
58 : S-Net D ok
59 : S-Net B ok
60 : S-Net A ok
61 : S-Net C ok
62 : Ten-Koh ok
63 : PO-101 ok
64 : QO-100 ok
65 : MinXSS-2 ok
66 : AO-95 ok
67 : RANGE-B ok
68 : RANGE-A ok
69 : MOVE-II ok
70 : SNUSat 2 ok
71 : SnugLite ok
72 : ITASat 1 ok
73 : EAGLET 1 ok
74 : ESEO ok
75 : CSIM ok
76 : JO-97 ok
77 : Suomi 100 ok
78 : ISAT ok
79 : UWE-4 ok
80 : Sparrow ok
81 : AISat 1 ok
82 : Prox-1 ok
83 : SONATE ok
84 : BeeSat 9 ok
85 : JAISAT-1 ok
86 : Taurus 1 ok
87 : Duchifat 3 ok
88 : OPS-SAT ok
89 : TO-108 ok
90 : FloripaSat 1 ok
91 : RS-44 ok
92 : BY70-2 ok
93 : UPMSat 2 ok
94 : AmicalSat ok
95 : SALSAT ok
96 : UVSQ-SAT ok
97 : YUSAT 1 ok
98 : SOMP 2b ok
99 : IDEASSat ok
100 : CubeSX-Sirius-HSE ok
101 : CubeSX-HSE ok
102 : KSU-Cubesat ok
103 : GRBAlpha ok
104 : Orbicraft-Zorkiy ok
105 : STECCO ok
106 : MO-110 ok
107 : TUBIN ok
108 : LEDSAT ok
109 : CUTE ok
110 : TeikyoSat 4 ok
111 : Z-Sat ok
112 : KOSEN 1 ok
113 : HO-113 ok
114 : Tevel-3 ok
115 : Tevel-8 ok
116 : Tevel-5 ok
117 : Tevel-6 ok
118 : Tevel-1 ok
119 : IRIS-A ok
120 : Tevel-7 ok
121 : Tevel-4 ok
122 : Tevel-2 ok
123 : SO-115 ok
124 : SO-114 ok
125 : OreSat0 ok
126 : Planetum 1 ok
127 : Foresail-1 ok
128 : SNUGLITE 2 ok
129 : IO-117 ok
130 : SelfieSat ok
131 : FO-118 ok
132 : SSS-2B ok
133 : CIRBE ok
134 : INSPIRE-Sat 7 ok
135 : RoseyCubesat 1 ok
136 : SO-120 ok
137 : MRC-100 ok
138 : UmKA 1 (RS40S) ok
139 : CubeBel-2 (EU11S) ok
140 : VERONIKA ok
141 : KAFASAT ok
142 : ENSO ok
143 : EIRSAT-1 ok
144 : SO-121 ok
145 : SONATE-2 ok
146 : KASHIWA ok
sorting by catalog number.................................................................................................................................................(146)
looking for duplicate.................................................................................................................................................(146)
sorting by name.................................................................................................................................................(146)
Data of 146 satellites over 146 have been updated on 20/05/24 at 07:35:24
Last edit: Dave van der Locht 2024-05-20
No, there is some issue with the OS satupdate. Even the keps from
your link do the same thing. Do you want this system? I can post it
on google drive for you. It is a virtual system running in
VirtualBox. I have been testing the new kernel that they have been
working on the AX.25 stack.
-73 de Chris KQ6UP
Last edit: Dave van der Locht 2024-05-21
Thanks for the reply Chris. I prefer to (initially) test on a clean Slackware installation with the latest LinFBB release (7.0.11).
If I encounter the same issue I'll need to check what's causing this. It doesn't seem to have any 'strings' with the kernel's AX.25 fixes/patches. Satupdat only relies on standard C libs.
Otherwise, when I'm getting errors too, your image could be helpful to figure out what's different / causing this at yours.
For what it is worth, I have never seen this on any other slackware or
Debian based system before. This only happens in Slackware-current. It is
a brand new system with only FBB and VE7FET's packet stuff installed on
it. I only mentioned the kernel patches to explain why I am running
Slackware-current instead of a stable release. I just applied a patch
manually this morning (the only one that I have done) to the stock 6.9.1
kernel. It is supposed to make the system stable when incoming connections
are coming in. We will see this afternoon when I get back home.
Also as an aside to the bug. I think the Linux version of TFKISS could
avoid the use of the Linux AX.25 stack as it emulates the TF2.7b hostmode
firmware. It does KISS ports or UDP/IP forwarding. The only problem is
that it needs to be brought up to date to compile on a modern system. I am
using it on Slackware 11 (the latest it will work on), and with TNN I get
FBB + NETROM and UDP/IP AX.25 tunnels without touching the Linux stuff. It
has been rock solid in this system.
Last edit: Dave van der Locht 2024-05-21
I've just installed a (64-bit) slackware-current test system using this night's ISO.
After compiling and installing VE7FET's libax25 I started compiling and installing LinFBB 7.0.11 from the tar.gz package.
Unfortunately I'm not getting any CRC errors using satupdat, it seems to function as expected.
Good to know. I am wondering if I should try to rebuild it against
the new libraries and try it again. I can also send you a kernel
patch that makes
6.9.1 stable for use with AX.25 if you are interested. 6.9.1 crashes
with incoming connections without it.
-Chris KQ6UP
Last edit: Dave van der Locht 2024-05-21
It is still doing it for me. What commands are you issuing it? I am
also using the bulletin keps found here (tho I tried the ones from the
link you sent me and had the same problem):
https://www.amsat.org/tle/daily-bulletin.txt
I am using BTRFS for my filesystem, but I am not thinking that should
affect anything.
-Chris KQ6UP
Last edit: Dave van der Locht 2024-05-21
I've used the exact same command parameters as you did: satupdat amsat.txt /n /s
To test if BTRFS causes issues you can create a clean slackware-current system and compile + install libax25 and linfbb. Eventually you can compare with creating a clean slackware-current system on an EXT4 filesystem. I've used EXT4 (default slackware-current). Satupdat also doesn't rely on any other libraries other than the standard C library.
I suggest to NOT test on the system which is having issues for now, to keep things simple and clean in determining a possible root cause.
About the BTRFS, it should not affect anything. But... If there's an issue with BTRFS or its interfaces/libraries in slackware-current, it CAN affect file operations or their output for sure.
I am having issues with BTRFS on this system, but it is related to making
tarballs from snapshots. The / file system goes to 100% even though I am
writing the tarball to nfs or even another mounted drive. BTRFS has been
how I do backups, as it is easy to take reliable snapshots of a live
system. However those snapshots are not as useful if I can’t dump them to
a tarball for offline safe keeping.
-I will have to build a new system as I am having issues with uronode
connecting on the NETROM layer. I am going to switch to the official repo
to see if is VE7FET’s libax25, or a problem common to both. So I can test
satupdate on EXT4 at that point.
Thanks,
Chris Maness
-Sent from my iPhone
On Tue, May 21, 2024 at 6:40 AM Dave van der Locht davevdl@users.sourceforge.net wrote:
Related
Tickets: #87
Did you do slackpkg update/upgrade-all? The image you linked to me
had 6.6.25 kernel. I did the slackpkg update which brought me to the
current and most recent stable fork off the mainline tree. That is
6.9.1. That way we are comparing apples to apples. I just built the
system with that image using ext4, but wanted to see if the filesystem
is what makes the difference because that would be odd to me. So if
you get yours up to 6.9.1, and it still works for you, I will proceed
with my experiment here. If you get the CRC error after moving to
6.9.1, then it is something else.
Thanks Dave
Last edit: Dave van der Locht 2024-05-22
My slackware-current test system is using the 6.9.1 kernel. I've tested satupdat with this kernel version using an EXT4 filesystem.
Ok. I will update it and test satupdate on the new EXT4 system.
Last edit: Dave van der Locht 2024-05-23
Now on EXT4. No difference. How do you compile without X support in
Slackware-current? I remove motif library while compiling, am not
sure if that would make a difference (I doubt it). I have done that
on other systems where having X configured causes compile to fail. Is
there a variable I can set before running ./configure that will turn
of X?
-Chris KQ6UP
Last edit: Dave van der Locht 2024-05-22
Strange issue you (still) have...
Compiling without X support is done with ./configure --disable-x-utils, see ./configure --help.
How do you download or transfer the input file onto the system?
Are you sure the input file isn't corrupted somehow?
You're sure you haven't done anything else besides installing the OS and compiling linfbb to test? Although higly unlikely, things that could break the standard C library?
And last but not least... Do you build and install LinFBB with any parameters? Or just plain:
./configure
./make
./make install
Will do that.
No. I only patched the kernel for the AX.25 bug, and I have downloaded
some various ways. I will also try copy and paste into ED. That is a
failsafe for me.
Just the simple thing ^ above. I will try again with the no-x flags.
Chris Maness
Ok, so you did something else before testing on a fresh install.
Please also try without patching the kernel (or doing any other things) before testing satupdat initially. Just to verify if something in the steps in between is or isn't messing things up big time. One step at a time...
But doing the slackpkg update/upgrade first, or no?
Thanks,
Chris Maness
-Sent from my iPhone
Last edit: Dave van der Locht 2024-05-23
You can test both... Before and after, just to see where things go (or already are) wrong at yours.
Last edit: Dave van der Locht 2024-05-23
Wow, fresh install Slackware-current and still getting the same error.
What browser are you using to download the keps? This has got to be
something obvious, and thank you for your patients. Are you also
using a x86_64 system?
I am doing satupdat with /n (and tried all three other possible flags
and get the same problem).
Last edit: Dave van der Locht 2024-05-23
I'm downloading the file directly on Linux with 'wget https://www.amsat.org/tle/current/nasabare.txt' No browser or other transfer method involved there.
I'm also using the 64-bit slackware-current version.
Just to make sure I was not going crazy, I tried the same keps
(downloaded from amsat.org) on my Slack14.1 system at work. Worked
like a charm! I am doing the EXACT same thing on the system at home.
The system at home is a fresh build with the iso that you linked too.
I built a freshly downloaded source from sourceforge, and did a
completely new install. See the output below:
satupdat dailytle.txt /n /s
Update of F6FBB's BBS satellite data base orbital parameters
Version 1.89 - February 2015 - Bernard Pidoux, f6bvp@amsat.org
Reading NASA format with CRC-10
Update keeping only satellites being in the input file
deleting data older than 100 days.
file satel.dat not found - new data base created !
reading file satel.dat
0 data less than 100 days
Reading file: dailytle.txt
1 : AO-07 ok
2 : UO-11 ok
3 : AO-16 ok
4 : LO-19 ok
5 : AO-27 ok
6 : IO-26 ok
7 : FO-29 ok
8 : NOAA-15 ok
9 : GO-32 ok
10 : ISS ok
11 : NO-44 ok
12 : SO-50 ok
13 : CO-55 ok
14 : CO-57 ok
15 : RS-22 ok
16 : NOAA-18 ok
17 : CO-58 ok
18 : CO-65 ok
19 : AAUSAT2 ok
20 : CO-66 ok
21 : RS-30 ok
22 : PRISM ok
23 : NOAA-19 ok
24 : SRMSAT ok
25 : HRBE ok
26 : RS-40 ok
27 : ZACUBE-1 ok
28 : Delfi-N3xt ok
29 : GOMX-1 ok
30 : LO-74 ok
31 : AO-73 ok
32 : SPROUT ok
33 : DTUSAT-2 ok
34 : EO-80 ok
35 : HODOYOSHI-1 ok
36 : XW-2C ok
37 : XW-2D ok
38 : LILACSAT-2 ok
39 : XW-2B ok
40 : IO-86 ok
41 : ChubuSat-2 ok
42 : ChubuSat-3 ok
43 : Horyu-4 ok
44 : Lapan A3 ok
45 : Pratham ok
46 : CAS-2T ok
47 : CAS-4B ok
48 : CAS-4A ok
49 : Aalto 1 ok
50 : URSA MAIOR ok
51 : Max Valier Sat ok
52 : D-SAT ok
53 : TechnoSat ok
54 : AO-91 ok
55 : TianYi 2 ok
56 : Zhou Enlai ok
57 : TianYi 6 ok
58 : S-Net D ok
59 : S-Net B ok
60 : S-Net A ok
61 : S-Net C ok
62 : Ten-Koh ok
63 : PO-101 ok
64 : QO-100 ok
65 : MinXSS-2 ok
66 : AO-95 ok
67 : RANGE-B ok
68 : RANGE-A ok
69 : MOVE-II ok
70 : SNUSat 2 ok
71 : SnugLite ok
72 : ITASat 1 ok
73 : EAGLET 1 ok
74 : ESEO ok
75 : CSIM ok
76 : JO-97 ok
77 : Suomi 100 ok
78 : ISAT ok
79 : UWE-4 ok
80 : Sparrow ok
81 : AISat 1 ok
82 : Prox-1 ok
83 : SONATE ok
84 : BeeSat 9 ok
85 : JAISAT-1 ok
86 : Taurus 1 ok
87 : Duchifat 3 ok
88 : OPS-SAT ok
89 : TO-108 ok
90 : FloripaSat 1 ok
91 : RS-44 ok
92 : BY70-2 ok
93 : UPMSat 2 ok
94 : AmicalSat ok
95 : SALSAT ok
96 : UVSQ-SAT ok
97 : YUSAT 1 ok
98 : SOMP 2b ok
99 : IDEASSat ok
100 : CubeSX-Sirius-HSE ok
101 : CubeSX-HSE ok
102 : KSU-Cubesat ok
103 : GRBAlpha ok
104 : Orbicraft-Zorkiy ok
105 : STECCO ok
106 : MO-110 ok
107 : TUBIN ok
108 : LEDSAT ok
109 : CUTE ok
110 : TeikyoSat 4 ok
111 : Z-Sat ok
112 : KOSEN 1 ok
113 : HO-113 ok
114 : Tevel-3 ok
115 : Tevel-8 ok
116 : Tevel-5 ok
117 : Tevel-6 ok
118 : Tevel-1 ok
119 : IRIS-A ok
120 : Tevel-7 ok
121 : Tevel-4 ok
122 : Tevel-2 ok
123 : SO-115 ok
124 : SO-114 ok
125 : OreSat0 ok
126 : Planetum 1 ok
127 : Foresail-1 ok
128 : SNUGLITE 2 ok
129 : IO-117 ok
130 : SelfieSat ok
131 : FO-118 ok
132 : SSS-2B ok
133 : CIRBE ok
134 : INSPIRE-Sat 7 ok
135 : RoseyCubesat 1 ok
136 : SO-120 ok
137 : MRC-100 ok
138 : UmKA 1 (RS40S) ok
139 : CubeBel-2 (EU11S) ok
140 : VERONIKA ok
141 : KAFASAT ok
142 : ENSO ok
143 : EIRSAT-1 ok
144 : SO-121 ok
145 : SONATE-2 ok
146 : KASHIWA ok
sorting by catalog
number.................................................................................................................................................(146)
looking for duplicate.................................................................................................................................................(146)
sorting by name.................................................................................................................................................(146)
Data of 146 satellites over 146 have been updated on 23/05/24 at 19:04:38
Last edit: Dave van der Locht 2024-05-30
Dave, did you pull the latest source off of sourceforge for your test?
I tried something. I pulled my satel.dat file that was working on my
system at work, and installed it on the slack-current system. The
satellite list was all scrambled in FBB. That is really weird, and I
have never seen that before. I have been able to use those files even
on WinFBB from that system.
-Chris KQ6UP
Last edit: Dave van der Locht 2024-05-30
As mentioned earlier I've tested with the 7.0.11 release of LinFBB (see Files section).
With the latest development (SVN) source there shouldn't be any difference. There doesn't seem to be any changes since 7.0.11 which might affect satupdat.
Regarding the scrambled satellite list... It's likely you've copied that manually from a 32-bit to a 64-bit system. Those are incompatible as several data types differ in size.
You CAN compile LinFBB on a 64-bit system with 32-bit data support. This ensures LinFBB is using / can use data files brought in from 32-bit versions of LinFBB. But... It's highly advisable NOT to do so.
Did you have to do anything different to your 64bit Slackware-current
to make sure there is 32 bit support? I did not with Slack15 release.
It all works fine here. But what you are explaining does sound like a
reasonable explanation with what is going on.
Last edit: Dave van der Locht 2024-05-30
No, I think you're misunderstanding me...
There's a config parameter in one of LinFBB's C header files to force support for FBB data files generated/used by a 32-bit version of FBB.
That parameter needs to be set ONLY if you need to use FBB datafiles from a 32-bit FBB version in a 64-bit version of FBB... It makes LinFBB on a 64-bit OS compatible with FBB datafiles coming from / generated with a 32-bit version of FBB.
Nothing more, nothing less...