Centos 7 install: bypass firewalld?

[mbeebe]

Hello,

We're doing a "try before you buy" of Fusion, but have run into a problem when installing on a clean Centos 7 box:

Code: Select all

Database installed OK
RESULT=0
Running './04-general.sh'...
FirewallD is not running
FirewallD is not running
FirewallD is not running
FirewallD is not running
Failed to execute operation: File exists
RESULT=1

===================
INSTALLATION ERROR!
===================
Installation step failed - exiting.
Check for error messages in the install log (install.log).

If you require assistance in resolving the issue, please include install.log
in your communications with Nagios technical support.

The script that failed was: './04-general.sh'

Needless to say this makes me very sad as a systems administrator.

Is there any way to skip/bypass the need for firewalld? I don't need a firewall on this box as it's inside a DMZ that's already behind a firewall.

I anxiously await your learned reply,


-- Mike Beebe

[lmiltchev]

Try commenting out the entire firewall section in the /tmp/nagiosfusion/setup/04-general.sh script (line 40 - 62):

Code: Select all

# ================
# Firewall
# ----------------

# Skip firewall configuration for Ubuntu for now
#if [ "$distro" == "Ubuntu" ] || [ "$distro" == "Debian" ]; then
#    echo "Skipping firewall configuration... Not enabled."
#else
    # Firewalld settings for CentOS/RHEL 7 (except 7.2)
#    if [ "$dist" == "el7" ]; then
#        set +e
#        if [ `command -v firewall-cmd` ]; then
#            firewall-cmd --zone=public --add-port=80/tcp --permanent
#            firewall-cmd --zone=public --add-port=403/tcp --permanent
#            firewall-cmd --zone=public --add-port=22/tcp --permanent
#            firewall-cmd --reload
#        fi
#        set -e
#    else
#        cp -f inc/iptables /etc/sysconfig
#        service iptables restart
#    fi
#fi

save, exit, and rerun the "fullinstall" script. Did the install complete?

[mbeebe]

Hello,

Yeah -- I actually re-wrote part of that script yesterday. There is some sort of "bug" in it, however, that I wasn't able to trace: the "file already exists" error. I'm not sure what's causing that. However, time didn't allow me to dig too deep.

What I did to work around the error was run:

bash --debug 04-general.sh

The "file already exists" issue arose, but the script finished running, and wrote the "done" file the next script is expecting. After jumping through more hoops than I can count, the installation finally completed successfully. Sadly, Fusion isn't going to solve my problem but it will offer a few other features that'll make management happy.


-- Mike Beebe

[mbellerue]

It's good to hear that the installation completed. Is it working as expected, or is there more we can help with? We want to make sure you're as happy a systems administrator as possible before we close this thread.

[mbeebe]

Nope -- you've been most helpful and I'm about as happy as I'm going to get.

Thanks again!