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

Hi all,

  I have a strange behavior with a CentOS7 host (fully patched). I have 
configured nics as old style format: ifcfg- ... due to I need to use 
openvswitch for my vms.

  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 ...".

  Are not supposed that systemd startups hosts more faster??

  ok, is it possible to fix this??

Thanks.

On 10/03/2015 04:47 PM, C.L. Martinez wrote:
> Hi all,
>
>   I have a strange behavior with a CentOS7 host (fully patched). I have
> configured nics as old style format: ifcfg- ... due to I need to use
> openvswitch for my vms.
>
>   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 ...".
>
>   Are not supposed that systemd startups hosts more faster??
>
>   ok, is it possible to fix this??
>
> Thanks.
Please, any idea how to fix this??

Sound like your modifications messed something with network configuration?

--
Eero

2015-10-03 19:47 GMT+03:00 C.L. Martinez <carlopmart at gmail.com>:
> Hi all,
>
>  I have a strange behavior with a CentOS7 host (fully patched). I have
> configured nics as old style format: ifcfg- ... due to I need to use
> openvswitch for my vms.
>
>  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 ...".
>
>  Are not supposed that systemd startups hosts more faster??
>
>  ok, is it possible to fix this??
>
> Thanks.
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
>

On 10/03/2015 07:47 PM, C.L. Martinez wrote:
> Hi all, [...]
>
>  Are not supposed that systemd startups hosts more faster??
> ts.centos.org/mailman/listinfo/centos
I think you misunderstand: systemd has a dependency management between 
services, that could make the boot faster.
Speeding up the boot was not the goal, it's an effect.

This looks like modifications broke network configuration and it may affect
startup speed.

Please try standard network configuration first.

--
Eero

2015-10-05 11:38 GMT+03:00 Mihamina Rakotomandimby <
mihamina.rakotomandimby at rktmb.org>:
> On 10/03/2015 07:47 PM, C.L. Martinez wrote:
>
>> Hi all, [...]
>>
>>  Are not supposed that systemd startups hosts more faster??
>> ts.centos.org/mailman/listinfo/centos
>>
>
> I think you misunderstand: systemd has a dependency management between
> services, that could make the boot faster.
> Speeding up the boot was not the goal, it's an effect.
>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
>

On Mon, Oct 05, 2015 at 06:42:01AM +0000, C.L. Martinez
wrote:
> Please, any idea how to fix this??
What's the output of "systemd-analyze blame"?

-- 
Jonathan Billings <billings at negate.org>

Em 03-10-2015 13:47, C.L. Martinez escreveu:
> Hi all,
>
>   I have a strange behavior with a CentOS7 host (fully patched). I have
> configured nics as old style format: ifcfg- ... due to I need to use
> openvswitch for my vms.
>
>   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 ...".
>
>   Are not supposed that systemd startups hosts more faster??
>
>   ok, is it possible to fix this??
While booting it, if you get out of the plymouth screen (press esc), you 
should be able to see a message like
'Waiting for <service name>...'
that should give you a direction already.

   Marcelo

On Mon, Oct 5, 2015 at 1:56 PM, Marcelo Ricardo Leitner
<marcelo.leitner at gmail.com> wrote:
> Em 03-10-2015 13:47, C.L. Martinez escreveu:
>>
>> Hi all,
>>
>>   I have a strange behavior with a CentOS7 host (fully patched). I have
>> configured nics as old style format: ifcfg- ... due to I need to use
>> openvswitch for my vms.
>>
>>   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 ...".
>>
>>   Are not supposed that systemd startups hosts more faster??
>>
>>   ok, is it possible to fix this??
>
>
> While booting it, if you get out of the plymouth screen (press esc), you
> should be able to see a message like
> 'Waiting for <service name>...'
> that should give you a direction already.
>
Nop, there is no errors ... Only the delay message ...

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.

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


...