asterisk users - Nov 2016 - Any reason Asterisk won't start without a rebuild on a cloned VPS?

Any ideas why a VPS, cloned from another instance (DigitalOcean
"droplets" if it matters), won't run on the new instance?

Everything else is the same; region, memory, disk, hypervisor version etc.

And everything else runs, just not Asterisk, unless I do a make
distclean in the /usr/src/asterisk directory, rebuild, and then it
runs just fine.

I'd understand if I was moving it to a machine with a different
kernel, but this is just a cloned instance.

Here's the kernel log for that time:

Nov 25 15:45:41  kernel: [  519.943161] traps: asterisk[1909] trap
invalid opcode ip:55a2ce786b63 sp:7ffc0f2604e0 error:0 in
asterisk[55a2ce68b000+2f6000]
Nov 25 15:46:19  kernel: [  557.633108] traps: asterisk[2677] trap
invalid opcode ip:560385143b63 sp:7ffd846cb540 error:0 in
asterisk[560385048000+2f6000]
Nov 25 15:46:22  kernel: [  560.387907] traps: asterisk[2678] trap
invalid opcode ip:5618d09a5b63 sp:7fff731341a0 error:0 in
asterisk[5618d08aa000+2f6000]
Nov 25 15:46:28  systemd[1]: Starting LSB: Asterisk PBX...
Nov 25 15:46:28  asterisk[2684]:  * Starting Asterisk PBX: asterisk
Nov 25 15:46:28  kernel: [  566.681372] traps: asterisk[2692] trap
invalid opcode ip:55b01c3feb63 sp:7ffd99b0dec0 error:0 in
asterisk[55b01c303000+2f6000]
Nov 25 15:46:28  asterisk[2684]: Illegal instruction
Nov 25 15:46:28  kernel: [  566.689693] traps: asterisk[2696] trap
invalid opcode ip:562036befb63 sp:7fff80876c80 error:0 in
asterisk[562036af4000+2f6000]
Nov 25 15:46:28  systemd[1]: asterisk.service: Control process exited,
code=exited status=132
Nov 25 15:46:28  systemd[1]: Failed to start LSB: Asterisk PBX.
Nov 25 15:46:28  systemd[1]: asterisk.service: Unit entered failed state.
Nov 25 15:46:28  systemd[1]: asterisk.service: Failed with result
'exit-code'.

BTW, while I'm in the log, any idea what this is about (less important)
63:Nov 28 11:31:23  kernel: [243839.969623] INFO: task asterisk:13711
blocked for more than 120 seconds.

On 29 November 2016 at 10:56, Jonathan H <lardconcepts at gmail.com>
wrote:
> Any ideas why a VPS, cloned from another instance (DigitalOcean
> "droplets" if it matters), won't run on the new instance?
>
> Everything else is the same; region, memory, disk, hypervisor version etc.
>
You probably need to select  "DONT_OPTIMIZE"  in make menuselect under
"Compiler Flags". This is generally required for VPS or any situation
where
the binary might be used on a slightly different CPU.

Hope this helps

-Barry Flanagan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20161129/c13906ac/attachment.html>

On Tue, Nov 29, 2016, at 07:15 AM, Barry Flanagan wrote:
> On 29 November 2016 at 10:56, Jonathan H <lardconcepts at gmail.com>
wrote:
> 
> > Any ideas why a VPS, cloned from another instance (DigitalOcean
> > "droplets" if it matters), won't run on the new
instance?
> >
> > Everything else is the same; region, memory, disk, hypervisor version
etc.
> >
> 
> You probably need to select  "DONT_OPTIMIZE"  in make menuselect
under
> "Compiler Flags". This is generally required for VPS or any
situation
> where
> the binary might be used on a slightly different CPU.
Close! The compiler flag to disable is BUILD_NATIVE. It instructs GCC to
build optimized for the CPU, if the binary is moved to a CPU that
differs - it may or may not work depending on how close they are.

-- 
Joshua Colp
Digium, Inc. | Senior Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
Check us out at: www.digium.com & www.asterisk.org