RDKB-63899 : Zebra restart marker observed in selfheal#296
RDKB-63899 : Zebra restart marker observed in selfheal#296aj970-crypto wants to merge 4 commits into
Conversation
There was a problem hiding this comment.
Pull request overview
Adds additional logging around routed/zebra startup and LAN/WAN event handling to help diagnose “zebra restart marker observed in selfheal” scenarios (RDKB-63899).
Changes:
- Add debug logs in
service_routed(C) for function entry, bridge mode, zebra start attempt, and LAN/WAN readiness. - Add event-trigger logs in init scripts for
wan-status/lan-statusrouted triggers. - Add additional LAN handler logs around ipv4 status handling, lan-status updates, and uptime markers.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| source/service_routed/service_routed.c | Adds log statements around routed init and zebra start/verification flow. |
| source/scripts/init/service.d/service_routed.sh | Logs when WAN/LAN “started” triggers routed start. |
| source/scripts/init/service.d/lan_handler.sh | Adds more detailed LAN up / lan-status / uptime logging for troubleshooting. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Signed-off-by: aj970 <akshaya_j@comcast.com>
aj970-crypto
force-pushed
the
feature/RDKB-63899
branch
from
72e915a to
ff3d690
Compare
| if [ -e "/usr/bin/print_uptime" ]; then | ||
| /usr/bin/print_uptime "Laninit_complete" | ||
| echo_t "LAN HANDLER : Laninit_complete uptime: $(cut -d. -f1 /proc/uptime)" | ||
| echo_t "LAN HANDLER : Checking lan-status after lan init complete, lan-status = $(sysevent get lan-status)" |
There was a problem hiding this comment.
lan init complete will be after lan-status started , remove extra sysevent get
There was a problem hiding this comment.
I added this log because I observed two Laninit_complete uptime entries in the logs. In the boottime.log, the first occurrence was considered even though LAN was not started at that point, while only during the second occurrence the LAN actually gets started. This check was added to confirm the lan-status during both instances.
| fi | ||
|
|
||
| elif [ x"ready" != x`sysevent get start-misc` ] && ( [ "$MANUFACTURE" = "Technicolor" ] || [ "$MANUFACTURE" = "Sercomm" ] ) ; then | ||
| echo_t "LAN HANDLER : box is from Technicolor or Sercomm, setting lan-status to started" |
There was a problem hiding this comment.
I added this comment to verify whether execution is reaching this point. This helps identify where the flow is breaking in cases where the LAN is not getting started.
aj970-crypto
force-pushed
the
feature/RDKB-63899
branch
from
2ee93c6 to
ad348e7
Compare
RDKB-63899 : Zebra restart marker observed in selfheal
Reason for change: Adding logs for tracking the issue in future if reproduced
Test Procedure: None
Risks: Low
Priority: P1