您正在查看 Apigee Edge 說明文件。
查看 Apigee X 說明文件。 資訊
問題
透過 Edge UI 或 Edge Management API 部署 API Proxy 修訂版本失敗,並顯示 ZooKeeper 的「擷取子項時發生錯誤」。
錯誤訊息
Error in deployment for environment prod. The revision is deployed, but traffic cannot flow. com.apigee.repository.RepositoryException{ code = repository.zookeeper.UnExpectedError, message = Unexpected error Error while fetching children for path : /organizations/myorg/environments/prod/apiproxies/tinkerbell/revisions, associated contexts = []};
可能原因
發生這個錯誤的常見原因是訊息處理器和 ZooKeeper 之間的網路連線問題。
診斷
注意:只有 Edge Private Cloud 使用者可以執行下列步驟。如果您使用的是 Edge Public Cloud,請與 Apigee Edge 支援團隊聯絡。
- 使用下列管理 API 呼叫,取得顯示錯誤的特定 API 部署狀態輸出內容:
curl -v http://<management-server-IPaddress>:<port#>/organizations/<orgname>/environments/<envname>/apis/<apiname>/deployments -u <username>
顯示錯誤的部署狀態輸出內容範例:
{ "environment" : [ { "name" : "prod", "revision" : [ { "configuration" : { "basePath" : "/", "steps" : [ ] }, "name" : "1", "server" : [ { "error" : "com.apigee.repository.RepositoryException: com.apigee.zookeeper.ZooKeeperException{ code = zookeeper.ErrorFetchingChildren, message = Error while fetching children for path : /organizations/gsc/environments/prod/apiproxies/apigee_test/revisions, associated contexts = []}", "status" : "error", "type" : [ "message-processor" ], "uUID" : "01fc5b23-8ad3-40bf-b059-2fc82cdac111" },
- 檢查訊息處理器 (
/opt/apigee/var/log/edge-message-processor/system.log
)。郵件處理器記錄中的錯誤範例
2017-05-29 01:25:40,592 main ERROR KERNEL - MicroKernel.deployAll() : MicroKernel.deployAll() : Error in deploying the deployment : WebService com.apigee.zookeeper.ZooKeeperException: Error while checking path existence for path : /regions/dc-2/pods/gateway/servers/099c2603-93a4-4b73-ae03-a55d130adb80/reachable at com.apigee.zookeeper.impl.ZooKeeperServiceImpl.exists(ZooKeeperServiceImpl.java:410) ~[zookeeper-1.0.0.jar:na] at com.apigee.zookeeper.impl.ZooKeeperServiceImpl.exists(ZooKeeperServiceImpl.java:394) ~[zookeeper-1.0.0.jar:na] at com.apigee.services.repository.zookeeper.ZKRepository.exists(ZKRepository.java:280) ~[repository-impl-1.0.0.jar:na] at com.apigee.services.repository.RepositoryServiceImpl.exists(RepositoryServiceImpl.java:234) ~[repository-impl-1.0.0.jar:na] at com.apigee.registration.info.StatusBuilder.build(StatusBuilder.java:26) ~[registration-1.0.0.jar:na] at com.apigee.registration.ServerRegistrationServiceImpl.buildServerInfo(ServerRegistrationServiceImpl.java:856) ~[registration-1.0.0.jar:na] at com.apigee.registration.ServerRegistrationServiceImpl.start(ServerRegistrationServiceImpl.java:122) ~[registration-1.0.0.jar:na] at com.apigee.kernel.service.deployment.ServiceDeployer.startService(ServiceDeployer.java:167) ~[microkernel-1.0.0.jar:na] at com.apigee.kernel.service.deployment.ServiceDeployer.deploy(ServiceDeployer.java:70) ~[microkernel-1.0.0.jar:na] at com.apigee.kernel.service.deployment.ServiceDeployer.deployDependantServices(ServiceDeployer.java:356) ~[microkernel-1.0.0.jar:na] at com.apigee.kernel.service.deployment.ServiceDeployer.deploy(ServiceDeployer.java:76) ~[microkernel-1.0.0.jar:na] at com.apigee.kernel.service.deployment.ServiceDeployer.deployDependantServices(ServiceDeployer.java:356) ~[microkernel-1.0.0.jar:na] at com.apigee.kernel.service.deployment.ServiceDeployer.deploy(ServiceDeployer.java:76) ~[microkernel-1.0.0.jar:na] at com.apigee.kernel.MicroKernel.deployAll(MicroKernel.java:178) [microkernel-1.0.0.jar:na] at com.apigee.kernel.MicroKernel.start(MicroKernel.java:139) [microkernel-1.0.0.jar:na] at com.apigee.kernel.MicroKernel.start(MicroKernel.java:135) [microkernel-1.0.0.jar:na] at com.apigee.kernel.MicroKernel.main(MicroKernel.java:84) [microkernel-1.0.0.jar:na] Caused by: org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /regions/dc-2/pods/gateway/servers/099c2603-93a4-4b73-ae03-a55d130adb80/reachable at org.apache.zookeeper.KeeperException.create(KeeperException.java:99) ~[zookeeper-3.4.6.jar:3.4.6-1569965] at org.apache.zookeeper.KeeperException.create(KeeperException.java:51) ~[zookeeper-3.4.6.jar:3.4.6-1569965] at org.apache.zookeeper.ZooKeeper.exists(ZooKeeper.java:1045) ~[zookeeper-3.4.6.jar:3.4.6-1569965] at org.apache.zookeeper.ZooKeeper.exists(ZooKeeper.java:1073) ~[zookeeper-3.4.6.jar:3.4.6-1569965] at com.apigee.zookeeper.impl.ZooKeeperServiceImpl.exists(ZooKeeperServiceImpl.java:402) ~[zookeeper-1.0.0.jar:na] ... 16 common frames omitted
- 如果您發現上述示例中的類似錯誤,請執行下列步驟:
- 請執行下列步驟,測試從訊息處理器與通訊埠 2181 上的 ZooKeeper 伺服器的連線:
- 如果可以使用 telnet,請使用 telnet:
telnet <ZooKeeper-IP> 2181
- 如果無法使用 telnet,請按照下列步驟使用 netcat 檢查連線:
nc -vz <ZooKeeper-IP> 2181
- 如果您收到「連線遭拒」或「連線逾時」回應,請與網路作業團隊聯絡。請參閱下方的「解析度」部分。
- 如果可以使用 telnet,請使用 telnet:
- 請執行下列步驟,測試從訊息處理器與通訊埠 2181 上的 ZooKeeper 伺服器的連線:
- 如果你發現任何其他情況,請與 Apigee Edge 支援團隊聯絡。
解析度
注意:只有 Edge Private Cloud 使用者可以執行下列步驟。如果您使用的是 Edge Public Cloud,請與 Apigee Edge 支援團隊聯絡。
- 與聯播網團隊合作執行以下動作:
-
- 確保訊息處理器與通訊埠 2181 上的所有 ZooKeeper 節點之間都能連線。
- 請從郵件處理器中移除所有防火牆限製或安全性規則設定,以允許連線至 ZooKeeper 伺服器上的通訊埠 2181。
- 如果「訊息處理器」發生網路問題,依據部署狀態輸出內容,重新啟動顯示錯誤的特定「訊息處理器」或許就能解決問題。重新啟動特定訊息處理器:
/opt/apigee/apigee-service/bin/apigee-service edge-message-processor restart
如果問題持續發生,請與 Apigee Edge 支援團隊聯絡。
-