Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 526934 - install-amd64-minimal-20141023.iso - start-stop-daemon: /sbin/dhcpcd is already running / ERROR: cannot start netmount as dhcpcd would not start
Summary: install-amd64-minimal-20141023.iso - start-stop-daemon: /sbin/dhcpcd is alrea...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Release Media
Classification: Unclassified
Component: InstallCD (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Release Team
URL:
Whiteboard:
Keywords:
Depends on: 608058
Blocks:
  Show dependency tree
 
Reported: 2014-10-26 15:15 UTC by peper17
Modified: 2018-01-10 14:18 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description peper17 2014-10-26 15:15:54 UTC
DHCPCD not started on install-amd64-minimal-20141023.iso

During boot

....
Starting DHCP Client Daemon...
start-stop-daemon: /sbin/dhcpcd is already running
Failed to start dhcpcd
ERROR: dhcpcd failed to start
ERROR: cannot start netmount as dhcpcd would not start
....
Comment 1 Ben Kohler gentoo-dev 2014-11-17 22:34:06 UTC
dhcpcd is actually already started by another service earlier, so this warning is mostly harmless.  But it's annoying nonetheless and should be fixed.  The root cause of this is a buggy script in catalyst.
Comment 2 abandoned account 2015-01-01 20:48:15 UTC
I think there must be some underlying issue here.

Even though dhcpcd is already running, I cannot stop it with:
/etc/init.d/dhcpcd stop
says:
* WARNING: dhcpcd is already stopped

and pgrep dhcpcd and cat /var/run/dhcpcd.pid  point to the same PID

The only time I can stop it(with that command) is when passing nodhcp boot option.

I tried reporting this here: https://bugs.gentoo.org/show_bug.cgi?id=18556#c2
but I don't think it will fall on deaf ears because the only people getting notified are those two people which are retired.

Bottom line is that because dhcpcd is already running, it will prevent net-setup from creating its /etc/resolv.conf and thus DNS will not work when following the instructions from here: https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Networking#Default:_Using_net-setup

A pkill dhcpcd prior to starting net-setup is the workaround so far.
Comment 3 abandoned account 2015-01-01 20:58:37 UTC
looks like /etc/init.d/autoconfig is the one starting dhcpcd manually, shouldn't it be using the /etc/init.d/dhcpcd script instead?!

look at line 530 in /etc/init.d/autoconfig
Comment 4 Ben Kohler gentoo-dev 2015-01-02 15:25:46 UTC
There are a few issues coming together to cause this.  Catalyst is supposed to be removing netmount from default runlevel (so nothing has "need net" in default) but bug 517042 is preventing that from happening.  

openrc doesn't know that autoconfig is already bringing up networking via dhcpcd, so it tries to find a net provider, and picks the direct dhcpcd service.  IMHO autoconfig should either stop calling dhcpcd, or it should get "provide net" added so rc dependencies are sane.
Comment 5 Ben Kohler gentoo-dev 2018-01-10 14:18:26 UTC
This is fixed in the last several installcd releases