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

[Mesut Altürk (JIRA)]

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

Mesut Altürk commented on ASTERISK-28418:
-----------------------------------------

Hi Kevin,

;ESXi VSphere 6.5
***************************************************************************
[root at localhost:~] ls -la /etc/localtime
-r--r--r--    1 root     root            56 Apr 11  2016 /etc/localtime

[root at localhost:~] echo $TZ

[root at localhost:~] timedatectl
-sh: timedatectl: not found

;Asterisk / Debian 8
***************************************************************************
root@:~# ls -la /etc/localtime
lrwxrwxrwx 1 root root 35 Jun 30 23:59 /etc/localtime -> /usr/share/zoneinfo/Europe/Istanbul

root@:~# echo $TZ
EET-2EEST,M3.5.0/3,M10.5.0/4

root@:~# timedatectl
Warning: Ignoring the TZ variable. Reading the system's time zone setting only.

      Local time: Mon 2019-07-01 14:57:10 +03
  Universal time: Mon 2019-07-01 11:57:10 UTC
        RTC time: Mon 2019-07-01 11:57:10
       Time zone: Europe/Istanbul (+03, +0300)
     NTP enabled: yes
NTP synchronized: yes
 RTC in local TZ: no
      DST active: n/a

root@:~# ps aux | grep asterisk
root      7745  0.0  0.0   4336   124 ?        S    Apr28   0:00 /bin/sh /usr/sbin/safe_asterisk -f
root      7749 16.2 34.2 4160228 1392008 ?     Sl   Apr28 15145:32 /usr/sbin/asterisk -f -f -vvvg -c
root     32211  0.0  0.0  12732  2084 pts/1    S+   14:59   0:00 grep asterisk


> 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: Mesut Altürk
>            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)