Am 31.01.2013 19:43, schrieb Ranjan Maitra:
Sorry, but I get the following error:
> systemctl stop iptables.service ip6tables.service; systemctl start firewalld.service
>
$ sudo systemctl start firewalld.service
Job for firewalld.service failed. See 'systemctl status
firewalld.service' and 'journalctl -xn' for details.
$ sudo systemctl status firewalld.service
firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service;
enabled) Active: failed (Result: exit-code) since Thu 2013-01-31
12:41:52 CST; 2s ago Process: 25777 ExecStart=/usr/sbin/firewalld
--nofork $FIREWALLD_ARGS (code=exited, status=1/FAILURE)
Jan 31 12:41:52 localhost.localdomain systemd[1]: Starting firewalld ...
Jan 31 12:41:52 localhost.localdomain firewalld[25777]: 2013-01-31 12...
Jan 31 12:41:52 localhost.localdomain firewalld[25777]: 2013-01-31 12...
Jan 31 12:41:52 localhost.localdomain systemd[1]: firewalld.service: ...
Jan 31 12:41:52 localhost.localdomain systemd[1]: Failed to start fir...
Jan 31 12:41:52 localhost.localdomain systemd[1]: Unit firewalld.serv...
this output is crippled by systemctl (thanks to systemd-guys for
a very bad usability at all with their strip and pagers all the time)
"systemctl status firewalld.service | cat" should bring better output
additionally /var/log/messages is normally the place to look
i personally do not use firewalld and will never use it because
i write my own iptables.sh scripts since years which are much
more powerful and also does not unload modules at changes which
is one of the "improvements" of firewalld cuased only by weak
implementations of the GUI crap