SOLVED IncrediblePBX13.2.iso problems take 2

[qtlnx]

Installation in VirtualBox ends up with Asterisk UP, while the same in KVM (sound enabled) ends up with Asterisk DOWN.
Am I missing something?

 

[wardmundy]

Probably. What's the platform??

 

[qtlnx]

libvirt 1.2.13.2-3.fc22.x86_64
# dmidecode | grep QEMU
Manufacturer: QEMU
Manufacturer: QEMU
Manufacturer: QEMU
Manufacturer: QEMU
Manufacturer: QEMU

 

[wardmundy]

Sorry. Not something we've used yet. Just watch the monitor during the install and see where it's blowing up. My guess is you're missing some dependencies for Asterisk.

 

[qtlnx]

From the point of view of operating system there must be absolutely no differences compare to VirtualBox.
I'll capture the install output and upload someplace for anyone interested to look at.

 

[wardmundy]

I hear what you're saying, but the results tell another story. Sorry.

 

[qtlnx]

in /var/log/asterisk/messages I see a bunch errors like "Unable to get our IP address"

[Jun 27 11:47:28] ERROR[25432] netsock2.c: getaddrinfo("IncrediblePBX.local", "(null)", ...): Name or service not known
[Jun 27 11:47:28] WARNING[25432] acl.c: Unable to lookup 'IncrediblePBX.local'

despite the fact that
cat /etc/hosts
127.0.0.1 pbx.local localhost IncrediblePBX.local localhost.localdomain localhost4 localhost4.localdomain4
::1 pbx.local localhost IncrediblePBX.local localhost.localdomain localhost6 localhost6.localdomain6

and

ping IncrediblePBX.local
PING pbx.local (127.0.0.1) 56(84) bytes of data.
64 bytes from pbx.local (127.0.0.1): icmp_seq=1 ttl=64 time=0.042 ms
...

I sent you a pointer to installation log file in a private conversation in case you are interested to look at it.

 

[wardmundy]

Reliable Internet connection is required for any Incredible PBX install to complete successfully.

 

[qtlnx]

With all respect to you, I beg you please stop talking about "reliable internet connection"!!
please read this http://blogs.digium.com/2015/02/24/install-asterisk-13-pjsip-centos-6/ and this http://lists.digium.com/pipermail/asterisk-users/2013-November/281242.html and update your IncrediblePBX13-12R.sh script to add required CFLAG or let me know where to add it.
Thanks you.

 

[wardmundy]

I assume your are referring to your PM in which you indicated:

please add required CFLAGS=-mtune=native. It has been a known asterisk requirement for several years, looks like.

As best I recall, this hasn't been a requirement since the Asterisk 1.8 days, except on the Amazon EC2 platform. And that was according to a single user, not Digium. We don't support Amazon EC2 so it probably won't be added at our end. Have you actually tried adding it to lines 327 and 329 to see if it works?

 

[qtlnx]

how exactly does the resulting line should look like? there also is configure for asterisk itself. is it needed there as well?

 

[qtlnx]

This requirement is not limited to Amazon EC2 (XEN) platform. KVM, which is now a main choice for virtual hosting is affected as well.
I added -mtune=native in both places, lines 327, 329 and 375, 377. Asterisk is now able to start.
When RedHat builds its rpms they use flags that don't cause "invalid instructions" on virtual platforms, I believe.

 

[wardmundy]

I'm not in a position to dispute your claim. Just wondering where you're getting your information?? We will do some further testing as time permits.

 

[wardmundy]

When RedHat builds its rpms they use flags that don't cause "invalid instructions" on virtual platforms, I believe.

Unfortunately, this is an Asterisk issue, not a RedHat one. You might want to pass along your suggestions to the Asterisk Development Team as well.

 

[hecatae]

This requirement is not limited to Amazon EC2 (XEN) platform. KVM, which is now a main choice for virtual hosting is affected as well.
I added -mtune=native in both places, lines 327, 329 and 375, 377. Asterisk is now able to start.
When RedHat builds its rpms they use flags that don't cause "invalid instructions" on virtual platforms, I believe.

I've never had to set those parameters on Xen 6.1, 6.2 or 6.5

What KVM platform are you using?

 

[qtlnx]

What KVM platform are you using?

listed above

 

[qtlnx]

Just wondering where you're getting your information??

root@IncrediblePBX:~ $ rpm --showrc | grep optflags
optflags : %{__global_cflags} -m32 -march=i686 -mtune=atom -fasynchronous-unwind-tables

 

[hecatae]

listed above

Fedora 22? which is end of life on 2016-07-19

I have had Incrediblepbx successfully working on OpenNode

 

[qtlnx]

Fedora 22? which is end of life on 2016-07-19

2016-07-19 is not yet here so my Fedora is fully up to date.
I'll re-run this on latest RHEL 7 when I get a chance.
However compiler is running on something installed by IncrediblePBX13.2.iso - I don't understand what you are talking about.

 

[qtlnx]

I checked another KVM on a completely different hardware - asterisk is running there.
On the failed system host CPU is
processor : 7
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i7
stepping : 9
and KVM is set to copy host processor configuration.
My point is that CFLAGS should be set to something that does not cause problems. I lost two days chasing this and would like not spend anymore time discussing. Just add whatever flags you feel necessary to avoid the problem. System flags from rpm build options is a 100% guarantee to work.