Hi Josep, that's a bug in Graylog2 0.92.0-rc.1 which has been fixed and will be part of Graylog2 0.92.0.
Cheers, Jochen Am Dienstag, 25. November 2014 17:28:52 UTC+1 schrieb Josep Maria Comas Serrano: > > Sorry, actually the error is: > > 2014-11-25 17:25:27,469 ERROR: > org.graylog2.plugin.rest.AnyExceptionClassMapper - Unhandled exception in > REST resource > org.graylog2.cluster.NodeNotFoundException: Unable to find node > 5470215ae4b0fd11ea0bc34c > at org.graylog2.cluster.NodeServiceImpl.byNodeId(NodeServiceImpl.java:81) > at > org.graylog2.rest.resources.system.ClusterResource.node(ClusterResource.java:100) > at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > Any ideas? > > Best, > > JM > > > On Tuesday, November 25, 2014 5:19:10 PM UTC+1, Josep Maria Comas Serrano > wrote: >> >> After we've upgraded to 0.92 rc1, we're not able to access Import >> Extractors on any Input configured: >> >> Oops, an error occured >> >> This exception has been logged with id *6kakegjje*. >> >> >> The error on the console is: >> >> >> ERROR: org.graylog2.periodical.NodePingThread - Uncaught exception in >> periodical >> com.mongodb.MongoException$Network: Read operation to server >> 192.168.7.192:27017 failed on database graylog2_setup >> at com.mongodb.DBTCPConnector.innerCall(DBTCPConnector.java:300) >> >> The same behaviour with Export Extractors. >> >> Any ideas? >> >> Best, >> >> JM >> > -- 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 graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
