Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
Hello! Again I am capturing in a remote location, without good communications, using a simple raspberry and a Serial Tap. It is permanently capturing as we are trying to catch a "sporadic" issue. As communications are bad, we are "chunking" the logs, in order to be able to download just the piece of log in which the issue eventually occurs. Now, we are chunking it "restarting" the ioninja-hwc process every 2 hours. It is easy using the systemd capabilities (using RuntimeMaxSec), but a side efect is that we have to set a minimun restart timeout (2 min), in order to avoid that the unit goes permantly disabled if a error happens (mainly, during installation, the raspberry is powered up before the serial tap is connected...).
Well, my point is, perhaps you could consider to add an option in the "ioninja-hwc" in order to allow "fragment" the logs (some similar, or simpler, to the opcions "-C" / "-G" available in tcpdump).
Regards!
Hello Josep,
I apologize once again for the delayed response
You’ve made a great point! The ability to auto-split the output file into volumes could indeed be very useful (and is also trivial to implement). We’ll include something like the --split command-line option in the next release of IO Ninja.
--split
If you like, I can send you a link to an internal build of ioninja-hwc for arm64 once this feature is ready (before the official release). Let me know!
ioninja-hwc
Hello again Vladimir, Of course, if you could send me the internal build, I am still with the field device installed and I will tried it! Thank you again Regards !
Hello! Just a small additional remark, if possible/feasible/reasonable, consider the options of splitting by size (eg. each "n" MB) and by time (eg. each "t" minutes). It is just an idea... perhaps it seems more logic just consider the size, but -eg. for my case- it is more convenient to have captures of info more or less time aligned (eg. daily aligned... in fact, I am currently splitting them each 6 hours) Regards! Josep
if possible/feasible/reasonable, consider the options of splitting by size (eg. each "n" MB) and by time (eg. each "t" minutes). It is just an idea... perhaps it seems more logic just consider the size, but -eg. for my case- it is more convenient to have captures of info more or less time aligned (eg. daily aligned... in fact, I am currently splitting them each 6 hours)
Good point! Let's have settings for both!
Perfect! Thank you again. Regards
Here's an internal build of IO Ninja for arm64:
https://tibbo.com/downloads/archive/ioninja/.internal/prerelease/ioninja-5.7.1-c-linux-arm64.tar.xz
The ioninja-hwc introduces two new parameters:
--split-size <bytes> and --split-time <seconds>
--split-size <bytes>
--split-time <seconds>
Both options can be used together; in this case, the splitting will occur based on whichever condition is met first. Both options support reasonable suffixes, e.g., --split-size=10M, --split-time=6h, etc.
--split-size=10M
--split-time=6h
Let me know if this works for you!
Hello. Thank you very much, Vladimir! Now it is not convenient to install this version in the field device, because just this days we have changed the "DUT" and it is important to acquire data in the same fashion that we have been doing it before. But, as soon as I can, I will try it and provide feedback. I take the opportunity of this post to wish you Merry Christmas! Regards
Hello Jose,
Sure, no rush with the feedback -- please take your time.
And thank you so much! Wishing you a Merry Christmas and a Happy New Year as well! Enjoy your winter holidays!