[Home]

Summary:ASTERISK-26535: Asterisk won't start after 13.12.1 update
Reporter:Anton Bulatov (keenan)Labels:
Date Opened:2016-10-31 03:33:02Date Closed:2016-11-02 07:12:10
Priority:MajorRegression?
Status:Closed/CompleteComponents:Channels/chan_pjsip
Versions:13.12.1 Frequency of
Occurrence
Constant
Related
Issues:
is duplicated byASTERISK-26577 asterisk -rx "......" show error
Environment:FreeBSD 11 amd64Attachments:
Description:After upgrading to version 13.12.1 asterisk refuses to start saying "No ethernet interface found for seeding global EID. You will have to set it manually."
Comments:By: Asterisk Team (asteriskteam) 2016-10-31 03:33:04.469-0500

The severity of this issue has been automatically downgraded from "Blocker" to "Major". The "Blocker" severity is reserved for issues which have been determined to block the next release of Asterisk. This severity can only be set by privileged users. If this issue is deemed to block the next release it will be updated accordingly during the triage process.

By: Asterisk Team (asteriskteam) 2016-10-31 03:33:05.220-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: George Joseph (gjoseph) 2016-10-31 12:06:35.579-0500

Can you provide a backtrace?
https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace

I've tried to reproduce this on FreeBSD10 and can't.

We'll definitely need the logs and, since the EID is generated from the interface mac addresses, we'll need a dump if "ifconfig" with the ip addresses removed or course.

You could also try the current 13 GIT branch since I just made changes to the EID code.


By: Anton Bulatov (keenan) 2016-11-02 01:34:39.472-0500

Sorry, boot failure was connected with lua port conflict, I had two versions installed (lua51 and lua52), after leaving lua51 only asterisk boots and works fine except for the message about EID, it is still showing up every time i execute 'asterisk' command.

Here's my ifconfig:
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
       options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
       ether 68:05:ca:1e:26:1e
       inet6 fe80::6a05:caff:fe1e:261e%em0 prefixlen 64 scopeid 0x1
       inet6 xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx prefixlen 64 autoconf
       inet xxx.xxx.xxx.xxx netmask 0xffffff00 broadcast xxx.xxx.xxx.xxx
       nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
       media: Ethernet autoselect (100baseTX <full-duplex>)
       status: active
igb0: flags=8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500
       options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
       ether d0:50:99:53:4f:78
       nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
       media: Ethernet autoselect
       status: no carrier
igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
       options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
       ether d0:50:99:53:4f:79
       inet xxx.xxx.xxx.xxx netmask 0xffffff00 broadcast xxx.xxx.xxx.xxx
       inet6 fe80::d250:99ff:fe53:4f79%igb1 prefixlen 64 scopeid 0x3
       inet6 xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx prefixlen 64
       nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
       media: Ethernet autoselect (1000baseT <full-duplex>)
       status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
       options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
       inet6 ::1 prefixlen 128
       inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
       inet 127.0.0.1 netmask 0xff000000
       nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
       groups: lo
lo1: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
       options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
       inet6 xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx prefixlen 64
       inet6 xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx prefixlen 64
       nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
       groups: lo
gre0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1476
       options=80000<LINKSTATE>
       tunnel inet xxx.xxx.xxx.xxx --> xxx.xxx.xxx.xxx
       inet xxx.xxx.xxx.xxx --> xxx.xxx.xxx.xxx  netmask 0xfffffffc
       nd6 options=69<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL,NO_RADR>
       groups: gre

By: George Joseph (gjoseph) 2016-11-02 07:12:10.380-0500

The issue with eid is usually harmless but it should be fixed in 13.13.