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??
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"?
Sound like your modifications messed something with network configuration?
-- Eero
2015-10-03 19:47 GMT+03:00 C.L. Martinez carlopmart@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@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@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@centos.org https://lists.centos.org/mailman/listinfo/centos
On 10/05/2015 08:43 AM, Eero Volotinen wrote:
This looks like modifications broke network configuration and it may affect startup speed.
Please try standard network configuration first.
Are you referring to use NetworkManager?? I can't. I need to use openvswitches in this host ...
On 10/5/2015 2:36 AM, C.L. Martinez wrote:
On 10/05/2015 08:43 AM, Eero Volotinen wrote:
This looks like modifications broke network configuration and it may affect startup speed.
Please try standard network configuration first.
Are you referring to use NetworkManager?? I can't. I need to use openvswitches in this host ...
just to see if thats the problem, remove openvswitches from your config, and if it boots fast, then you know the delay is related to that.
On Mon, Oct 5, 2015 at 3:11 PM, John R Pierce pierce@hogranch.com wrote:
On 10/5/2015 2:36 AM, C.L. Martinez wrote:
On 10/05/2015 08:43 AM, Eero Volotinen wrote:
This looks like modifications broke network configuration and it may affect startup speed.
Please try standard network configuration first.
Are you referring to use NetworkManager?? I can't. I need to use openvswitches in this host ...
just to see if thats the problem, remove openvswitches from your config, and if it boots fast, then you know the delay is related to that.
-- john r pierce, recycling bits in santa cruz
Uhmm ... but I need to startup openvswitches at boot ... I only see one option: start openvswitches when libvirtd starts ...
On 10/5/2015 11:53 PM, C. L. Martinez wrote:
Uhmm ... but I need to startup openvswitches at boot ... I only see one option: start openvswitches when libvirtd starts ...
my suggestion was to help isolate the cause of this boot delay. if removing the openvswitch from your network configuration took out the delay, then you'd KNOW thats the problem, and you could work to further isolate why. if that didn't take out the delay, then the delay is somewhere else. telling me you need openvswitch isn't helping.
On Tue, Oct 6, 2015 at 7:45 AM, John R Pierce pierce@hogranch.com wrote:
On 10/5/2015 11:53 PM, C. L. Martinez wrote:
Uhmm ... but I need to startup openvswitches at boot ... I only see one option: start openvswitches when libvirtd starts ...
my suggestion was to help isolate the cause of this boot delay. if removing the openvswitch from your network configuration took out the delay, then you'd KNOW thats the problem, and you could work to further isolate why. if that didn't take out the delay, then the delay is somewhere else. telling me you need openvswitch isn't helping.
Ok, removed all openvswitches and it boots more fast, but message about LSB tasks continues ...
Arrived to this point, I am pretty sure I have a problem using old nic config ... If I disable all nics configs, voila!! ... Server boots ok.
Ok, all problems are reduced to nic settings.
The only option I see is to start openvswitches from libvirtd, but what about ethX configs??
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@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&o...
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@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&o...
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.
On 10/07/2015 12:07 AM, C.L. Martinez wrote:
Thanks Gordon. I think the same: it is a bug (another one with systemd).
It's not a systemd bug. If I'm correct, it's a bug in the openvswitch init scripts. It's simply wrong for a component of the network startup to tell systemd that it needs to start after the network service is up.
-
C. L. Martinez -
C.L. Martinez
-
Eero Volotinen -
Gordon Messmer -
John R Pierce -
Jonathan Billings -
Marcelo Ricardo Leitner -
Mihamina Rakotomandimby