Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #168157 > unrolled thread

Delay at boot - network

Back to article view | Back to linux.debian.user

Contents

  Delay at boot - network Hans <hans.ullrich@loop.de> - 2016-05-22 22:10 +0200
    Re: Delay at boot - network <tomas@tuxteam.de> - 2016-05-22 22:30 +0200
      Re: Delay at boot - network Hans <hans.ullrich@loop.de> - 2016-05-22 22:40 +0200
        Re: Delay at boot - network <tomas@tuxteam.de> - 2016-05-23 09:10 +0200
          Re: Delay at boot - network Hans <hans.ullrich@loop.de> - 2016-05-23 09:20 +0200
            Re: Delay at boot - network <tomas@tuxteam.de> - 2016-05-23 09:30 +0200
              Re: Delay at boot - network Hans <hans.ullrich@loop.de> - 2016-05-23 10:00 +0200
                Re: Delay at boot - network Jeremy Nicoll <jn.ml.dbn.25@letterboxes.org> - 2016-05-25 11:50 +0200
                  Re: Delay at boot - network Hans <hans.ullrich@loop.de> - 2016-05-25 12:30 +0200
                    Re: Delay at boot - network <tomas@tuxteam.de> - 2016-05-25 16:20 +0200
                    Re: Delay at boot - network Jude DaShiell <jdashiel@panix.com> - 2016-05-25 16:20 +0200
                    Re: Delay at boot - network Brian <ad44@cityscape.co.uk> - 2016-05-25 18:40 +0200
                      Re: Delay at boot - network Hans <hans.ullrich@loop.de> - 2016-05-25 20:40 +0200
                        Re: Delay at boot - network Hans <hans.ullrich@loop.de> - 2016-05-25 21:30 +0200
                      [Solved] Re: Delay at boot - network Hans <hans.ullrich@loop.de> - 2016-06-09 13:30 +0200

#168157 — Delay at boot - network

Hello list,

I do not want to mourn, just searching for an info. 

Can someone tell me, what has changed in the kernel (I believe, it is since 
kernel 3.4, but do not know exactly), that the boot progress hangs about 1 - 
1,5 minutes, when the network is started?

I am using /etc/network/interfaces witrh a static IP, so it should start fast 
and not wait for something. In earlier kernels, there was no wait, just 
straight boot.

Why the delay now? Would be happy, if someone could enlighten me, and maybe 
give me a clue, if I can something configure to improve it.

And please, I do not want to mourn! Just want to know.

Ah, and I do NOT use network-manager (not installed), but wicd instead.

Thanks for reading this.

Best

Hans

[toc] | [next] | [standalone]

#168158

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, May 22, 2016 at 10:04:53PM +0200, Hans wrote:
> Hello list,
> 
> I do not want to mourn, just searching for an info. 
> 
> Can someone tell me, what has changed in the kernel (I believe, it is since 
> kernel 3.4, but do not know exactly), that the boot progress hangs about 1 - 
> 1,5 minutes, when the network is started?

Sorry I can't be more specific, but 1.5 minutes looks a bit like a name
resolution timeout.

regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAldCFcYACgkQBcgs9XrR2kYofACfWASHjAMqshBgQmGDqWjO+VWb
klwAn32+MBej2KjTjHctpMe55OCKulF1
=U6LZ
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#168160

Hi Tomas,
> Sorry I can't be more specific, but 1.5 minutes looks a bit like a name
> resolution timeout.
> 
Hmm, the DNS is also preconfigured. I see a counter at boot, which counts up to 
1min 30 sec, then continues booting. If necessary, I can create a video within 
virtualbox, but this should be an exception, shouldn`t it?

I believe, the delay might be caused by a mega check (maybe testing a lot of 
networkcards or firmwares, whatever), but that is just an idea.
> regards
> -- tomás

Best

Hans

[toc] | [prev] | [next] | [standalone]

#168175

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, May 22, 2016 at 10:33:47PM +0200, Hans wrote:
> Hi Tomas,
> > Sorry I can't be more specific, but 1.5 minutes looks a bit like a name
> > resolution timeout.
> > 
> Hmm, the DNS is also preconfigured. I see a counter at boot, which counts up to 
> 1min 30 sec, then continues booting.

That sounds strange. Can you describe that?

>                                    If necessary, I can create a video within 
> virtualbox, but this should be an exception, shouldn`t it?

No, sorry. I only "do" text.

