Code: Select all
Jan 13 01:45:36 ns1 systemd: Cannot add dependency job for unit firewalld.service, ignoring: Unit firewalld.service is masked.
Code: Select all
Jan 13 01:45:36 ns1 systemd: Cannot add dependency job for unit firewalld.service, ignoring: Unit firewalld.service is masked.
Code: Select all
find /usr/lib/systemd/system -type f -exec grep -Hi firewalld {} \;
Here is the output:giulix63 wrote:Please, post the output of the following command run as root:Code: Select all
find /usr/lib/systemd/system -type f -exec grep -Hi firewalld {} \;
find /usr/lib/systemd/system -type f -exec grep -Hi firewalld {} \;
/usr/lib/systemd/system/firewalld.service:Description=firewalld - dynamic firewall daemon
/usr/lib/systemd/system/firewalld.service:EnvironmentFile=-/etc/sysconfig/firewalld
/usr/lib/systemd/system/firewalld.service:ExecStart=/usr/sbin/firewalld --nofork --nopid $FIREWALLD_ARGS
/usr/lib/systemd/system/firewalld.service:BusName=org.fedoraproject.FirewallD1
/usr/lib/systemd/system/firewalld.service:Alias=dbus-org.fedoraproject.FirewallD1.service
It seems I had already installed and been using it:giulix63 wrote:To use iptables, after masking firewalld as you already did, install and enable the iptables-services package.
but how to get rid of that message in the log?yum install iptables-services
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: centos.sonn.com
* extras: mirrors.unifiedlayer.com
* updates: mirrors.sonic.net
Package iptables-services-1.4.21-16.el7.x86_64 already installed and latest version
Nothing to do
Code: Select all
systemctl -l status iptables
Yep, but firewalld had been masked and stopped from the very beginning:giulix63 wrote:Your output is consistent with one on a system running firewalld.
Code: Select all
systemctl mask firewalld
systemctl stop firewalld
systemctl enable iptables
systemctl start iptables
Yes, it is running per:giulix63 wrote:Is the iptables service enabled and running? Apart from that, I wouldn't know of any more places to look at. It is just a warning, anyway...
Code: Select all
systemctl -l status iptables
● iptables.service - IPv4 firewall with iptables
Loaded: loaded (/usr/lib/systemd/system/iptables.service; enabled; vendor preset: disabled)
Active: active (exited) since Sun 2015-12-27 09:40:43 PST; 2 weeks 3 days ago
Process: 908 ExecStart=/usr/libexec/iptables/iptables.init start (code=exited, status=0/SUCCESS)
Main PID: 908 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/iptables.service
Dec 27 09:40:42 ns1.myhost.com systemd[1]: Starting IPv4 firewall with iptables...
Dec 27 09:40:43 ns1.myhost.com iptables.init[908]: iptables: Applying firewall rules: [ OK ]
Dec 27 09:40:43 ns1.myhots.com systemd[1]: Started IPv4 firewall with iptables.
What I meant is that there is no evident difference between your configuration and one that uses firewalld to explain that message. That being said, you're right, although probably you won't find much interest in getting support for fixing cosmetic issues on something that is about to be decommissioned... Just my opinion, anyway.yngens wrote: Yep, but firewalld had been masked and stopped from the very beginning:
You mean iptables? I though it is a solid one and would be around for a while. In that case I should probably start getting accustomed to firewalld. Thanks anyway!giulix63 wrote:something that is about to be decommissioned...