We have a FreePBX HA solution which has been running great for a while, however today we had a power failure and the HA solution will not start.
This is the output of pcs status
Cluster name: freepbx-ha
Last updated: Fri May 18 18:05:19 2018
Last change: Fri May 18 18:03:44 2018
Stack: cman
Current DC: freepbx-a - partition WITHOUT quorum
Version: 1.1.11-97629de
2 Nodes configured
22 Resources configured
Node freepbx-b: OFFLINE (standby)
Online: [ freepbx-a ]
Full list of resources:
spare_ip (ocf::heartbeat:IPaddr2): Started freepbx-a
floating_ip (ocf::heartbeat:IPaddr2): Started freepbx-a
Master/Slave Set: ms-asterisk [drbd_asterisk]
Masters: [ freepbx-a ]
Stopped: [ freepbx-b ]
Master/Slave Set: ms-mysql [drbd_mysql]
Masters: [ freepbx-a ]
Stopped: [ freepbx-b ]
Master/Slave Set: ms-httpd [drbd_httpd]
Masters: [ freepbx-a ]
Stopped: [ freepbx-b ]
Master/Slave Set: ms-spare [drbd_spare]
Masters: [ freepbx-a ]
Stopped: [ freepbx-b ]
spare_fs (ocf::heartbeat:Filesystem): Started freepbx-a
Resource Group: mysql
mysql_fs (ocf::heartbeat:Filesystem): Started freepbx-a
mysql_ip (ocf::heartbeat:IPaddr2): Started freepbx-a
mysql_service (ocf::heartbeat:mysql): Started freepbx-a
Resource Group: asterisk
asterisk_fs (ocf::heartbeat:Filesystem): Started freepbx-a
asterisk_ip (ocf::heartbeat:IPaddr2): Started freepbx-a
asterisk_service (ocf::heartbeat:freepbx): Stopped
Resource Group: httpd
httpd_fs (ocf::heartbeat:Filesystem): Stopped
httpd_ip (ocf::heartbeat:IPaddr2): Stopped
httpd_service (ocf::heartbeat:apache): Stopped
Clone Set: ClusterMon-SMTP-clone [ClusterMon-SMTP]
Started: [ freepbx-a ]
Stopped: [ freepbx-b ]
Failed actions:
asterisk_service_start_0 on freepbx-a 'unknown error' (1): call=223, status=Timed Out, last-rc-change='Fri May 18 18:03:53 2018', queued=0ms, exec=30001ms
freepbx-b is currently powered off and I have also run /usr/local/asterisk/fixcluster but it does not help
It looks like the issue is with Asterisk not being able to start - I thought this could be due to the fact that /var/www is not mounted in drbd but checking the logs after a reboot, it looks like httpd starts then asterisk attempts to start but then fails and then it unmounts /var/www
Unsure where else to look for the issue, so any help appreciated?
Asterisk should never take 240 seconds to start! This is probably a DNS issue on your end. If your machine has no DNS, then you need to make sure there’s nothing in /etc/resolv.conf, otherwise it will hang on startup.
It doesn’t take 240 seconds to start, probably more like 40 - 60 seconds, which is still longer than the default timeout of 30 seconds.
DNS is also fine and can resolve addresses. There is no internet access though, so unsure if this makes a difference to startup time (wouldn’t think so)