RDKBACCL-904 : UDHCPC Zombie Process Persists even after WAN Manager …#281
Open
RDKBACCL-904 : UDHCPC Zombie Process Persists even after WAN Manager …#281
Conversation
…Restart Reason for change : UDHCPC Zombie Process Persists even after WAN Manager Restart Test Procedure: Build and flash the image , check the zombies Risks: None
cpokuru
reviewed
Mar 3, 2026
Contributor
cpokuru
left a comment
cpokuru
left a comment
There was a problem hiding this comment.
can you please test this with dhcp manager changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
RDKBACCL-904 : UDHCPC Zombie Process Persists even after WAN Manager Restart
Reason for change : UDHCPC Zombie Process Persists even after WAN Manager Restart
Test Procedure: Build and flash the image , check the zombies
Risks: None
Results
root@Filogic-GW:
# systemctl stop RdkWanManager.service#root@Filogic-GW:
root@Filogic-GW:
## systemctl status RdkWanManager.serviceroot@Filogic-GW:
○ RdkWanManager.service - Rdk Wan Manager service
Loaded: loaded (/lib/systemd/system/RdkWanManager.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Fri 2025-10-03 11:53:40 UTC; 2s ago
Process: 41719 ExecStartPre=/bin/sh /lib/rdk/run_rm_key.sh (code=exited, status=0/SUCCESS)
Process: 41754 ExecStartPre=/bin/touch /tmp/OS_WANMANAGER_ENABLED (code=exited, status=0/SUCCESS)
Process: 41762 ExecStartPre=/bin/sh -c (/usr/ccsp/utopiaInitCheck.sh) (code=exited, status=0/SUCCESS)
Process: 41771 ExecStart=/usr/rdk/wanmanager/wanmanager -subsys $Subsys (code=exited, status=0/SUCCESS)
Process: 953125 ExecStop=/bin/sh -c echo "
date: Stopping/Restarting RdkWanManager" >> ${PROCESS_RESTART_LOG} (code=exited, status=0/SUCCESS)Main PID: 41798 (code=killed, signal=TERM)
2025 Oct 03 11:53:39 Filogic-GW wanmanager[953055]: sh: rdisc6: command not found
2025 Oct 03 11:53:39 Filogic-GW wanmanager[953076]: Conf file /etc/debug.ini open success
2025 Oct 03 11:53:39 Filogic-GW wanmanager[953076]: rdk_logger_init /etc/debug.ini Already Stack Level Logging processed... not processing again.
2025 Oct 03 11:53:39 Filogic-GW wanmanager[953082]: sh: rdisc6: command not found
2025 Oct 03 11:53:39 Filogic-GW wanmanager[953103]: Conf file /etc/debug.ini open success
2025 Oct 03 11:53:39 Filogic-GW wanmanager[953103]: rdk_logger_init /etc/debug.ini Already Stack Level Logging processed... not processing again.
2025 Oct 03 11:53:40 Filogic-GW wanmanager[953112]: sh: rdisc6: command not found
2025 Oct 03 11:53:40 Filogic-GW systemd[1]: Stopping Rdk Wan Manager service...
2025 Oct 03 11:53:40 Filogic-GW systemd[1]: RdkWanManager.service: Deactivated successfully.
2025 Oct 03 11:53:40 Filogic-GW systemd[1]: Stopped Rdk Wan Manager service.
root@Filogic-GW:
# systemctl start RdkWanManager.service#root@Filogic-GW:
root@Filogic-GW:
##root@Filogic-GW:
root@Filogic-GW:
## ps | grep -rn " Z"| grep -v "grep"root@Filogic-GW:
root@Filogic-GW:~#