[arm-allstar] logging ideas.. was: update has an error

Tom Hayward tom at tomh.us
Fri Jul 28 10:37:53 EST 2017


You can do something like this after it has rotated:

LOG=$(tail -n $LOWWATER log.1; cat log)

Tom KD7LXL

On Fri, Jul 28, 2017 at 8:34 AM, David McGough <kb4fxc at inttek.net> wrote:
>
> All the syslog utilities that I'm readily familiar with aren't as smart as
> I'd like;  these common tools will rotate all log entries into the waste
> basket after a period of time and leave the administrator looking at empty
> files....Ideally, the mechanism would always keep at least the amount of
> log data specified by the low water mark setting...
>
> Anyhow, we'll figure out some strategy!
>
> 73, David KB4FXC
>
>
>
> On Fri, 28 Jul 2017, Tom Hayward wrote:
>
>> I definitely had something more simple in mind, like checking the
>> return code of processes started by the menu.
>>
>> Most syslog utilities support log rotation on both size and time. I
>> haven't looked at which one you use in Hamvoip, but it could probably
>> be configured with the buffer capability you describe.
>>
>> Tom KD7LXL
>>
>> On Fri, Jul 28, 2017 at 7:52 AM, David McGough <kb4fxc at inttek.net> wrote:
>> >
>> > Hi Tom,
>> >
>> > I agree that in certain scenarios additional debugging info or logs would
>> > be very useful, as you suggest. As we all know, logs can also be a
>> > problem, if allowed to grow without maintenance....I recently had a low
>> > memory issue due to logs on a busy RPi3 that had been up continuously for
>> > 2+ months.
>> >
>> > Ideally, application messages and those generated from Admin Menu
>> > operations would get stored in a circular buffer, which could then be
>> > queried from a menu option. There are already several tools which could be
>> > used, but, I'd like to have a little more flexibility---perhaps a
>> > ring-buffer log that has a low and high water mark, but also includes a
>> > timestamp. So, the plan would be to weight the size of the buffer, between
>> > the water marks, based on the age of the log entries. The log would be
>> > allowed to grow up to the high water mark in bursts, but then would shrink
>> > back to the low mark after a period of time.
>> >
>> > Do you (or anyone?) know of an ready-to-use tool that'll do this???
>> >
>> >
>> > 73, David KB4FXC
>> >
>> >
>> > On Thu, 27 Jul 2017, "Tom Hayward via arm-allstar" wrote:
>> >
>> >> On Thu, Jul 27, 2017 at 9:24 AM, "C B via arm-allstar"
>> >> <arm-allstar at hamvoip.org> wrote:
>> >> >
>> >> > Thanks
>> >> > would you consider having the error messages stay on the screen until a OK button is pressed?
>> >> > this may be helpful.
>> >> > Chris
>> >>
>> >> That would be really helpful for any admin menu command that returned
>> >> an error. The other day when I was affected by the buffer overflow bug
>> >> for long hostnames, the observed behavior was that clicking
>> >> simpleusb-tune-menu in the menu would immediately go back to the menu.
>> >> I had to run the command from a bash shell before I could see that
>> >> there was an error message and non-zero return code. Luckily I was the
>> >> one working on it because the repeater owner I was working with isn't
>> >> as familiar with Linux and probably wouldn't have thought to try that.
>> >> The admin menu hides the complexity of bash, but in its current form
>> >> it also hides all of the error detection and reporting functionality
>> >> we have in bash.
>> >>
>> >> Tom KD7LXL
>> >> _______________________________________________
>> >>
>> >> arm-allstar mailing list
>> >> arm-allstar at hamvoip.org
>> >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>> >>
>> >> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>> >>
>> >
>>
>


More information about the arm-allstar mailing list