Mailinglist Archive: opensuse (736 mails)

< Previous Next >
Re: [opensuse] Why doesn't firewalld start at boot?
29.10.2018 16:14, Dave Plater пишет:


On 29/10/2018 14:47, Patrick Shanahan wrote:
* Dave Plater <dplater.list@xxxxxxxxx> [10-29-18 08:44]:


On 29/10/2018 14:33, Carlos E. R. wrote:
On 29/10/2018 13.30, Dave Plater wrote:


On 29/10/2018 14:21, Carlos E. R. wrote:
On 29/10/2018 13.12, Per Jessen wrote:
Carlos E. R. wrote:


Well, it is running. No problem with it that I can see.

That is when it is started manually - the problem is $SUBJ.

Then check the logs after boot. That's the only way to know what
happened.


All I can find, the two bottom lines are when I started it manually.
# journalctl -b|grep firewalld
Oct 29 11:46:54 Arbuthnot systemd[1]:
is_symlink_with_known_name(firewalld.service,
dbus-org.fedoraproject.FirewallD1.service) → 1
Oct 29 13:10:49 Arbuthnot systemd[1]: Starting firewalld - dynamic
firewall daemon...
Oct 29 13:10:52 Arbuthnot systemd[1]: Started firewalld - dynamic
firewall daemon.

As far as I can see, you did not have it enabled previously.

After boot :
# systemctl status firewalld
● firewalld.service - firewalld - dynamic firewall daemon
    Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled;
vendor preset: disabled)
    Active: inactive (dead)
      Docs: man:firewalld(1)
Note what line 3 says:
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled;
It doesn't start at boot.

correct, it's not directed to do so.  explained in previous mail.

I had SuSEfirewall2 installed also, don't know if that's got anything to
do with it.

Yes, it does. SuSEfirewall2.service conflicts with firewalld.service
meaning if something cause SuSEfirewall2.service be started
firewalld.service will be stopped (although in this case we should see
it in status output). Also if both are part of the same transaction, one
of them will be dropped. That is likely what happens here. I just
installed SuSEfirewall2, enabled service and rebooted. firewalld.service
is dead after reboot. Unfortunately systemd is notoriously bad with
logging so you do not see it. With debug you will get

Oct 29 20:08:05 linux-99af systemd[1]: firewalld.service: Looking at job
firewalld.service/start conflicted_by=no
Oct 29 20:08:05 linux-99af systemd[1]: firewalld.service: Looking at job
firewalld.service/stop conflicted_by=yes
Oct 29 20:08:05 linux-99af systemd[1]: firewalld.service: Fixing
conflicting jobs firewalld.service/start,firewalld.service/stop by
deleting job firewalld.service/start

But note that even *NOW* it does not say what other service causes conflict.

I just uninstalled, with -u, all firewall packages then
reinstalled firewalld. After a reboot it was completely disabled, I've
enabled it and started it, the rules for kdeconnect were still there.
/etc/sysconfig/network/config  is set at yes and most probably was all
along. (on that note it does state "if the SuSEfirewall when enabled
 should get started when network interfaces are started.") I'm going to
reboot now and if it doesn't start automatically I'll try a bug report.
Thanks
Dave P



--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >