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

    I have setup a new cluster, and notice that the nodes are failing over back and forth non-stop. I saw the forum topic about misconfigured network settings in HAAst, but I confirmed they are correct.

    One clue I see in the HAAst log file is that the Asterisk wrapper start is exiting with error code 3. What does that mean?

    Avatar photoTelium Support Group
    Participant
    Post count: 262

    If the Asterisk control file (wrapper) is exiting with code 3, that means Asterisk is taking too long to start. I recommend you disable the HAAst service and manually try to start the Asterisk service directly.

    I suspect you will see a long and slow (or errored) start of Asterisk. The systemd service file included with Asterisk is not ideal for cluster use and can cause slow startup. If you are using systemd please try the service file offered by Telium here:

    https://telium.io/topic/cant-start-asterisk-exit-code-158/

    • This reply was modified 4 years, 4 months ago by WebMaster.
    Avatar photoCustomer Inquiry
    Participant
    Post count: 201

    Your replacement systemd file solved my problem. I found discussions on the Digium forum about the parameters (used in the Digium provided service file) and causing slow Asterisk start. I also found this link https://community.asterisk.org/t/solved-centos-7-compatible-init-d-or-systemd-script-for-asterisk-13/66359/2 which makes reference to the same.

    I noticed your recommended SystemD service file also removes the restart parameter, which I realize makes perfect sense since HAAst should be controlling starts/stops of Asterisk, not systemd.

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