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

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

no network after jessie -> stretch

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

Contents

  no network after jessie -> stretch "D. R. Evans" <doc.evans@gmail.com> - 2017-06-21 18:00 +0200
    Re: no network after jessie -> stretch Gian Carlo <ingats@tin.it> - 2017-06-21 21:30 +0200
      Re: no network after jessie -> stretch Felix Miata <mrmazda@earthlink.net> - 2017-06-21 21:40 +0200
        Re: no network after jessie -> stretch "D. R. Evans" <doc.evans@gmail.com> - 2017-06-22 01:50 +0200
          Re: no network after jessie -> stretch Fungi4All <fungilife@protonmail.com> - 2017-06-22 03:00 +0200
      Re: no network after jessie -> stretch "D. R. Evans" <doc.evans@gmail.com> - 2017-06-21 22:30 +0200
        Re: no network after jessie -> stretch Felix Miata <mrmazda@earthlink.net> - 2017-06-21 22:40 +0200
          Re: no network after jessie -> stretch Jude DaShiell <jdashiel@panix.com> - 2017-06-22 04:50 +0200
    Re: no network after jessie -> stretch Michael Biebl <biebl@debian.org> - 2017-06-21 21:50 +0200
    quasi-SOLVED: Re: no network after jessie -> stretch "D. R. Evans" <doc.evans@gmail.com> - 2017-06-23 00:40 +0200
      Re: quasi-SOLVED: Re: no network after jessie -> stretch Fungi4All <fungilife@protonmail.com> - 2017-06-23 05:50 +0200
        Re: quasi-SOLVED: Re: no network after jessie -> stretch "D. R. Evans" <doc.evans@gmail.com> - 2017-06-23 16:30 +0200
          Re: quasi-SOLVED: Re: no network after jessie -> stretch David Wright <deblis@lionunicorn.co.uk> - 2017-06-23 16:50 +0200
            Re: quasi-SOLVED: Re: no network after jessie -> stretch "D. R. Evans" <doc.evans@gmail.com> - 2017-06-23 17:40 +0200
              Re: quasi-SOLVED: Re: no network after jessie -> stretch David Wright <deblis@lionunicorn.co.uk> - 2017-06-25 02:50 +0200
                Re: quasi-SOLVED: Re: no network after jessie -> stretch "D. R. Evans" <doc.evans@gmail.com> - 2017-06-26 19:10 +0200
                  Re: quasi-SOLVED: Re: no network after jessie -> stretch Joe <joe@jretrading.com> - 2017-06-26 19:40 +0200
          Re: quasi-SOLVED: Re: no network after jessie -> stretch Henrique de Moraes Holschuh <hmh@debian.org> - 2017-06-23 17:00 +0200
          Re: quasi-SOLVED: Re: no network after jessie -> stretch Fungi4All <fungilife@protonmail.com> - 2017-06-23 23:40 +0200
            Re: quasi-SOLVED: Re: no network after jessie -> stretch SDA <marathon.durandal@gmail.com> - 2017-06-24 05:00 +0200

#182477 — no network after jessie -> stretch

[Multipart message — attachments visible in raw view] — view raw

I just completed an upgrade to stretch on an i386 machine.

There were no obvious showstopping errors during the install. I saw a few
"unable to delete directory; directory not empty" errors fly by, but nothing
that seemed dangerous, and the installation didn't complain about anything.

But when I tried the reboot following the upgrade, I lost all network
connectivity. The boot screen said:
  Failed to Start Network Manager Wait Online

It also suggested issuing the command:
 systemctl status NetworkManager-wait-online.service
but that merely says unhelpfully :
  "unit entered failed state"
and
  "Failed with result 'exit-code'"

