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
MP 将更新到合同的较新版本。
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 中没有预配键空间 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 中没有预配键空间 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"]],["最后更新时间 (UTC)：2025-09-03。"],[[["\u003cp\u003eThis document provides guidance on using runtime logs to diagnose problems with Apigee hybrid's \u003ccode\u003eapigee-runtime\u003c/code\u003e pods, which manage API proxy traffic and policy execution.\u003c/p\u003e\n"],["\u003cp\u003eRuntime system logs can be accessed using the \u003ccode\u003ekubectl logs\u003c/code\u003e command, allowing for real-time monitoring of pod activity and troubleshooting of issues, such as errors.\u003c/p\u003e\n"],["\u003cp\u003eLog entries provide detailed information about the loading of contract configurations from the management plane, including version changes and loading the most recent contract.\u003c/p\u003e\n"],["\u003cp\u003eDeployment errors, particularly those related to missing keyspaces in Cassandra, are documented in the logs, along with steps to identify and address these problems.\u003c/p\u003e\n"],["\u003cp\u003eMessage processor error codes, identifiable by the \u003ccode\u003eruntime.sync.\u003c/code\u003e prefix, offer insights into issues like contract loading failures and recommend resolutions for problems like corrupted files.\u003c/p\u003e\n"]]],[],null,["# Runtime logs\n\n| You are currently viewing version 1.10 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.10/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 apigee apigee-runtime-apigee-gcp-prod1-test-blue-hd77q\n```\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:"]]
