Introduction

Logging and Log Upload are critical aspects when considering large-scale RDK deployment. CPEs have a space constraint to store device logs for future use so either we store them for a limited number of days in CPE or in cloud servers.

Logs play a crucial role in RDK deployments by providing data for deriving field metrics and assessing the criticality of situations, such as determining whether an issue needs immediate attention or can wait until the next day. Controlled log uploads, ranging from 100% to very small numbers (2-3%) based on device maturity, help manage the volume of data. Configurable upload intervals, typically set to once a day, and the right level of abstraction ensure a balance between available storage space and the logs generated. Additionally, rotate-backup-upload policies are implemented to maintain efficient log management. Log Upload uses XConf as the primary endpoint, allowing the configuration to enable or disable log upload for a device or group of devices. During bootup, the CPE retrieves configuration information from XConf, and based on rules defined in the XConf server, it can control whether a particular device needs to perform log uploads. This setup allows for the sampling of devices from a larger population. The configuration server is responsible for retrieving and delivering settings to any client, and it supports configurable upload methods such as HTTPS, HTTP, and TFTP.

Architecture

RDK Log Upload Mechanism

LogUploadProcess

Log uploader (/usr/bin/logupload) is responsible for gathering local logs, packaging them, and uploading them to a remote URL. A client-side scheduler would control when it executes, but it could also be activated via immediate triggers from the log upload checker or other local actions.

The Uploader is responsible for sending CPE log files to a remote file store. It performs the following:

Responds to triggers (i.e. from cron)
Checks local Device Settings for the URL of the file store, the logs it should send, and the repository it should use
Gets connection credentials
Makes a connection to the remote server and sends the files

Repository

https://github.com/rdkcentral/dcm-agent

How CPEs Upload Logs and Metrics

1) Boot-time initialization and configuration fetch

Device boots and core services start (dcmd, telemetry2.0, reboot helpers, service plugins).

DCM/XConf configuration is fetched using device identity attributes (for example: MAC, model, firmware, environment) by telemetry2.0 process.

2025-11-28T19:06:47.125Z telemetry2_0[1177]:  251128-19:06:47.123393 [mod=T2, lvl=INFO] [tid=2488] T2: Curl Using XCONF URI : https://xconf.rdkcentral.com/loguploader/getT2Settings?estbMacAddress=D8%3a3A%3aDD%3a0D%3a16%3aB7&firmwareVersion=lib32-application-test-image-RPI4-20251030114955&model=RDKERPi4&manufacturer=RaspberryPi&partnerId=community&accountId=%221234%22&ecmMacAddress=D8%3a3A%3aDD%3a0D%3a16%3aB7&env=dev&controllerId=2504&channelMapId=2345&vodId=15660&timezone=America%2fNew_York&version=2 with Length :379
2025-11-28T19:06:47.125Z telemetry2_0[1177]:  251128-19:06:47.125776 [mod=T2, lvl=INFO] [tid=2488] doHttpGet with url https://xconf.rdkcentral.com/loguploader/getT2Settings?estbMacAddress=D8%3a3A%3aDD%3a0D%3a16%3aB7&firmwareVersion=lib32-application-test-image-RPI4-20251030114955&model=RDKERPi4&manufacturer=RaspberryPi&partnerId=community&accountId=%221234%22&ecmMacAddress=D8%3a3A%3aDD%3a0D%3a16%3aB7&env=dev&controllerId=2504&channelMapId=2345&vodId=15660&timezone=America%2fNew_York&version=2

XConf returns log-upload policy, typically including:

upload schedule (cron-like)
upload endpoint URL
upload protocol (HTTP/HTTPS)

behavior toggles (e.g., reboot upload, mTLS controls via RFC)

root@raspberrypi4-64-rdke:~# cat /opt/.t2persistentfolder/DCMresponse.txt
{"urn:settings:GroupName":"MW_RPi45","urn:settings:CheckOnReboot":true,"urn:settings:TimeZoneMode":"UTC","urn:settings:CheckSchedule:cron":"2 2 * * *",
"urn:settings:CheckSchedule:DurationMinutes":0,"urn:settings:LogUploadSettings:Message":null,"urn:settings:LogUploadSettings:Name":"RPi45",
"urn:settings:LogUploadSettings:NumberOfDays":0,"urn:settings:LogUploadSettings:UploadRepositoryName":"m8RPiFullTest45",
"urn:settings:LogUploadSettings:UploadRepository:URL":"https://xconf.rdkcentral.com/logTelemetryServer/logportal.php",
"urn:settings:LogUploadSettings:UploadRepository:uploadProtocol":"HTTP","urn:settings:LogUploadSettings:UploadOnReboot":true,
"urn:settings:LogUploadSettings:UploadImmediately":false,"urn:settings:LogUploadSettings:upload":true,
"urn:settings:LogUploadSettings:UploadSchedule:cron":"5 0 * * *","urn:settings:LogUploadSettings:UploadSchedule:levelone:cron":null,
"urn:settings:LogUploadSettings:UploadSchedule:leveltwo:cron":null,"urn:settings:LogUploadSettings:UploadSchedule:levelthree:cron":null,
"urn:settings:LogUploadSettings:UploadSchedule:TimeZoneMode":"UTC","urn:settings:LogUploadSettings:UploadSchedule:DurationMinutes":0,
"urn:settings:VODSettings:Name":null,"urn:settings:VODSettings:LocationsURL":null,"urn:settings:VODSettings:SRMIPList":null,
"urn:settings:TelemetryProfile":{"@type":"PermanentTelemetryProfile","id":"fcda6fb8-953d-4699-85b2-70e6f4824c9e",
"telemetryProfile":[{"header":"NW_DNSMASQ_STARTED","content":"dnsmasq: starting /usr/bin/dnsmasq","type":"NetworkManager.log","pollingFrequency":"0"},
{"header":"SYST_ERR_LogUpload_Failed","content":"sysint","type":"<event>","pollingFrequency":"0"},
{"header":"Xi_wifiMAC_split","content":"sysint","type":"<event>","pollingFrequency":"0"},{"header":"Uptime","content":"Device.DeviceInfo.UpTime","type":"dataModel","pollingFrequency":"0"}],
"schedule":"3","expires":0,"telemetryProfile:name":"RDKMA_Test",
"uploadRepository:URL":"http://xconf.rdkcentral.com/xconf/logupload.php","uploadRepository:uploadProtocol":"HTTP"}}

