| Summary: | iptables-1.4.17-1: entered failed state | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Dick Gevers <dvgevers> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | chmielu1_a, tmb |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | iptables-1.4.17-1.mga3 | CVE: | |
| Status comment: | |||
$ rpm -qa |grep iptables-1.4 iptables-1.4.17-1.mga3 $ rpm -ql iptables |grep init /usr/libexec/ip6tables.init /usr/libexec/iptables.init $ cat /lib/systemd/system/ip*tables.service |grep init ExecStart=/usr/lib64/ip6tables.init start ExecStop=/usr/lib64/ip6tables.init stop ExecReload=/usr/lib64/ip6tables.init reload ExecStart=/usr/lib64/iptables.init start ExecStop=/usr/lib64/iptables.init stop ExecReload=/usr/lib64/iptables.init reload $ CC:
(none) =>
chmielu1_a Oops, my bad. this is a fallout of libexec change. Thanks for the report. fixed in iptables-1.4.17-2.mga3 Status:
NEW =>
RESOLVED |
Description of problem: # systemctl status iptables.service iptables.service - iptables Firewall for IPv4 Loaded: loaded (/usr/lib/systemd/system/iptables.service; enabled) Active: failed (Result: exit-code) since Sun, 2013-01-06 20:20:52 UTC; 3s ago Process: 3222 ExecStart=/usr/lib64/iptables.init start (code=exited, status=203/EXEC) CGroup: name=systemd:/system/iptables.service Jan 06 20:20:52 ... systemd[1]: Starting iptables Firewall for IPv4... Jan 06 20:20:52 ... systemd[1]: iptables.service: main process exited, code=exited, status=203/EXEC Jan 06 20:20:52 ... systemd[1]: Failed to start iptables Firewall for IPv4. Jan 06 20:20:52 ... systemd[1]: Unit iptables.service entered failed state This is on 3 different Cauldron machines. Reverting to 1.4.16.3-1 the problem is solved.