1. Forum
  2. Usenet
  3. NEWS.SOFTWARE.NNTP

  • checking INN logs

    From jdanield@21:1/5 to All on Mon Jan 17 17:33:48 2022
    Hello :-)

    I receive INN logs on my mailbox. Is there some warning I could check to
    make me aware of a problem?

    thanks
    jdd

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From jdanield@21:1/5 to All on Thu Jan 20 16:00:56 2022
    Le 20/01/2022 à 15:18, Julien ÉLIE a écrit :
    Bonjour Jean-Daniel,

    bonjour :-)

    Unknown entries from news log file:
    First 2 / 2 lines (100.0%)
    Jan 10 22:49:07 news innd[1843773]: SERVER peer can't contain peer in /home/news/etc/incoming.conf line 9
    Jan 10 22:49:07 news innd[1843773]: SERVER Syntax error in /home/news/etc/incoming.conf at or before line 9

    I don't have these ones but some:

    2022-01-19T03:00:01.574081+01:00 ns507557 innd: SERVER servermode paused
    or
    2022-01-20T03:00:33.349821+01:00 ns507557 innd: SERVER paused Expiring
    process 5389

    and nothing in logs/news.err or crit


    Log entries by program:
    Program name Lines %Lines Size %Size
    nnrpd 30827 64.4% 3.1 MB 54.7%
    [...]


    nothing for nnrpd

    but if I filter for crit or error, I'm pretty sure to get the most
    important things?

    thanks
    jdd



    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Julien_=c3=89LIE?=@21:1/5 to All on Thu Jan 20 15:18:31 2022
    Bonjour Jean-Daniel,

    I receive INN logs on my mailbox. Is there some warning I could check to
    make me aware of a problem?

    Critical issues, logged in the news.crit file, will be mailed by innwatch every 10 minutes (parameter innwatchsleeptime in inn.conf).

    In your daily Usenet report, you might want to have a look at the beginning of the file. There may be "Unknown entries from news log file" and "Error log" Sections that could be worth investigating if present.



    It would appear this way in the mail (or HTML report):


    Daily Usenet report from xxx to yyy

    Unknown entries from news log file:
    First 2 / 2 lines (100.0%)
    Jan 10 22:49:07 news innd[1843773]: SERVER peer can't contain peer in /home/news/etc/incoming.conf line 9
    Jan 10 22:49:07 news innd[1843773]: SERVER Syntax error in /home/news/etc/incoming.conf at or before line 9

    Log entries by program:
    Program name Lines %Lines Size %Size nnrpd 30827 64.4% 3.1 MB 54.7% [...]


    --
    Julien ÉLIE

    « Love is blind but marriage is an eye-opener. »

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Julien_=c3=89LIE?=@21:1/5 to All on Thu Jan 20 17:17:09 2022
    Bonjour Jean-Daniel,

    Unknown entries from news log file:
    First 2 / 2 lines (100.0%)
    Jan 10 22:49:07 news innd[1843773]: SERVER peer can't contain peer in
    /home/news/etc/incoming.conf line 9
    Jan 10 22:49:07 news innd[1843773]: SERVER Syntax error in
    /home/news/etc/incoming.conf at or before line 9

    I don't have these ones but some:

    2022-01-19T03:00:01.574081+01:00 ns507557 innd: SERVER servermode paused
    or
    2022-01-20T03:00:33.349821+01:00 ns507557 innd: SERVER paused Expiring process 5389

    I indeed hope you do not have such "Syntax error" lines in your daily
    Usenet reports :)
    Do the "paused" and "Expiring process" lines appear in your daily
    reports in the "Unknown entries from news log file section"? They
    should not.

    When you said you were receiving INN logs on your mailbox, weren't you
    speaking of logs sent by news.daily? (the subject of these mails
    contains "Daily Usenet report")
    Were you speaking of simply sending you by mail the entire news logs?



    and nothing in logs/news.err or crit


    Log entries by program:
    Program name                                     Lines  %Lines
    Size  %Size
    nnrpd                                            30827   64.4%    3.1
    MB  54.7%
    [...]

    nothing for nnrpd

    but if I filter for crit or error, I'm pretty sure to get the most
    important things?

    The most important things are already handled by innwatch and news.daily (notably calling scanlogs and innreport). You don't have to rewrite a
    log processor.

    --
    Julien ÉLIE

    « Love is blind but marriage is an eye-opener. »

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From jdanield@21:1/5 to All on Thu Jan 20 17:43:00 2022
    Le 20/01/2022 à 17:17, Julien ÉLIE a écrit :

    I indeed hope you do not have such "Syntax error" lines in your daily
    Usenet reports :)

    no, none such

    Do the "paused" and "Expiring process" lines appear in your daily
    reports in the "Unknown entries from news log file section"? They
    should not.

    yes, they do

    When you said you were receiving INN logs on your mailbox, weren't you speaking of logs sent by news.daily?

    yes, dayly report, end also somewhere

    "innwatch is not running"

    and I have lot of unkwnon entries and this is not very clear:

    http://www.mibsoftware.com/userkt/inn/faq7/0042.htm

    thanks
    jdd

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Julien_=c3=89LIE?=@21:1/5 to All on Thu Jan 20 20:24:26 2022
    Bonjour Jean-Daniel,

    Do the "paused" and "Expiring process" lines appear in your daily
    reports in the "Unknown entries from news log file section"?  They
    should not.

    yes, they do

    Yet, these lines are well-known by innreport.

    In your <pathlog>/news.notice file, do dates really look like:

    2022-01-19T03:00:01.574081+01:00 ns507557 innd: SERVER servermode paused

    and not:

    Jan 20 04:15:01 news innd[1998322]: SERVER servermode paused



    When you said you were receiving INN logs on your mailbox, weren't you
    speaking of logs sent by news.daily?

    yes, dayly report, end also somewhere

    "innwatch is not running"

    There's something wrong in your setup then.
    innwatch is started at the same time all other parts of INN start (by
    the rc.news script).



    and I have lot of unkwnon entries and this is not very clear

    ... you should not have such unknown entries.

    --
    Julien ÉLIE

    « Love is blind but marriage is an eye-opener. »

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From jdanield@21:1/5 to All on Thu Jan 20 23:20:59 2022
    Le 20/01/2022 à 20:24, Julien ÉLIE a écrit :
    Bonjour Jean-Daniel,

    Do the "paused" and "Expiring process" lines appear in your daily
    reports in the "Unknown entries from news log file section"?  They
    should not.

    yes, they do

    Yet, these lines are well-known by innreport.

    In your <pathlog>/news.notice file, do dates really look like:

    2022-01-19T03:00:01.574081+01:00 ns507557 innd: SERVER servermode paused

    and not:

    Jan 20 04:15:01 news innd[1998322]: SERVER servermode paused



    When you said you were receiving INN logs on your mailbox, weren't you
    speaking of logs sent by news.daily?

    yes, dayly report, end also somewhere

    "innwatch is not running"

    There's something wrong in your setup then.
    innwatch is started at the same time all other parts of INN start (by
    the rc.news script).



    and I have lot of unkwnon entries and this is not very clear

    ... you should not have such unknown entries.


    logs> grep paused news.notice
    2022-01-20T03:00:01.746770+01:00 ns507557 innd: SERVER servermode paused 2022-01-20T03:00:33.349821+01:00 ns507557 innd: SERVER paused Expiring
    process 5389

    only two lines

    thanks
    jdd

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)