[Home]

Summary:ASTERISK-25358: dateformat not read from logger.conf by remote console
Reporter:Igor Liferenko (Igor Liferenko)Labels:patch
Date Opened:2015-08-31 08:31:43Date Closed:2021-03-22 11:17:26
Priority:MinorRegression?
Status:Closed/CompleteComponents:Documentation
Versions:11.19.0 13.1.1 13.5.0 Frequency of
Occurrence		Constant
Related
Issues:
Environment:Attachments:( 0) date_and_call_id.patch
Description:My setup:

logger.conf:
[general]
dateformat=%F %T
[logfiles]
console => notice,warning,error,debug,verbose

asterisk.conf:
[options]
timestamp = yes

I need timestamps in asterisk remote console so as to leave it running in screen and if something happens it would be easier to debug things.

So, I add 'timestamp = yes' to asterisk.conf. But timestamp format is not read from logger.conf by 'asterisk -rvvv' for unknown reason and it shows timestamps partly in default format, and partly in "dateformat", which looks ugly:

...
[Aug 31 20:17:40]     -- Registered IAX2 to 'X.X.X.X:4569', who sees us as X.X.X.X:4569 with no messages waiting
[2015-08-31 20:17:41] NOTICE[31380]: chan_iax2.c:11159 socket_process_helper: Peer 'iax-provider' is now REACHABLE! Time: 150
...
Comments:By: Asterisk Team (asteriskteam) 2015-08-31 08:31:45.897-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
By: Matt Jordan (mjordan) 2015-09-05 14:41:10.346-0500

This occurs because the a remote console doesn't read the attributes set in {{logger.conf}}. Note that it only affects remote consoles (as the issue summary says), as a 'core console' does properly get the altered {{dateformat}} setting from {{logger.conf}}.
By: Rusty Newton (rnewton) 2015-09-08 09:09:06.770-0500

Hmm, we should at least make it clear in logger.conf what to expect. Also noting that we use the term "root console" instead of "core console" in logger.conf.
By: Mark Murawski (kobaz) 2021-02-26 17:35:42.442-0600

Patch pending submission to gerrit!
By: Mark Murawski (kobaz) 2021-02-26 17:36:16.855-0600

Bug Marshals: This also affects 16+
By: Mark Murawski (kobaz) 2021-02-26 17:41:41.622-0600

This patch (against 16.15) fixes two regressions:

-Address client console connections to respect dateformat from logger.conf
-As add support for sending call-ids to the console


By: Mark Murawski (kobaz) 2021-02-26 18:01:06.537-0600

https://gerrit.asterisk.org/c/asterisk/+/15545
By: Mark Murawski (kobaz) 2021-03-17 11:03:58.498-0500

This can be assigned to me.

Thanks.
By: Friendly Automation (friendly-automation) 2021-03-22 11:17:27.606-0500

Change 15545 merged by George Joseph:
logger: Console sessions will now respect logger.conf dateformat= option

[https://gerrit.asterisk.org/c/asterisk/+/15545|https://gerrit.asterisk.org/c/asterisk/+/15545]
By: Friendly Automation (friendly-automation) 2021-03-22 11:18:04.659-0500

Change 15683 merged by George Joseph:
logger: Console sessions will now respect logger.conf dateformat= option

[https://gerrit.asterisk.org/c/asterisk/+/15683|https://gerrit.asterisk.org/c/asterisk/+/15683]
By: Friendly Automation (friendly-automation) 2021-03-22 11:18:19.114-0500

Change 15682 merged by George Joseph:
logger: Console sessions will now respect logger.conf dateformat= option

[https://gerrit.asterisk.org/c/asterisk/+/15682|https://gerrit.asterisk.org/c/asterisk/+/15682]