Hi! Could you try the latest RC version for 0.20.2? It should have the fix for the message loading issue. I suspect that your stream definition does not properly match the messages, which can be hard to spot when you don't have the example message to work with.
That warning is harmless, and the log level should be lowered, it's mostly there for us to catch bugs early. The other problems sound suspiciously like malformed data in mongodb, yes. Did you start with a fresh mongodb database? Did you maybe upgrade from an earlier version? All non-preview versions of 0.20 should be upgradable, but there were issues with the preview versions not being upgradable. I would suggest trying to start with a fresh installation on the side to see if that resolves your issues, and if so, starting with a fresh mongodb database for your production setup. Best, Kay On Thu, May 1, 2014 at 11:51 PM, Tyler Bell <[email protected]> wrote: > Howdy - I have a single Graylog-server instance with 2 back-end > ElasticSearch nodes (v0.90.10). Server resources are great for now. ES heap > space would max out/crash, and I'd have to restart ES, but I bumped up the > memory. No issues since. > > One of my issues is that I can create Streams, but messages are never > populated in them. Trying to load a test message does nothing and I heard > that was a current bug. I get NO ERRORS in the log other than a warning when > I pause and start the stream. The interface shows that its no longer paused, > but perhaps its not really getting updated in the back-end? > > 2014-05-01 14:44:12,347 [play-akka.actor.default-dispatcher-35] WARN > lib.ApiClient - POST without body, this doesn't make sense, > java.lang.IllegalStateException: null > at > lib.ApiClientImpl$ApiRequestBuilder.requestBuilderForUrl(ApiClientImpl.java:552) > [graylog2-web-interface.graylog2-web-interface-0.20.1.jar:0.20.1] > at > lib.ApiClientImpl$ApiRequestBuilder.execute(ApiClientImpl.java:351) > [graylog2-web-interface.graylog2-web-interface-0.20.1.jar:0.20.1] > at models.StreamService.resume(StreamService.java:103) > [graylog2-web-interface.graylog2-web-interface-0.20.1.jar:0.20.1] > at controllers.StreamsController.resume(StreamsController.java:180) > [graylog2-web-interface.graylog2-web-interface-0.20.1.jar:0.20.1] > at > Routes$$anonfun$routes$1$$anonfun$applyOrElse$21$$anonfun$apply$61.apply(routes_routing.scala:769) > [graylog2-web-interface.graylog2-web-interface-0.20.1.jar:na] > at > Routes$$anonfun$routes$1$$anonfun$applyOrElse$21$$anonfun$apply$61.apply(routes_routing.scala:769) > [graylog2-web-interface.graylog2-web-interface-0.20.1.jar:na] > at > play.core.Router$HandlerInvoker$$anon$7$$anon$2.invocation(Router.scala:183) > [com.typesafe.play.play_2.10-2.2.2-RC1.jar:2.2.2-RC1] > at play.core.Router$Routes$$anon$1.invocation(Router.scala:377) > [com.typesafe.play.play_2.10-2.2.2-RC1.jar:2.2.2-RC1] > at play.core.j.JavaAction$$anon$1.call(JavaAction.scala:56) > [com.typesafe.play.play_2.10-2.2.2-RC1.jar:2.2.2-RC1] > at play.GlobalSettings$1.call(GlobalSettings.java:64) > [com.typesafe.play.play_2.10-2.2.2-RC1.jar:2.2.2-RC1] > at play.mvc.Security$AuthenticatedAction.call(Security.java:45) > [com.typesafe.play.play_2.10-2.2.2-RC1.jar:2.2.2-RC1] > at play.core.j.JavaAction$$anon$3.apply(JavaAction.scala:91) > [com.typesafe.play.play_2.10-2.2.2-RC1.jar:2.2.2-RC1] > at play.core.j.JavaAction$$anon$3.apply(JavaAction.scala:90) > [com.typesafe.play.play_2.10-2.2.2-RC1.jar:2.2.2-RC1] > at > play.core.j.FPromiseHelper$$anonfun$flatMap$1.apply(FPromiseHelper.scala:82) > [com.typesafe.play.play_2.10-2.2.2-RC1.jar:2.2.2-RC1] > at > play.core.j.FPromiseHelper$$anonfun$flatMap$1.apply(FPromiseHelper.scala:82) > [com.typesafe.play.play_2.10-2.2.2-RC1.jar:2.2.2-RC1] > at > scala.concurrent.Future$$anonfun$flatMap$1.apply(Future.scala:251) > [org.scala-lang.scala-library-2.10.3.jar:na] > at > scala.concurrent.Future$$anonfun$flatMap$1.apply(Future.scala:249) > [org.scala-lang.scala-library-2.10.3.jar:na] > at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:32) > [org.scala-lang.scala-library-2.10.3.jar:na] > at > play.core.j.HttpExecutionContext$$anon$2.run(HttpExecutionContext.scala:37) > [com.typesafe.play.play_2.10-2.2.2-RC1.jar:2.2.2-RC1] > at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:42) > [com.typesafe.akka.akka-actor_2.10-2.2.0.jar:2.2.0] > at > akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:386) > [com.typesafe.akka.akka-actor_2.10-2.2.0.jar:2.2.0] > at > scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) > [org.scala-lang.scala-library-2.10.3.jar:na] > at > scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) > [org.scala-lang.scala-library-2.10.3.jar:na] > at > scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) > [org.scala-lang.scala-library-2.10.3.jar:na] > at > scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107) > [org.scala-lang.scala-library-2.10.3.jar:na] > > Another issue I'm seeing is when using the search bar, which works fine, and > trying to add a search query to a dashboard. I have several dashboards > created, but they are never listed when trying to add a query. It just shows > the "No Dashboards. Create one?" message. > > When setting up ldap authentication, I'm getting the "Connection OK" and > "Test Login OK" messages when testing my parameters, but we are not actually > seeing queries on the Domain Controller side. Again, no errors in the logs. > > It seems like Graylog server and ElasticSearch are working fine here since > I'm processing logs without errors and can search for messages. Could this > be a possible issue with the mongo database? There are no errors there > either, but a lot of this stuff that I am having issues with is all saved in > Mongo. > > If anyone has any thoughts on this one, I'd greatly appreciate reading them! > > -- > You received this message because you are subscribed to the Google Groups > "graylog2" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
