On 11/17/2011 12:24 PM, Michael Schwendt wrote:
Fedora 16 x86_64 plus updates-testing
Some time ago systemd has started with reporting that both the iptables4
and iptables6 services fail at boot time. For example:
| Starting IPv4 firewall with iptables...
| Starting IPv4 firewall with
On 11/19/2011 09:25 AM, Claude Jones wrote:
Anyone has seen this, too?
Yes, I'm getting something similar, but it gets crazier! Running this
produces the following:
***
status iptables.service
status: Unable to connect to
status: Unable to connect to Upstart: Failed to connect to socket
/com/ubuntu/upstart: Connection refused
***
What is that reference to an Ubuntu folder about??? It doesn't exist on
my system.
Upstart is a different
On Thu, 17 Nov 2011 19:52:00 -0700, TCH (T.C.) wrote:
# systemctl status iptables.service
#iptables.service - IPv4 firewall with iptables
Loaded: loaded (/lib/systemd/system/iptables.service; enabled)
Active: failed since Thu, 17 Nov 2011 18:19:23 +0100; 2min 31s ago
Fedora 16 x86_64 plus updates-testing
Some time ago systemd has started with reporting that both the iptables4
and iptables6 services fail at boot time. For example:
| Starting IPv4 firewall with iptables...
| Starting IPv4 firewall with iptables failed, see 'systemctl status
iptables.service'
On Thu, Nov 17, 2011 at 3:24 PM, Michael Schwendt mschwe...@gmail.com wrote:
Fedora 16 x86_64 plus updates-testing
Some time ago systemd has started with reporting that both the iptables4
and iptables6 services fail at boot time. For example:
| Starting IPv4 firewall with iptables...
|
Michael Schwendt wrote:
Anyone has seen this, too?
My iptables is starting normally without user-intervention.
Do you have customized iptables rules? If you do, try it without them?
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
On Thu, Nov 17, 2011 at 12:24 PM, Michael Schwendt mschwe...@gmail.com wrote:
Fedora 16 x86_64 plus updates-testing
...
Once logged in, I can start it manually without problems. SELinux is not
the culprit. The services fail also when running permissive mode. It seems
as if it's another race
On Thu, 17 Nov 2011 13:13:01 -0500, DM (Deron) wrote:
Fedora 16 x86_64 plus updates-testing
...
Once logged in, I can start it manually without problems. SELinux is not
the culprit. The services fail also when running permissive mode. It seems
as if it's another race between systemd
On Thu, Nov 17, 2011 at 10:24 AM, Michael Schwendt mschwe...@gmail.com wrote:
Fedora 16 x86_64 plus updates-testing
Some time ago systemd has started with reporting that both the iptables4
and iptables6 services fail at boot time. For example:
| Starting IPv4 firewall with iptables...
|
10 matches
Mail list logo
