[opensuse] query on "wicked" on boot on Tumbleweed
Hi if i escape the boot sequence to watch the services starting, it get stops on "wicked" with this message:- A start job is running for wicked managed network interfaces (30s/) it seems to be pausing for something else as the number in brackets starts at "1s" and usually gets to to "30s" before it "times out". Anyone know whats going on? it holds up a fairly fast boot regards Ian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Wed, 22 Apr 2015 13:08:25 +0100 ianseeks <ianseeks@yahoo.co.uk> пишет:
Hi
if i escape the boot sequence to watch the services starting, it get stops on "wicked" with this message:- A start job is running for wicked managed network interfaces (30s/)
it seems to be pausing for something else as the number in brackets starts at "1s" and usually gets to to "30s" before it "times out". Anyone know whats going on?
It probably waits for interfaces to appear or be configured. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wednesday 22 Apr 2015 19:49:04 Andrei Borzenkov wrote:
В Wed, 22 Apr 2015 13:08:25 +0100
ianseeks <ianseeks@yahoo.co.uk> пишет:
Hi
if i escape the boot sequence to watch the services starting, it get stops on "wicked" with this message:- A start job is running for wicked managed network interfaces (30s/)
it seems to be pausing for something else as the number in brackets starts at "1s" and usually gets to to "30s" before it "times out". Anyone know whats going on?
It probably waits for interfaces to appear or be configured. Thanks. Wasn't this one of the problems that the new init system was supposed to cure i.e. not having to wait for other services to be up and running while starting others? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Apr 23, 2015 at 1:21 PM, ianseeks <ianseeks@yahoo.co.uk> wrote:
On Wednesday 22 Apr 2015 19:49:04 Andrei Borzenkov wrote:
В Wed, 22 Apr 2015 13:08:25 +0100
ianseeks <ianseeks@yahoo.co.uk> пишет:
Hi
if i escape the boot sequence to watch the services starting, it get stops on "wicked" with this message:- A start job is running for wicked managed network interfaces (30s/)
it seems to be pausing for something else as the number in brackets starts at "1s" and usually gets to to "30s" before it "times out". Anyone know whats going on?
It probably waits for interfaces to appear or be configured. Thanks. Wasn't this one of the problems that the new init system was supposed to cure i.e. not having to wait for other services to be up and running while starting others?
For other services, that are not required. If some service says that it needs networking to continue, it will wait for networking to be up (or timeout). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/23/2015 06:42 AM, Andrei Borzenkov wrote:
On Thu, Apr 23, 2015 at 1:21 PM, ianseeks <ianseeks@yahoo.co.uk> wrote:
On Wednesday 22 Apr 2015 19:49:04 Andrei Borzenkov wrote:
В Wed, 22 Apr 2015 13:08:25 +0100
ianseeks <ianseeks@yahoo.co.uk> пишет:
Hi
if i escape the boot sequence to watch the services starting, it get stops on "wicked" with this message:- A start job is running for wicked managed network interfaces (30s/)
it seems to be pausing for something else as the number in brackets starts at "1s" and usually gets to to "30s" before it "times out". Anyone know whats going on?
It probably waits for interfaces to appear or be configured. Thanks. Wasn't this one of the problems that the new init system was supposed to cure i.e. not having to wait for other services to be up and running while starting others?
For other services, that are not required. If some service says that it needs networking to continue, it will wait for networking to be up (or timeout).
And of course the corollary applies: if someone who hasn't taken the time to learn how systemd units work and tries to write one for a networking service that DOES NOT wait for the basic networking service to be up, then there is a problem. Said person is likely to blame system rather than his lack of understanding. Once upon a time the professions of/business of computing dealt with such things as 'dependency trees' (or call-trees if yu were programming) as a matter of course and they were were a normal part of the design process. We still have them around, but they seem to be 'derivative' (e.g. An option in 'htop' or on 'ps' or 'systemd-analyze critical-chain') rather than part of the design process. I do not understand why this should be so. In the real world we do understand dependencies and ordering. Things like putting your socks on before your shoes and many other things are so obvious to us. How come things like systemd unit dependencies aren't? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thursday 23 Apr 2015 07:38:03 Anton Aylward wrote:
On 04/23/2015 06:42 AM, Andrei Borzenkov wrote:
On Thu, Apr 23, 2015 at 1:21 PM, ianseeks <ianseeks@yahoo.co.uk> wrote:
On Wednesday 22 Apr 2015 19:49:04 Andrei Borzenkov wrote:
В Wed, 22 Apr 2015 13:08:25 +0100
ianseeks <ianseeks@yahoo.co.uk> пишет:
Hi
if i escape the boot sequence to watch the services starting, it get stops on "wicked" with this message:- A start job is running for wicked managed network interfaces (30s/)
it seems to be pausing for something else as the number in brackets starts at "1s" and usually gets to to "30s" before it "times out". Anyone know whats going on?
It probably waits for interfaces to appear or be configured.
Thanks. Wasn't this one of the problems that the new init system was supposed to cure i.e. not having to wait for other services to be up and running while starting others?
For other services, that are not required. If some service says that it needs networking to continue, it will wait for networking to be up (or timeout).
And of course the corollary applies: if someone who hasn't taken the time to learn how systemd units work and tries to write one for a networking service that DOES NOT wait for the basic networking service to be up, then there is a problem. Said person is likely to blame system rather than his lack of understanding.
I've personally not made any changes as i don;t know enough to do so which also means i have no idea what is asking wicked to wait. Its only in the last few months or so this 30 second wait has come about. my system used to boot quite quickly but i don't know if this enforced delay coincided with me upgrading from 13.1 to Tumbleweed. If its necessary, then i have to live with it.
Once upon a time the professions of/business of computing dealt with such things as 'dependency trees' (or call-trees if yu were programming) as a matter of course and they were were a normal part of the design process. We still have them around, but they seem to be 'derivative' (e.g. An option in 'htop' or on 'ps' or 'systemd-analyze critical-chain') rather than part of the design process.
I do not understand why this should be so. In the real world we do understand dependencies and ordering.
Things like putting your socks on before your shoes and many other things are so obvious to us. How come things like systemd unit dependencies aren't?
> Q: Are you sure? > >> A: Because it reverses the logical flow of conversation. >> >>> Q: Why is top posting frowned upon?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Andrei Borzenkov -
Anton Aylward -
ianseeks