Modify

Opened 4 years ago

Closed 4 years ago

#14079 closed defect (fixed)

log entries via logger have [faulty] error status on a Linksys NSLU2

Reported by: Mike Brady <mikebrady@…> Owned by: developers
Priority: normal Milestone: Chaos Calmer 15.05
Component: packages Version: Trunk
Keywords: Cc:

Description

If you use logger to log something into logread, it shows up as an error rather than a user notice. Below is an extract:

root@OpenWrt:/# logger "Sample log entry"

root@OpenWrt:/# logread

Sat Aug 24 17:43:54 2013 auth.none kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sat Aug 24 17:43:54 2013 auth.none kernel: [    0.000000]   DMA zone: 0 pages reserved
...
Sat Aug 24 17:44:21 2013 authpriv.info syslog: jffs2 is not ready - marker found
Sat Aug 24 17:44:21 2013 daemon.info sysinit: switch2jffs: jffs2 is not ready - marker found
Sat Aug 24 17:44:21 2013 auth.err kernel: [   38.972569] jffs2_scan_eraseblock(): End of filesystem marker found at 0x0
Sat Aug 24 17:44:27 2013 auth.err kernel: [   38.979568] jffs2_build_filesystem(): unlocking the mtd device... done.
Sat Aug 24 17:44:57 2013 auth.err kernel: [   44.970458] jffs2_build_filesystem(): erasing all blocks after the end marker... done.
Sat Aug 24 17:44:57 2013 auth.error kernel: [   74.761416] jffs2: notice: (1956) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
Sat Aug 24 17:44:58 2013 daemon.info sysinit: - init complete -
...
Sat Aug 24 17:51:08 2013 authpriv.error root: Sample log entry

root@OpenWrt:/# cat /etc/banner 
  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 BARRIER BREAKER (Bleeding Edge, r37834)
 ...
root@OpenWrt:/# 

You can see that the logger notice is given an "authpriv.error" priority listing. If I understand it correctly, the priority listing should be "user.notice".

This bug has been around for quite a while, and is not a big deal unless, like me, you have a kind of a watchdog process monitoring the log file for genuine error messages.

(The build is r37834 but with the Linux Version set to 3.10.4 rather than 3.10.9.)

Kind regards.

Attachments (0)

Change History (2)

comment:1 Changed 4 years ago by Mike Brady <mikebrady@…>

This has been fixed. It seems that my patch was incorporated in a new build. I'd be grateful if you would close the ticket and mark it fixed.

comment:2 Changed 4 years ago by jow

  • Resolution set to fixed
  • Status changed from new to closed

Thank you for you feedback!

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.