Home Forums HAast (High Availability for Asterisk) Installation & Upgrade Problem starting Asterisk on SystemD+Initd system

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • Avatar photoCustomer Inquiry
    Participant
    Post count: 201

    I run a unique distro of Linux which uses SystemD, but also still uses init scripts for some apps (like Asterisk). Everything worked great until I upgraded to HAAst 2.3.1.15 now Asterisk won’t start right. How do I fix this

    Avatar photoTelium Support Group
    Participant
    Post count: 262

    Given the growing popularity of SystemD (most new Linux distros use it), as of version 2.3.1.15 HAAst changed how it interacts with system services. HAAst now uses SystemD as the default.

    More specifically, if HAAst detects that a PBX’s Linux uses SystemD, then it will start and stop services using systemctl. If the PBX’s Linux does not uses SystemD, then HAAst will start and stop services using initd scripts.

    If you find that this change broke your system, then the simplest solution is to create a SystemD service file for Asterisk on your system, and remove/rename the initd script for Asterisk (after disabling the Asterisk initd service). Have a look at this topic https://telium.io/search/Can%5C%27t+start+Asterisk+exit+code+158/ for an example asterisk.service file.

    • This reply was modified 4 years, 4 months ago by WebMaster.
    Avatar photoTelium Support Group
    Participant
    Post count: 262

    UPDATE: Based on feedback this change helped some users, but hurt others. So we’ve created a SUPPORTCODE which you can add to your haast.conf file which will force HAAst to use initd, even if your Linux distribution uses systemd.

    Just send an email to support requesting the code, and then HAAst will operate as it did before. Note that you must be running HAAst version 2.3.2.2 or later for the SUPPORTCODE to work.

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.