開啟 Pod 殼層後，您可以在 /opt/apigee/var/log/apigee-runtime/config.log 下方找到混合訊息處理器記錄。
合約版本資訊
下表簡要說明從管理層載入合約的相關記錄項目：
記錄項目
意義
hybrid-runtime Apigee-Timer-9 INFO RUNTIME-SYNC-SERVICE -
RuntimeSyncServiceImpl.updateToVersion() : Switched to newer version
750 from version null
MP 已改用較新版本的設定合約。
hybrid-runtime Apigee-Timer-6 INFO RUNTIME-SYNC-SERVICE -
RuntimeSyncServiceImpl.loadLatestVersionIfAvailable() : Found a newer
version 750
MP 從 version.properties 載入最新的合約設定版本。
hybrid-runtime Apigee-Timer-6 INFO RUNTIME-SYNC-SERVICE -
RuntimeSyncServiceImpl.updateToVersion() : Attempting to update to a newer version 750
管理員端程式會更新至較新的設定合約版本。
hybrid-runtime Apigee-Timer-6 INFO RUNTIME-SYNC-SERVICE -
RuntimeSyncServiceImpl.updateToVersion() : Switched to newer version 751 from version 750
MP 從 version.properties 載入最新的合約設定版本。
部署錯誤
下列執行階段錯誤與快取代理程式部署作業有關：
記錄項目
意義
hybrid-runtime org:hybrid env:prod Apigee-Main-6 ERROR i.a.h.e.i.HermesEngineImpl
- HermesEngineImpl.handleHermesException() : Keyspace cache_hybrid_hybrid does not exist
在 Cassandra 中未佈建 Keyspace cache_orgname_hybrid。
hybrid-runtime org:hybrid Apigee-Timer-9 ERROR c.a.s.e.k.HybridEncryptionKeyServiceImpl
- HybridEncryptionKeyServiceImpl.getEncryptionKey() : Encryption key does not exist for
organization hybrid and type KmsKey
在 Cassandra 中未佈建 Keyspace kms_orgname_hybrid。
訊息處理工具部署錯誤記錄
在訊息處理器記錄中尋找下列部署錯誤項目：
記錄項目
說明
hybrid-runtime org:hybrid env:prod Apigee-Main-6 ERROR i.a.h.e.i.HermesEngineImpl - HermesEngineImpl.handleHermesException() : Keyspace cache_hybrid_hybrid does not exist
鍵空間 cache_orgname_hybrid is not provisioned in Cassandra.
hybrid-runtime org:hybrid Apigee-Timer-9 ERROR c.a.s.e.k.HybridEncryptionKeyServiceImpl - HybridEncryptionKeyS erviceImpl.getEncryptionKey() : Encryption key does not exist for organization hybrid and type KmsKey
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eThis documentation version 1.5 is end of life and users should upgrade to a newer version, as indicated in the supported versions section.\u003c/p\u003e\n"],["\u003cp\u003eRuntime logs are useful for troubleshooting \u003ccode\u003eapigee-runtime\u003c/code\u003e pod issues, as these pods contain message processors that handle API proxy traffic and policy execution.\u003c/p\u003e\n"],["\u003cp\u003eYou can use the \u003ccode\u003ekubectl logs\u003c/code\u003e command to view real-time runtime system logs, providing insights into the status and behavior of the runtime pods.\u003c/p\u003e\n"],["\u003cp\u003eMessage processor log files can also be accessed directly on the \u003ccode\u003eapigee-runtime\u003c/code\u003e pod's filesystem in the \u003ccode\u003e/opt/apigee/var/log/apigee-runtime/config.log\u003c/code\u003e directory, which requires using \u003ccode\u003ekubectl exec\u003c/code\u003e to open a shell in the pod.\u003c/p\u003e\n"],["\u003cp\u003eLog entries related to contract loading and deployment errors, including keyspace issues and error codes such as \u003ccode\u003eruntime.sync.ContractLoadFailedMessage\u003c/code\u003e, can help identify and resolve configuration and deployment problems within the runtime environment.\u003c/p\u003e\n"]]],[],null,["# Runtime logs\n\n| You are currently viewing version 1.5 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nUse the runtime logs to help diagnose problems with the `apigee-runtime` pods. Each\nruntime pod contains a message processor, which is responsible for processing API proxy traffic,\nexecuting policies, routing requests, and more.\n\nUsing runtime logs\n------------------\n\n\nLogs are a good way to troubleshoot problems with your installation. See\n[Logging](/apigee/docs/hybrid/v1.5/logging) for details.\n\n### Use the logs command\n\n\nYou can view runtime system logs using the `kubectl logs` command. For example: \n\n```\nkubectl logs -f -n hybrid apigee-runtime-apigee-gcp-prod1-test-blue-hd77q\n```\n\n### Viewing logs on the filesystem\n\n\u003cbr /\u003e\n\n\nYou can find the message processor log files on the `apigee-runtime` pod's\nfilesystem. To view the files, open a shell in an `apigee-runtime` pod: \n\n```\nkubectl exec -it -n namespace apigee-runtime-pod-name bash\n```\n\nFor example: \n\n```\nkubectl exec -it -n hybrid apigee-runtime-apigee-gcp-prod1-test-blue-cnj5x bash\n```\n\nOnce you have the pod shell open, you can find hybrid message processor logs under\n\n`/opt/apigee/var/log/apigee-runtime/config.log`.\n\n### Contract version information\n\n\nThe following table briefly describes log entries related to loading the contract from the management plane:\n\n### Deployment errors\n\n\nThe following runtime errors relate to proxy deployments:\n\n### Message processor deployment error logs\n\nLook for the following deployment error entries in the message processor logs:\n\nMessage processor error codes\n-----------------------------\n\n\nError codes for the message processor start with `runtime.sync.`\u003cvar translate=\"no\"\u003eerror-name\u003c/var\u003e.\nFor example:"]]
