Gunakan log runtime untuk membantu mendiagnosis masalah pada pod apigee-runtime. Setiap pod runtime berisi pemroses pesan, yang bertanggung jawab untuk memproses traffic proxy API, menjalankan kebijakan, merutekan permintaan, dan lainnya.
Menggunakan log runtime
Log adalah cara yang baik untuk memecahkan masalah terkait penginstalan Anda. Lihat
Logging untuk mengetahui detailnya.
Menggunakan perintah log
Anda dapat melihat log sistem runtime menggunakan perintah kubectl logs. Contoh:
Setelah shell pod terbuka, Anda dapat menemukan log pemroses pesan campuran di bagian
/opt/apigee/var/log/apigee-runtime/config.log.
Informasi versi kontrak
Tabel berikut menjelaskan secara singkat entri log yang terkait dengan pemuatan kontrak dari bidang pengelolaan:
Entri Log
Arti
hybrid-runtime Apigee-Timer-9 INFO RUNTIME-SYNC-SERVICE -
RuntimeSyncServiceImpl.updateToVersion() : Switched to newer version
750 from version null
MP berubah menjadi kontrak konfigurasi versi yang lebih baru.
hybrid-runtime Apigee-Timer-6 INFO RUNTIME-SYNC-SERVICE -
RuntimeSyncServiceImpl.loadLatestVersionIfAvailable() : Found a newer
version 750
MP memuat versi konfigurasi kontrak terbaru dari version.properties.
hybrid-runtime Apigee-Timer-6 INFO RUNTIME-SYNC-SERVICE -
RuntimeSyncServiceImpl.updateToVersion() : Attempting to update to a newer version 750
MP diupdate ke versi kontrak konfigurasi yang lebih baru.
hybrid-runtime Apigee-Timer-6 INFO RUNTIME-SYNC-SERVICE -
RuntimeSyncServiceImpl.updateToVersion() : Switched to newer version 751 from version 750
MP memuat versi konfigurasi kontrak terbaru dari version.properties.
Error saat deployment
Error runtime berikut terkait dengan deployment proxy:
Entri Log
Arti
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
Keyspace cache_orgname_hybrid tidak disediakan di Cassandra.
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
Keyspace kms_orgname_hybrid tidak disediakan di Cassandra.
Log error deployment pemroses pesan
Cari entri error deployment berikut di log pemroses pesan:
Entri log
Deskripsi
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
Ruang kunci 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
Keyspace kms_orgname_hybrid tidak disediakan di Cassandra.
Kode error pemroses pesan
Kode error untuk pemroses pesan dimulai dengan runtime.sync.error-name.
Contoh:
Alasan: Error ini dapat disebabkan oleh skema yang tidak valid, file spesifikasi
kontrak yang rusak, atau
kontrak yang tidak valid. Masalah apa pun dari masalah ini dapat mencegah pemroses pesan memuat file spec.
Solusi: Pastikan file spesifikasi kontrak tersedia, sistem file tidak rusak, atau skema/kontrak valid.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-05 UTC."],[[["\u003cp\u003eThis documentation version (1.4) is end-of-life, and users should upgrade to a newer, supported version for continued support and updates.\u003c/p\u003e\n"],["\u003cp\u003eRuntime logs are essential for diagnosing issues within \u003ccode\u003eapigee-runtime\u003c/code\u003e pods, which handle API proxy traffic, policy execution, and request routing.\u003c/p\u003e\n"],["\u003cp\u003eLogs can be accessed through the \u003ccode\u003ekubectl logs\u003c/code\u003e command for real-time viewing or by opening a shell in the \u003ccode\u003eapigee-runtime\u003c/code\u003e pod to navigate the filesystem logs located at \u003ccode\u003e/opt/apigee/var/log/apigee-runtime/config.log\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe logs provide information on contract version updates, detailing when the management plane (MP) switches to or loads newer contract versions.\u003c/p\u003e\n"],["\u003cp\u003eLogs also show errors related to message processor deployments, such as missing keyspaces in Cassandra or issues with loading the contract specification file.\u003c/p\u003e\n"]]],[],null,["# Runtime logs\n\n| You are currently viewing version 1.4 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.4/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:"]]
