You are here: Home » Topic » svn-1545 is chatty with syslog

svn-1545 is chatty with syslog

This topic contains 3 replies, has 2 voices, and was last updated by  rpedde 10 years, 4 months ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #1315

    Gonzo
    Participant

    Hi,

    first of all, congratulations to the svn-1545 release and to making it into the center of Roku attention!

    I just upgraded from 1340 to 1545. But mt-daapd is quite chatty: Even though I have configured a logfile in mt-daapd.conf (and mt-daapd happily writes to that too), it keeps logging a lot of other stuff to syslog at daemon.alert levels. IMHO, this is a bit exaggerated:

    Apr 19 22:52:20 condorito mt-daapd[11377]: [ID 702911 daemon.alert] Plugin loaded: rsp/svn-1545
    Apr 19 22:52:20 condorito mt-daapd[11377]: [ID 702911 daemon.alert] Plugin loaded: daap/svn-1545
    Apr 19 22:52:20 condorito mt-daapd[11377]: [ID 702911 daemon.alert] Starting rendezvous daemon
    Apr 19 22:52:20 condorito mt-daapd[11377]: [ID 702911 daemon.alert] Starting signal handler
    Apr 19 22:52:20 condorito mt-daapd[11379]: [ID 702911 daemon.alert] Old database version: 11, expecting 13
    Apr 19 22:52:20 condorito mt-daapd[11379]: [ID 702911 daemon.alert] Upgrading db: 11 –> 12
    Apr 19 22:52:20 condorito mt-daapd[11379]: [ID 702911 daemon.alert] Upgrading db: 12 –> 13
    Apr 19 22:52:21 condorito mt-daapd[11379]: [ID 702911 daemon.alert] Initializing database
    Apr 19 22:52:21 condorito mt-daapd[11379]: [ID 702911 daemon.alert] Full reload…
    Apr 19 22:52:22 condorito mt-daapd[11379]: [ID 702911 daemon.alert] Starting mp3 scan

    Is that a bug? Or did I overlook something in the config?

    Best regards,
    Constantin

    #10254

    rpedde
    Participant

    @gonzo wrote:

    Hi,

    first of all, congratulations to the svn-1545 release and to making it into the center of Roku attention!

    I just upgraded from 1340 to 1545. But mt-daapd is quite chatty: Even though I have configured a logfile in mt-daapd.conf (and mt-daapd happily writes to that too), it keeps logging a lot of other stuff to syslog at daemon.alert levels. IMHO, this is a bit exaggerated:

    Apr 19 22:52:20 condorito mt-daapd[11377]: [ID 702911 daemon.alert] Plugin loaded: rsp/svn-1545
    Apr 19 22:52:20 condorito mt-daapd[11377]: [ID 702911 daemon.alert] Plugin loaded: daap/svn-1545
    Apr 19 22:52:20 condorito mt-daapd[11377]: [ID 702911 daemon.alert] Starting rendezvous daemon
    Apr 19 22:52:20 condorito mt-daapd[11377]: [ID 702911 daemon.alert] Starting signal handler
    Apr 19 22:52:20 condorito mt-daapd[11379]: [ID 702911 daemon.alert] Old database version: 11, expecting 13
    Apr 19 22:52:20 condorito mt-daapd[11379]: [ID 702911 daemon.alert] Upgrading db: 11 –> 12
    Apr 19 22:52:20 condorito mt-daapd[11379]: [ID 702911 daemon.alert] Upgrading db: 12 –> 13
    Apr 19 22:52:21 condorito mt-daapd[11379]: [ID 702911 daemon.alert] Initializing database
    Apr 19 22:52:21 condorito mt-daapd[11379]: [ID 702911 daemon.alert] Full reload…
    Apr 19 22:52:22 condorito mt-daapd[11379]: [ID 702911 daemon.alert] Starting mp3 scan

    Is that a bug? Or did I overlook something in the config?

    Best regards,
    Constantin

    Some of that really is chattier than it should be. I’ll have to look at what goes into the syslog right now. I know the windows event log I already tuned down a bit, I may need to do it again.

    — Ron

    #10255

    Gonzo
    Participant

    Hi Ron,

    Some of that really is chattier than it should be. I’ll have to look at what goes into the syslog right now. I know the windows event log I already tuned down a bit, I may need to do it again.

    thanks! The easiest way is probably to tune the severity levels. The stuff I see should probably be daemon.info for the “I’m now doing x” stuff and maybe daemon.notice for special actions like “upgrading db”.

    Have a nice weekend,
    Constantin

    #10256

    rpedde
    Participant

    @gonzo wrote:

    Hi Ron,

    Some of that really is chattier than it should be. I’ll have to look at what goes into the syslog right now. I know the windows event log I already tuned down a bit, I may need to do it again.

    thanks! The easiest way is probably to tune the severity levels. The stuff I see should probably be daemon.info for the “I’m now doing x” stuff and maybe daemon.notice for special actions like “upgrading db”.

    Have a nice weekend,
    Constantin

    Not sure how I’m mapping the warning levels. But that sounds like a reasonable level. I’m not sure I *ever* want debug quantities going into syslog, only to logfile, so I need to separate what goes into syslog, what goes into logfile, and what goes into both, and at what level.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.