Google 会使用 AI 技术将内容翻译成您偏好的语言。AI 翻译可能包含错误。

提取路径的子项时出错

您正在查看 Apigee Edge 文档。
转到 Apigee X 文档。 info

问题

通过 Edge 界面或 Edge 管理 API 部署 API 代理修订版本失败，并显示 ZooKeeper 错误 "Error while fetching children for path"。

错误消息

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

如果您观察到与上例中所示类似的错误，请执行以下步骤：
1. 按照以下步骤测试从消息处理器到 ZooKeeper 服务器在端口 2181 上的连接：
  1. 如果 telnet 可用，请使用 telnet：
```
telnet <ZooKeeper-IP> 2181
```
  2. 如果 telnet 不可用，请使用 netcat 检查连接，如下所示：
```
nc -vz <ZooKeeper-IP> 2181
```
  3. 如果您收到“Connection Refused”或“Connection timed out”响应，请与您的网络运营团队联系。请参阅下面的解决方案 部分。
如果您观察到任何其他问题，请与 Apigee Edge 支持团队联系。

解决方案

注意：只有 Edge Private Cloud 用户可以执行以下步骤。如果您使用的是 Edge Public Cloud，请与 Apigee Edge 支持团队联系。

与您的网络团队合作，以：
1. 1. 确保消息处理器和所有 ZooKeeper 节点之间在端口 2181 上允许连接。
  2. 移除消息处理器中的任何防火墙限制或安全规则设置，以允许连接到 ZooKeeper 服务器上的端口 2181。
2. 如果消息处理器存在网络问题，则重新启动显示错误的特定消息处理器（根据部署状态输出）可能会解决该问题。重新启动特定消息处理器：
```
/opt/apigee/apigee-service/bin/apigee-service edge-message-processor restart
```
如果问题仍然存在，请与 Apigee Edge 支持团队联系。