CentOS - Oct 2015 - Systemd spends 6 min. to startup a host

On Tue, Oct 6, 2015 at 6:53 AM, Gordon Messmer <gordon.messmer at
gmail.com> wrote:
> On 10/03/2015 09:47 AM, C.L. Martinez wrote:
>>
>>  All works well, except when I reboot this server. Systemd spends 6
min.
>> to startup this host!!! .. It stops with: "A start job is running
for LSB:
>> Raise network ...".
>
>
>
https://www.google.com/search?q=systemd+lsb+raise+network&ie=utf-8&oe=utf-8
>
> If your problem is similar to the first few google hits, then some part of
> your configuration is probably calling "service something
restart" or
> "systemctl restart something".  The service being restarted
requires
> network.target to be available, which only happens after the interfaces are
> all up, which is a deadlock condition.
>
> If you provide all of the configuration files you edited to enable
> openvswitch, we might be able to give you more specific advice. Your
> original question was quite vague.
>
Yes, my problem is very similar as described in Debian's bugtracker.
Ok, here is my openvswitches config:

DEVICE=dmzprif
DEVICETYPE=ovs
TYPE=OVSBridge
STP=off
ONBOOT=yes

DEVICE=encif
DEVICETYPE=ovs
TYPE=OVSBridge
STP=off
ONBOOT=yes

DEVICE=prodif
DEVICETYPE=ovs
TYPE=OVSBridge
STP=off
IPADDR=172.22.55.1
NETMASK=255.255.255.240
GATEWAY=172.22.55.14
ONBOOT=yes

DEVICE=vpnif
DEVICETYPE=ovs
TYPE=OVSBridge
STP=off
ONBOOT=yes

... and nics attached to some of these openvswitches:

DEVICE=eth0
OVS_BRIDGE=pubif
DEVICETYPE=ovs
TYPE=OVSPort
ONBOOT=yes

DEVICE=eth1
OVS_BRIDGE=prodif
DEVICETYPE=ovs
TYPE=OVSPort
ONBOOT=yes


...

On 10/05/2015 11:58 PM, C. L. Martinez wrote:
> Yes, my problem is very similar as described in Debian's bugtracker.
The problem might be a bug.  Ask the openvswitch people.

It looks like the problem is probably:
/etc/sysconfig/network-scripts/ifup-ovs calls "systemctl start 
openvswitch-nonetwork.service"
openvswitch-nonetwork.service "Wants" openvswitch.service
openvswitch.service is "After" network.target
network.target is the one that called ifup-ovs

So there's a deadlock.

At least, that's the best I can figure from looking at it briefly.

On 10/06/2015 06:14 PM, Gordon Messmer wrote:
> On 10/05/2015 11:58 PM, C. L. Martinez wrote:
>> Yes, my problem is very similar as described in Debian's
bugtracker.
>
> The problem might be a bug.  Ask the openvswitch people.
>
> It looks like the problem is probably:
> /etc/sysconfig/network-scripts/ifup-ovs calls "systemctl start
> openvswitch-nonetwork.service"
> openvswitch-nonetwork.service "Wants" openvswitch.service
> openvswitch.service is "After" network.target
> network.target is the one that called ifup-ovs
>
> So there's a deadlock.
>
> At least, that's the best I can figure from looking at it briefly.
Thanks Gordon. I think the same: it is a bug (another one with systemd).

I will do what I am thinking previously: I will start openvswitches from 
libvirtd and I will see how it goes.

Thanks.