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

[Nikola Ciprich (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205198#comment-205198 ] 

Nikola Ciprich commented on ASTERISK-21168:
-------------------------------------------

so to confirm - DEBUG messages are enabled on both the systems that seem to fail and the ones that appear fine, but on the ones that fail at some point you have changed the level of DEBUG by using the CLI command?

- actually it's the opposite. Yes, I have debug messages logging enabled on both failing and nonfailing systems. On (failing) systems when I've enabled debugging using core set debug 10 as I was requested, problem vanished..

Can you tell us the following about the systems that exhibit the behavior and the ones that don't:
Has Asterisk been started with any number of -v or -d flags?

- no -v's, no -d's

Is asterisk.conf identical to the one you posted here? (that is with no verbose= or debug= options set?)

- yes, no verbose, no debug mention in asterisk.conf


                
> 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
>         Attachments: asterisk.conf, logger.conf
>
>
> 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: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira