[ARGUS] Ubuntu 24.04, openargus 5, radium file rotation

[Michael Sanderson]

Hi Carter.  I recently upgraded my sensor host to Ubuntu 24.04.  I got the dreaded buffer overflow issue with the Ubuntu package for argus 3.  I found posts about this issue.  I built openargus 5 from the main branch of the git repo for both the server and the clients.  I'm again collecting data from my argus 5 daemon with a radium 5 client on a different Ubuntu 24.04 host.

Radium is configured to write to a file which is rotated every 15 minutes.  However, file rotation is behaving differently from version 3.

With version 3, I was able to move the file aside, radium would detect that and begin writing a new file, starting with a file header for argus before the argus data.  Ra was able to read any of the files.

With version 5, radium is detecting that the file have been moved and begins writing a new file.  However, that file is unreadable by ra.  It appears to be missing the file header for argus and simply starts with argus data.  ra can read the first file that radium creates (probably assuming a non-existent or empty file to start with), but not any of the files after the first rotation.  I can cat all the files since radium started and feed the whole stream to ra, but that's highly undesirable.

Is this expected?  Am I doing something wrong?

My current workaround is to stop radium, move the file, start radium.  I know I'm losing some of the data stream from my sensor.

The first file that radium creates starts with this, where the part up to and including ffff ffff looks to be consistently the same.

od -x data | head
0000000 1885 2000 0000 0000 71e5 cb50 0000 0000
0000020 0000 0000 0000 0000 6f68 554c 0d00 53e7
0000040 6f68 554c 0d00 62e7 0005 0000 0000 0000
0000060 0000 0000 0000 0000 0000 0000 0000 0000
*
0000160 0000 0000 0000 0000 0000 0000 ffff ffff
0000200 3015 3a00 0301 0321 7261 7567 a200 5252


If I don't stop/start, the file created after a rotation starts like this:

od -x data.2025.07.09-19\:00\:01  | head
0000000 3015 3a00 0301 0321 7261 7567 4300 83d7
0000020 0102 0541 220a 30af 678e f910 0006 46cd
0000040 a11a 2020 7d03 0618 6f68 1d1b 0e00 0f8f
0000060 0000 fb05 0000 0000 0000 fb05 0110 0302
0000100 0500 4802 0600 3a0d 0530 2002 0000 1f00
0000120 0000 0900 7004 0000 0000 4000 0000 8d00
0000140 6f68 1d1b f538 fa1d 0000 1d00 b18d a88e
0000160 b18d 8b8f 7537 5b70 0000 0200 0000 e200
0000200 0000 0000 0000 0000 0000 0000 2302 071b
0000220 b405 0000 6f68 1d1b f638 bd31 0000 1a00

I'm guessing that I can repair my unreadable files by prepending the header.

Thanks for you assistance,
    Michael Sanderson