@Brian: this is what you see if whoopsie is the only thing reporting on syslog. If any other thing report something, it breaks the "repeated" logic of the syslog daemon and you ends up with the thing reported here.
What should happen is that whoopsie should log the "online" message only when it is BACK online (from offline or other statuses), not every few seconds of so. The logic would be something like (pseudo code).
if status==ONLINE and last_syslog_message==ONLINE then
do nothing
else
log ONLINE
fi
you can add this in /etc/rsyslog.d/00-whoopsie.conf and the messages won't be logged anymore:
# whoopsie generates a lot of messages of "online"
# these are worthless and can be filtered
if $programname == 'whoopsie' and $msg == ' online' then ~
but that way you do not see even the first "online" which is arguably worth to be logged.
@Brian: this is what you see if whoopsie is the only thing reporting on syslog. If any other thing report something, it breaks the "repeated" logic of the syslog daemon and you ends up with the thing reported here.
What should happen is that whoopsie should log the "online" message only when it is BACK online (from offline or other statuses), not every few seconds of so. The logic would be something like (pseudo code).
if status==ONLINE and last_syslog_ message= =ONLINE then
do nothing
else
log ONLINE
fi
Meanwhile, a workaround is offered here: http:// askubuntu. com/a/407935/ 16395:
you can add this in /etc/rsyslog. d/00-whoopsie. conf and the messages won't be logged anymore:
# whoopsie generates a lot of messages of "online"
# these are worthless and can be filtered
if $programname == 'whoopsie' and $msg == ' online' then ~
but that way you do not see even the first "online" which is arguably worth to be logged.