(Sorry for any typing errors... since there's no network connectivity, I have
to retype anything :-( )

Any help in diagnosing, or, even better, fixing the problem will be gratefully
received.

It probably goes without saying, but I'll say it anyway: prior to this
upgrade, the network connectivity was fine (and has been through several
earlier versions of debian).

  Doc

-- 
Web:  http://enginehousebooks.com/drevans

[toc] | [next] | [standalone]

#182483

Il 21/06/2017 18:00, D. R. Evans ha scritto:
> I just completed an upgrade to stretch on an i386 machine.
> 
> There were no obvious showstopping errors during the install. I saw a few
> "unable to delete directory; directory not empty" errors fly by, but nothing
> that seemed dangerous, and the installation didn't complain about anything.
> 
> But when I tried the reboot following the upgrade, I lost all network
> connectivity. The boot screen said:
>   Failed to Start Network Manager Wait Online
It may be related to this:

https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

What is the output of "/sbin/ifconfig"?
Do you see "eth0" or something like "enXXXXXX"?

gc

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

#182484

Gian Carlo composed on 2017-06-21 21:05 (UTC+0200):
.
> What is the output of "/sbin/ifconfig"?
> Do you see "eth0" or something like "enXXXXXX"?
.
ip is not included in a default Stretch install. Try 'ip a'
-- 
"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/

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

#182495

[Multipart message — attachments visible in raw view] — view raw

Felix Miata wrote on 06/21/2017 01:33 PM:
> Gian Carlo composed on 2017-06-21 21:05 (UTC+0200):
> .
>> What is the output of "/sbin/ifconfig"?
>> Do you see "eth0" or something like "enXXXXXX"?
> .
> ip is not included in a default Stretch install. Try 'ip a'
> 

That command seems to give more or less the same output is ifconfig, but in a
different format and with rather less detail. Anyway, like the ifconfig
command, it lists eth0, eth1 and lo.

  Doc

-- 
Web:  http://enginehousebooks.com/drevans

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

#182496

[Multipart message — attachments visible in raw view] — view raw

My fix in such occassions has been to download in a medium commonly used (stick, common partition with a system that
has net access) the .deb packages for connman and cmst and install them to the isolated system using dpkg, then reboot.
Most likely whatever previous networking set-up there is connman will override and fix for you. Especially helpful with wifi.
I will probably get some heat from the anti-gui brigade but if it is a quick fix and you get online then you can figure it all out
and correct whatever .conf there was a glitch at.

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

#182488

[Multipart message — attachments visible in raw view] — view raw

Gian Carlo wrote on 06/21/2017 01:05 PM:

> What is the output of "/sbin/ifconfig"?

It's too long to type it all. If you want some part of it, please let me know
and I'll try to type it without too many mistakes.

> Do you see "eth0" or something like "enXXXXXX"?

eth0, eth1 and lo are the three named interfaces it returns.

(Historically, eth0 is the one that has been actually been used, and it is
supposed to get an IP address via DHCP from my main server. Naturally, since
the interface never came into service after the upgrade, my server didn't hand
out a lease when the upgraded machine booted, since it never saw the DHCP
request.)

  Doc

-- 
Web:  http://enginehousebooks.com/drevans

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

#182489

D. R. Evans composed on 2017-06-21 14:20 (UTC-0600):
.
> eth0, eth1 and lo are the three named interfaces it returns.
.
> (Historically, eth0 is the one that has been actually been used, and it is
> supposed to get an IP address via DHCP from my main server... 
.
If eth0 is the name you wish used, it's probably sufficient to do #3 at the
bottom of:

<https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/>

I use net.ifnames=0 in all my Grub stanzas. I'm bad with names, yet eth0 is a
name I can and do remember.
-- 
"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/

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

#182498

I found that to be the case and fixed it by adding missing information 
to /etc/network/interfaces.  What was missing was the allow-hotplug 
line;
wpa-ssid,
wpa-psk
On Wed, 21 Jun 2017, Felix Miata wrote:

> Date: Wed, 21 Jun 2017 16:35:30
> From: Felix Miata <mrmazda@earthlink.net>
> To: debian-user@lists.debian.org
> Subject: Re: no network after jessie -> stretch
> Resent-Date: Wed, 21 Jun 2017 20:35:50 +0000 (UTC)
> Resent-From: debian-user@lists.debian.org
> 
> D. R. Evans composed on 2017-06-21 14:20 (UTC-0600):
> .
>> eth0, eth1 and lo are the three named interfaces it returns.
> .
>> (Historically, eth0 is the one that has been actually been used, and it is
>> supposed to get an IP address via DHCP from my main server...
> .
> If eth0 is the name you wish used, it's probably sufficient to do #3 at the
> bottom of:
>
> <https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/>
>
> I use net.ifnames=0 in all my Grub stanzas. I'm bad with names, yet eth0 is a
> name I can and do remember.
>

-- 

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

#182485

[Multipart message — attachments visible in raw view] — view raw

Am 21.06.2017 um 17:53 schrieb D. R. Evans:
> I just completed an upgrade to stretch on an i386 machine.
> 
> There were no obvious showstopping errors during the install. I saw a few
> "unable to delete directory; directory not empty" errors fly by, but nothing
> that seemed dangerous, and the installation didn't complain about anything.
> 
> But when I tried the reboot following the upgrade, I lost all network
> connectivity. The boot screen said:
>   Failed to Start Network Manager Wait Online

Please share more details about your network configuration.
Do you use ifupdown to manage your interface, NetworkManager, something
else?

The error message above indicates, that you have network-manager
installed and since stretch NetworkManager-wait-online.service is
enabled by default (it wasn't in jessie).

Now, if you don't actually manage your interfaces with NetworkManager,
NetworkManager-wait-online.service might run into a timeout (of 30s).

The output nmcli might be helpful.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

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

#182525 — quasi-SOLVED: Re: no network after jessie -> stretch

[Multipart message — attachments visible in raw view] — view raw

D. R. Evans wrote on 06/21/2017 09:53 AM:

> But when I tried the reboot following the upgrade, I lost all network
> connectivity. The boot screen said:
>   Failed to Start Network Manager Wait Online
> 
> It also suggested issuing the command:
>  systemctl status NetworkManager-wait-online.service
> but that merely says unhelpfully :
>   "unit entered failed state"
> and
>   "Failed with result 'exit-code'"
> 

At least the network is starting now. To get it working, I ran first ran KDE
instead of my normal i3 desktop, and told the KDE systems settings tool
explicitly that I wanted eth0 to be started and get a DHCP address at startup.
Now eth0 seems to be working properly following reboots (although of course I
really have no idea why it wasn't working before, since I'd made no changes to
a system that has worked perfectly for years).

But the problem with the "Start Network Manager Online" service remains. It
adds about 30 useless seconds to the boot time while the system waits for it
to time out, so it sure would be nice to know how to get rid of the delay somehow.

  Doc

PS In answer to someone's question: I first set up networking on the machine
years ago, when I first installed debian, and at that time I just told the
configuration script during installation that I wanted eth0 to get an address
from DHCP. I've never had to touch it since then until the problem after this
latest upgrade.

-- 
Web:  http://enginehousebooks.com/drevans

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

#182527 — Re: quasi-SOLVED: Re: no network after jessie -> stretch

[Multipart message — attachments visible in raw view] — view raw

> From: doc.evans@gmail.com
> To: debian-user@lists.debian.org
>
> D. R. Evans wrote on 06/21/2017 09:53 AM:
> It adds about 30 useless seconds to the boot time while the system waits for it
> to time out, so it sure would be nice to know how to get rid of the delay somehow.

30 useless seconds! What has humanity been reduced to? How many times a day
do you reboot?

The zapatistas have talked about time and what it would take to take it back from
the masters, to be in control of your life and your time. How many have spent 30sec
to understand?

Evolution is a very slow process, hey doc?

> Doc

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

#182540 — Re: quasi-SOLVED: Re: no network after jessie -> stretch

[Multipart message — attachments visible in raw view] — view raw

Fungi4All wrote on 06/22/2017 09:48 PM:
>> From: doc.evans@gmail.com
>> To: debian-user@lists.debian.org
>>
>> D. R. Evans wrote on 06/21/2017 09:53 AM:
>> It adds about 30 useless seconds to the boot time while the system waits for it
>> to time out, so it sure would be nice to know how to get rid of the delay somehow.
> 
> 30 useless seconds! What has humanity been reduced to? How many times a day
> do you reboot?

The machine in question is usually used for realtime control of external
hardware. If a reboot is necessary, then those 30 seconds are indeed 30 lost
seconds of ongoing operation. It does matter.

Anyway, my question is technical, not philosophical, which seems appropriate
for a technical reflector.

Can anyone provide suggestions as to how to remove this delay?

  Doc

-- 
Web:  http://enginehousebooks.com/drevans

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

#182543 — Re: quasi-SOLVED: Re: no network after jessie -> stretch

On Fri 23 Jun 2017 at 08:25:00 (-0600), D. R. Evans wrote:
> Fungi4All wrote on 06/22/2017 09:48 PM:
> >> From: doc.evans@gmail.com
> >> To: debian-user@lists.debian.org
> >>
> >> D. R. Evans wrote on 06/21/2017 09:53 AM:
> >> It adds about 30 useless seconds to the boot time while the system waits for it
> >> to time out, so it sure would be nice to know how to get rid of the delay somehow.
> > 
> > 30 useless seconds! What has humanity been reduced to? How many times a day
> > do you reboot?
> 
> The machine in question is usually used for realtime control of external
> hardware. If a reboot is necessary, then those 30 seconds are indeed 30 lost
> seconds of ongoing operation. It does matter.

I agree entirely. I also think it's ridiculous and embarrassing
that I often have to wait 90 more seconds to close down;
wheezy could manage this in 5 or, occasionally, up to 10 seconds.

> Anyway, my question is technical, not philosophical, which seems appropriate
> for a technical reflector.
> 
> Can anyone provide suggestions as to how to remove this delay?

Did you miss https://lists.debian.org/debian-user/2017/06/msg00858.html
which gave one possibility? It also asked for two things, neither of
which were forthcoming. I can't find any explicit statement as to
how you start your network, so any responses have been based on
guesswork.

Cheers,
David.

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

#182550 — Re: quasi-SOLVED: Re: no network after jessie -> stretch

[Multipart message — attachments visible in raw view] — view raw

David Wright wrote on 06/23/2017 08:42 AM:

>> Can anyone provide suggestions as to how to remove this delay?
> 
> Did you miss https://lists.debian.org/debian-user/2017/06/msg00858.html
> which gave one possibility? It also asked for two things, neither of
> which were forthcoming. I can't find any explicit statement as to
> how you start your network, so any responses have been based on
> guesswork.
> 

Sorry, I thought that my statement about just entering info during the first
installation would supply the requested information. Here is a bit more
detail, formatted as a response to
<d06d3b16-9c47-5e1e-b747-4859bc5bec33@debian.org>:

> Please share more details about your network configuration.

I'm not sure what details are needed. I input the information once, long ago,
telling debian to use DHCP on eth0. I have not touched anything
network-related since then. If you have a specific question in mind, please
let me know and I'll try to answer it.

> Do you use ifupdown to manage your interface, NetworkManager, something
> else?

I have no idea. I boot the system, and it works. I know that sounds snide and
like I'm being an idiot, but it's the truth: once I had input the information
when first installing debian, it all just worked and I never had to know
anything about what debian was doing under the hood. Whatever the default was
prior to stretch, I assume that that's what I was using.

(The version of debian on the system has always been plain debian stable,
whichever version was the official stable at the time.)

>
> The error message above indicates, that you have network-manager
> installed and since stretch NetworkManager-wait-online.service is
> enabled by default (it wasn't in jessie).
>
> Now, if you don't actually manage your interfaces with NetworkManager,
> NetworkManager-wait-online.service might run into a timeout (of 30s).
>
> The output nmcli might be helpful.
>

Now that eth0 is working properly, I can provide the output from nmcli without
having to type it all :-) :

----

n7dr@shack:~/projects/drlog$ nmcli
eth0: connected to Wired connection 1
        "Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter"
        ethernet (8139too), 00:13:D4:93:04:FB, hw, mtu 1500
        ip4 default
        inet4 192.168.0.50/24
        inet6 fe80::e6ec:1d58:4ed2:9964/64

eth1: disconnected
        "Winbond Electronics W89C940"
        1 connection available
        ethernet (ne2k-pci), 00:20:78:19:8E:AF, hw, mtu 1500

lo: unmanaged
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

DNS configuration:
        servers: 192.168.0.1
        interface: eth0

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(5) manual pages for complete usage details.
n7dr@shack:~/projects/drlog$

----

  Doc

-- 
Web:  http://enginehousebooks.com/drevans

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

#182617 — Re: quasi-SOLVED: Re: no network after jessie -> stretch

On Fri 23 Jun 2017 at 09:37:18 (-0600), D. R. Evans wrote:
> David Wright wrote on 06/23/2017 08:42 AM:
> 
> >> Can anyone provide suggestions as to how to remove this delay?
> > 
> > Did you miss https://lists.debian.org/debian-user/2017/06/msg00858.html
> > which gave one possibility? It also asked for two things, neither of
> > which were forthcoming. I can't find any explicit statement as to
> > how you start your network, so any responses have been based on
> > guesswork.
> > 
> 
> Sorry, I thought that my statement about just entering info during the first
> installation would supply the requested information. Here is a bit more
> detail, formatted as a response to
> <d06d3b16-9c47-5e1e-b747-4859bc5bec33@debian.org>:
> 
> > Please share more details about your network configuration.
> 
> I'm not sure what details are needed. I input the information once, long ago,
> telling debian to use DHCP on eth0. I have not touched anything
> network-related since then. If you have a specific question in mind, please
> let me know and I'll try to answer it.
> 
> > Do you use ifupdown to manage your interface, NetworkManager, something
> > else?
> 
> I have no idea. I boot the system, and it works. I know that sounds snide and
> like I'm being an idiot, but it's the truth: once I had input the information
> when first installing debian, it all just worked and I never had to know
> anything about what debian was doing under the hood. Whatever the default was
> prior to stretch, I assume that that's what I was using.
> 
> (The version of debian on the system has always been plain debian stable,
> whichever version was the official stable at the time.)

I'm not the person to help with NM, but in the absence of other
replies…

> > The error message above indicates, that you have network-manager
> > installed and since stretch NetworkManager-wait-online.service is
> > enabled by default (it wasn't in jessie).

this would suggest a cause. Do you need the network before your login
prompt appears or not? If not, it looks like systemd needs telling that.
I think this just came up in a contemporaneous thread here, but in a
disk-mounting context rather than networking.

> > Now, if you don't actually manage your interfaces with NetworkManager,
> > NetworkManager-wait-online.service might run into a timeout (of 30s).

You originally wrote "about 30 useless seconds". It is worth stating
whether that is a counted-down timeout period or just an estimate of
a period you have wait. (I'm assuming you've done nothing to increase
the flow of console messages when you boot.)

> >
> > The output nmcli might be helpful.
> >
> 
> Now that eth0 is working properly, I can provide the output from nmcli without
> having to type it all :-) :
> 
> ----
> 
> n7dr@shack:~/projects/drlog$ nmcli
> eth0: connected to Wired connection 1
>         "Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter"
>         ethernet (8139too), 00:13:D4:93:04:FB, hw, mtu 1500
>         ip4 default
>         inet4 192.168.0.50/24
>         inet6 fe80::e6ec:1d58:4ed2:9964/64
> 
> eth1: disconnected
>         "Winbond Electronics W89C940"
>         1 connection available
>         ethernet (ne2k-pci), 00:20:78:19:8E:AF, hw, mtu 1500

I have no idea whether the status of eth1 could have any bearing
because I don't know where one makes ones wishes known to NM,
not having used it.

> lo: unmanaged
>         loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
> 
> DNS configuration:
>         servers: 192.168.0.1
>         interface: eth0

Cheers,
David.

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

#182694 — Re: quasi-SOLVED: Re: no network after jessie -> stretch

[Multipart message — attachments visible in raw view] — view raw

David Wright wrote on 06/24/2017 06:42 PM:

> 
>>> The error message above indicates, that you have network-manager
>>> installed and since stretch NetworkManager-wait-online.service is
>>> enabled by default (it wasn't in jessie).
> 
> this would suggest a cause. Do you need the network before your login
> prompt appears or not? If not, it looks like systemd needs telling that.
> I think this just came up in a contemporaneous thread here, but in a
> disk-mounting context rather than networking.
> 

Well, some remote disk filesystems get mounted at boot time -- so that
obviously needs a functioning network -- but I have no idea whether that
happens before the login prompt appears. It is definitely true that by the
time I am logged in (which is very fast, since I use i3), the network is up
and running.

I'll go look at the disk-mounting thread and see if there's something useful
there.

>>> Now, if you don't actually manage your interfaces with NetworkManager,
>>> NetworkManager-wait-online.service might run into a timeout (of 30s).
> 
> You originally wrote "about 30 useless seconds". It is worth stating
> whether that is a counted-down timeout period or just an estimate of
> a period you have wait. (I'm assuming you've done nothing to increase
> the flow of console messages when you boot.)

This is a counted-up period. I forget precisely what appears on the screen,
but it's a counter that counts upwards; and, strangely, it doesn't suggest
that there's a 30-second timeout (it's of the form "<nnn>s / No timeout", or
something like that, where the <nnn> increments each second). But when it hits
30 seconds, it does time out and the rest of the boot sequence occurs.

> 
> I have no idea whether the status of eth1 could have any bearing
> because I don't know where one makes ones wishes known to NM,
> not having used it.

Ditto. (At least, "not having used it knowingly".)

Nothing is plugged into eth1, and I have never told the system to configure
that interface, so one would hope that it would be completely ignored. But I
have no idea if that's actually what happens. The error message from NM is
singularly unhelpful :-(

  Doc

-- 
Web:  http://enginehousebooks.com/drevans

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

#182699 — Re: quasi-SOLVED: Re: no network after jessie -> stretch

On Mon, 26 Jun 2017 11:02:10 -0600
"D. R. Evans" <doc.evans@gmail.com> wrote:

> David Wright wrote on 06/24/2017 06:42 PM:
> 
> > Do you need the network before your
> > login prompt appears or not? If not, it looks like systemd needs
> > telling that. I think this just came up in a contemporaneous thread
> > here, but in a disk-mounting context rather than networking.
> >   
> 
> Well, some remote disk filesystems get mounted at boot time -- so that
> obviously needs a functioning network -- but I have no idea whether
> that happens before the login prompt appears. It is definitely true
> that by the time I am logged in (which is very fast, since I use i3),
> the network is up and running.
> 
> I'll go look at the disk-mounting thread and see if there's something
> useful there.
> 
>

If you don't actually need the remote file systems for the boot process
itself, then systemd has an option to automount fstab entries when
first needed. This can cut down boot time. Include:
	noauto
and
	x-systemd.automount
among the options. I have my workstation's cifs mounts set up that way,
and there's no perceptible delay in opening one for the first time.
They stay mounted then until shutdown. It works for local drives as
well, but they're less of a problem.

-- 
Joe

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

#182545 — Re: quasi-SOLVED: Re: no network after jessie -> stretch

On Fri, 23 Jun 2017, D. R. Evans wrote:
> Can anyone provide suggestions as to how to remove this delay?

Yes.  The fastest way would be to ask your network administrator for a
static IP and DNS information, so that you can do static configuration.
This is faster than DHCP even when everything is working right.

Configure it directly on /etc/network/interfaces the right way, that
removes the wait on network manager:

auto eth0
iface eth0 inet static
        address <your IP>
        netmask <your netmask>
        gateway <your gateway>

"man interfaces"  will give you the details.

DNS depends:  we support several ways to autoconfigure it, and that ends
up getting in the way.  You'd need to ensure resolvconf and other such
packages are NOT present, and configure /etc/resolv.conf directly.

The above solution should result in the fastest boot, but it is
certainly not the *easiest*.

The easiest long-term would be to find out what the heck is wrong in
your system, because it is not supposed to waste 30s waiting for
anything in the first place.


PS: "auto eth0" in /etc/network/interface means "wait for this thing to
be online before you proceed", and plays well with networked
filesystems, etc.  There is an alternative: "allow-hotplug eth0", which
will react for the eth0 device showing up, and try to bring networking
when that happens.  THAT is known to sometimes cause issues when you
have any networked filesystems that get touched during boot.

-- 
  Henrique Holschuh

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

#182561 — Re: quasi-SOLVED: Re: no network after jessie -> stretch

[Multipart message — attachments visible in raw view] — view raw

> From: doc.evans@gmail.com
> To: debian-user@lists.debian.org <debian-user@lists.debian.org>
> Fungi4All wrote on 06/22/2017 09:48 PM:
>>> From: doc.evans@gmail.com
>>> To: debian-user@lists.debian.org
>>>
>>> D. R. Evans wrote on 06/21/2017 09:53 AM:
>>> It adds about 30 useless seconds to the boot time while the system waits for it
>>> to time out, so it sure would be nice to know how to get rid of the delay somehow.
>>
>> 30 useless seconds! What has humanity been reduced to? How many times a day
>> do you reboot?
> Anyway, my question is technical, not philosophical, which seems appropriate
> for a technical reflector.

You are the calling yourself a doctor, as far as I know that is a doctor of philosophy.
What would I know, I'm just a technician! But for life's sake I hope you are not in
the life sciences as you probably don't deserve your title.
In other words, the answer to your question can not come in 30sec, it may
take millenniums to answer.

> Doc

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

#182571 — Re: quasi-SOLVED: Re: no network after jessie -> stretch

On Fri, Jun 23, 2017 at 05:37:29PM -0400, Fungi4All wrote:
>      From: doc.evans@gmail.com
>      To: debian-user@lists.debian.org <debian-user@lists.debian.org>
>      Fungi4All wrote on 06/22/2017 09:48 PM:
>      >> From: doc.evans@gmail.com
>      >> To: debian-user@lists.debian.org
>      >>
>      >> D. R. Evans wrote on 06/21/2017 09:53 AM:
>      >> It adds about 30 useless seconds to the boot time while the system
>      waits for it
>      >> to time out, so it sure would be nice to know how to get rid of the
>      delay somehow.
>      >
>      > 30 useless seconds! What has humanity been reduced to? How many times
>      a day
>      > do you reboot?
>      Anyway, my question is technical, not philosophical, which seems
>      appropriate
>      for a technical reflector.
> 
>    You are the calling yourself a doctor, as far as I know that is a doctor
>    of philosophy.
>    What would I know, I'm just a technician!  But for life's sake I hope you
>    are not in
>    the life sciences as you probably don't deserve your title.
>    In other words, the answer to your question can not come in 30sec, it may
>    take millenniums to answer.

This is uncalled for Fungi4All: please refrain from such childish behaviour 
on this list. And must you write HTML emails for gawds sake?

[toc] | [prev] | [standalone]

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

csiph-web