Hi all,
first post to this list, hopefully on topic!
I've a VPS, KVM-based, OpenSuse Leap 15.0. firewalld 0.5.5, OpenSuse pkg-ed version. Working fine for a long time.
Since recent hardware issues on the hostsystem of my VPS the provider has had to "hard reboot" all VPS including mine on the hostsystem, unfortunately several times, some sort of "reboot loop".
Thought this should be no issue for jounaled file systems, but, however, since this hard reboots "something" is messed up in my network config. Although all relevant config files I'm aware of are identical on VPS and latest backup.
Symptoms:
- firewalld could be started by systemd, without errors.But iptables -L -n does not show anything.
- firewall-cmd runs into a DBUS error:
# firewall-cmd --state
ERROR:dbus.proxies:Introspect error on :1.63:/org/fedoraproject/FirewallD1: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
For all flags I've tested, like --get-default-zone etc.
Currently this issue prevents also nic eth0 to get up, only possible if firewalld was stopped and started later again. But same issue after next reboot.
Any ideas in which direction I should search to solve this painful issue? As said, compared all config files below /etc/firewalld, /etc/wicked (wickedd used in OpenSuse if Network Manager is not used), /etc/sysconfig/network. Couldn't find a single difference, all sizes and all timestamps are the same, made some digs into file contents, also the same.
No really helpful information with journalctl -b, can provide, if wanted.
Any hints highly appreciated!
Regards,
Michael
