Add RFC log interpretation documentation

[Copilot]

Users misinterpret "NOT IN RFC!" log messages as errors when checking if RFC is operational. This message indicates a feature is not configured on the xconf server—expected behavior that defaults to disabled.

Changes

• README.md: Repository overview, quick start guide, component descriptions
• docs/RFC_LOG_INTERPRETATION.md: Comprehensive log interpretation guide including:
  • Normal startup sequence indicators
  • Feature state patterns (configured enabled/disabled vs unconfigured)
  • Common scenarios with log examples
  • Troubleshooting workflow

Key clarifications

"NOT IN RFC!" is not an error. It means:

[IFE]:: Requesting WIFI_TM_DC (RFC_ENABLE_WIFI_TM_DC) NOT IN RFC!
[IFE]:: isFeatureEnabled WIFI_TM_DC Returns 0

• Feature config file /opt/secure/RFC/.RFC_WIFI_TM_DC.ini does not exist
• System defaults to disabled (returns 0)
• RFC can be fully operational while showing these messages

RFC is working if logs show:

RFC:Device is Online
getRFCParameter: http server is ready
curl response : 0 http response code: 200

Documentation includes example analysis matching the original question's log pattern.

Original prompt

cat rfcscript.log
2026-01-19T17:54:54.309Z [RFC] Requesting /opt/secure/RFC/.RFC_CGROUPENABLE.ini
2026-01-19T17:54:54.402Z [RFC] Requesting /opt/secure/RFC/.RFC_CGROUPENABLE.ini
2026-01-20T01:18:06.678Z [RFC] Requesting /opt/secure/RFC/.RFC_IDS.ini
2026-01-20T01:18:08.120Z [RFC] Requesting /opt/secure/RFC/.RFC_WEBKIT_INSPECTOR.ini
2026-01-20T01:18:11.679Z [RFC] Requesting /opt/secure/RFC/.RFC_SLAACSUPPORT.ini
2026-01-20T01:18:14.535Z [RFC] Requesting /opt/secure/RFC/.RFC_WEBAUTOMATION.ini
Conf file /etc/debug.ini open success
IARM_Bus_IsConnected invalid state
IARM_Init group name = com.comcast.rdk.iarm.bus member name = RDKVRFCMgrEvent
setting init done
Registering RDKVRFCMgrEvent
dispatchThread RDKVRFCMgrEvent launched
260120-01:23:29.914153 [mod=RFCMGR, lvl=INFO] [tid=9301] [main][98] RFC: Starting service, creating lock
260120-01:23:29.914547 [mod=RFCMGR, lvl=INFO] [tid=9301] [main][114] Waiting for IP Acquistion
260120-01:23:29.914582 [mod=RFCMGR, lvl=INFO] [tid=9301] [CheckDeviceIsOnline][319] Checking IP and Route configuration
260120-01:23:29.914638 [mod=RFCMGR, lvl=INFO] [tid=9301] [CheckIProuteConnectivity][218] Received Route Config file
260120-01:23:29.914708 [mod=RFCMGR, lvl=INFO] [tid=9301] [CheckIProuteConnectivity][231] ip address=IPV6 fe80::aedb:48ff:fe06:3382

260120-01:23:29.914749 [mod=RFCMGR, lvl=INFO] [tid=9301] [CheckDeviceIsOnline][324] Checking IP and Route configuration found
260120-01:23:29.914773 [mod=RFCMGR, lvl=INFO] [tid=9301] [CheckDeviceIsOnline][325] Checking DNS Nameserver configuration
260120-01:23:29.914835 [mod=RFCMGR, lvl=INFO] [tid=9301] [CheckDeviceIsOnline][328] DNS Nameservers are available
260120-01:23:29.914860 [mod=RFCMGR, lvl=INFO] [tid=9301] [main][116] Starting execution of RFCManager
260120-01:23:29.914881 [mod=RFCMGR, lvl=INFO] [tid=9301] [main][120] RFC:Device is Online
260120-01:23:29.915133 [mod=RFCAPI, lvl=INFO] [tid=9301] getRFCParameter: http server is ready
260120-01:23:29.918081 [mod=RFCAPI, lvl=INFO] [tid=9301] getRFCParam data = {"names" : ["Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Identity.DbgServices.Enable"]}, datalen = 82
260120-01:23:29.931946 [mod=RFCAPI, lvl=INFO] [tid=9301] curl response : 0 http response code: 200
260120-01:23:29.932618 [mod=RFCAPI, lvl=INFO] [tid=9301] Curl response: {
"parameters": [{
"name": "Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Identity.DbgServices.Enable",
"value": "false",
"dataType": 3,
"parameterCount": 1,
"message": "Default Value"
}],
"statusCode": 38
}
260120-01:23:29.932793 [mod=RFCMGR, lvl=INFO] [tid=9301] [read_RFCProperty][191] RFC name=Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Identity.DbgServices.Enable,type=3,value=false,status=38
260120-01:23:29.932829 [mod=RFCMGR, lvl=INFO] [tid=9301] [isDebugServicesEnabled][148] rfc Debug services = false
260120-01:23:29.932877 [mod=RFCAPI, lvl=INFO] [tid=9301] getRFCParam data = {"names" : ["Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Bootstrap.XconfUrl"]}, datalen = 73
260120-01:23:29.937278 [mod=RFCAPI, lvl=INFO] [tid=9301] curl response : 0 http response code: 200
260120-01:23:29.938622 [mod=RFCAPI, lvl=INFO] [tid=9301] Curl response: {
"parameters": [{
"name": "Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Bootstrap.XconfUrl",
"value": "https://secure.xconfds.coast.xcal.tv",
"dataType": 0,
"parameterCount": 1,
"message": "Success"
}],
"statusCode": 0
}
260120-01:23:29.938737 [mod=RFCMGR, lvl=INFO] [tid=9301] [read_RFCProperty][191] RFC name=Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Bootstrap.XconfUrl,type=0,value=https://secure.xconfds.coast.xcal.tv,status=0
260120-01:23:29.938763 [mod=RFCMGR, lvl=INFO] [tid=9301] XconfUrl: = https://secure.xconfds.coast.xcal.tv, found after 1 attempts
260120-01:23:29.939139 [mod=COMMONUTILITIES, lvl=INFO] [tid=9301] getDevicePropertyData : Trying device property data for WHOAMI_SUPPORT and buf size=8
260120-01:23:29.939231 [mod=RFCMGR, lvl=ERROR] [tid=9301] [checkWhoamiSupport][129] Failed to get WHOAMI_SUPPORT property. Status: -1
260120-01:23:29.939266 [mod=RFCMGR, lvl=INFO] [tid=9301] GetRFCPartnerID: PartnerID = xglobal
260120-01:23:29.939478 [mod=RFCMGR, lvl=INFO] [tid=9301] [GetServURL][1119] _xconf_server_url: [https://xconf.xcal.tv/featureControl/getSettings]
260120-01:23:29.939604 [mod=COMMONUTILITIES, lvl=INFO] [tid=9301] doCurlInit: curl init success
260120-01:23:29.939647 [mod=COMMONUTILITIES, lvl=INFO] [tid=9301] getJsonRpcData : CURL: Setting For jsonrpc_auth_token
260120-01:23:29.952560 [mod=COMMONUTILITIES, lvl=INFO] [tid=9301] Curl Connected to http://127.0.0.1:9998/jsonrpc (127.0.0.1) port 9998
260120-01:23:29.952631 [mod=COMMONUTILITIES, lvl=INFO] [tid=9301] Curl return code...

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.