FYI CentOS 7 + IncrediblePBX install fails

[Michelle Dupuis]

I've created a fresh CentOS 7.2.11 x86_64 install and run the incredible PBX installation script for CentOS.

Although the script runs, the first clue something is wrong appears when the installed is done..it says go to http:// to administer the system. (No hostname)

On reboot, the httpd daemon stops after a minute. It starts, but is then killed (I can't figure out why).

The IP, hostname, etc. are all set correctly. I suspect something in the installer script breaks with CentOS 7.

Problems confirmed so far:
httpd.conf sets ServerLimit to 5 - I had to raise to 256 to get service to start.
httpd.conf default mutex fails - I had to change the Mutex to posixsem,
Now looks like this:

<IfModule prefork.c>
Mutex posixsem mpm-accept
StartServers 3
MinSpareServers 3
MaxSpareServers 4
ServerLimit 256
MaxClients 256
MaxRequestsPerChild 4000
</IfModule>

 

[wardmundy]

You shouldn't need 256 Apache web threads to get Apache to run reliably.

 

[Michelle Dupuis]

ok - well 5 didn't work, so I bumped it up (based on anther posting I found)...and that seemed to work then. I realized I could drop that down a lot.

I don't understand the mutex issue (but again found a workaround on the internet). Strangely the httpd started fine and kept running before the iPBX install...so something changed but I can't track what

One more recommendation: Disable the epel repo before starting the install script! Due to a packaging conflict with one package in the epel repo, the IncrediblePBX install script will complete but critical packages will be missing. So disable the epel repo BEFORE running the installer. (epel is very popular, so it might be worth adding a warning to the start of the install script)

Perhaps just a CentOS 7 issue...perhaps a general issue..in addition to setting the hostname through the hostname command, CentOS7 users should use 'hostnamectl'. As well CentOS 7 users should ensure a hostname and fqhostname are present in the /etc/hosts file before starting the installer.

 

[Michelle Dupuis]

I've attached an update to the status program which had a couple of bugs/incompatibilities. The test for fail2ban did not work properly (now tests for service status), and the test for hylafax did not work properly (now ignore grep in grep result). As well I added a couple of optional lines to the status output. Only if HAAst (High Availability for Asterisk) or SecAst (Security for Asterisk) packages are installed, will they show an UP/DN status. If not installed they will not appear in the output.