Discussion:
[Grml] My DHCP client isn't started automatically anymore
Hermann
2009-10-10 09:09:36 UTC
Permalink
Hi,
since a safe-upgrade on 08.10.09, dhclient3 does not start automatically
anymore.
I use a router )Fritzbox), which is connected via USB to my machine. The
hardware gets detected properly, and I have activated DHCP on the
Fritzbox.
The internal IP has not changed.
Reconfiguring the network via grml-config results in turning on the
client, but specifying the startup of dhclient at boot, fails.
Although I answer this question with "yes", the client doesn't start
with the boot procedure. The config script exits with code 1 shown at the
prompt, but there are no error messages on the screen.
The only thing that works is to include the networking script into the
startup procedure by:
update-rc.d networking defaults
This was not necessary before.
The client's binary has the date of 05.10.09, although the problems came
up yesterday.
I include the contents of my /etc/network/interfaces here:

auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp

Any hints?
Hermann
Hermann
2009-10-11 10:16:48 UTC
Permalink
Post by Hermann
Hi,
since a safe-upgrade on 08.10.09, dhclient3 does not start automatically
anymore.
I use a router )Fritzbox), which is connected via USB to my machine. The
hardware gets detected properly, and I have activated DHCP on the
Fritzbox.
The internal IP has not changed.
Reconfiguring the network via grml-config results in turning on the
client, but specifying the startup of dhclient at boot, fails.
Although I answer this question with "yes", the client doesn't start
with the boot procedure. The config script exits with code 1 shown at the
prompt, but there are no error messages on the screen.
The only thing that works is to include the networking script into the
update-rc.d networking defaults
This was not necessary before.
The client's binary has the date of 05.10.09, although the problems came
up yesterday.
auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp
Any hints?
I deactivated the networking script again and activated the bootlogd
program.
Here are the related lines from /var/log/boot:

Sun Oct 11 11:38:53 2009: Setting up networking....
Sun Oct 11 11:38:53 2009: Cleaning up temporary files....
Sun Oct 11 11:38:54 2009: Setting up resolvconf...done.
Sun Oct 11 11:38:56 2009: Not starting as we're not running in a vm.
Sun Oct 11 11:38:56 2009: Running 0dns-down to make sure resolv.conf is ok...done.
Sun Oct 11 11:38:56 2009: Cleaning up temporary files....

What does this mean? "not in a vm"?
If this should stand for "virtual machine", I don't understand this
entry at all. I've installed GRML as only OS on that machine.
Hermann
Michael Prokop
2009-10-11 10:23:32 UTC
Permalink
Post by Hermann
Post by Hermann
since a safe-upgrade on 08.10.09, dhclient3 does not start automatically
anymore.
[...]

