High Availability-FreePBX GUI down

Commercial Modules
1

I have a problem with my FreePBX GUI being down. I switched HA nodes around, then all my phones went down until I restarted Asterisk.

Now I can access the FreePBX GUI only using the IP address of my master node, not using my floating IP.
pcs resource show floating_ip shows the correct floating IP.

What could be wrong?

[[email protected] ~]# pcs status
Cluster name:
Last updated: Wed Sep 2 12:06:28 2015
Last change: Wed Sep 2 11:41:56 2015 via crmd on freepbx-b
Stack: cman
Current DC: freepbx-a - partition with quorum
Version: 1.1.10-14.el6-368c726
2 Nodes configured
20 Resources configured

Online: [ freepbx-a freepbx-b ]

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 ]
Slaves: [ freepbx-b ]
Master/Slave Set: ms-mysql [drbd_mysql]
Masters: [ freepbx-a ]
Slaves: [ freepbx-b ]
Master/Slave Set: ms-httpd [drbd_httpd]
Masters: [ freepbx-a ]
Slaves: [ freepbx-b ]
Master/Slave Set: ms-spare [drbd_spare]
Masters: [ freepbx-a ]
Slaves: [ 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): Started freepbx-a
Resource Group: httpd
httpd_fs (ocf::heartbeat:Filesystem): Started freepbx-a
httpd_ip (ocf::heartbeat:IPaddr2): Started freepbx-a
httpd_service (ocf::heartbeat:apache): Started freepbx-a

PCSD Status:
Error: no nodes found in corosync.conf

[[email protected] ~]# cat /proc/drbd

1: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r-----
ns:5928 nr:2208 dw:8136 dr:4481 al:27 bm:20 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0
2: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r-----
ns:74212 nr:14592 dw:92888 dr:10137 al:26 bm:18 lo:1 pe:1 ua:0 ap:1 ep:1 wo:f oos:0
3: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r-----
ns:13220 nr:2376 dw:15608 dr:35429 al:17 bm:18 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0
4: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r-----
ns:4 nr:8 dw:12 dr:705 al:1 bm:2 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0

[[email protected] ~]# pcs resource show floating_ip
Resource: floating_ip (class=ocf provider=heartbeat type=IPaddr2)
Attributes: ip=10.1.1.178 iflabel=ext-ip
Operations: monitor interval=30s (floating_ip-monitor-interval-30s)

2

Your best bet may be to open a ticket on this.
https://support.schmoozecom.com/

3

Would that be paid support?
We purchased one week ago.

4

You can open a commercial module ticket. They can look to see if everything is installed ok and look for any apparent bugs. If it looks like something that requires paid support they would refer you to paid support.

5

That looks perfect to me. Is it possible that you’ve somehow assigned the floating IP address to the incorrect interface? Try ‘ifconfig -a’ and make sure that the floating IP is bound to the correct interface.

(Note that it auto-detects. If it’s assigned to the wrong interface, it’s because the IP address on the wrong interface is part of the network that your floating IP address - 10.1.1.178 - is a member of)

6

Thanks Rob.

Came back by itself after an hour and has been up since.
I guess that was a temporary hickup.