Project

General

Profile

Actions

Bug #5555

open

mislabelled entries in syslog

Added by Andrew Stormont over 6 years ago. Updated about 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Start date:
2015-01-22
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:

Description

In my system log I see a lot of this sort of thing:

2015-01-21T13:53:11.027361-08:00 localhost genunix: [ID 486395 kern.info] NOTICE: e1000g0 link down

Where the message begins with "NOTICE" but it's in kern.info and not kern.notice.

Again:

2015-01-21T12:14:23.530625-08:00 localhost genunix: [ID 321598 kern.info] NOTICE: iommulib_nexus_register: rootnex-1: Succesfully registered NEXUS i86pc nexops=fffffffffbd141c0

Possibly down to me using rsyslog but I'm not sure.

Actions #1

Updated by Gary Mills about 6 years ago

I'm seeing the same thing with the stock syslog daemon:

May  2 15:39:29 ati rge: [ID 801725 kern.info] NOTICE: rge0: Using MSI interrupt type
May  2 15:39:29 ati mac: [ID 469746 kern.info] NOTICE: rge0 registered
May  2 15:39:33 ati mac: [ID 435574 kern.info] NOTICE: rge0 link up, 1000 Mbps, full duplex
May  2 15:28:51 tyan mac: [ID 486395 kern.info] NOTICE: e1000g0 link down
May  2 15:30:24 tyan mac: [ID 469746 kern.info] NOTICE: e1000g0 registered
May  2 15:30:27 tyan mac: [ID 435574 kern.info] NOTICE: e1000g0 link up, 1000 Mbps, full duplex

Should the log severity level match the severity level included in the message, or should they be independant? I'm wondering if this is really an error, or just the way things are done in illumos.

Actions #2

Updated by Andrew Stormont about 6 years ago

I'm not sure. I'd have thought labelling should be left up to syslog entirely.

Actions

Also available in: Atom PDF