Your message dated Mon, 01 Feb 2021 13:47:21 +0100
with message-id <[email protected]>
and subject line Re: firewalld: fails to start and so delays system boot
has caused the Debian Bug report #823921,
regarding firewalld: fails to start and so delays system boot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
823921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823921
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: firewalld
Version: 0.4.1.2-1
Severity: normal

Hello,

        $ sudo journalctl  | grep firewalld
        May 10 14:57:04 perseus systemd[1]: Starting firewalld - dynamic 
firewall daemon...
        May 10 14:58:34 perseus systemd[1]: firewalld.service: Start operation 
timed out. Terminating.
        May 10 14:58:34 perseus systemd[1]: Failed to start firewalld - dynamic 
firewall daemon.
        May 10 14:58:34 perseus systemd[1]: firewalld.service: Unit entered 
failed state.
        May 10 14:58:34 perseus audit[1]: SERVICE_START pid=1 uid=0 
auid=4294967295 ses=4294967295 msg='unit=firewalld comm="systemd" 
exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
        May 10 14:58:34 perseus systemd[1]: firewalld.service: Failed with 
result 'timeout'.

        $ systemctl status firewalld.service | cat
        ● firewalld.service - firewalld - dynamic firewall daemon
           Loaded: loaded (/lib/systemd/system/firewalld.service; enabled; 
vendor preset: enabled)
           Active: failed (Result: timeout) since Tue 2016-05-10 14:58:34 CEST; 
3min 7s ago
          Process: 606 ExecStart=/usr/sbin/firewalld --nofork --nopid 
(code=killed, signal=TERM)
         Main PID: 606 (code=killed, signal=TERM)

But when the system is up restarting firewalld works just fine:

        $ time sudo systemctl restart firewalld
        
        real    0m0.355s
        user    0m0.004s
        sys     0m0.000s

        $ systemctl status firewalld.service | cat
        ● firewalld.service - firewalld - dynamic firewall daemon
           Loaded: loaded (/lib/systemd/system/firewalld.service; enabled; 
vendor preset: enabled)
           Active: active (running) since Tue 2016-05-10 15:03:39 CEST; 25s ago
         Main PID: 2548 (firewalld)
            Tasks: 2 (limit: 512)
           CGroup: /system.slice/firewalld.service
                   └─2548 /usr/bin/python3 -Es /usr/sbin/firewalld --nofork 
--nopid

It cannot be fixed by purging and reinstalling firewalld.

Best regards
Uwe

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (800, 'testing'), (600, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages firewalld depends on:
ii  dbus                 1.10.8-1
ii  gir1.2-glib-2.0      1.48.0-2
ii  init-system-helpers  1.31
ii  iptables             1.6.0-2
ii  policykit-1          0.105-15
ii  python3-dbus         1.2.4-1
ii  python3-gi           3.20.1-1
ii  python3-slip-dbus    0.6.1-3
pn  python3:any          <none>

Versions of packages firewalld recommends:
ii  ebtables  2.0.10.4-3.4
ii  ipset     6.29-1

firewalld suggests no packages.

-- Configuration Files:
/etc/firewalld/firewalld.conf [Errno 13] Permission denied: 
u'/etc/firewalld/firewalld.conf'
/etc/firewalld/lockdown-whitelist.xml [Errno 13] Permission denied: 
u'/etc/firewalld/lockdown-whitelist.xml'

-- no debconf information

--- End Message ---
--- Begin Message ---
On Sat, 10 Nov 2018 16:52:56 +0100 Michael Biebl <[email protected]>
wrote:

> You you still reproduce the issue?
> Never seen such a failure myself.

Closing, since I can't reproduce myself and the existing information is
not sufficient to further debug this.

Regards,
Michael

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers

Reply via email to