> I believe, the delay might be caused by a mega check (maybe testing a lot of 
> networkcards or firmwares, whatever), but that is just an idea.
> > regards

Hm. Doesn't ring a bell with me.

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAldCqzwACgkQBcgs9XrR2kZHMACfanGNaUlT/mg9ElmY7j8pdPeG
6ncAn29Q5s1/29ntz3jbkMdryI3UP8Qf
=7BAN
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#168177

Hi Tomas,
> > Hmm, the DNS is also preconfigured. I see a counter at boot, which counts
> > up to 1min 30 sec, then continues booting.
> 
> That sounds strange. Can you describe that?

Well, you see all the messages at boot. Then, when it comes to the network, 
the scrolling of the messages stop and there is a line like this (Note the 
text is not original!!!:

network startimg anbd so on snd so on (30sec/5min)

You see the counter of the "30sec" count up to 1min30, then the boot process 
is continuing.

Does this help? Maybe someone else can describe better, someone with better 
background know-hnow and maybe English natively speaking.

> -- tomás

Hans

[toc] | [prev] | [next] | [standalone]

#168178

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, May 23, 2016 at 09:13:52AM +0200, Hans wrote:
> Hi Tomas,
> > > Hmm, the DNS is also preconfigured. I see a counter at boot, which counts
> > > up to 1min 30 sec, then continues booting.
> > 
> > That sounds strange. Can you describe that?
> 
> Well, you see all the messages at boot. Then, when it comes to the network, 
> the scrolling of the messages stop and there is a line like this (Note the 
> text is not original!!!:
> 
> network startimg anbd so on snd so on (30sec/5min)
> 
> You see the counter of the "30sec" count up to 1min30, then the boot process 
> is continuing.
> 
> Does this help? Maybe someone else can describe better, someone with better 
> background know-hnow and maybe English natively speaking.

I see. Sorry I'm a bit pressed now. Look through those two bug reports
and let us know wheter anything sounds familiar:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798314
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754218

Are you running SysV init or systemd?

regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAldCsN4ACgkQBcgs9XrR2kblGgCePX/So9IA6B8uPuaYLTL0IHFD
+c8Amwal6IG0XXi1wVsiuLQDsCvLFpy6
=rjyC
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#168179

> I see. Sorry I'm a bit pressed now. Look through those two bug reports
> and let us know wheter anything sounds familiar:
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798314
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754218

Yes, both bugreports describe, what I also discovered. However, my environment 
does not use NFS (like one uses), and I have not to wait at shutdown, as the 
other one describes. But the behaviour at boot is the same, as in these 
bugreports is described. 
> 
> Are you running SysV init or systemd?
> 
My environment:
I am running debian/testing with systemd. The partitions /home, /usr and /var 
are seperated and they are encrypted with luks. All partitions mount at boot 
well. I am running this profile now for many years. 

The behaviour did NOT appear with the change from SysV to systemd, but a long 
long time later. 

It definetely appeared with a kernel upgrade. Sadly I cannot tell, which kernel 
version did this change. As I recognized this as a feature not a bug, I did 
not file a bugreport at that time, sorry for that.

Maybe you should know, that it also appears on all hardware (I have an EEEPC, 
some Desktop PC's and an Acer Aspire 7520 notebook). 

Please feel free to ask for more information. 

> regards
> -- tomás

Best
Hans

[toc] | [prev] | [next] | [standalone]

#168242

On Mon, 23 May 2016, at 08:49, Hans wrote:
> > I see. Sorry I'm a bit pressed now. Look through those two bug reports
> > and let us know wheter anything sounds familiar:
> > 
> >   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798314
> >   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754218
> 
> Yes, both bugreports describe, what I also discovered. However, my
> environment 
> does not use NFS (like one uses), and I have not to wait at shutdown, as
> the 
> other one describes. But the behaviour at boot is the same, as in these 
> bugreports is described. 

When you get this delay, what's in the scrolling messages in the last
few lines 
before the delay itself?

Are they (on your various machines) always the same sorts of lines?


-- 
Jeremy Nicoll - my opinions are my own.

[toc] | [prev] | [next] | [standalone]

#168244

> When you get this delay, what's in the scrolling messages in the last
> few lines
> before the delay itself?
The last message is:
started konsole fonts and....

Then:
(1 of 1) A start job is running for LSB: Raise network interfaces. (1min 30s / 
5min 30s)
> 
> Are they (on your various machines) always the same sorts of lines?
Yes, different times are shown, but in the same manner.

I googled a bit, and it might be related to systemd. Other people got the same 
problem, with different delay times (up to 15 minutes). That happened mostly 
after an upgrade.

Note: I am using /etc/network/interfaces and network-manager is not installed.
As others mentioned, I commented "allow hotplug" line out, with no success.

This behaviour seem to be a well known problem, buit it looks like there is no 
general solution. 

I have erverything static! Here is my complete /etc/network/interfaces:


--------------------------------------------snip -----------------------------
auto lo wlan0 eth0 usb0

iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

iface eth0 inet static
        address 192.168.2.12
        netmask 255.255.255.0
        broadcast 192.168.2.255
        gateway 192.168.2.1


#### Accesspoint #########

# iface eth1 inet static
#       wireless_mode Master
#       wireless_essid any
#       wireless_keymode open
#       wireless_channel 3
#       address 192.168.5.1
#       netmask 255.255.255.0
#       broadcast 192.168.5.255
#       gateway 192.168.5.1


#### at home ######

iface wlan0 inet static
        address 192.168.1.102
        netmask 255.255.255.0
        broadcast 192.168.1.255
        gateway 192.168.1.1
        wpa-driver wext
        wpa-scan-ap 1
        wpa-key-mgt WPA-PSK
        wpa-ssid anonymized
        wpa-psk anonymized
        dns-nameservers 208.67.222.222 208.67.220.220

# iface wlan0 inet static
#       address 192.168.1.102
#       netmask 255.255.255.0
#       broadcast 192.168.1.255
#       gateway 192.168.1.2
#       wireless_mode managed
#       wireless_essid stargazer
#       wireless_key 3A1B3C3EF9
#       wireless_keymode open
#       dns-nameservers 208.67.222.222 208.67.220.220

#### Experimental

# iface wlan1 inet static
#       address 10.5.5.1
#       netmask 255.255.255.0
#       network 10.5.0.0
#       broadcast 10.5.5.255
#       gateway 192.168.1.1

# iface wlan1 inet dhcp
#       wireless_mode ad-hoc
#       wireless_keymode open
#       wireless_key off
#       wireless_ap 10.2.46.1


#### on the road ######

# iface wlan0 inet dhcp
#       wireless_mode managed
#       wireless_essid any
#       wireless_key off
#       wireless_ap auto
#       wireless_keymode open

# iface wlan0 inet static
#       address 192.168.1.30
#       netmask 255.255.255.0
#       broadcast 192.168.1.255
#       gateway 192.168.1.1
#       wireless_mode managed
#       wireless_essid any
#       wireless_key off
#       wireless_ap auto
#       wireless_keymode open


#### mit WPA  ######

# iface wlan0 inet dhcp
#     pre-up /sbin/wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf

# Work network configuration

# iface eth0 inet static
#       address 192.168.1.102
#       netmask 255.255.255.0
#       broadcast 192.168.1.255
#       gateway 192.168.1.1

mapping hotplug
script grep
map usb0

iface usb0 inet static
    address 192.168.129.1
    network 192.168.129.0
    netmask 255.255.255.0
    broadcast 192.168.129.255

------------------------------ snap ------------------------------

Most entries are commented out. And as you see, everything is static, NO dhcp.
This configuration is now unchanged for many years. 

Looks for me like a timeout problem somewhere. 

Hope this helps.

Best

Hans 

[toc] | [prev] | [next] | [standalone]

#168246

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, May 25, 2016 at 12:20:52PM +0200, Hans wrote:
> > When you get this delay, what's in the scrolling messages in the last
> > few lines
> > before the delay itself?
> The last message is:
> started konsole fonts and....
> 
> Then:
> (1 of 1) A start job is running for LSB: Raise network interfaces. (1min 30s / 
> 5min 30s)
> > 
> > Are they (on your various machines) always the same sorts of lines?
> Yes, different times are shown, but in the same manner.
> 
> I googled a bit, and it might be related to systemd. Other people got the same 
> problem, with different delay times (up to 15 minutes). That happened mostly 
> after an upgrade.
> 
> Note: I am using /etc/network/interfaces and network-manager is not installed.
> As others mentioned, I commented "allow hotplug" line out, with no success.
> 
> This behaviour seem to be a well known problem, buit it looks like there is no 
> general solution. 
> 
> I have erverything static! Here is my complete /etc/network/interfaces:

Sorry I can't help you much with systemd. My knowledge level there is
insignificant. But there are folks around here who should be better at
this.

There's a tool around systemd which helps you debug what's happening
when and how long it takes. That might offer you some clues.

The other thing I'd try is selectively enabling the interfaces in
/etc/nework/interfaces and seeing how that impacts behaviour (e.g.
all disabled, only eth0, only usb0, and so on).

Sorry for being so unspecific.

Regards
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAldFspYACgkQBcgs9XrR2kZJ5wCfaAS3GQv89cTFTwmgNjvxh999
MG8An23eIhx+WyaPxB+jH0sjLm2otxNg
=JPuB
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#168247

On Wed, 25 May 2016, Hans wrote:

> Date: Wed, 25 May 2016 06:20:52
> From: Hans <hans.ullrich@loop.de>
> To: debian-user@lists.debian.org
> Cc: Jeremy Nicoll <jn.ml.dbn.25@letterboxes.org>
> Subject: Re: Delay at boot - network
> Resent-Date: Wed, 25 May 2016 10:21:30 +0000 (UTC)
> Resent-From: debian-user@lists.debian.org
> 
>> When you get this delay, what's in the scrolling messages in the last
>> few lines
>> before the delay itself?
> The last message is:
> started konsole fonts and....
>
> Then:
> (1 of 1) A start job is running for LSB: Raise network interfaces. (1min 30s /
> 5min 30s)
>>
>> Are they (on your various machines) always the same sorts of lines?
> Yes, different times are shown, but in the same manner.
>
> I googled a bit, and it might be related to systemd. Other people got the same
> problem, with different delay times (up to 15 minutes). That happened mostly
> after an upgrade.
>
> Note: I am using /etc/network/interfaces and network-manager is not installed.
> As others mentioned, I commented "allow hotplug" line out, with no success.
>
> This behaviour seem to be a well known problem, buit it looks like there is no
> general solution.
>
> I have erverything static! Here is my complete /etc/network/interfaces:
>
>
> --------------------------------------------snip -----------------------------
> auto lo wlan0 eth0 usb0
>
> iface lo inet loopback
> address 127.0.0.1
> netmask 255.0.0.0
>
> iface eth0 inet static
>        address 192.168.2.12
>        netmask 255.255.255.0
>        broadcast 192.168.2.255
>        gateway 192.168.2.1
>
>
> #### Accesspoint #########
>
> # iface eth1 inet static
> #       wireless_mode Master
> #       wireless_essid any
> #       wireless_keymode open
> #       wireless_channel 3
> #       address 192.168.5.1
> #       netmask 255.255.255.0
> #       broadcast 192.168.5.255
> #       gateway 192.168.5.1
>
>
> #### at home ######
>
> iface wlan0 inet static
>        address 192.168.1.102
>        netmask 255.255.255.0
>        broadcast 192.168.1.255
>        gateway 192.168.1.1
>        wpa-driver wext
>        wpa-scan-ap 1
>        wpa-key-mgt WPA-PSK
>        wpa-ssid anonymized
>        wpa-psk anonymized
>        dns-nameservers 208.67.222.222 208.67.220.220
>
> # iface wlan0 inet static
> #       address 192.168.1.102
> #       netmask 255.255.255.0
> #       broadcast 192.168.1.255
> #       gateway 192.168.1.2
> #       wireless_mode managed
> #       wireless_essid stargazer
> #       wireless_key 3A1B3C3EF9
> #       wireless_keymode open
> #       dns-nameservers 208.67.222.222 208.67.220.220
>
> #### Experimental
>
> # iface wlan1 inet static
> #       address 10.5.5.1
> #       netmask 255.255.255.0
> #       network 10.5.0.0
> #       broadcast 10.5.5.255
> #       gateway 192.168.1.1
>
> # iface wlan1 inet dhcp
> #       wireless_mode ad-hoc
> #       wireless_keymode open
> #       wireless_key off
> #       wireless_ap 10.2.46.1
>
>
> #### on the road ######
>
> # iface wlan0 inet dhcp
> #       wireless_mode managed
> #       wireless_essid any
> #       wireless_key off
> #       wireless_ap auto
> #       wireless_keymode open
>
> # iface wlan0 inet static
> #       address 192.168.1.30
> #       netmask 255.255.255.0
> #       broadcast 192.168.1.255
> #       gateway 192.168.1.1
> #       wireless_mode managed
> #       wireless_essid any
> #       wireless_key off
> #       wireless_ap auto
> #       wireless_keymode open
>
>
> #### mit WPA  ######
>
> # iface wlan0 inet dhcp
> #     pre-up /sbin/wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
>
> # Work network configuration
>
> # iface eth0 inet static
> #       address 192.168.1.102
> #       netmask 255.255.255.0
> #       broadcast 192.168.1.255
> #       gateway 192.168.1.1
>
> mapping hotplug
> script grep
> map usb0
>
> iface usb0 inet static
>    address 192.168.129.1
>    network 192.168.129.0
>    netmask 255.255.255.0
>    broadcast 192.168.129.255
>
> ------------------------------ snap ------------------------------
>
> Most entries are commented out. And as you see, everything is static, NO dhcp.
> This configuration is now unchanged for many years.
>
> Looks for me like a timeout problem somewhere.
>
> Hope this helps.
>
> Best
>
> Hans
>
I have this error too and I'm trying to bring up networking from command 
line interface as well.  One package I forgot to install which may be 
causing my error is crda and I'll also have to configure that package for 
in my case the United States.  It may be a missing crda package is doing 
this unless debian installer installs and/or correctly configures crda 
for users using wifi connections automatically.  Hope this helps.

>

--

[toc] | [prev] | [next] | [standalone]

#168250

On Wed 25 May 2016 at 12:20:52 +0200, Hans wrote:

> > When you get this delay, what's in the scrolling messages in the last
> > few lines
> > before the delay itself?
> The last message is:
> started konsole fonts and....

Not likely to be the problem.
 
> Then:
> (1 of 1) A start job is running for LSB: Raise network interfaces. (1min 30s / 
> 5min 30s)

Some script in /etc/init.d which uses the network could be cause.

> > Are they (on your various machines) always the same sorts of lines?
> Yes, different times are shown, but in the same manner.
> 
> I googled a bit, and it might be related to systemd. Other people got the same 
> problem, with different delay times (up to 15 minutes). That happened mostly 
> after an upgrade.

systemd is waiting for some script to complete. It doesn't just carry on
immediately in case something gets broken.

Boot with 'systemd.log_level=debug' and examine 'journalctl --alb' closely.

> Note: I am using /etc/network/interfaces and network-manager is not installed.
> As others mentioned, I commented "allow hotplug" line out, with no success.
> 
> This behaviour seem to be a well known problem, buit it looks like there is no 
> general solution. 
> 
> I have erverything static! Here is my complete /etc/network/interfaces:

[...snip...]

The idea to boot with only eth0 in the interfaces file is a good one.

[toc] | [prev] | [next] | [standalone]

#168251

Hi Brian,
> systemd is waiting for some script to complete. It doesn't just carry on
> immediately in case something gets broken.
> 
> Boot with 'systemd.log_level=debug' and examine 'journalctl --alb' closely.
I did, as you told, and strangely, at the moment this behaviour disappered. 
However, it may be related to a new behaviour: After booting the system up, 
wlan is not available. I have to do:
rmmod ath5k
modprobe ath5k
then start wicd and connection works.

This is part of the output of the journal, maybe it helps.

......
......

Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/21 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=28 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 kernel: ieee80211 phy0: Selected rate control 
algorithm 'minstrel_ht'
Mai 25 20:10:02 protheus2 kernel: ath5k: phy0: Atheros AR2425 chip found (MAC: 
0xe2, PHY: 0x70)
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/83 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=30 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/83 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=29 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/45 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=31 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/45 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=30 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/92 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=32 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/92 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=31 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/55 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=33 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/55 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=32 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=JobNew cookie=34 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=JobNew cookie=33 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/16 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=35 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/16 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=34 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/57 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=36 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/57 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=35 
reply_cookie=0 error=n/a
.....
.....
.....
Mai 25 20:10:02 protheus2 systemd[1]: dev-sda5.device: Merged into installed 
job dev-sda5.device/start as 93
Mai 25 20:10:02 protheus2 systemd[1]: laptop-mode.service: Enqueued job 
laptop-mode.service/start as 183
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=method_return 
sender=n/a destination=n/a object=n/a interface=n/a member=n/a cookie=46 
reply_cookie=1 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/93 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=47 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/93 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=47 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/4 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=48 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/4 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=48 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/84 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=49 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/84 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=49 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/30 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=50 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/30 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=50 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/45 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=51 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/45 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=51 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/307 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=52 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/307 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=52 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/92 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=53 
reply_cookie=0 error=n/a
Mai 25 20:10:02 protheus2 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/job/92 interface=org.
.....
.....
....
Mai 25 20:10:25 protheus2 systemd-logind[1549]: Sent message type=method_call 
sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus 
interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=11 
reply_cookie=0 error=n/a
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> rfkill1: found WiFi 
radio killswitch (at 
/sys/devices/pci0000:00/0000:00:0d.0/0000:05:00.0/ieee80211/phy0/rfkill1) 
(driver ath5k)
Mai 25 20:10:25 protheus2 systemd-logind[1549]: Got message type=method_return 
sender=org.freedesktop.DBus destination=:1.0 object=n/a interface=n/a 
member=n/a cookie=10 reply_cookie=11 error=n/a
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> rfkill0: found WiFi 
radio killswitch (at /sys/devices/platform/acer-wmi/rfkill/rfkill0) (platform 
driver acer-wmi)
Mai 25 20:10:25 protheus2 systemd-logind[1549]: Sent message type=method_call 
sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus 
interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=12 
reply_cookie=0 error=n/a
Mai 25 20:10:25 protheus2 systemd-logind[1549]: Got message type=method_return 
sender=org.freedesktop.DBus destination=:1.0 object=n/a interface=n/a 
member=n/a cookie=11 reply_cookie=12 error=n/a
Mai 25 20:10:25 protheus2 systemd-logind[1549]: Inhibitor NetworkManager 
(NetworkManager muss Netzwerke abschalten) pid=1502 uid=0 mode=delay started.
Mai 25 20:10:25 protheus2 systemd-logind[1549]: Sent message type=signal 
sender=n/a destination=n/a object=/org/freedesktop/login1 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=13 
reply_cookie=0 error=n/a
Mai 25 20:10:25 protheus2 systemd-logind[1549]: Sent message 
type=method_return sender=n/a destination=:1.6 object=n/a interface=n/a 
member=n/a cookie=14 reply_cookie=14 error=n/a
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> WiFi hardware radio set 
enabled
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> WWAN hardware radio set 
enabled
Mai 25 20:10:25 protheus2 systemd-rfkill[1178]: All events read and idle, 
exiting.
Mai 25 20:10:25 protheus2 systemd-logind[1549]: Got message type=signal 
sender=:1.1 destination=n/a 
object=/org/freedesktop/systemd1/unit/systemd_2drfkill_2eservice 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=126 
reply_cookie=0 error=n/a
.....
.....
.....
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> Loaded device plugin: 
/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> Loaded device plugin: 
/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> Loaded device plugin: 
/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> Loaded device plugin: 
/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so
Mai 25 20:10:25 protheus2 dbus[1585]: [system] Activating service 
name='org.freedesktop.ModemManager' (using servicehelper)
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> WiFi enabled by radio 
killswitch; enabled by state file
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> WWAN enabled by radio 
killswitch; enabled by state file
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> WiMAX enabled by radio 
killswitch; enabled by state file
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> Networking is enabled 
by state file
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> (lo): link connected
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> (lo): carrier is ON
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> (lo): new Generic 
device (driver: 'unknown' ifindex: 1)
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> (lo): exported as 
/org/freedesktop/NetworkManager/Devices/0
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> (eth0): carrier is OFF
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> (eth0): new Ethernet 
device (driver: 'forcedeth' ifindex: 2)
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> (eth0): exported as 
/org/freedesktop/NetworkManager/Devices/1
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> (wlan0): using nl80211 
for WiFi device control
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> (wlan0): driver 
supports Access Point (AP) mode
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> (wlan0): new 802.11 
WiFi device (driver: 'ath5k' ifindex: 3)
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> (wlan0): exported as 
/org/freedesktop/NetworkManager/Devices/2
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> (wlan0): device state 
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Mai 25 20:10:25 protheus2 NetworkManager[1502]: <info> (wlan0): preparing 
device
Mai 25 20:10:25 protheus2 systemd[1]: Started Network Manager.
Mai 25 20:10:25 protheus2 dnsmasq[2398]: lese /var/run/dnsmasq/resolv.conf
Mai 25 20:10:26 protheus2 wpa_supplicant[2177]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=00:1a:4f:21:8e:32 reason=0
Mai 25 20:10:26 protheus2 NetworkManager[1502]: <info> (wlan0): reset MAC 
address to 00:1D:D9:4C:88:10
.....
....
.....
............................................................

And lots of more errors, the whole file is 1,4MB big. I am wondering, what 
Network-Manager has to do with it, it is not installed!
At last. I see these, what appears a dozen times:


Mai 25 20:10:29 protheus2 NetworkManager[1502]: <error> [1464199829.950194] 
[supplicant-manager/nm-supplicant-interface.c:856] interface_add_cb(): 
(wlan0): error adding interface: wpa_supplicant couldn't grab this interface.
Mai 25 20:10:29 protheus2 NetworkManager[1502]: <info> (wlan0): supplicant 
interface state: starting -> down
Mai 25 20:10:29 protheus2 wpa_supplicant[2671]: ctrl_iface exists and seems to 
be in use - cannot override it
Mai 25 20:10:29 protheus2 wpa_supplicant[2671]: Delete 
'/run/wpa_supplicant/wlan0' manually if it is not used anymore
Mai 25 20:10:29 protheus2 wpa_supplicant[2671]: Failed to initialize control 
interface '/run/wpa_supplicant'.
                                                You may have another 
wpa_supplicant process already running or the file was
                                                left by an unclean termination 
of wpa_supplicant in which case you will need
                                                to manually remove this file 
before starting wpa_supplicant again.
Mai 25 20:10:30 protheus2 NetworkManager[1502]: <error> [1464199830.056549] 
[supplicant-manager/nm-supplicant-interface.c:856] interface_add_cb(): 
(wlan0): error adding interface: wpa_supplicant couldn't grab this interface.
Mai 25 20:10:30 protheus2 NetworkManager[1502]: <info> (wlan0): supplicant 
interface state: starting -> down
Mai 25 20:10:30 protheus2 wpa_supplicant[2671]: ctrl_iface exists and seems to 
be in use - cannot override it
Mai 25 20:10:30 protheus2 wpa_supplicant[2671]: Delete 
'/run/wpa_supplicant/wlan0' manually if it is not used anymore
Mai 25 20:10:30 protheus2 wpa_supplicant[2671]: Failed to initialize control 
interface '/run/wpa_supplicant'.
                                                You may have another 
wpa_supplicant process already running or the file was
                                                left by an unclean termination 
of wpa_supplicant in which case you will need
                                                to manually remove this file 
before starting wpa_supplicant again.
.....
....

I have to onspect this, too. Please do nothing at the moment, I have to check 
several things, and then I will send message again.

Thanks for the hints, I will come back.

Best

Hans

[toc] | [prev] | [next] | [standalone]

#168252

> 
> I have to onspect this, too. Please do nothing at the moment, I have to
> check several things, and then I will send message again.
> 
> Thanks for the hints, I will come back.
> 
> Best
> 
> Hans

I am answering myself. I found a lot of files belonging to package "network-
manager", which I had installed some weeks ago.

It is not explainable, why so much is left from the package, after 
deinstallation. Strangely I had to install the package, then deinstall the 
package, to get rid of the crap. Although I am always using the "purge" 
directive with aptitude, there were about 7 files left, even in /etc, /usr/lib 
and /usr/bin. Weired....

Looks like either the package has changed during the last weeks or something 
in the database of dpkg was not ok.

Hans

[toc] | [prev] | [next] | [standalone]

#168736 — [Solved] Re: Delay at boot - network

Hi Brian,
as promised, I want to report my last experiences. The problem with the delay 
on both of my notebooks is solved.

Due to your help, I could figured out, that the process network-manager caused 
the delay. This happened, because the purge of the package was not completed, 
so that binary files and some config files stayed on the system. New installation 
and then deinstallation with purge did the trick.

A similar problem was with my EEEPC. In this case, the package ntpdate 
searched for an IP 192.168.178.1 (which is my fritzbox), and did not find it. 
Of course it cannot find it, because I am behind another router, with the IP 
range 192.168.1.*. However, in none of the configuration files of ntpdate the IP 
192.168.178.1 appeared! As ntpdate is not necessary and is fully successed 
through the package ntp, I deinstalled and purged ntpdate and everything was 
working again.

Thank you for pointing me to the systemctrl commands, so I could see, learn 
and solve the problem.

Best

Hans

 

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web