mesos / logstash

Logstash on Mesos

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Core dump (outside of DCOS)

wegel opened this issue · comments

commented

Hi,

Is this supported outside of DCOS? When I try to manually run the logstash-scheduler like so:

docker run --net=host -e 'JAVA_OPTS=-Xmx256m -Dmesos.logstash.web.port=9092 -Dmesos.logstash.framework.name=logstash -Dmesos.logstash.logstash.heap.size=512 -Dmesos.logstash.executor.heap.size=256 -Dmesos.zk=zk://127.0.0.1:2181/mesos -Dmesos.logstash.volumes=/var/log/mesos' mesos/logstash-scheduler:0.0.6

...I'm getting a core dump:

15:53:01.543 [main] INFO  o.a.m.logstash.scheduler.Application - Starting Application with PID 9 (/tmp/logstash-scheduler.jar started by root in /)
15:53:01.554 [main] DEBUG o.a.m.logstash.scheduler.Application - Running with Spring Boot v1.2.5.RELEASE, Spring v4.1.7.RELEASE
15:53:02.344 [main] INFO  o.s.b.c.e.AnnotationConfigEmbeddedWebApplicationContext - Refreshing org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@7f38eabc: startup date [Wed Sep 16 15:53:02 UTC 2015]; root of context hierarchy
15:53:04.984 [main] INFO  o.s.b.f.s.DefaultListableBeanFactory - Overriding bean definition for bean 'beanNameViewResolver': replacing [Root bean: class [null]; scope=; abstract=false; lazyInit=false; autowireMode=3; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=org.springframework.boot.autoconfigure.web.ErrorMvcAutoConfiguration$WhitelabelErrorViewConfiguration; factoryMethodName=beanNameViewResolver; initMethodName=null; destroyMethodName=(inferred); defined in class path resource [org/springframework/boot/autoconfigure/web/ErrorMvcAutoConfiguration$WhitelabelErrorViewConfiguration.class]] with [Root bean: class [null]; scope=; abstract=false; lazyInit=false; autowireMode=3; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=org.springframework.boot.autoconfigure.web.WebMvcAutoConfiguration$WebMvcAutoConfigurationAdapter; factoryMethodName=beanNameViewResolver; initMethodName=null; destroyMethodName=(inferred); defined in class path resource [org/springframework/boot/autoconfigure/web/WebMvcAutoConfiguration$WebMvcAutoConfigurationAdapter.class]]
15:53:05.726 [main] INFO  o.h.validator.internal.util.Version - HV000001: Hibernate Validator 5.1.3.Final
15:53:07.036 [main] INFO  o.s.b.c.e.j.JettyEmbeddedServletContainerFactory - Server initialized with port: 9092
15:53:07.043 [main] INFO  org.eclipse.jetty.server.Server - jetty-9.2.11.v20150529
15:53:07.344 [main] INFO  / - Initializing Spring embedded WebApplicationContext
15:53:07.345 [main] INFO  o.s.web.context.ContextLoader - Root WebApplicationContext: initialization completed in 5144 ms
15:53:09.241 [main] INFO  o.s.b.c.e.ServletRegistrationBean - Mapping servlet: 'dispatcherServlet' to [/]
15:53:09.249 [main] INFO  o.s.b.c.e.FilterRegistrationBean - Mapping filter: 'characterEncodingFilter' to: [/*]
15:53:09.250 [main] INFO  o.s.b.c.e.FilterRegistrationBean - Mapping filter: 'hiddenHttpMethodFilter' to: [/*]
15:53:10.080 [main] INFO  o.e.j.server.handler.ContextHandler - Started o.s.b.c.e.j.JettyEmbeddedWebAppContext@1112dfb5{/,null,AVAILABLE}
15:53:10.084 [main] INFO  org.eclipse.jetty.server.Server - Started @11379ms
WARNING: Logging before InitGoogleLogging() is written to STDERR
F0916 15:53:10.293172    19 process.cpp:889] Name or service not known
*** Check failure stack trace: ***
/tmp/start-scheduler.sh: line 2:     9 Aborted                 (core dumped) java $JAVA_OPTS -Djava.library.path=/usr/local/lib -jar /tmp/logstash-scheduler.jar

Any idea? Thanks.

@simon-labrecque Thanks for opening this issue! We are investigating problem at the moment.

@simon-labrecque Have a look at #37. It contains a Main runner which deploys Logstash on Mini-Mesos.

I don't know what the cause was here, but I don't know how to reproduce it and I think @frankscholten was saying that he fixed it in 38d6818, which tweaks some JVM memory settings.