Effective values are resolved into local runtime config used by callers/uploader - /tmp/DCMSetting.conf

Common config sources used at runtime

XConf/DCM settings:
- LogUploadSettings:UploadRepository:URL
- LogUploadSettings:UploadRepository:uploadProtocol
- LogUploadSettings:UploadOnReboot
Local files:
- /etc/dcm.properties or /opt/dcm.properties (e.g., LOG_SERVER)
- /tmp/DCMSettings.conf (resolved runtime values)

2) How log upload is triggered after boot

After boot, upload may start from any of these trigger paths:

A) Scheduled trigger (DCM scheduler)

dcmd executes scheduled job (DCM_LOGUPLOAD_SCHED).
Calls uploadstblogs_run() with trigger type TRIGGER_SCHEDULED.

B) Maintenance window trigger

MaintenanceManager runs maintenance task chain.
Upload task invokes upload binary/wrapper (/usr/bin/logupload) from /lib/rdk/Start_MaintenanceTasks.sh

C) On-demand app/API trigger

org.rdk.SystemServices.uploadLogsAsync initiates immediate upload path.
Caller resolves protocol/URL and invokes uploadstblogs_run () with trigger type TRIGGER_MANUAL.

D) TR69hostif immediate trigger (UploadLogsNow RFC)

RFC: Device.DeviceInfo.X_RDKCENTRAL-COM_xOpsDeviceMgmt.Logging.xOpsDMUploadLogsNow
Invokes uploadstblogs_run()with uploadlogsnow_mode=true ON_DEMAND

E) Reboot upload trigger

Boot sequence waits on marker synchronization (backup_logs, reboot info, telemetry markers).
Then uploader runs with TRIGGER_REBOOT (subject to timeout guards).

3) Endpoint and how it is chosen

The final upload destination is selected from resolved config:

Primary: XConf/DCM upload repository values (URL, uploadProtocol)
Fallback/auxiliary: local properties (LOG_SERVER) depending on caller path
Security mode:
- plain HTTP/HTTPS as configured
- mTLS/xPKI path

So the uploader reaches the cloud URL from DCM/XConf policy (or caller fallback), using configured protocol/security mode.

4) How it executes on-device (what runs)

Regardless of trigger source, execution pattern is:

Acquire concurrency lock: /tmp/.log-upload.lock
Collect eligible logs
Apply exclusions/filters
Create compressed archive (tar.gz)
Upload archive to configured endpoint
Record completion:
- maintenance path may emit completion/error signaling
- uploadlogsnow writes /tmp/logUploadStatus.txt

5) “Downloads and executes” clarification

In this flow, the device typically downloads configuration, not a new upload executable.

Downloaded from server: policy/config (schedule, URL, protocol, flags)
Executed locally: existing on-device upload engine (uploadstblogs/logupload path via caller)
In short: backend tells the device where/when/how to upload; device uses its preinstalled binaries to perform upload.

6) Quick reference table (post-boot perspective)

Trigger source	Can happen after boot?	Typical interface	Endpoint source
DCM scheduler	Yes (periodic)	uploadstblogs_run()	XConf-delivered DCM settings
MaintenanceManager	Yes	external upload command/script	resolved DCM & runtime config from script
SystemServices API	Yes (manual)	API -> call uploadstblogs_run()	DCM settings from local runtime config - temp file: /tmp/DCMSettings.conf (/etc/dcm.properties or /opt/dcm.properties)
TR69hostif UploadLogsNow	Yes (immediate)	uploadstblogs_run()uploadlogsnow	resolved upload config from XConf
Reboot flow	Yes (early post-boot)	uploadstblogs_run()	resolved upload config from XConf

7) Runtime monitoring

Use:

tail -f /opt/logs/dcmscript.log

For UploadLogsNow status:

cat /tmp/logUploadStatus.txt

Configuring server details

The value set for Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.Telemetry.ConfigURL determines where the device will fetch its DCM/Telemetry settings. Those settings, in turn, provide the URL for log upload and other related parameters.

This can be retrieved from xconf server as a response to the RFC query: https://xconf.rdkcentral.com/featureControl/getSettings?<parameters>

For RDK7 release in community devices, this is set from https://github.com/rdkcentral/meta-image-assembler-rdke/blob/main/conf/community-rfc-configs.ini

mTLS support

RDKE LogUpload functionality expects mTLS connection by default to Download & upload logs to the server.
Support to add mTLS to RDKM XConf server is under investigation
RDKCLOUD-74 - Getting issue details... STATUS
RDKECOREMW-870 - Getting issue details... STATUS
Until then, logUpload functionality is broken in RDKE builds

Configuration Details

⁠To know how XConf server-side configuration and feature validation are done please refer to User guide for configuration and feature validation .

Validation details

Pre-requisite

Configure the XCONF server with the values

Update the rules and configs in XCONF server. Please refer this Feature Validation(LogUpload) on configuring DCM configurations in the RDKM XCONF server.

Client side

1) Make sure that required RFC parameters are configured before starting the validation and file community-rfc-configs.ini is present in /etc/rfcdefaults/ path to do so.

/etc/rfcdefaults# ls -l
-rw-r--r--    1 root     root           352 Jan 30 05:11 community-rfc-configs.ini

2) Ensure telemetry process is running by checking the pid

root@raspberrypi4-64-rdke:~# pidof telemetry2_0 
1312

3) Invoke system service query for setting timezone

root@raspberrypi4-64-rdke:/opt/persistent# curl -d '{"jsonrpc":"2.0","id":"3","method": "org.rdk.System.setTimeZoneDST","params": {"timeZone": "America/New_York"}}' http://127.0.0.1:9998/jsonrpc 
{"jsonrpc":"2.0","id":3,"result":{"success":true}} 
root@raspberrypi4-64-rdke:/opt/persistent# cat timeZoneDST 
America/New_York
root@raspberrypi4-64-rdke:/opt/persistent#

4) Check the Telemetry URL

tr181 -g Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.Telemetry.ConfigURL
https://xconf.rdkcentral.com/loguploader/getT2Settings

5) Restart telemetry2_0 service

Steps to validate

