[asterisk-bugs] [JIRA] (ASTERISK-25407) Asterisk fails to log to multiple syslog destinations
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Wed Jul 27 10:16:21 CDT 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-25407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asterisk Team updated ASTERISK-25407:
-------------------------------------
Target Release Version/s: 14.0.0
> Asterisk fails to log to multiple syslog destinations
> -----------------------------------------------------
>
> Key: ASTERISK-25407
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-25407
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Core/Logging
> Affects Versions: SVN
> Environment: Slackware Linux x86-64
> Reporter: Elazar Broad
> Severity: Minor
> Target Release: 11.20.0, 11.23.0, 13.6.0, 13.9.0, 14.0.0
>
> Attachments: 25407_v1.patch
>
>
> When configuring more than one syslog destinations in logger.conf, Asterisk will only log to the last one in the configuration. For example:
> syslog.local1 => error, warning, notice
> syslog.local2 => security
> Everything is logged to local2.
> This is due to the fact that the final call to openlog() in make_log_channel() supersedes the previous calls. My humble suggestion would be to eliminate the openlog() call, as the syslog() call in ast_log_vsyslog() will open the log as needed; pass the channel facility to ast_log_vsyslog() and use the LOG_MAKEPRI macro to ensure the message is sent to the correct facility. I have tested this successfully on my system and will post a patch to reviewboard in the morning.
> Thanks,
> Elazar
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list