[asterisk-bugs] [JIRA] (ASTERISK-28418) Timezone Problem

[Kevin Harwell (JIRA)]

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

Kevin Harwell commented on ASTERISK-28418:
------------------------------------------

This is quite the unusual one. I am not discounting Asterisk's potential involvement here, but I wonder if this is some odd problem between the host, and hosted VM. If you can please provide the following information:

What OS is the host running? What OS is the hosted VM running? If possible please attach the _config.log_ file (can be found in the top level Asterisk directory where you built Asterisk from). Please also attach your _logger.conf_ file. As this is running Asterisk in VM where are Asterisk's libraries, executable, and configurations stored? In the VM itself or shared from the host?

If applicable what are the outputs of the following system commands for both host, and hosted:
{noformat}
$ ls -la /etc/localtime
{noformat}
{noformat}
$ echo $TZ
{noformat}
I know you have already provided above, but please provide again for both host and hosted, and associate it with the above information:
{noformat}
$ timedatectl
{noformat}
How is the system time, and timezone getting set when the VM is created? Could there be any scripts that are later setting the time and/or timezone?

> Timezone Problem
> ----------------
>
>                 Key: ASTERISK-28418
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28418
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 13.23.1
>            Reporter: Mesut Altürk
>            Assignee: Unassigned
>            Severity: Minor
>              Labels: pjsip
>
> Hello,
> I'm using Asterisk Asterisk 13.23.1. About 10 days later my rules are not working.  It records incorrect data on the CDR table. Then when I enter the CLI, I see that the time of modules like "chan_sip.c, acl.c, netsock2.c" is wrong, but the times of other messages are correct. I can't get a detailed log because it always comes along. But there's CLI out here. What could be the reason?
> {noformat}
> root@:~# timedatectl
> 	Local time: Fri 2019-05-17 15:26:10 +03
> 	Universal time: Fri 2019-05-17 12:26:10 UTC
> 	RTC time: Fri 2019-05-17 12:26:10
> 	Time zone: Europe/Istanbul (+03, +0300)
> 	NTP enabled: no
> 	NTP synchronized: yes
> 	RTC in local TZ: no
> 	DST active: n/a
> root@:~# asterisk -rvvvv -T
> [May 17 15:26:42]     -- Executing [s at macro-stdexten-withoutvm:32] Dial("SIP/156205-00019cfa", "SIP/156111,30,TtrXx") in new stack
> [May 17 15:26:42]   == Using SIP RTP TOS bits 184
> [May 17 15:26:42]   == Using SIP RTP CoS mark 5
> [May 17 15:26:42]     -- Called SIP/156111
> [May 17 15:26:42]     -- SIP/156111-00019cfb is ringing
> [2019-05-17 12:26:42] ERROR[4991]: netsock2.c:305 ast_sockaddr_resolve: getaddrinfo("sip.sunucunuz.com", "(null)", ...): Name or service not known
> [2019-05-17 12:26:42] WARNING[4991]: acl.c:835 resolve_first: Unable to lookup 'sip.sunucunuz.com'
> [2019-05-17 12:26:42] WARNING[4991]: acl.c:974 ast_ouraddrfor: Cannot connect to (null): Invalid argument
> [2019-05-17 12:26:42] WARNING[4991]: chan_sip.c:3781 __sip_xmit: sip_xmit of 0x7f44c0928360 (len 392) to (null) returned -1: Invalid argument
> [2019-05-17 12:26:42] NOTICE[4991]: chan_sip.c:15906 sip_reg_timeout:    -- Registration for '@sip.sunucunuz.com' timed out, trying again (Attempt #370)
> [2019-05-17 12:26:42] ERROR[4991]: netsock2.c:305 ast_sockaddr_resolve: getaddrinfo("sip.sunucunuz.com", "(null)", ...): Name or service not known
> [2019-05-17 12:26:42] WARNING[4991]: acl.c:835 resolve_first: Unable to lookup 'sip.sunucunuz.com'
> [2019-05-17 12:26:42] WARNING[4991]: acl.c:974 ast_ouraddrfor: Cannot connect to (null): Invalid argument
> [2019-05-17 12:26:42] WARNING[4991]: chan_sip.c:3781 __sip_xmit: sip_xmit of 0x7f4531f87a50 (len 394) to (null) returned -1: Invalid argument
> [2019-05-17 12:26:42] NOTICE[4991]: chan_sip.c:15906 sip_reg_timeout:    -- Registration for '@sip.sunucunuz.com' timed out, trying again (Attempt #42523)
> [2019-05-17 12:26:43] ERROR[4991]: netsock2.c:305 ast_sockaddr_resolve: getaddrinfo("sip.host.com.tr", "(null)", ...): Name or service not known
> [2019-05-17 12:26:43] WARNING[4991]: acl.c:835 resolve_first: Unable to lookup 'sip.host.com.tr'
> [2019-05-17 12:26:43] WARNING[4991]: acl.c:974 ast_ouraddrfor: Cannot connect to (null): Invalid argument
> [2019-05-17 12:26:43] WARNING[4991]: chan_sip.c:3781 __sip_xmit: sip_xmit of 0x7f44c068d3f0 (len 388) to (null) returned -1: Invalid argument
> [2019-05-17 12:26:43] NOTICE[4991]: chan_sip.c:15906 sip_reg_timeout:    -- Registration for '@sip.host.com.tr' timed out, trying again (Attempt #42524)
> [May 17 15:26:43]     -- SIP/161112-00019cf8 answered SIP/161115-00019cf7
> [May 17 15:26:43]     -- Channel SIP/161112-00019cf8 joined 'simple_bridge' basic-bridge <56bd8beb-a408-4c10-be5a-a44bd69c270e>
> [May 17 15:26:43]     -- Channel SIP/161115-00019cf7 joined 'simple_bridge' basic-bridge <56bd8beb-a408-4c10-be5a-a44bd69c270e>
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)