curl --header "Content-Type: application/json" --request POST --data '{"jsonrpc":"2.0","id":"3","method":"Controller.1.activate","params":{"callsign":"org.rdk.MaintenanceManager"}}' http://127.0.0.1:9998/jsonrpc

Maintanencemanager invocation is handling through UI side. For current validation, we are following this approach.

1. Check DCM process is active

root@raspberrypi4-64-rdke:~# systemctl status dcmd
● dcmd.service - To start dcm daemon
   Loaded: loaded (/lib/systemd/system/dcmd.service; enabled; vendor preset: enabled)
   Active: active (exited) since Fri 2025-10-03 16:07:08 EDT; 1 months 21 days ago
  Process: 1183 ExecStart=/usr/bin/dcmd (code=exited, status=0/SUCCESS)
 Main PID: 1183 (code=exited, status=0/SUCCESS)
    Tasks: 8 (limit: 512)
   CGroup: /system.slice/dcmd.service
           ├─1194 /usr/bin/dcmd
           ├─2781 /bin/busybox sh /lib/rdk/uploadSTBLogs.sh Fallbacklogupload 1 1 1 HTTP https://xconf.rdkcentral.com/logTelemetryServer/logportal.php
           └─2877 sleep 330

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
root@raspberrypi4-64-rdke:~#

2. check DCMresponse.txt entry is created in /opt/.t2persistentfolder

Note - Telemetry2_0 retrieves configuration information from XConf - DCMresponse.txt, if it fails, dcm upload will not start.

root@raspberrypi4-64-rdke:~# cat /opt/.t2persistentfolder/DCMresponse.txt
{
    "urn:settings:GroupName":"MW_RPi45",
    "urn:settings:CheckOnReboot":true,
    "urn:settings:TimeZoneMode":"UTC",
    "urn:settings:CheckSchedule:cron":"2 2 * * *",
    "urn:settings:CheckSchedule:DurationMinutes":0,
    "urn:settings:LogUploadSettings:Message":null,
    "urn:settings:LogUploadSettings:Name":"RPi45",
    "urn:settings:LogUploadSettings:NumberOfDays":0,
    "urn:settings:LogUploadSettings:UploadRepositoryName":"m8RPiFullTest45",
    "urn:settings:LogUploadSettings:UploadRepository:URL":"https://xconf.rdkcentral.com/logTelemetryServer/logportal.php",
    "urn:settings:LogUploadSettings:UploadRepository:uploadProtocol":"HTTP",
    "urn:settings:LogUploadSettings:UploadOnReboot":true,
    "urn:settings:LogUploadSettings:UploadImmediately":false,
    "urn:settings:LogUploadSettings:upload":true,
    "urn:settings:LogUploadSettings:UploadSchedule:cron":"5 0 * * *",
    "urn:settings:LogUploadSettings:UploadSchedule:levelone:cron":null,
    "urn:settings:LogUploadSettings:UploadSchedule:leveltwo:cron":null,
    "urn:settings:LogUploadSettings:UploadSchedule:levelthree:cron":null,
    "urn:settings:LogUploadSettings:UploadSchedule:TimeZoneMode":"UTC",
    "urn:settings:LogUploadSettings:UploadSchedule:DurationMinutes":0,
    "urn:settings:VODSettings:Name":null,
    "urn:settings:VODSettings:LocationsURL":null,
    "urn:settings:VODSettings:SRMIPList":null,
    "urn:settings:TelemetryProfile": {
        "@type":"PermanentTelemetryProfile",
        "id":"fcda6fb8-953d-4699-85b2-70e6f4824c9e",
        "telemetryProfile":[ {
            "header": "DNSMASQ_STARTED", "content":"dnsmasq: starting /usr/bin/dnsmasq", "type":"NetworkManager.log", "pollingFrequency":"1"
        },{
            "header": "MEDIA_ERROR_NETWORK_ERROR", "content":"onMediaError NETWORK ERROR(10)", "type":"receiver.log", "pollingFrequency":"1"
        }
    ],
    "schedule":"3",
    "expires":0,
    "telemetryProfile:name":"RDKMA_Test",
    "uploadRepository:URL":"http://xconf.rdkcentral.com/xconf/logupload.php",
    "uploadRepository:uploadProtocol":"HTTP"
   }
}
root@raspberrypi4-64-rdke: ~#

Success Logs

