[opensuse-factory] big start delay each boot @
[Fresh e17 32 bit HTTP M4 snapshot installation just hours ago] "A start job is running for LSB: Configure network interfaces and set up routing" Not timed, but delay estimated at well over 2 minutes. Installation was begun with net.ifnames=0 on cmdline, but networking seems working as intended on eth0. /var/log/warn seems to be the only log with a clue, but I don't recognize what's happening except for some apparent time gaps: http://fm.no-ip.com/Tmp/SUSE/Factory/varlogwarn131m4-gx260.txt Only glitch I noticed during installation was a checksum/shasum problem with schrodinger, whatever that is. I tabooed wireless*, plymouth and splashy. Bug (in what)? How do I get boot time down to reasonable? y2logs: http://fm.no-ip.com/Tmp/SUSE/Factory/y2l-gx260-131m4.tgz -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
В Tue, 13 Aug 2013 12:25:30 -0400
Felix Miata
[Fresh e17 32 bit HTTP M4 snapshot installation just hours ago]
"A start job is running for LSB: Configure network interfaces and set up routing"
Not timed, but delay estimated at well over 2 minutes. Installation was begun with net.ifnames=0 on cmdline, but networking seems working as intended on eth0. /var/log/warn seems to be the only log with a clue, but I don't recognize what's happening except for some apparent time gaps: http://fm.no-ip.com/Tmp/SUSE/Factory/varlogwarn131m4-gx260.txt
What network.service resolves to? bor@opensuse:~> systemctl --no-pager show network.service -p FragmentPath -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-08-13 20:31 (GMT+0400) Andrey Borzenkov composed:
13 Aug 2013 12:25:30 -0400 Felix Miata composed:
[Fresh e17 32 bit HTTP M4 snapshot installation just hours ago]
"A start job is running for LSB: Configure network interfaces and set up routing"
Not timed, but delay estimated at well over 2 minutes. Installation was begun with net.ifnames=0 on cmdline, but networking seems working as intended on eth0. /var/log/warn seems to be the only log with a clue, but I don't recognize what's happening except for some apparent time gaps: http://fm.no-ip.com/Tmp/SUSE/Factory/varlogwarn131m4-gx260.txt
What network.service resolves to?
bor@opensuse:~> systemctl --no-pager show network.service -p FragmentPath
FragmentPath= -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 13.08.2013 18:25, schrieb Felix Miata:
[Fresh e17 32 bit HTTP M4 snapshot installation just hours ago]
"A start job is running for LSB: Configure network interfaces and set up routing"
Not timed, but delay estimated at well over 2 minutes. Installation was begun with net.ifnames=0 on cmdline, but networking seems working as intended on eth0. /var/log/warn seems to be the only log with a clue, but I don't recognize what's happening except for some apparent time gaps: http://fm.no-ip.com/Tmp/SUSE/Factory/varlogwarn131m4-gx260.txt
Try "systemd-analyze blame" to see what's taking too long. And check for "job xxx timed out" messages in "journalctl -b" -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-08-13 23:05 (GMT+0200) Stefan Seyfried composed:
Felix Miata composed:
[Fresh e17 32 bit HTTP M4 snapshot installation just hours ago]
"A start job is running for LSB: Configure network interfaces and set up routing"
Not timed, but delay estimated at well over 2 minutes. Installation was begun with net.ifnames=0 on cmdline, but networking seems working as intended on eth0. /var/log/warn seems to be the only log with a clue, but I don't recognize what's happening except for some apparent time gaps: http://fm.no-ip.com/Tmp/SUSE/Factory/varlogwarn131m4-gx260.txt
Try "systemd-analyze blame" to see what's taking too long.
first place: 5min 2ms network.service second place: 7.338s systemd-fsck@dev....
And check for "job xxx timed out" messages in "journalctl -b"
http://fm.no-ip.com/Tmp/SUSE/Factory/journalctl-b-gx260-os131m4.txt tail of journalctl - b output shows the five minutes, but it's not terribly clear to me where the problem might lie. First line in the saved tail is: ifup[900]: Aug 13 16:55:27 gx260 network[403]: if-up.d/21-cifs: line 57: /bin/mountpoint: No such file or directory Avahi isn't anything I ever use knowingly. Is /bin/mountpoint something from the failed schrodinger package? /usr/bin/mountpoint does exist. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-08-13 17:31 (GMT-0400) Felix Miata composed:
On 2013-08-13 23:05 (GMT+0200) Stefan Seyfried composed:
Felix Miata composed:
[Fresh e17 32 bit HTTP M4 snapshot installation just hours ago]
"A start job is running for LSB: Configure network interfaces and set up routing"
Not timed, but delay estimated at well over 2 minutes. Installation was begun with net.ifnames=0 on cmdline, but networking seems working as intended on eth0. /var/log/warn seems to be the only log with a clue, but I don't recognize what's happening except for some apparent time gaps: http://fm.no-ip.com/Tmp/SUSE/Factory/varlogwarn131m4-gx260.txt
Try "systemd-analyze blame" to see what's taking too long.
first place: 5min 2ms network.service second place: 7.338s systemd-fsck@dev....
And check for "job xxx timed out" messages in "journalctl -b"
http://fm.no-ip.com/Tmp/SUSE/Factory/journalctl-b-gx260-os131m4.txt tail of journalctl - b output shows the five minutes, but it's not terribly clear to me where the problem might lie. First line in the saved tail is: ifup[900]: Aug 13 16:55:27 gx260 network[403]: if-up.d/21-cifs: line 57: /bin/mountpoint: No such file or directory
Avahi isn't anything I ever use knowingly. Is /bin/mountpoint something from the failed schrodinger package? /usr/bin/mountpoint does exist.
Appears bug already filed: https://bugzilla.novell.com/show_bug.cgi?id=834693 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, Am Dienstag, 13. August 2013 schrieb Felix Miata:
First line in the saved tail is: ifup[900]: Aug 13 16:55:27 gx260 network[403]: if-up.d/21-cifs: line 57: /bin/mountpoint: No such file or directory
Avahi isn't anything I ever use knowingly. Is /bin/mountpoint something from the failed schrodinger package? /usr/bin/mountpoint does exist.
On 12.3, /bin/mountpoint exists (package sysvinit-tools) On Factory, it moved to /usr/bin/mountpoint (package util-linux) So it looks like nobody told the maintainer of /etc/sysconfig/network/if-up.d/21-cifs that the "mountpoint" binary was moved. -> Please check which package this file belongs to, and open a bugreport ;-) For testing, you can fix the path in this script yourself to see if it has something to do with your slow boot times. Regards, Christian Boltz -- Aber das ist dann ungefähr so filigran wie mit 'nem Rambock die Haustür aufzumachen, nur weil man den Schlüssel tief im Rucksack verbuddelt hat. [Peer Heinlein in postfixbuch-users] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 14 Aug 2013 00:21, Christian Boltz
So it looks like nobody told the maintainer of /etc/sysconfig/network/if-up.d/21-cifs that the "mountpoint" binary was moved. -> Please check which package this file belongs to, and open a bugreport ;-)
FYI: in OSS 12.3 the "owner" of that file was the package "samba-client". -Yamaban. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Aug 14, 2013 at 12:44:53AM +0200, Yamaban wrote:
On Wed, 14 Aug 2013 00:21, Christian Boltz
wrote: [snip] So it looks like nobody told the maintainer of /etc/sysconfig/network/if-up.d/21-cifs that the "mountpoint" binary was moved. -> Please check which package this file belongs to, and open a bugreport ;-)
FYI: in OSS 12.3 the "owner" of that file was the package "samba-client".
openSUSE 12.2 was the last release which included the symbolic link /etc/sysconfig/network/if-{down,up}.d/21-cifs pointing to /etc/sysconfig/network//scripts/cifs Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
participants (6)
-
Andrey Borzenkov
-
Christian Boltz
-
Felix Miata
-
Lars Müller
-
Stefan Seyfried
-
Yamaban