Hi, it looks like the query to Elasticsearch is taking too long to complete so the configured timeout kicks in. Please make sure that your Elasticsearch cluster has enough resources to actually complete those requests.
You can also increase the timeout of the Elasticsearch client in Graylog using the elasticsearch_request_timeout option ( https://github.com/Graylog2/graylog2-server/blob/1.3.0/misc/graylog2.conf#L194-L197 ). Cheers, Jochen On Wednesday, 16 December 2015 11:12:57 UTC+1, Sriranga Kulkarni wrote: > > thanks for the response. I see the error below in graylog-server/server.log > > > *2015-12-16T09:09:07.295Z ERROR [AnyExceptionClassMapper] Unhandled > exception in REST resource* > > *org.elasticsearch.ElasticsearchTimeoutException: Timeout waiting for > task...* > * at > org.elasticsearch.action.support.AdapterActionFuture.actionGet(AdapterActionFuture.java:73)* > * at > org.graylog2.indexer.elasticsearch.GlobalTimeoutClient$GlobalTimeoutActionFuture.actionGet(GlobalTimeoutClient.java:150)* > * at > org.graylog2.indexer.searches.Searches.histogram(Searches.java:467)* > * at > org.graylog2.rest.resources.search.RelativeSearchResource.histogramRelative(RelativeSearchResource.java:252)* > * at sun.reflect.GeneratedMethodAccessor128.invoke(Unknown Source)* > * at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)* > * at java.lang.reflect.Method.invoke(Method.java:606)* > * at > org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)* > * at > org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)* > * at > org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)* > * at > org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:205)* > * at > org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)* > * at > org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)* > * at > org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)* > * at > org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)* > * at > org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:308)* > * at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)* > * at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)* > * at org.glassfish.jersey.internal.Errors.process(Errors.java:315)* > * at org.glassfish.jersey.internal.Errors.process(Errors.java:297)* > * at org.glassfish.jersey.internal.Errors.process(Errors.java:267)* > * at > org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)* > * at > org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:291)* > * at > org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1140)* > * at > org.graylog2.jersey.container.netty.NettyContainer.messageReceived(NettyContainer.java:356)* > * at > org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)* > * at > org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)* > * at > org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)* > * at > org.jboss.netty.handler.execution.ChannelUpstreamEventRunnable.doRun(ChannelUpstreamEventRunnable.java:43)* > * at > org.jboss.netty.handler.execution.ChannelEventRunnable.run(ChannelEventRunnable.java:67)* > * at > com.codahale.metrics.InstrumentedExecutorService$InstrumentedRunnable.run(InstrumentedExecutorService.java:176)* > * at > org.jboss.netty.handler.execution.MemoryAwareThreadPoolExecutor$MemoryAwareRunnable.run(MemoryAwareThreadPoolExecutor.java:606)* > * at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)* > * at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)* > * at java.lang.Thread.run(Thread.java:745)* > > > On Wednesday, December 16, 2015 at 3:39:58 PM UTC+5:30, Jochen Schalanda > wrote: >> >> Hi, >> >> HTTP response status 500 means "Internal Server Error", so there should >> be some error messages in the logs of your Graylog server node(s) hinting >> to the problem. >> >> >> Cheers, >> Jochen >> >> On Wednesday, 16 December 2015 10:15:41 UTC+1, Sriranga Kulkarni wrote: >>> >>> I am not able to see all messages from web. please find the versions i >>> am using >>> >>> graylog-server 1.2.2-1 >>> >>> graylog-web 1.2.2-1 >>> elasticsearch 1.6.0 >>> >>> the error i get when i say all messages is >>> >>> Oh no, something went wrong! >>> >>> (You caused a org.graylog2.restclient.lib.APIException. API call failed >>> GET http://@ >>> 127.0.0.1:12900/search/universal/relative/histogram?range=0&interval=week&query=*&range_type=relative >>> >>> returned 500 Internal Server Error body: >>> {"type":"ApiError","message":"Timeout waiting for task."}) >>> >>> *Reason:* There was a problem with your search. We expected HTTP 200, >>> but got a HTTP 500. >>> >> -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/45668648-22cb-4791-899f-6062a6342c44%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
