我们可以看到我们的Jfrog服务经常关闭，我们已经配置了Crontab，它可以立即启动Jfrog。
但这里的问题是它影响了我们的jenkins构建，并且除了router-service.log之外，日志中没有错误。
下面包括了router-service log。
2022-10-13T18:53:50.522Z [jfrou] [ERROR] [03d6f1c55eb36f37] [external_topology.go:79 ] [main ] [] - Failed fetching external topology from Access: Get "http://localhost:8040/access/api/v1/topology": context deadline exceeded
2022-10-13T18:53:55.093Z [jfrou] [ERROR] [34485554c5ada198] [local_topology.go:134 ] [main ] [] - periodic send heartbeat failed for 175 consecutive times. Last error: failed sending heartbeat information to Access: failed closing Access grpc client: closing heartbeat client and waiting for response timed-out
2022-10-13T18:53:55.197Z [jfrou] [WARN ] [226f3a72430aaafe] [local_topology.go:274 ] [main ] [] - Readiness test failed with the following error: "required node services are missing or unhealthy"
2022-10-13T18:54:00.199Z [jfrou] [ERROR] [226f3a72430aaafe] [local_topology.go:134 ] [main ] [] - periodic send heartbeat failed for 176 consecutive times. Last error: failed sending heartbeat information to Access: failed closing Access grpc client: closing heartbeat client and waiting for response timed-out
2022-10-13T18:54:00.302Z [jfrou] [WARN ] [4081475d82aceec3] [local_topology.go:274 ] [main ] [] - Readiness test failed with the following error: "required node services are missing or unhealthy"
2022-10-13T18:54:05.304Z [jfrou] [ERROR] [4081475d82aceec3] [local_topology.go:134 ] [main ] [] - periodic send heartbeat failed for 177 consecutive times. Last error: failed sending heartbeat information to Access: failed closing Access grpc client: closing heartbeat client and waiting for response timed-out
2022-10-13T18:54:05.407Z [jfrou] [WARN ] [492a2b85447ed5b2] [local_topology.go:274 ] [main ] [] - Readiness test failed with the following error: "required node services are missing or unhealthy"
2022-10-13T18:54:05.623Z [jfrou] [ERROR] [32aa341a8a54b5e8] [external_topology.go:79 ] [main ] [] - Failed fetching external topology from Access: Get "http://localhost:8040/access/api/v1/topology": context deadline exceeded
2022-10-13T18:54:10.409Z [jfrou] [ERROR] [492a2b85447ed5b2] [local_topology.go:134 ] [main ] [] - periodic send heartbeat failed for 178 consecutive times. Last error: failed sending heartbeat information to Access: failed closing Access grpc client: closing heartbeat client and waiting for response timed-out
2022-10-13T18:54:10.513Z [jfrou] [WARN ] [59da1d3d86839010] [local_topology.go:274 ] [main ] [] - Readiness test failed with the following error: "required node services are missing or unhealthy"
2022-10-13T18:54:15.514Z [jfrou] [ERROR] [59da1d3d86839010] [local_topology.go:134 ] [main ] [] - periodic send heartbeat failed for 179 consecutive times. Last error: failed sending heartbeat information to Access: failed closing Access grpc client: closing heartbeat client and waiting for response timed-out
2022-10-13T18:54:15.617Z [jfrou] [WARN ] [034ba642a0140355] [local_topology.go:274 ] [main ] [] - Readiness test failed with the following error: "required node services are missing or unhealthy"
2022-10-13T18:54:20.619Z [jfrou] [ERROR] [034ba642a0140355] [local_topology.go:134 ] [main ] [] - periodic send heartbeat failed for 180 consecutive times. Last error: failed sending heartbeat information to Access: failed closing Access grpc client: closing heartbeat client and waiting for response timed-out任何人都可以让我们知道这个问题的原因或可能性是什么？
1条答案
按热度按时间w9apscun1#
根据错误片段，问题似乎与Access Service有关，该服务不接受来自路由器的任何连接，并且请求超时。
首先，检查access-service.log中的日志，这将有助于处理正确的错误。
这可能是因为访问服务过载，连接数已用完。一个可能的原因是检查为任何CI用户配置的任何过期/不正确的密码，这可能会在频繁重试的情况下对访问服务造成巨大负载。