Skip to content

RDKCOM-5604: RDKBDEV-3456, RDKBACCL-1777 Set systemd 'SyslogIdentifier' parameter#65

Open
mcbridematt wants to merge 2 commits into
rdkcentral:developfrom
mcbridematt:develop
Open

RDKCOM-5604: RDKBDEV-3456, RDKBACCL-1777 Set systemd 'SyslogIdentifier' parameter#65
mcbridematt wants to merge 2 commits into
rdkcentral:developfrom
mcbridematt:develop

Conversation

@mcbridematt

Copy link
Copy Markdown

This patch has been part of meta-rdk-bsp-arm for a while and I believe it would be beneficial to upstream it.

A previous changeset made all services invoked via the "/bin/sh -c '(...)'" pattern, which causes all syslog/journalctl entries to have the sh process name.

This can cause a lot of confusion when viewing the system log via journalctl:

sh[5613]: Fetching values to form parodus command line arguments
sh[5151]: result =
sh[5151]: result = rdkb-generic-broadband-image_rdkb-2025q1-kirkstone_20250606001224
sh[5613]: Framing command for parodus
sh[5613]: Starting parodus with the following arguments
sh[5613]: ModelName=RPI  SerialNumber=  Manufacturer=Traverse  HW_MAC=00:0a:fa:24:29:5d ...
sh[5808]: rdk_dyn_log_initg_dl_socket = 3 __progname = parodus
sh[5551]: Conf file /etc/debug.ini open success
sh[5551]: rdk_dyn_log_initg_dl_socket = 3 __progname = CcspTandDSsp
sh[5551]: rdk_logger_init /etc/debug.ini Already Stack Level Logging processed... not processing again.
sh[5551]: ****LOADING DM LIBRARY***************
sh[5573]: CosaEthInferface initialization done!
sh[5573]: CcspHalExtSw_getAssociatedDevice not implemented on generic arm platforms yet

In the above output there is a mix of CcspPandMSsp, Parodus and CcspEthAgent, which is very confusing.

Setting the SyslogIdentifier in each systemd unit file allows the correct ident to be applied to the log entries:

PsmSsp[1820]: rdk_dyn_log_initg_dl_socket = 3 __progname = PsmSsp
CcspEthAgent[3754]: CcspHalExtSw_getAssociatedDevice not implemented on generic arm platforms yet

A previous changeset made all services invoked
via the "/bin/sh -c '(...)'" pattern, which causes all
syslog/journalctl entries to have the "sh" process name.

This can cause a lot of confusion when viewing the system log via journalctl:

rdkb-arm sh[5613]: Fetching values to form parodus command line arguments
rdkb-arm sh[5151]: result =
rdkb-arm sh[5151]: result = rdkb-generic-broadband-image_rdkb-2025q1-kirkstone_20250606001224
rdkb-arm sh[5613]: Framing command for parodus
rdkb-arm sh[5613]: Starting parodus with the following arguments
rdkb-arm sh[5613]: ModelName=RPI  SerialNumber=  Manufacturer=Traverse  HW_MAC=00:0a:fa:24:29:5d ...
rdkb-arm sh[5808]: rdk_dyn_log_initg_dl_socket = 3 __progname = parodus
rdkb-arm sh[5551]: Conf file /etc/debug.ini open success
rdkb-arm sh[5551]: rdk_dyn_log_initg_dl_socket = 3 __progname = CcspTandDSsp
rdkb-arm sh[5551]: rdk_logger_init /etc/debug.ini Already Stack Level Logging processed... not processing again.
rdkb-arm sh[5551]: ****LOADING DM LIBRARY***************
rdkb-arm sh[5573]: CosaEthInferface initialization done!
rdkb-arm sh[5573]: CcspHalExtSw_getAssociatedDevice not implemented on generic arm platforms yet

In the above output there is a mix of CcspPandMSsp, Parodus and CcspEthAgent, which
is very confusing.

Setting the SyslogIdentifier in each systemd unit file allows the correct
ident to be applied to the log entries:

PsmSsp[1820]: rdk_dyn_log_initg_dl_socket = 3 __progname = PsmSsp
CcspEthAgent[3754]: CcspHalExtSw_getAssociatedDevice not implemented on generic arm platforms yet
Copilot AI review requested due to automatic review settings June 25, 2026 11:26

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR upstreams an existing patch to set SyslogIdentifier in multiple systemd unit files so that logs emitted by services started via /bin/sh -c ... show a meaningful identifier instead of sh in journalctl.

Changes:

  • Add SyslogIdentifier=... to key CCSP/RDK service unit files to improve journal/syslog attribution.
  • Standardize log identifiers per service to reduce ambiguity when multiple components log concurrently.

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated no comments.

Show a summary per file
File Description
systemd_units/RdkWanManager.service Adds SyslogIdentifier for clearer journald identification of RdkWanManager logs.
systemd_units/PsmSsp.service Adds SyslogIdentifier so PsmSsp logs don’t appear under sh.
systemd_units/notifyComp.service Adds SyslogIdentifier for notifyComp to improve log attribution.
systemd_units/CcspXdnsSsp.service Adds SyslogIdentifier for correct identification of CcspXdnsSsp output.
systemd_units/CcspTr069PaSsp.service Adds SyslogIdentifier to improve readability of TR-069 PA logs.
systemd_units/CcspTandDSsp.service Adds SyslogIdentifier for correct T&D log attribution.
systemd_units/CcspPandMSsp.service Adds SyslogIdentifier for PAM logs to avoid sh attribution.
systemd_units/CcspLMLite.service Adds SyslogIdentifier for LM Lite logs.
systemd_units/CcspEthAgent.service Adds SyslogIdentifier for EthAgent logs.
systemd_units/CcspCrSsp.service Adds SyslogIdentifier for CcspCrSsp logs.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@mahanteshchitt mahanteshchitt changed the title Set systemd 'SyslogIdentifier' parameter RDKBDEV-3456, RDKBACCL-1777 :Set systemd 'SyslogIdentifier' parameter Jun 25, 2026
@pradeeptakdas pradeeptakdas changed the title RDKBDEV-3456, RDKBACCL-1777 :Set systemd 'SyslogIdentifier' parameter RDKCOM-5604: RDKBDEV-3456, RDKBACCL-1777 Set systemd 'SyslogIdentifier' parameter Jun 26, 2026
@AkhilaReddyK7 AkhilaReddyK7 added the community-contribution Contribution from community label Jun 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community-contribution Contribution from community

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

5 participants