root@raspberrypi4-64-rdke:~# cat /opt/logs/dcmscript.log
2025-10-03T20:07:08.499Z dcmd[1172]:  rdk_dyn_log_initg_dl_socket = 3 __progname = dcmd
2025-10-03T20:07:08.499Z dcmd[1172]:  Conf file /etc/debug.ini open success
2025-10-03T20:07:08.499Z dcmd[1172]:  251003-20:07:08.498454 [mod=DCM, lvl=INFO] [tid=1172] [DCM] main[261]: Starting DCM Process: 1172
2025-10-03T20:07:08.500Z dcmd[1172]:  251003-20:07:08.499314 [mod=DCM, lvl=INFO] [tid=1172] [DCM] main[270]: Exiting the main process
2025-10-03T20:07:08.503Z dcmd[1172]:  251003-20:07:08.500801 [mod=DCM, lvl=INFO] [tid=1175] [DCM] dcmUtilsCheckDaemonStatus[161]: Opening new pid file
2025-10-03T20:07:08.503Z dcmd[1172]:  251003-20:07:08.501238 [mod=DCM, lvl=INFO] [tid=1175] [DCM] dcmSettingGetValueFromFile[99]: Key: RDK_PATH Value: /lib/rdk
2025-10-03T20:07:08.503Z dcmd[1172]:  251003-20:07:08.501351 [mod=DCM, lvl=INFO] [tid=1175] [DCM] dcmSettingGetValueFromFile[99]: Key: ENABLE_MAINTENANCE Value: true
2025-10-03T20:07:08.503Z dcmd[1172]:  251003-20:07:08.501586 [mod=RBUSCORE, lvl=INFO] [tid=1175] RBus Enabled
2025-10-03T20:07:08.503Z dcmd[1172]:  251003-20:07:08.501641 [mod=RBUS, lvl=INFO] [tid=1175] rbus open for component: T2TODCM
2025-10-03T20:07:08.503Z dcmd[1172]:  251003-20:07:08.501739 [mod=RBUSCORE, lvl=INFO] [tid=1175] RBus Enabled
2025-10-03T20:07:08.503Z dcmd[1172]:  251003-20:07:08.501821 [mod=RBUSCORE, lvl=INFO] [tid=1175] Broker address: unix:///tmp/rtrouted
2025-10-03T20:07:08.503Z dcmd[1172]:  251003-20:07:08.503141 [mod=RBUS, lvl=INFO] [tid=1175]  rbus open (T2TODCM) success
2025-10-03T20:07:08.503Z dcmd[1172]:  251003-20:07:08.503194 [mod=DCM, lvl=INFO] [tid=1175] [DCM] dcmDaemonMainInit[161]: T2 is enabled
2025-10-03T20:07:08.510Z dcmd[1172]:  251003-20:07:08.509493 [mod=DCM, lvl=INFO] [tid=1175] [DCM] dcmRbusGetT2Version[322]: Telemetry 2 Version: 2.0.1
2025-10-03T20:07:08.510Z dcmd[1172]:  251003-20:07:08.509563 [mod=DCM, lvl=INFO] [tid=1175] [DCM] dcmDaemonMainInit[164]: T2 Version: 2.0.1
2025-10-03T20:07:08.511Z dcmd[1172]:  251003-20:07:08.509949 [mod=RBUS, lvl=INFO] [tid=1175] Device.DCM.Setconfig 19:00:11.659684
2025-10-03T20:07:08.511Z dcmd[1172]:  251003-20:07:08.510857 [mod=RBUS, lvl=INFO] [tid=1175] Device.DCM.Processconfig 19:00:11.660630
2025-10-03T20:07:08.511Z dcmd[1172]:  251003-20:07:08.510943 [mod=RBUS, lvl=INFO] [tid=1175] file /tmp/rbus_subs_T2TODCM
2025-10-03T20:07:08.511Z dcmd[1172]:  251003-20:07:08.511659 [mod=RBUS, lvl=INFO] [tid=1179] item=19:00:11.659684
2025-10-03T20:07:08.511Z dcmd[1172]:  251003-20:07:08.511748 [mod=RBUS, lvl=INFO] [tid=1179] item=19:00:11.660630
2025-10-03T20:07:08.511Z dcmd[1172]:  251003-20:07:08.511786 [mod=RBUS, lvl=INFO] [tid=1179] subs past due
2025-10-03T20:07:08.512Z dcmd[1172]:  251003-20:07:08.511842 [mod=RBUS, lvl=INFO] [tid=1179] Device.DCM.Setconfig subscribing
2025-10-03T20:07:08.517Z dcmd[1172]:  251003-20:07:08.516620 [mod=DCM, lvl=INFO] [tid=1175] [DCM] main[307]: Loading the Default config
2025-10-03T20:07:08.517Z dcmd[1172]:  251003-20:07:08.516808 [mod=DCM, lvl=INFO] [tid=1175] [DCM] dcmSettingDefaultBoot[717]: Fetching the Default Boot config from /opt/.t2persistentfolder/DCMresponse.txt
2025-10-03T20:07:08.518Z dcmd[1172]:  251003-20:07:08.518613 [mod=RBUS, lvl=INFO] [tid=1179] Device.DCM.Setconfig no provider. retry in 1000 ms with 599992 left
2025-10-03T20:07:08.519Z dcmd[1172]:  251003-20:07:08.518715 [mod=RBUS, lvl=INFO] [tid=1179] Device.DCM.Processconfig subscribing
2025-10-03T20:07:08.525Z dcmd[1172]:  251003-20:07:08.522386 [mod=RBUS, lvl=INFO] [tid=1179] Device.DCM.Processconfig no provider. retry in 1000 ms with 599989 left
2025-10-03T20:07:08.525Z dcmd[1172]:  251003-20:07:08.522554 [mod=RBUS, lvl=INFO] [tid=1179] item=19:00:12.668388
2025-10-03T20:07:08.525Z dcmd[1172]:  251003-20:07:08.522616 [mod=RBUS, lvl=INFO] [tid=1179] item=19:00:12.672185
2025-10-03T20:07:08.525Z dcmd[1172]:  251003-20:07:08.522675 [mod=RBUS, lvl=INFO] [tid=1179] subs due in 996 miliseconds nextSendTime=19:00:12.668388
2025-10-03T20:07:08.597Z dcmd[1172]:  251003-20:07:08.596722 [mod=RBUS, lvl=INFO] [tid=1177] Consumer=rbus.telemetry2_0.INBOX.1193 SUBSCRIBED to event=Device.X_RDKCENTREL-COM.Reloadconfig
2025-10-03T20:07:08.597Z dcmd[1172]:  251003-20:07:08.596796 [mod=DCM, lvl=INFO] [tid=1177] [DCM] rbusSendEventCB[161]: rbusSendEvent event registered Device.X_RDKCENTREL-COM.Reloadconfig
2025-11-25T20:46:19.261Z dcmd[1172]:  251125-20:46:19.261476 [mod=RBUS, lvl=INFO] [tid=1179] item=19:00:12.668388
2025-11-25T20:46:19.262Z dcmd[1172]:  251125-20:46:19.261561 [mod=RBUS, lvl=INFO] [tid=1179] item=19:00:12.672185
2025-11-25T20:46:19.262Z dcmd[1172]:  251125-20:46:19.261599 [mod=RBUS, lvl=INFO] [tid=1179] subs past due
2025-11-25T20:46:19.262Z dcmd[1172]:  251125-20:46:19.261653 [mod=RBUS, lvl=INFO] [tid=1179] Device.DCM.Setconfig subscribing
2025-11-25T20:46:19.264Z dcmd[1172]:  251125-20:46:19.263570 [mod=RBUSCORE, lvl=INFO] [tid=1179] Subscription for Device.DCM.Setconfig::Device.DCM.Setconfig is now active.
2025-11-25T20:46:19.264Z dcmd[1172]:  251125-20:46:19.263656 [mod=RBUS, lvl=INFO] [tid=1179] Device.DCM.Setconfig subscribe retries succeeded
2025-11-25T20:46:19.264Z dcmd[1172]:  251125-20:46:19.263697 [mod=DCM, lvl=INFO] [tid=1179] [DCM] rbusAsyncSubCB[204]: Subscription Device.DCM.Setconfig event Success
2025-11-25T20:46:19.264Z dcmd[1172]:  251125-20:46:19.263846 [mod=RBUS, lvl=INFO] [tid=1179] item=19:00:12.672185
2025-11-25T20:46:19.264Z dcmd[1172]:  251125-20:46:19.263908 [mod=RBUS, lvl=INFO] [tid=1179] subs due in 1 miliseconds nextSendTime=19:00:12.672185
2025-11-25T20:46:19.265Z dcmd[1172]:  251125-20:46:19.265331 [mod=RBUS, lvl=INFO] [tid=1179] item=19:00:12.672185
2025-11-25T20:46:19.265Z dcmd[1172]:  251125-20:46:19.265383 [mod=RBUS, lvl=INFO] [tid=1179] subs past due
2025-11-25T20:46:19.265Z dcmd[1172]:  251125-20:46:19.265438 [mod=RBUS, lvl=INFO] [tid=1179] Device.DCM.Processconfig subscribing
2025-11-25T20:46:19.267Z dcmd[1172]:  251125-20:46:19.266895 [mod=DCM, lvl=INFO] [tid=1175] [DCM] main[326]: Telemetry Events subscriptions is success
2025-11-25T20:46:19.267Z dcmd[1172]:  251125-20:46:19.266944 [mod=DCM, lvl=INFO] [tid=1175] [DCM] dcmRbusSendEvent[227]: dcmRbusSendEvent ++in
2025-11-25T20:46:19.267Z dcmd[1172]:  251125-20:46:19.266951 [mod=RBUSCORE, lvl=INFO] [tid=1179] Subscription for Device.DCM.Processconfig::Device.DCM.Processconfig is now active.
2025-11-25T20:46:19.267Z dcmd[1172]:  251125-20:46:19.267012 [mod=RBUS, lvl=INFO] [tid=1179] Device.DCM.Processconfig subscribe retries succeeded
2025-11-25T20:46:19.267Z dcmd[1172]:  251125-20:46:19.267047 [mod=DCM, lvl=INFO] [tid=1179] [DCM] rbusAsyncSubCB[204]: Subscription Device.DCM.Processconfig event Success
2025-11-25T20:46:19.267Z dcmd[1172]:  251125-20:46:19.267228 [mod=DCM, lvl=INFO] [tid=1175] [DCM] dcmRbusSendEvent[266]: dcmRbusSendEvent --out
2025-11-25T20:46:19.267Z dcmd[1172]:  251125-20:46:19.267264 [mod=DCM, lvl=INFO] [tid=1175] [DCM] main[333]: Sent Event to telemetry for configuraion path
2025-11-25T20:46:21.518Z dcmd[1172]:  251125-20:46:21.517492 [mod=DCM, lvl=INFO] [tid=1177] [DCM] rbusSetConf[92]: configPath: /opt/.t2persistentfolder/DCMresponse.txt
2025-11-25T20:46:21.518Z dcmd[1172]:  251125-20:46:21.517571 [mod=DCM, lvl=INFO] [tid=1177] [DCM] rbusSetConf[95]: Recieved eventName: Device.DCM.Setconfig, Event type: 3, Event Name: Device.DCM.Setconfig
2025-11-25T20:46:21.518Z dcmd[1172]:  251125-20:46:21.517643 [mod=DCM, lvl=INFO] [tid=1177] [DCM] rbusProcConf[131]: Recieved eventName: Device.DCM.Processconfig, Event type: 3, Event Name: Device.DCM.Processconfig
2025-11-25T20:46:22.268Z dcmd[1172]:  251125-20:46:22.267830 [mod=DCM, lvl=INFO] [tid=1175] [DCM] main[341]: Start Scheduling
2025-11-25T20:46:22.268Z dcmd[1172]:  251125-20:46:22.268103 [mod=DCM, lvl=INFO] [tid=1175] [DCM] dcmSettingParseConf[487]: Log Upload protocol: HTTP
2025-11-25T20:46:22.268Z dcmd[1172]:  251125-20:46:22.268147 [mod=DCM, lvl=INFO] [tid=1175] [DCM] dcmSettingParseConf[496]: Log Upload URL: https://xconf.rdkcentral.com/logTelemetryServer/logportal.php
2025-11-25T20:46:22.269Z dcmd[1172]:  251125-20:46:22.268182 [mod=DCM, lvl=INFO] [tid=1175] [DCM] dcmSettingParseConf[505]: TimeZone : UTC
2025-11-25T20:46:22.269Z dcmd[1172]:  251125-20:46:22.268220 [mod=DCM, lvl=INFO] [tid=1175] [DCM] dcmSettingParseConf[510]: DCM_LOGUPLOAD_REBOOT: 1
2025-11-25T20:46:22.269Z dcmd[1172]:  251125-20:46:22.268260 [mod=DCM, lvl=INFO] [tid=1175] [DCM] dcmSettingParseConf[518]: DCM_LOGUPLOAD_CRON: 5 0 * * *
2025-11-25T20:46:22.269Z dcmd[1172]:  251125-20:46:22.268292 [mod=DCM, lvl=INFO] [tid=1175] [DCM] dcmSettingParseConf[526]: DCM_DIFD_CRON: 2 2 * * *
2025-11-25T20:46:22.278Z dcmd[1172]:  251125-20:46:22.276982 [mod=DCM, lvl=INFO] [tid=1175] [DCM] dcmSettingParseConf[550]: urn:settings:LogUploadSettings:UploadSchedule:cron is present setting cron jobs
2025-11-25T20:46:22.893Z : /lib/rdk/uploadSTBLogs.sh: Called with 3 attempts
2025-11-25T20:46:22.934Z : /lib/rdk/uploadSTBLogs.sh: USAGE: /lib/rdk/uploadSTBLogs.sh <TFTP Server IP> <Flag (STB delay or not)> <SCP_SERVER> <UploadOnReboot> <UploadProtocol> <UploadHttpLink> <RRD_FLAG> <RRD_UPLOADLOG_FILE>
2025-11-25T20:46:23.004Z : /lib/rdk/uploadSTBLogs.sh: Check Codebig flag,,,
2025-11-25T20:46:23.042Z : /lib/rdk/uploadSTBLogs.sh: Build Type: dev Log file: D83ADD0D16B7_Logs_11-25-25-08-46PM.tgz UploadProtocol: HTTP UploadHttpLink: https://xconf.rdkcentral.com/logTelemetryServer/logportal.php
2025-11-25T20:46:23.133Z : /lib/rdk/uploadSTBLogs.sh: upload_flag = true
2025-11-25T20:46:23.164Z : /lib/rdk/uploadSTBLogs.sh: DCM log Folder does not exist . Creating now
2025-11-25T20:46:23.008Z dcmd[1172]:  sh: bad number
2025-11-25T20:46:23.224Z dcmd[1172]:  ls: /opt/logs/*.pcap*: No such file or directory
2025-11-25T20:46:23.446Z : /lib/rdk/uploadSTBLogs.sh: UploadOnReboot set to true
2025-11-25T20:46:23.450Z dcmd[1172]:  sh: 5: unknown operand
2025-11-25T20:46:23.467Z dcmd[1172]:  sh: /opt/logs/PreviousLogs/11-25-25-08-50PM-ConnectionStats.txt: unknown operand
2025-11-25T20:46:23.775Z : /lib/rdk/uploadSTBLogs.sh: Sleeping for seven minutes
Retrieving CPU instantaneous information for telemetry support
Retrieving virtual memory information for telemetry support
Retrieving CPU Temperature for telemetry support
2025-11-25T20:58:37.202Z : /lib/rdk/uploadSTBLogs.sh: Done sleeping
sh: /opt/logs/PreviousLogs/11-25-25-08-50PM-ConnectionStats.txt: unknown operand
2025-11-25T20:58:37.261Z dcmd[1172]:  rm: can't remove 'D83ADD0D16B7_Logs_11-25-25-08-46PM.tgz': No such file or directory
2025-11-25T20:58:37.338Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-CapDebug.txt
2025-11-25T20:58:37.378Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-ConnectionStats.txt
2025-11-25T20:58:37.421Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-NMMonitor.log
2025-11-25T20:58:37.461Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-NetworkManager.log
2025-11-25T20:58:37.517Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-access.log
2025-11-25T20:58:37.567Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-audiocapturemgr.log
2025-11-25T20:58:37.610Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-bluez.log
2025-11-25T20:58:37.649Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-bluez.log.1
2025-11-25T20:58:37.704Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-bluez.log.2
2025-11-25T20:58:37.747Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-btmgrlog.txt
2025-11-25T20:58:37.810Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-btmgrlog.txt.1
2025-11-25T20:58:37.857Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-btmgrlog.txt.2
2025-11-25T20:58:37.905Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-core_log.txt
2025-11-25T20:58:37.947Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-ctrlm_log.txt
2025-11-25T20:58:38.008Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-dcmscript.log
2025-11-25T20:58:38.070Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-device_details.log
2025-11-25T20:58:38.108Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-disk_cleanup.log
2025-11-25T20:58:38.157Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-dnsmasq.log
2025-11-25T20:58:38.209Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-dropbear.log
2025-11-25T20:58:38.248Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-gst-cleanup.log
2025-11-25T20:58:38.297Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-ipSetupLogs.txt
2025-11-25T20:58:38.373Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-iptables.log
2025-11-25T20:58:38.417Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-lighttpd.error.log
2025-11-25T20:58:38.473Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-logrotate.log
2025-11-25T20:58:38.525Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-maintenance.log
2025-11-25T20:58:38.622Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-messages.txt
2025-11-25T20:58:38.679Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-mount_log.txt
2025-11-25T20:58:38.725Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-ntp.log
2025-11-25T20:58:38.771Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-parodus.log
2025-11-25T20:58:38.852Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-rdk_milestones.log
2025-11-25T20:58:38.925Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-rdk_shell.log
2025-11-25T20:58:38.967Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-rdm_status.log
2025-11-25T20:58:39.038Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-rebootInfo.log
2025-11-25T20:58:39.080Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-rebootreason.log
2025-11-25T20:58:39.130Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-remote-debugger.log
2025-11-25T20:58:39.180Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-residentapp.log
2025-11-25T20:58:39.214Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-rfcscript.log
2025-11-25T20:58:39.253Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-ripple.log
2025-11-25T20:58:39.302Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-routerInfo.log
2025-11-25T20:58:39.382Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-rtrouted.log
2025-11-25T20:58:39.427Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-sslendpoints.log
2025-11-25T20:58:39.482Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-startup_stdout_log.txt
2025-11-25T20:58:39.523Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-swupdate.log
2025-11-25T20:58:39.564Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-syslog_fallback.log
2025-11-25T20:58:39.602Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-system.log
2025-11-25T20:58:39.640Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-systimemgr.log
2025-11-25T20:58:39.685Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-telemetry2_0.txt.0
2025-11-25T20:58:39.725Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-top_log.txt
2025-11-25T20:58:39.777Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-tr69hostif.log
2025-11-25T20:58:39.812Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-uimgr_log.txt
2025-11-25T20:58:39.851Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-version.txt
2025-11-25T20:58:39.888Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-webconfig.log
2025-11-25T20:58:39.929Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-wpa_supplicant.log
2025-11-25T20:58:39.965Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-wpeframework.log
2025-11-25T20:58:39.999Z : /lib/rdk/uploadSTBLogs.sh: Processing file...11-25-25-08-50PM-zram.log
2025-11-25T20:58:41.712Z : /lib/rdk/uploadSTBLogs.sh: reboot_reason:  , uploadLog:true and UploadLogsOnUnscheduledReboot.Disable RFC: false
2025-11-25T20:58:41.733Z : /lib/rdk/uploadSTBLogs.sh: Uploading Logs with DCM
2025-11-25T20:58:41.750Z dcmd[1172]:  ls: /opt/logs/*-moca.pcap: No such file or directory
11-25-25-08-50PM-CapDebug.txt
11-25-25-08-50PM-ConnectionStats.txt
11-25-25-08-50PM-NMMonitor.log
11-25-25-08-50PM-NetworkManager.log
11-25-25-08-50PM-access.log
11-25-25-08-50PM-audiocapturemgr.log
11-25-25-08-50PM-bluez.log
11-25-25-08-50PM-bluez.log.1
11-25-25-08-50PM-bluez.log.2
11-25-25-08-50PM-btmgrlog.txt
11-25-25-08-50PM-btmgrlog.txt.1
11-25-25-08-50PM-btmgrlog.txt.2
11-25-25-08-50PM-core_log.txt
11-25-25-08-50PM-ctrlm_log.txt
11-25-25-08-50PM-dcmscript.log
11-25-25-08-50PM-device_details.log
11-25-25-08-50PM-disk_cleanup.log
11-25-25-08-50PM-dnsmasq.log
11-25-25-08-50PM-dropbear.log
11-25-25-08-50PM-gst-cleanup.log
11-25-25-08-50PM-ipSetupLogs.txt
11-25-25-08-50PM-iptables.log
11-25-25-08-50PM-lighttpd.error.log
11-25-25-08-50PM-logrotate.log
11-25-25-08-50PM-maintenance.log
11-25-25-08-50PM-messages.txt
11-25-25-08-50PM-mount_log.txt
11-25-25-08-50PM-ntp.log
11-25-25-08-50PM-parodus.log
11-25-25-08-50PM-rdk_milestones.log
11-25-25-08-50PM-rdk_shell.log
11-25-25-08-50PM-rdm_status.log
11-25-25-08-50PM-rebootInfo.log
11-25-25-08-50PM-rebootreason.log
11-25-25-08-50PM-remote-debugger.log
11-25-25-08-50PM-residentapp.log
11-25-25-08-50PM-rfcscript.log
11-25-25-08-50PM-ripple.log
11-25-25-08-50PM-routerInfo.log
11-25-25-08-50PM-rtrouted.log
11-25-25-08-50PM-sslendpoints.log
11-25-25-08-50PM-startup_stdout_log.txt
11-25-25-08-50PM-swupdate.log
11-25-25-08-50PM-syslog_fallback.log
11-25-25-08-50PM-system.log
11-25-25-08-50PM-systimemgr.log
11-25-25-08-50PM-telemetry2_0.txt.0
11-25-25-08-50PM-top_log.txt
11-25-25-08-50PM-tr69hostif.log
11-25-25-08-50PM-uimgr_log.txt
11-25-25-08-50PM-version.txt
11-25-25-08-50PM-webconfig.log
11-25-25-08-50PM-wpa_supplicant.log
11-25-25-08-50PM-wpeframework.log
11-25-25-08-50PM-zram.log
11-25-25-08-58PM-CapDebug.txt
11-25-25-08-58PM-ConnectionStats.txt
11-25-25-08-58PM-NMMonitor.log
11-25-25-08-58PM-NetworkManager.log
11-25-25-08-58PM-access.log
11-25-25-08-58PM-audiocapturemgr.log
11-25-25-08-58PM-bluez.log
11-25-25-08-58PM-bluez.log.1
11-25-25-08-58PM-bluez.log.2
11-25-25-08-58PM-btmgrlog.txt
11-25-25-08-58PM-btmgrlog.txt.1
11-25-25-08-58PM-btmgrlog.txt.2
11-25-25-08-58PM-core_log.txt
11-25-25-08-58PM-ctrlm_log.txt
11-25-25-08-58PM-dcmscript.log
11-25-25-08-58PM-device_details.log
11-25-25-08-58PM-disk_cleanup.log
11-25-25-08-58PM-dnsmasq.log
11-25-25-08-58PM-dropbear.log
11-25-25-08-58PM-gst-cleanup.log
11-25-25-08-58PM-ipSetupLogs.txt
11-25-25-08-58PM-iptables.log
11-25-25-08-58PM-lighttpd.error.log
11-25-25-08-58PM-logrotate.log
11-25-25-08-58PM-maintenance.log
11-25-25-08-58PM-messages.txt
11-25-25-08-58PM-mount_log.txt
11-25-25-08-58PM-ntp.log
11-25-25-08-58PM-parodus.log
11-25-25-08-58PM-rdk_milestones.log
11-25-25-08-58PM-rdk_shell.log
11-25-25-08-58PM-rdm_status.log
11-25-25-08-58PM-rebootInfo.log
11-25-25-08-58PM-rebootreason.log
11-25-25-08-58PM-remote-debugger.log
11-25-25-08-58PM-residentapp.log
11-25-25-08-58PM-rfcscript.log
11-25-25-08-58PM-ripple.log
11-25-25-08-58PM-routerInfo.log
11-25-25-08-58PM-rtrouted.log
11-25-25-08-58PM-sslendpoints.log
11-25-25-08-58PM-startup_stdout_log.txt
11-25-25-08-58PM-swupdate.log
11-25-25-08-58PM-syslog_fallback.log
11-25-25-08-58PM-system.log
11-25-25-08-58PM-systimemgr.log
11-25-25-08-58PM-telemetry2_0.txt.0
11-25-25-08-58PM-top_log.txt
11-25-25-08-58PM-tr69hostif.log
11-25-25-08-58PM-uimgr_log.txt
11-25-25-08-58PM-version.txt
11-25-25-08-58PM-webconfig.log
11-25-25-08-58PM-wpa_supplicant.log
11-25-25-08-58PM-wpeframework.log
11-25-25-08-58PM-zram.log
last_reboot
2025-11-25T20:59:43.996Z : /lib/rdk/uploadSTBLogs.sh: RFC_EncryptCloudUpload_Enable:
2025-11-25T20:59:44.029Z : /lib/rdk/uploadSTBLogs.sh: HttpLogUpload: Codebig is disabled UseCodebig=0
2025-11-25T20:59:44.064Z : /lib/rdk/uploadSTBLogs.sh: HttpLogUpload: Attempting direct log upload
2025-11-25T20:59:44.118Z : /lib/rdk/uploadSTBLogs.sh: RFC_EncryptCloudUpload_Enable:
2025-11-25T20:59:44.147Z : /lib/rdk/uploadSTBLogs.sh: MTLS defaulted
2025-11-25T20:59:44.164Z : /lib/rdk/uploadSTBLogs.sh: Connect with mTLS certificate from xPKI
2025-11-25T20:59:44.232Z : /lib/rdk/uploadSTBLogs.sh: Curl Connected to xconf.rdkcentral.com () port
2025-11-25T20:59:44.257Z : /lib/rdk/uploadSTBLogs.sh: Connect with mTLS certificate from xPKI Curl return code: , http code:
2025-11-25T20:59:44.292Z : /lib/rdk/uploadSTBLogs.sh: HttpLogUpload: Direct log upload attempt return: retry=1, httpcode=
2025-11-25T20:59:44.173Z dcmd[1172]:  /lib/rdk/uploadSTBLogs.sh: line 148: exec_curl_mtls: not found
2025-11-25T20:59:44.179Z dcmd[1172]:  cat: can't open '/tmp/logupload_http_code': No such file or directory
2025-11-25T21:00:44.327Z : /lib/rdk/uploadSTBLogs.sh: HttpLogUpload: Attempting direct log upload
2025-11-25T21:00:44.350Z : /lib/rdk/uploadSTBLogs.sh: RFC_EncryptCloudUpload_Enable:
2025-11-25T21:00:44.375Z : /lib/rdk/uploadSTBLogs.sh: MTLS defaulted
2025-11-25T21:00:44.400Z : /lib/rdk/uploadSTBLogs.sh: Connect with mTLS certificate from xPKI
2025-11-25T21:00:44.404Z dcmd[1172]:  /lib/rdk/uploadSTBLogs.sh: line 148: exec_curl_mtls: not found
2025-11-25T21:00:44.407Z dcmd[1172]:  cat: can't open '/tmp/logupload_http_code': No such file or directory
2025-11-25T21:00:44.524Z : /lib/rdk/uploadSTBLogs.sh: Curl Connected to xconf.rdkcentral.com () port
2025-11-25T21:00:44.550Z : /lib/rdk/uploadSTBLogs.sh: Connect with mTLS certificate from xPKI Curl return code: , http code:
2025-11-25T21:00:44.592Z : /lib/rdk/uploadSTBLogs.sh: HttpLogUpload: Direct log upload attempt return: retry=2, httpcode=
2025-11-25T21:01:44.616Z : /lib/rdk/uploadSTBLogs.sh: HttpLogUpload: Attempting direct log upload
2025-11-25T21:01:44.665Z : /lib/rdk/uploadSTBLogs.sh: RFC_EncryptCloudUpload_Enable:
2025-11-25T21:01:44.690Z : /lib/rdk/uploadSTBLogs.sh: MTLS defaulted
2025-11-25T21:01:44.725Z : /lib/rdk/uploadSTBLogs.sh: Connect with mTLS certificate from xPKI
2025-11-25T21:01:44.757Z dcmd[1172]:  /lib/rdk/uploadSTBLogs.sh: line 148: exec_curl_mtls: not found
2025-11-25T21:01:44.762Z dcmd[1172]:  cat: can't open '/tmp/logupload_http_code': No such file or directory
2025-11-25T21:01:44.845Z : /lib/rdk/uploadSTBLogs.sh: Curl Connected to xconf.rdkcentral.com () port
2025-11-25T21:01:44.880Z : /lib/rdk/uploadSTBLogs.sh: Connect with mTLS certificate from xPKI Curl return code: , http code:
2025-11-25T21:01:44.915Z : /lib/rdk/uploadSTBLogs.sh: HttpLogUpload: Direct log upload attempt return: retry=3, httpcode=
2025-11-25T21:02:44.951Z : /lib/rdk/uploadSTBLogs.sh: HttpLogUpload: Direct log upload failed: httpcode=
2025-11-25T21:02:44.980Z : /lib/rdk/uploadSTBLogs.sh: S3 upload query Failed
2025-11-25T21:02:45.018Z : /lib/rdk/uploadSTBLogs.sh: HTTP log upload failed
2025-11-25T21:02:45.030Z dcmd[1172]:  ls: /opt/logs/*.pcap*: No such file or directory
2025-11-25T21:02:50.054Z dcmd[1172]:  sh: /opt/logs/PreviousLogs/11-25-25-08-50PM-ConnectionStats.txt: unknown operand
2025-11-25T21:02:52.478Z : /lib/rdk/uploadSTBLogs.sh: Deleting from Previous Logs  Folder
2025-11-25T21:02:52.500Z IARM_event_send[6476]:  IARM_event_sender  Entering 6476

2025-11-25T21:02:52.501Z IARM_event_send[6476]:  >>>>> Send IARM_BUS_NAME EVENT current Event Name =LogUploadEvent,evenstatus=1
2025-11-25T21:02:52.527Z IARM_event_send[6476]:  >>>>> Generate IARM_BUS_NAME EVENT current Event Name =LogUploadEvent,eventstatus=1
2025-11-25T21:02:52.527Z IARM_event_send[6476]:  >>>>> IARM SUCCESS  Event Name =LogUploadEvent,sysStateEvent=45
2025-11-25T21:02:53.038Z IARM_event_send[6476]:  IARM_event_sender closing

2025-11-25T21:02:53.065Z IARM_event_send[6478]:  IARM_event_sender  Entering 6478

2025-11-25T21:02:53.066Z IARM_event_send[6478]:  >>>>> Send IARM_BUS_NAME EVENT current Event Name =MaintenanceMGR,evenstatus=5
2025-11-25T21:02:53.093Z IARM_event_send[6478]:  >>>>> Generate IARM_BUS_NAME EVENT current Event Name =MaintenanceMGR,eventstatus=5
2025-11-25T21:02:53.094Z IARM_event_send[6478]:  >>>>> Identified MaintenanceMGR
2025-11-25T21:02:53.102Z IARM_event_send[6478]:  >>>>> IARM SUCCESS  Event  = 5
2025-11-25T21:02:53.601Z IARM_event_send[6478]:  IARM_event_sender closing

Retrieving CPU instantaneous information for telemetry support
Retrieving virtual memory information for telemetry support
Retrieving CPU Temperature for telemetry support
root@raspberrypi4-64-rdke:~#

RDK Resources

[RDK Preferred]

Code Management Facility

RDK Forums

[RDK Conferences]

RDK Support

Archives

Introduction

Architecture

RDK Log Upload Mechanism

LogUploadProcess

Repository

How CPEs Upload Logs and Metrics

Configuration Details

Validation details

Pre-requisite

Steps to validate

Success Logs

RDK Resources

[*RDK Preferred*]

Code Management Facility

RDK Forums

[RDK Conferences]

RDK Support

Archives

RDK Log Upload - uploadSTBLogs.sh

Introduction

Architecture

RDK Log Upload Mechanism

LogUploadProcess

Repository

How CPEs Upload Logs and Metrics

Configuration Details

Validation details

Pre-requisite

Steps to validate

Success Logs

[RDK Preferred]