Right now and as of core 167, the System Logs do not offer a filter or better a section for selection, for NUT messages.
Maybe worth having a look and add an appropriate entry for filtering?
Hi @Michael (bug reporter)
Can you provide an attachment which has a copy of the lines from /var/log/messages that relate to NUT.
I installed NUT on my vm testbed and configured it but because I don't have a UPS attached to my vm system, it failed to start and there was nothing in the logs labelled as coming from NUT except for an entry which was labelled as coming from upsd.
Would it be OK, if I give you those lines in plain text format, below:
# cat /var/log/messages | grep upsmon
Sep 17 16:12:36 ipfire upsmon: Signal 15: exiting
Sep 17 16:12:36 ipfire upsmon: upsmon parent: read
Sep 17 16:12:46 ipfire upsmon: Startup successful
I just stopped NUT and restarted which put those lines into messages
Created attachment 1089 [details]
syslog output for some nut logs
Just modified log.dat myself to show the output of those three line, pls. see attachment.
(In reply to Michael from comment #3)
> Created attachment 1089 [details]
> syslog output for some nut logs
> Just modified log.dat myself to show the output of those three line, pls.
> see attachment.
Hi @ Michael,
Can you give me the changes you made in log.dat so I don't re-invent the wheel.
(In reply to Adolf Belka from comment #4)
> Hi @ Michael,
> Can you give me the changes you made in log.dat so I don't re-invent the
Inserted line 'nut', in no special order, pls. adjust as you like.
my %sections = (
'unbound' => '(unbound: \[.*:.*\])(.*:.*$)',
'nut' => '(upsmon\[.*?\]: )',
And translations, inserted line 'nut':
my %trsections = (
'unbound' => 'DNS: Unbound',
'nut' => 'Nut',
That's all! The labels can be modified as you like
Thanks. For the patch can I use your name and email address from this bug for the Tested-by: and Suggested-by: git tags?
Yes, no problem!
Patch fix has been submitted into the dev mailing liust and patchwork.
Patch committed into next repository for Core Update 171
I have tested this on Core Update 171 Testing on my vm testbed and can confirm that NUT is available in the dropdown box for the System Logs now.
As I am not using a UPS system with my virtual testbed I can't properly test this out.
Hopefully @Michael can test this out and give the feedback.
On a related note, there is also no System Log selection for the apcupsd add-on.
I don't know if this bug fix has anything to do with it but something has gone wrong with System Logs in CU171. See Community Post ...
(In reply to Charles Brown from comment #12)
> On a related note, there is also no System Log selection for the apcupsd
Please raise this as a separate bug.
(In reply to Charles Brown from comment #13)
> I don't know if this bug fix has anything to do with it but something has
> gone wrong with System Logs in CU171. See Community Post ...
I already looked at this. This only added in NUT as a menu item on the log.dat page, which then filters what is already in the messages log.
(In reply to Adolf Belka from comment #14)
> (In reply to Charles Brown from comment #12)
> > On a related note, there is also no System Log selection for the apcupsd
> > add-on.
> > -cab
> Please raise this as a separate bug.