iridium-extractor creates debug files. no debug parameter used.

[DickvanNoort]

I'm seriously confused so I reach out for some help from the experts..

I manage 3 iridium decoder sites. All 3 run on an RPi-5 based on "DragonOS_Pi64_Beta42.img.gz ".
Only one of them produces a huge amount of debug data in the /tmp folder.
fft_burst_tagger-bursts.log
fft_burst_tagger-peaks-filtered.log
fft_burst_tagger-peaks.log

The iridium-extractor on all 3 sites is dated: Sep 8 2025.
Attached is the script I use to start iridium-extractor
and the "AIRSPY-C16255-SR10-BW9-ososdr.conf" attached as "AIRSPY-C16255-SR10-BW9-ososdr.txt"

start-Iridium-extractor-test-v01.sh

AIRSPY-C16255-SR10-BW9-ososdr.txt

Any help is much appreciated.

Cheers,
Dick

[eimann]

I bet the one writing the fft debug to /tmp is started with -v, can you check this please?

[DickvanNoort]

Correct, it has the -v parameter.
As it is documented as
-v: Verbose
will output some additional info when starting up.
see: https://github.com/muccc/gr-iridium#-v-verbose
I did not expect this behavior.

Just removed the -v parameter and that indeed solves it.
Hmmm I very much like the additional info when starting up.
So I guess/hope this will be fixed at some time in the future and just show additional info at startup.

Thank you for your fast response and solution..

Cheers,
Dick

[eimann]

Thanks for confirming. You're right that the README is misleading here. The -v flag is wired straight into the fft_burst_tagger's debug mode in the code, which is what creates those /tmp logs.

The docs only mention the startup info part, so the current behavior doesn't match what's promised.
I might get to splitting these apart next week, so -v would just give you the startup info again and the debug files would move behind a separate flag. No promises on timing, but it's on my list.

[DickvanNoort]

It indeed is very misleading (understatement).
Glad you are willing to look at it.

And what I learned is that using the issues capability works great.
I'm struggling with another problem where iridium-extractor is running out of memory and dies or reboots the RPi-5.
As a retired software person I tend to analyse problems as long as needed to be able to post a reproducible case. As that in general is the shortest route to a fix.
Will hopefully find time to draft in issue on the "out of memory" problem in a few days.

Cheers and thanks again,
Dick

[eimann]

Always happy to help! :)