Red Hat Bugzilla – Bug 979731
firewalld times out during boot, causes long boot time
Last modified: 2013-10-22 10:36:28 EDT
Description of problem:
When i upgraded to F19-beta, I had some difficulty booting. Once I disabled RHGB, I found a 30-45-second pause where firewalld and avahi flip back and forth forbidding the system to boot until they have finished failing.
The system log says this about firewalld:
systemd: firewalld.service operation timed out. Terminating.
/var/log/firewalld is empty.
The system doesn't seem to boot up at all with RHGB teardrop being displayed. If you cancel the Fedora teardrop thing by pressing the down-arrow BEFORE the firewalld/avahi waiting message displays, the boot process will eventually move forward. I haven't had much luck if I boot and go get coffee and forget to cancel RHGB first.
This is just my home laptop, and it was a dirty upgrade from F18-F19 using FedUp, which otherwise really went quite well.
There has been a problem with with a firewalld version in beta, but this only happened if firewalld was stopped using systemd.
Please update to the latest firewalld version in F-19. Please report if the problem is still there, then.
Will do (I'm at work now, so it'll be a few hours).
I turned firewalld off Saturday since--as I studied my startup process--it DOES startup the iptables firewall first anyway, and I already understand that one.
yum update doesn't reveal any newer versions of firewalld.
HOWEVER, when I booted this evening with firewalld DISABLED, I let RHGB go, and it did the same thing (stopped on the teardrop logo screen with the teardrop full). The disk stopped spinning, and nothing would do to restore control but to kill power.
Upon rebooting, and down-arrowing the RHGB off, this time it paused with the red Cylon asterisks for a good 60 seconds trying to load Network Manager (unlike with RHGB going, the disk never stops spinning).
ANYWAY, doing a:
systemctl start firewalld
...when the system is completely started up works FINE, so I've got something ELSE going on.
I'll be darned if I can figure out how to REPORT it, but I feel like firewalld isn't actually at fault like I thought at first.
I'm having a similar issue with firewalld-0.3.7-1.fc19.noarch, but when restarting after booting.
Cristian: What is the issue exactly? What is happening?
I think it was a one time thing only, maybe caused by a combination with libvirtd. If it happens again, I'll try to provide more details.