Re: blank resolv.conf
Roy Marples
Tue Nov 10 11:08:14 2020
On 10/11/2020 11:00, Jan Pohanka wrote:
10. 11. 2020 v 11:50 odesílatel Roy Marples <roy@xxxxxxxxxxxx> napsal:
On 10/11/2020 10:45, Jan Pohanka wrote:
Maybe I have found the reason!
dhcpcd is running twice on my device
$ ps | grep dh
188 root dhcpcd eth0
215 root /sbin/dhcpcd -f /etc/dhcpcd.conf
Is it a problem? One of the instances is started by an init.d script
provided by a buildroot package. The second one probably by ifup
scripts, but I do not see it now. I have to search...
Yes, that would be the reason.
The first instance is specific to eth0 and the second is for all interfaces.
If they started the other way around this would not be a problem, but as eth0
started first it is.
You'll need to fix that without my help :/
And yes, if you had resolvconf installed this issue would be mitagted, but would
only hide other issues as the various dhcpcd instances would be competing to
process RENEW messages.
Maybe I should see if I can add code to stop dhcpcd running in master mode if it
can detect any single interface running already.
Roy
That is probably some incompatibility among older buildroot, busybox
and dhcpcd. We have updated just the dhcpcd package some time ago and
I did not notice the second instance.
Thank you for your help. I will share the result if I find it....
Well, dhcpcd has behaved this way since dhcpcd-5 so I unless you upgraded from a
really old version - and this is unlikely as you have started dhcpcd in master
mode which imples >= 5 - then the issue must be elsewhere. ie not related to
dhcpcd upgrade.
Roy
Archive administrator: postmaster@marples.name