You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2019/09/10 11:12:12 UTC

[GitHub] [skywalking] zhaoxunyong opened a new issue #3448: Clients of Skywalking cannot be register by themselves.

zhaoxunyong opened a new issue #3448: Clients of Skywalking cannot be register by themselves.
URL: https://github.com/apache/skywalking/issues/3448
 
 
   Please answer these questions before submitting your issue.
   
   - Why do you submit this issue?
   - [ ] Question or discussion
   - [ ] Bug
   - [ ] Requirement
   - [ ] Feature or performance improvement
   
   ___
   ### Bug
   - Which version of SkyWalking, OS and JRE?
   SkyWalking: 6.3.0
   OS: 7.6.1810
   JRE: 1.8
   
   - What happen?
   
   My skywalking has the error - "java.lang.OutOfMemoryError: Java heap space" occurred. After I adjusted the JVM options and reboot the server(not agent), but I found some of my clients could't be register by themselves. the logs as the following:
   
   The angent logs:
   ---------------------------
   DEBUG 2019-09-10 18:10:15:408 SkywalkingAgent-4-ServiceAndEndpointRegisterClient-0 ServiceAndEndpointRegisterClient :  ServiceAndEndpointRegisterClient running, status:DISCONNECT.
   
   2019-09-10 19:06:23,556 - org.apache.skywalking.oap.server.core.register.service.ServiceInstanceInventoryRegister - 108 [grpc-default-executor-36] WARN  [] - Service instance 177 heartbeat, but not found in storage. 2019-09-10 19:06:23,557 - org.apache.skywalking.oap.server.receiver.register.provider.handler.v6.grpc.ServiceInstancePingServiceHandler - 68 [grpc-default-executor-36] WARN  [] - Can't find service by service instance id from cache, service instance id is: 177, will send a reset command to agent side
   
   
   I thought rebooting the agant will be recovered. I rememberd this version will register by themselves automatically, I don't need to restart angent any more. but why will it happen?
   
   Please help me out to to diagnose the issues. 
   
   Thanks~

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services