Asterisk Server no longer runs after reboot.

For clarification, it would be helpful to know what Linux Distribution is being run and what version of Asterisk you have installed.

Some reasons your software may fail after an emergency migration:

• If Asterisk was installed from source, it may have compiled the code too tightly bound to a specific processor version. Emergency maintenance often means a Linode moved to a different physical host. If the Linode was running on a host with a newer processor when Asterisk was compiled, it may have tried to use features not available on a host with a different version of the processor. You can ask Linode Support to see if they can migrate your Linode to another host having the original hardware, or you can recompile Asterisk on the new host. This page suggests disabling the BUILD_NATIVE option during compile when building for a virtual hosting environment

• If the Asterisk server was not enabled at the same time it was started, it will not come backup after a reboot. On most systems the command to enable software to run at boot time is:

sudo systemctl enable asterisk.service
sudo systemctl start asterisk.service

• There may have been a configuration change since the last time Asterisk was started. An error introduced to a configuration file with out restarting the service will wait indefinitely until the next reboot to cause problems.

• If the Linode powered off abruptly due to hardware failure a lock file may exist on the disk that is preventing it from restarting. The lock file will usually be called /var/run/asterisk/asterisk.pid.

• If you have selected "Latest 64Bit Kernel" in your Linode's Configuration Profile, a reboot could cause you to boot with a newer and possibly incompatible kernel.

• A filesystem check can help determine if there is any disk corruption. This can be done in Rescue Mode