You don't have sysv-rc + insserv installed, right?
Post by Hermann
I deactivated the networking script again and activated the bootlogd
program.
Sun Oct 11 11:38:53 2009: Setting up networking....
Sun Oct 11 11:38:53 2009: Cleaning up temporary files....
Sun Oct 11 11:38:54 2009: Setting up resolvconf...done.
Sun Oct 11 11:38:56 2009: Not starting as we're not running in a vm.
Sun Oct 11 11:38:56 2009: Running 0dns-down to make sure resolv.conf is ok...done.
Sun Oct 11 11:38:56 2009: Cleaning up temporary files....
What does this mean? "not in a vm"?
If this should stand for "virtual machine", I don't understand this
entry at all. I've installed GRML as only OS on that machine.
% grep ' vm\.' /etc/init.d/*
/etc/init.d/open-vm-tools: echo "Not starting as we're not running in a vm."

Not relevant/related.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.mur.at/pipermail/grml/attachments/20091011/17f6ff32/attachment.pgp
Hermann
2009-10-11 10:53:09 UTC
Permalink
Post by Michael Prokop
Post by Hermann
since a safe-upgrade on 08.10.09, dhclient3 does not start automatically
anymore.
[...]
You don't have sysv-rc + insserv installed, right?
No, none of them.
Why did it work before Friday?
What to do? Leave it as it is, e.g. using the networking script, or is
it better to install the mentioned programs?
Hermann
Michael Prokop
2009-10-12 12:13:29 UTC
Permalink
Post by Hermann
Post by Michael Prokop
Post by Hermann
since a safe-upgrade on 08.10.09, dhclient3 does not start automatically
anymore.
[...]
You don't have sysv-rc + insserv installed, right?
No, none of them.
Why did it work before Friday?
No idea what has changed on your box.
Does manually running 'ifup eth0' work?
Post by Hermann
What to do? Leave it as it is, e.g. using the networking script, or is
it better to install the mentioned programs?
No, do NOT install sysv-rc + insserv.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.mur.at/pipermail/grml/attachments/20091012/7c2877dd/attachment.pgp
Michael Prokop
2009-10-12 12:13:29 UTC
Permalink
Post by Hermann
Post by Michael Prokop
Post by Hermann
since a safe-upgrade on 08.10.09, dhclient3 does not start automatically
anymore.
[...]
You don't have sysv-rc + insserv installed, right?
No, none of them.
Why did it work before Friday?
No idea what has changed on your box.
Does manually running 'ifup eth0' work?
Post by Hermann
What to do? Leave it as it is, e.g. using the networking script, or is
it better to install the mentioned programs?
No, do NOT install sysv-rc + insserv.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://ml.grml.org/pipermail/grml/attachments/20091012/7c2877dd/attachment-0002.pgp>
Michael Prokop
2009-10-12 12:13:29 UTC
Permalink
Post by Hermann
Post by Michael Prokop
Post by Hermann
since a safe-upgrade on 08.10.09, dhclient3 does not start automatically
anymore.
[...]
You don't have sysv-rc + insserv installed, right?
No, none of them.
Why did it work before Friday?
No idea what has changed on your box.
Does manually running 'ifup eth0' work?
Post by Hermann
What to do? Leave it as it is, e.g. using the networking script, or is
it better to install the mentioned programs?
No, do NOT install sysv-rc + insserv.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://ml.grml.org/pipermail/grml/attachments/20091012/7c2877dd/attachment-0003.pgp>
Hermann
2009-10-11 10:53:09 UTC
Permalink
Post by Michael Prokop
Post by Hermann
since a safe-upgrade on 08.10.09, dhclient3 does not start automatically
anymore.
[...]
You don't have sysv-rc + insserv installed, right?
No, none of them.
Why did it work before Friday?
What to do? Leave it as it is, e.g. using the networking script, or is
it better to install the mentioned programs?
Hermann
Hermann
2009-10-11 10:53:09 UTC
Permalink
Post by Michael Prokop
Post by Hermann
since a safe-upgrade on 08.10.09, dhclient3 does not start automatically
anymore.
[...]
You don't have sysv-rc + insserv installed, right?
No, none of them.
Why did it work before Friday?
What to do? Leave it as it is, e.g. using the networking script, or is
it better to install the mentioned programs?
Hermann
Michael Prokop
2009-10-11 10:23:32 UTC
Permalink
Post by Hermann
Post by Hermann
since a safe-upgrade on 08.10.09, dhclient3 does not start automatically
anymore.
[...]

You don't have sysv-rc + insserv installed, right?
Post by Hermann
I deactivated the networking script again and activated the bootlogd
program.
Sun Oct 11 11:38:53 2009: Setting up networking....
Sun Oct 11 11:38:53 2009: Cleaning up temporary files....
Sun Oct 11 11:38:54 2009: Setting up resolvconf...done.
Sun Oct 11 11:38:56 2009: Not starting as we're not running in a vm.
Sun Oct 11 11:38:56 2009: Running 0dns-down to make sure resolv.conf is ok...done.
Sun Oct 11 11:38:56 2009: Cleaning up temporary files....
What does this mean? "not in a vm"?
If this should stand for "virtual machine", I don't understand this
entry at all. I've installed GRML as only OS on that machine.
% grep ' vm\.' /etc/init.d/*
/etc/init.d/open-vm-tools: echo "Not starting as we're not running in a vm."

Not relevant/related.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://ml.grml.org/pipermail/grml/attachments/20091011/17f6ff32/attachment-0002.pgp>
Michael Prokop
2009-10-11 10:23:32 UTC
Permalink
Post by Hermann
Post by Hermann
since a safe-upgrade on 08.10.09, dhclient3 does not start automatically
anymore.
[...]

You don't have sysv-rc + insserv installed, right?
Post by Hermann
I deactivated the networking script again and activated the bootlogd
program.
Sun Oct 11 11:38:53 2009: Setting up networking....
Sun Oct 11 11:38:53 2009: Cleaning up temporary files....
Sun Oct 11 11:38:54 2009: Setting up resolvconf...done.
Sun Oct 11 11:38:56 2009: Not starting as we're not running in a vm.
Sun Oct 11 11:38:56 2009: Running 0dns-down to make sure resolv.conf is ok...done.
Sun Oct 11 11:38:56 2009: Cleaning up temporary files....
What does this mean? "not in a vm"?
If this should stand for "virtual machine", I don't understand this
entry at all. I've installed GRML as only OS on that machine.
% grep ' vm\.' /etc/init.d/*
/etc/init.d/open-vm-tools: echo "Not starting as we're not running in a vm."

Not relevant/related.

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://ml.grml.org/pipermail/grml/attachments/20091011/17f6ff32/attachment-0003.pgp>
Hermann
2009-10-10 09:09:36 UTC
Permalink
Hi,
since a safe-upgrade on 08.10.09, dhclient3 does not start automatically
anymore.
I use a router )Fritzbox), which is connected via USB to my machine. The
hardware gets detected properly, and I have activated DHCP on the
Fritzbox.
The internal IP has not changed.
Reconfiguring the network via grml-config results in turning on the
client, but specifying the startup of dhclient at boot, fails.
Although I answer this question with "yes", the client doesn't start
with the boot procedure. The config script exits with code 1 shown at the
prompt, but there are no error messages on the screen.
The only thing that works is to include the networking script into the
startup procedure by:
update-rc.d networking defaults
This was not necessary before.
The client's binary has the date of 05.10.09, although the problems came
up yesterday.
I include the contents of my /etc/network/interfaces here:

auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp

Any hints?
Hermann
Hermann
2009-10-11 10:16:48 UTC
Permalink
Post by Hermann
Hi,
since a safe-upgrade on 08.10.09, dhclient3 does not start automatically
anymore.
I use a router )Fritzbox), which is connected via USB to my machine. The
hardware gets detected properly, and I have activated DHCP on the
Fritzbox.
The internal IP has not changed.
Reconfiguring the network via grml-config results in turning on the
client, but specifying the startup of dhclient at boot, fails.
Although I answer this question with "yes", the client doesn't start
with the boot procedure. The config script exits with code 1 shown at the
prompt, but there are no error messages on the screen.
The only thing that works is to include the networking script into the
update-rc.d networking defaults
This was not necessary before.
The client's binary has the date of 05.10.09, although the problems came
up yesterday.
auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp
Any hints?
I deactivated the networking script again and activated the bootlogd
program.
Here are the related lines from /var/log/boot:

Sun Oct 11 11:38:53 2009: Setting up networking....
Sun Oct 11 11:38:53 2009: Cleaning up temporary files....
Sun Oct 11 11:38:54 2009: Setting up resolvconf...done.
Sun Oct 11 11:38:56 2009: Not starting as we're not running in a vm.
Sun Oct 11 11:38:56 2009: Running 0dns-down to make sure resolv.conf is ok...done.
Sun Oct 11 11:38:56 2009: Cleaning up temporary files....

What does this mean? "not in a vm"?
If this should stand for "virtual machine", I don't understand this
entry at all. I've installed GRML as only OS on that machine.
Hermann
Hermann
2009-10-10 09:09:36 UTC
Permalink
Hi,
since a safe-upgrade on 08.10.09, dhclient3 does not start automatically
anymore.
I use a router )Fritzbox), which is connected via USB to my machine. The
hardware gets detected properly, and I have activated DHCP on the
Fritzbox.
The internal IP has not changed.
Reconfiguring the network via grml-config results in turning on the
client, but specifying the startup of dhclient at boot, fails.
Although I answer this question with "yes", the client doesn't start
with the boot procedure. The config script exits with code 1 shown at the
prompt, but there are no error messages on the screen.
The only thing that works is to include the networking script into the
startup procedure by:
update-rc.d networking defaults
This was not necessary before.
The client's binary has the date of 05.10.09, although the problems came
up yesterday.
I include the contents of my /etc/network/interfaces here:

auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp

Any hints?
Hermann
Hermann
2009-10-11 10:16:48 UTC
Permalink
Post by Hermann
Hi,
since a safe-upgrade on 08.10.09, dhclient3 does not start automatically
anymore.
I use a router )Fritzbox), which is connected via USB to my machine. The
hardware gets detected properly, and I have activated DHCP on the
Fritzbox.
The internal IP has not changed.
Reconfiguring the network via grml-config results in turning on the
client, but specifying the startup of dhclient at boot, fails.
Although I answer this question with "yes", the client doesn't start
with the boot procedure. The config script exits with code 1 shown at the
prompt, but there are no error messages on the screen.
The only thing that works is to include the networking script into the
update-rc.d networking defaults
This was not necessary before.
The client's binary has the date of 05.10.09, although the problems came
up yesterday.
auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp
Any hints?
I deactivated the networking script again and activated the bootlogd
program.
Here are the related lines from /var/log/boot:

Sun Oct 11 11:38:53 2009: Setting up networking....
Sun Oct 11 11:38:53 2009: Cleaning up temporary files....
Sun Oct 11 11:38:54 2009: Setting up resolvconf...done.
Sun Oct 11 11:38:56 2009: Not starting as we're not running in a vm.
Sun Oct 11 11:38:56 2009: Running 0dns-down to make sure resolv.conf is ok...done.
Sun Oct 11 11:38:56 2009: Cleaning up temporary files....

What does this mean? "not in a vm"?
If this should stand for "virtual machine", I don't understand this
entry at all. I've installed GRML as only OS on that machine.
Hermann
Loading...