You know that feeling within testing where you need to virtualize at least one database server and you’re still facing connection issues? Call me piggie, but when I’m doing anything in a localhost realm, I’m skipping creating rules and always disable firewall and SELinux.
1) SELinux
Be sure you have disabled value in this file:
1 2 3 4 5 6 7 8 9 10 11 12 13 |
[db2inst1@localhost ~]$ cat /etc/selinux/config # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing – SELinux security policy is enforced. # permissive – SELinux prints warnings instead of enforcing. # disabled – No SELinux policy is loaded. SELINUX=disabled # SELINUXTYPE= can take one of these two values: # targeted – Targeted processes are protected, # minimum – Modification of targeted policy. Only selected processes are protected. # mls – Multi Level Security protection. SELINUXTYPE=targeted |
2) Firewall – few steps:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
[root@localhost db2inst1]# systemctl disable firewalld rm ‘/etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service’ rm ‘/etc/systemd/system/basic.target.wants/firewalld.service’ [root@localhost db2inst1]# systemctl stop firewalld [root@localhost db2inst1]# systemctl status firewalld firewalld.service – firewalld – dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled) Active: inactive (dead) Dec 26 14:14:57 localhost.localdomain systemd[1]: Starting firewalld – dynamic firewall daemon… Dec 26 14:14:58 localhost.localdomain systemd[1]: Started firewalld – dynamic firewall daemon. Dec 26 14:19:07 localhost.localdomain systemd[1]: Stopping firewalld – dynamic firewall daemon… Dec 26 14:19:09 localhost.localdomain systemd[1]: Stopped firewalld – dynamic firewall daemon. [root@localhost db2inst1]# |
All done.
-a-