arugal commented on pull request #4624:
URL: https://github.com/apache/skywalking/pull/4624#issuecomment-618807919


   > Health check fail logs:
   > 
   > ```
   > start container of testcase.name=vertx-web-3.x-scenario-3.7.0
   > WARNING: Your kernel does not support swap limit capabilities or the 
cgroup is not mounted. Memory limited without swap.
   > 2020-04-09 06:15:32.231:INFO::main: Logging initialized @493ms to 
org.eclipse.jetty.util.log.StdErrLog
   > 2020-04-09 06:15:32.499:INFO:oejs.Server:main: jetty-9.4.2.v20170220
   > 2020-04-09 06:15:32.569:INFO:oejsh.ContextHandler:main: Started 
o.e.j.s.ServletContextHandler@d29f28{/,null,AVAILABLE}
   > 2020-04-09 06:15:32.576:INFO:oejs.AbstractConnector:main: Started 
ServerConnector@1151e434{HTTP/1.1,[http/1.1]}{0.0.0.0:12800}
   > 2020-04-09 06:15:32.577:INFO:oejs.Server:main: Started @839ms
   > SLF4J: Class path contains multiple SLF4J bindings.
   > SLF4J: Found binding in 
[jar:file:/run/vertx-web-3.x-scenario/libs/vertx-web-3.x-scenario.jar!/BOOT-INF/lib/logback-classic-1.1.11.jar!/org/slf4j/impl/StaticLoggerBinder.class]
   > SLF4J: Found binding in 
[jar:file:/run/vertx-web-3.x-scenario/libs/vertx-web-3.x-scenario.jar!/BOOT-INF/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
   > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
explanation.
   > SLF4J: Actual binding is of type 
[ch.qos.logback.classic.util.ContextSelectorStaticBinder]
   >  health check failed!-scenario-3.7.0 
url=http://localhost:8080/vertx-web-3-scenario/case/healthCheck, 
status=HTTP/1.1 404 Not Found
   > hostname: brandon-XPS-15-7590(127.0.1.1) 
   > ```
   
   Hi @BFergerson @dmsolr 
   We don't seem to have solved the problem, right? 


----------------------------------------------------------------
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:
[email protected]


Reply via email to