[asterisk-bugs] [JIRA] (ASTERISK-21168) asterisk logger stops logging VERBOSE and NOTICE messages after some time.

[Rusty Newton (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-21168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rusty Newton updated ASTERISK-21168:
------------------------------------

    Assignee: Nikola Ciprich
      Status: Waiting for Feedback  (was: Triage)

If we can't reproduce this issue, there is nothing we can do.

You'll need to help us by looking into what happens around the time the logger stops logging.

Also, please attach your logger.conf and asterisk.conf files. (More Actions > Attach files)

You could also add the message type DEBUG, and after the issue occurs provide us the log so we look at whats going on right before the issue occurs.

In general, we'll need more specific information about what is happening on the system, what is happening in Asterisk and need any relevant configuration files.
                
> asterisk logger stops logging VERBOSE and NOTICE messages after some time.
> --------------------------------------------------------------------------
>
>                 Key: ASTERISK-21168
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21168
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/General
>    Affects Versions: 1.8.20.1
>         Environment: RHEL5
>            Reporter: Nikola Ciprich
>            Assignee: Nikola Ciprich
>
> We're usually using notice,warning,error,debug,verbose logging on our asterisk boxes. (either to file, or using syslog). however, it's happening, that after some time asterisk starts logging only WARNING/ERROR messages. We usually find out when we need to investigate some problem, that logs are incomplete... What is strange is, that when asterisk console is connected (using asterisk -rvvvvvvv), logging immetiately starts working, on the other side, forcing logger reload using "asterisk -rx "logger reload") doesn't help.. We've observed this behaviour on wide variety of versions from 1.4.x to 1.8.x.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira