New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zombie process #57
Comments
Does this patch to the dhcpcd plugin for NetworkManager help at all? If not, do any prior versions of dhcpcd work? |
I'll try your patch and let you know. thx in advance The distribution (slackware) provides 9.4.0 but it doesn't have your last patch :
and after suspend/resume we have no ipv4 & no nameserver (ipv4) in /etc/resolv.conf |
x100 thx !!
after resume :
|
Nice! Can you test that dhcpcd-9.4.0 works with the NetworkManager patch please? |
Already done And the result is :
The fact is that I made all my tests with your latest dev release (9.99.0) and everything works as expected |
So to be clear, as things stand now, with the above NetworkManager patch, dhcpcd-9.4.0 doesn't list IPv4 nameservers but the development branch does after a suspend resume? If so, can you test the dhcpcd-9 branch please as that will be released as dhcpcd-9.4.1 "soon". |
Yes, it may seem confusing In fact : First we have an issue with IPv4 nameservers (not present in resolv.conf), so I cloned your current dev tree of dhcpcd (9.99.0) After that, everything worked fine except (after logout/login) and zombie process So, if we don't care about zombie process, for now, the latest stable release of NetworkManager (1.32.10) is fine. (not a big deal) |
OK, so the only difference between dhcpcd-9 branch and master is process management. If you can test the dhcpcd-9 branch (which currently builds as version 9.4.0 still) it will hopefully work for you. Can you test this please? |
I'll do |
doesn't work...
|
Hmmmmmmm. And yet it works with the master branch of dhcpcd? I really don't understand why. |
yes, indeed ...
|
And after the suspend/resume, it works well too. |
Here is the /var/log/messages for both :
dhcpcd-9
this is missing : |
Can you add --debug to the NetworkManager process and restest please? logs will be much more verbose. |
After resume :
|
Can you repeat but with dhcpcd-master please? |
After resume (master branch) :
|
FYI, I hard coded this :
in my /etc/rc.d/rc.networkmanager Let me know if you need more tests. |
Strange behaviour with your NetworkManager patch & dhcpcd 9.4.0 (stable release) After a suspend/resume (or NM restart), it's like previous dhcpcd processes are stil there
same with dhcpcd-9 all dhcpcd processes seem to be killed on NM restart |
In case, here is our dhcpcd.conf |
I added the "debug" option in dhcpcd.conf, just in case For what I see, this message in syslog (dhcpcd-9) does not appear with dhcpcd-master messages_9_suspend_resume.txt |
Hi, A member reported this on the forum :
Maybe, it can be usefull |
Hi, I thought I'd try and chime in (I'm the forum member that marav is citing above :-) ). I have the same issue, tried to bisect today, but from 9.3.0 to 9.4.0. I downgraded NetworkManager to version 1.28, since the later version in Slackware-current requires dhcpcd to have the --configure option. However, in terms of dhcpcd behavIor, I didn't notice much difference during bisection. I've found one decisive commit: [7726055] dhcpcd: Don't create launcher process if keeping in foreground With this commit, I get more and more dhcpcd processes after each resume, when using the dhcpcd-9 branch. If I revert it, I get a whole new set of dhcpcd processes after each resume, i.e., everything gets cleaned up nicely. However, I don't get an ip4 nameserver in resolv.conf, nor do I get an ip4 default route. I noticed also that a whole list of "dhcp4 (wlan0): option" messages is missing from the NetworkManager output in /var/log/messages. I have very limited coding skills, I couldn't take it further than that. Like marav says, the dhcpcd master branch works. |
Hi,
After that, he said : Sounds good |
Without that commit though, NetworkManager waitpid(2) will fail which makes the patch I posted above fail with a basic start/stop of the interface through NetworkManager. This is because it will think the launcher process controls dhcpcd which it doesn't. |
Hi Roy, I'm too unfamiliar with all the technicalities here to properly understand what you're saying... However, indeed without your patch it seems NetworkManager is missing a lot of information (at least, /var/log/messages is missing loads of NM dhcp4 info lines), and IP4 default gateway and nameservers don't get set. It seems I only get an IP4-address and nothing more. (IP6 working without issue with slaac.) However, with your patch the number of dhcpcd processes begins to pile up every time I resume. That was the issue I hoped to resolve by bisecting. (And it did, but not without the above detrimental side effects.) My hope is that this knowledge would give you a better clue of what's going on in the dhcpcd-9 branch :-) In a related vein, do you have any concrete plans already for doing a release from the master branch? |
Anyway, |
I plan to release dhcpcd-9.4.1 soonish and dhcpcd-10 will follow later. |
Thanks for the update Roy. That's a very good news I couldn't help a lot on this, but let me know if you need some kind of end-user test |
After a long time since the last returns, no problem with dhcpcd-9.4.1 Thx again for all Roy! |
Version :
dhcpcd 9.99.0
NetworkManager : 1.32.10
Each time I logout/login or during the suspend/resume process
The original parent PID of dhcpcd becomes a zombie process
before suspend
after resume
Another one, after 2 logout/login:
The strace log during a suspend/resume :
dhcpcd :
https://pastebin.com/LJ9AkJxG
NetworkManager:
https://pastebin.com/Xe2H80Tr
The text was updated successfully, but these errors were encountered: