Summary:	ASTERISK-29788: symbol lookup and trap invalid opcode errors with migrated VM
Reporter:	JoshV (veeg)	Labels:
Date Opened:	2021-12-04 15:42:01.000-0600	Date Closed:	2021-12-04 15:42:02.000-0600
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	.Release/Targets
Versions:	13.38.1	Frequency of Occurrence
Related Issues:
Environment:	Debian 10, 64bit, on vultr.com	Attachments:
Description:	Recently, my Asterisk application started crashing. Process would not launch on SIP Invites and could not even launch console. I was getting the following errors and the like: asterisk symbol lookup error: undefined symbol: kernel: [1388.62997]  asterisk [811] trap invalid opcode..error: 0 in asterisk.. After much digging, I learned that my VPS provider migrated the virtual machine to another host live. I rebooted many times and nothing. I restored from older version and nothing. I finally asked provider to migrate back to original/same architecture and it worked. I then realized that Asterisk may have been compiled using CPU optimization. What are my options now? Is there a way to re-compile? I found the following switch: menuselect/menuselect --disable BUILD_NATIVE menuselect.makeopts Is this the only thing I should be looking at moving forward? Or should I rebuild a new VPS from scratch? I prefer to rebuild in place but I want to make sure it's resilient with live migrations. Thank you.
Comments:	By: Asterisk Team (asteriskteam) 2021-12-04 15:42:02.571-0600 Per the Asterisk versions page [1], the maintenance (bug fix) support for the Asterisk branch you are using has ended. For continued maintenance support please move to a supported branch of Asterisk. After testing with a supported branch, if you find this problem has not been resolved, please open a new issue against the latest version of that Asterisk branch. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions By: Asterisk Team (asteriskteam) 2021-12-04 15:42:02.937-0600 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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. 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]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].