Hi Lorenzo,
the error message you've seen ("[…] We expected HTTP 200, but got a HTTP
-1.") is usually a sign of a request timeout. By default the request
timeout for HTTP requests from the Graylog web interface to a Graylog
server node is 5 seconds and can be customized in the configuration file of
your Graylog web interface, see
https://github.com/Graylog2/graylog2-web-interface/blob/1.2.0/misc/graylog-web-interface.conf.example#L31-L32
for
details.
Of course it would also be interesting to find out why the request worked
in the past and is running into a timeout right now. You should find some
hints about this in your Graylog server node's log messages.
Cheers,
Jochen
On Monday, 14 September 2015 16:39:21 UTC+2, Lorenzo Marotta wrote:
>
> Hello everyone,
>
> i've been running Graylog (currently, version 1.1.6) on a three node
> cluster for several months, and recently (i suspect, from last week) the
> "System/Overview" page on the Web Interface has stopped running.
>
> The error is
>
> *Reason:* Could not fetch system information. We expected HTTP 200, but
> got a HTTP -1.
>
>
> And the stack trace is
>
> ---cut---
>
> - org.graylog2.restclient.lib.ApiClientImpl$ApiRequestBuilder#execute (
> *ApiClientImpl.java:451*)
> - org.graylog2.restclient.models.ClusterService#getNumberOfSystemMessages
> (*ClusterService.java:128*)
> - controllers.SystemController#index (*SystemController.java:69*)
> -
> Routes$$anonfun$routes$1$$anonfun$applyOrElse$41$$anonfun$apply$561#apply
> (*routes_routing.scala:1931*)
> -
> Routes$$anonfun$routes$1$$anonfun$applyOrElse$41$$anonfun$apply$561#apply
> (*routes_routing.scala:1931*)
> - play.core.Router$HandlerInvokerFactory$$anon$4#resultCall (
> *Router.scala:264*)
> -
> play.core.Router$HandlerInvokerFactory$JavaActionInvokerFactory$$anon$15$$anon$1#invocation
>
> (*Router.scala:255*)
> - play.core.j.JavaAction$$anon$1#call (*JavaAction.scala:55*)
> - play.GlobalSettings$1#call (*GlobalSettings.java:67*)
> - play.mvc.Security$AuthenticatedAction#call (*Security.java:44*)
> - play.core.j.JavaAction$$anonfun$11#apply (*JavaAction.scala:82*)
> - play.core.j.JavaAction$$anonfun$11#apply (*JavaAction.scala:82*)
> - scala.concurrent.impl.Future$PromiseCompletingRunnable#liftedTree1$1
> (*Future.scala:24*)
> - scala.concurrent.impl.Future$PromiseCompletingRunnable#run (
> *Future.scala:24*)
> - play.core.j.HttpExecutionContext$$anon$2#run (
> *HttpExecutionContext.scala:40*)
> - play.api.libs.iteratee.Execution$trampoline$#execute (
> *Execution.scala:46*)
> - play.core.j.HttpExecutionContext#execute (
> *HttpExecutionContext.scala:32*)
> - scala.concurrent.impl.Future$#apply (*Future.scala:31*)
> - scala.concurrent.Future$#apply (*Future.scala:485*)
> - play.core.j.JavaAction$class#apply (*JavaAction.scala:82*)
> -
> play.core.Router$HandlerInvokerFactory$JavaActionInvokerFactory$$anon$15$$anon$1#apply
>
> (*Router.scala:252*)
> -
> play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4$$anonfun$apply$5#apply
> (*Action.scala:130*)
> -
> play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4$$anonfun$apply$5#apply
> (*Action.scala:130*)
> - play.utils.Threads$#withContextClassLoader (*Threads.scala:21*)
> - play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4#apply (
> *Action.scala:129*)
> - play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4#apply (
> *Action.scala:128*)
> - scala.Option#map (*Option.scala:145*)
> - play.api.mvc.Action$$anonfun$apply$1#apply (*Action.scala:128*)
> - play.api.mvc.Action$$anonfun$apply$1#apply (*Action.scala:121*)
> - play.api.libs.iteratee.Iteratee$$anonfun$mapM$1#apply (
> *Iteratee.scala:483*)
> - play.api.libs.iteratee.Iteratee$$anonfun$mapM$1#apply (
> *Iteratee.scala:483*)
> - play.api.libs.iteratee.Iteratee$$anonfun$flatMapM$1#apply (
> *Iteratee.scala:519*)
> - play.api.libs.iteratee.Iteratee$$anonfun$flatMapM$1#apply (
> *Iteratee.scala:519*)
> -
> play.api.libs.iteratee.Iteratee$$anonfun$flatMap$1$$anonfun$apply$14#apply
> (*Iteratee.scala:496*)
> -
> play.api.libs.iteratee.Iteratee$$anonfun$flatMap$1$$anonfun$apply$14#apply
> (*Iteratee.scala:496*)
> - scala.concurrent.impl.Future$PromiseCompletingRunnable#liftedTree1$1
> (*Future.scala:24*)
> - scala.concurrent.impl.Future$PromiseCompletingRunnable#run (
> *Future.scala:24*)
> - akka.dispatch.TaskInvocation#run (*AbstractDispatcher.scala:41*)
> - akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask#exec (
> *AbstractDispatcher.scala:393*)
> - scala.concurrent.forkjoin.ForkJoinTask#doExec (
> *ForkJoinTask.java:260*)
> - scala.concurrent.forkjoin.ForkJoinPool$WorkQueue#runTask (
> *ForkJoinPool.java:1339*)
> - scala.concurrent.forkjoin.ForkJoinPool#runWorker (
> *ForkJoinPool.java:1979*)
> - scala.concurrent.forkjoin.ForkJoinWorkerThread#run (
> *ForkJoinWorkerThread.java:107*)
>
>
> ---cut---
>
> MongoDB runs as a replica set of 3 nodes, on the 3 servers which also run
> graylog-server and graylog-web.
>
> Apart from the unavailability of the system information, everything seems
> to be OK.
> I tried checking the configurationm files, and everything seems to be OK;
> i've just reinstalled graylog-server and graylog-web on all three nodes,
> but to no avail.
>
> Has everyone here experienced a similar problem?
> Could it be related with a corruption of the configuration data in
> Mongodb? Just an idea...
>
> The error appear on the web interface of all 3 nodes.
>
> Long live and prosper,
>
> Lorenzo
>
--
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/881f9bae-d0b7-4917-83a0-31005e7c3766%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
