Mailinglist Archive: opensuse-bugs (2150 mails)

< Previous Next >
[Bug 758441] systemd starts and then immediately stops SuSEfirewall2 when FW_CUSTOMRULES are run in the background

https://bugzilla.novell.com/show_bug.cgi?id=758441

https://bugzilla.novell.com/show_bug.cgi?id=758441#c8


Thomas Blume <thomas.blume@xxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
CC| |thomas.blume@xxxxxxxx
InfoProvider| |mpost@xxxxxxxx

--- Comment #8 from Thomas Blume <thomas.blume@xxxxxxxx> 2014-04-15 15:17:00
UTC ---
I've checked the issue in 12.1 versus 13.1 by putting a loop in
/root/bin/firewall_setup. Then I've put it into
/etc/sysconfig/scripts/SuSEfirewall2-custom:

fw_custom_after_finished() {
# these are the rules to be loaded after the firewall is fully configured
/root/bin/firewall_setup &
# true


and executed:

rcSuSEfirewall2 restart

On 12.1 it doesn't return as Mark reported:

linux-juaq:~ # cat /etc/SuSE-release
openSUSE 12.1 (x86_64)
VERSION = 12.1
CODENAME = Asparagus
linux-juaq:~ # systemctl status SuSEfirewall2_setup.service
SuSEfirewall2_setup.service - LSB: SuSEfirewall2 phase 2
Loaded: loaded (/etc/init.d/SuSEfirewall2_setup)
Active: active (running) since Tue, 15 Apr 2014 16:50:35 +0200; 6min ago
Process: 25464 ExecStop=/etc/init.d/SuSEfirewall2_setup stop (code=exited,
status=0/SUCCESS)
Process: 25537 ExecStart=/etc/init.d/SuSEfirewall2_setup start
(code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/SuSEfirewall2_setup.service
├ 25621 /bin/sh /root/bin/firewall_setup
└ 26031 sleep 1


But on 13.1 it returns:

linux-poml:~ # cat /etc/SuSE-release
openSUSE 13.1 (x86_64)
VERSION = 13.1
CODENAME = Bottle
# /etc/SuSE-release is deprecated and will be removed in the future, use
/etc/os-release instead
linux-poml:~ # systemctl status SuSEfirewall2_setup.service
SuSEfirewall2.service - SuSEfirewall2 phase 2
Loaded: loaded (/usr/lib/systemd/system/SuSEfirewall2.service; enabled)
Active: active (exited) since Di 2014-04-15 16:50:29 CEST; 4min 36s ago
Process: 8202 ExecStop=/usr/sbin/SuSEfirewall2 systemd_stop (code=exited,
status=0/SUCCESS)
Process: 8221 ExecStart=/usr/sbin/SuSEfirewall2 boot_setup (code=exited,
status=0/SUCCESS)
Main PID: 8221 (code=exited, status=0/SUCCESS)

Apr 15 16:50:29 linux-poml systemd[1]: Starting SuSEfirewall2 phase 2...
Apr 15 16:50:29 linux-poml SuSEfirewall2[8228]: Setting up rules from
/etc/sysconfig/SuSEfirewall2 ...
Apr 15 16:50:29 linux-poml SuSEfirewall2[8240]: Firewall customary rules loaded
from /etc/sysconfig/scripts/SuSEfirewall2-custom
Apr 15 16:50:29 linux-poml SuSEfirewall2[8221]: running 0 iteration
Apr 15 16:50:29 linux-poml SuSEfirewall2[8303]: Firewall rules successfully set
Apr 15 16:50:29 linux-poml systemd[1]: Started SuSEfirewall2 phase 2.



Reason is most probably that on 13.1 a proper services files for SUSEfirewall2
exist:

linux-poml:~ # rpm -ql SuSEfirewall2 | grep systemd
/usr/lib/systemd/system/SuSEfirewall2.service
/usr/lib/systemd/system/SuSEfirewall2_init.service
linux-poml:~ #


While on 12.1 there are none.

linux-juaq:~ # rpm -ql SuSEfirewall2 | grep systemd
linux-juaq:~ #


So, I would conclude that the issue was resolved by introducing the proper
services files.
Mark, if you have no objections, I would close the bug therewith.

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
< Previous Next >
This Thread
  • No further messages