Bug 754147 - shorewall fails to start
Summary: shorewall fails to start
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: shorewall
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jonathan Underwood
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-15 14:18 UTC by Nerijus Baliūnas
Modified: 2011-11-15 15:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-15 15:06:34 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Nerijus Baliūnas 2011-11-15 14:18:05 UTC 
After systemctl start shorewall.service I see in syslog:

shorewall.service has an ExecReload setting, which is not allowed for Type=oneshot services. Refusing.

It starts after I comment out "Type=oneshot" in /lib/systemd/system/shorewall.service.

But now shorewall does not start at boot:
ERROR: Can't determine the IP address of eth2: Firewall state not changed

Is it possible to start shorewall only after /etc/rc.d/init.d/network starts?
Comment 1 Nerijus Baliūnas 2011-11-15 15:06:34 UTC 
Changing the line
After=syslog.target
to
After=syslog.target network.target
helped. But I see this is done in 4.4.23.3-6.fc16 already in updates-testing.
Should probably be pushed to updates until more reports start to come.
Note You need to log in before you can comment on or make changes to this bug.