Hi, which actions in the web interface produce those timeout messages? Can you reproduce what you did, when the timeout occurred?
Cheers, Jochen On Monday, 9 November 2015 13:01:28 UTC+1, eleftherios Banos wrote: > > Hi, > > After we updated to the latest 1.2.2 version an error occurs. In detail, > when, stop and start the docker image, everything works normally, but after > some time the error occurs at the application.log: > > > 2015-11-09 09:15:02,753 - [ERROR] - from > org.graylog2.restclient.lib.ApiClient in servernodes-refresh-0 > API call timed out > java.util.concurrent.TimeoutException: null > at > com.ning.http.client.providers.netty.future.NettyResponseFuture.get(NettyResponseFuture.java:159) > > ~[com.ning.async-http-client-1.9.31.jar:na] > at > org.graylog2.restclient.lib.ApiClientImpl$ApiRequestBuilder.executeOnAll(ApiClientImpl.java:608) > > ~[org.graylog2.graylog2-rest-client--1.2.2-1.2.2.jar:na] > at > org.graylog2.restclient.lib.ServerNodesRefreshService.resolveConfiguredNodes(ServerNodesRefreshService.java:97) > > [org.graylog2.graylog2-rest-client--1.2.2-1.2.2.jar:na] > at > org.graylog2.restclient.lib.ServerNodesRefreshService.access$400(ServerNodesRefreshService.java:42) > > [org.graylog2.graylog2-rest-client--1.2.2-1.2.2.jar:na] > at > org.graylog2.restclient.lib.ServerNodesRefreshService$1.run(ServerNodesRefreshService.java:126) > > [org.graylog2.graylog2-rest-client--1.2.2-1.2.2.jar:na] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > [na:1.8.0_60] > at > java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) > [na:1.8.0_60] > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) > > [na:1.8.0_60] > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) > > [na:1.8.0_60] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > > [na:1.8.0_60] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > > [na:1.8.0_60] > at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60] > > > > I am using the same node-id and server-secret, after upgrading to the > last version. I can not figure out what this error is about. > I suppose that is because i updated to the newest version 1.2.2 of > graylog. Maybe it is necessary to delete all the data (as still I am > working on a testing environment), but I would like to make sure that the > same problem not happens when on production in the future. > > The configuration I am using for the docker graylog instance is > "GRAYLOG_RETENTION="--size=3 --indices=10" -e ES_MEMORY=2g". Not sure if it > is proper, to use "--indices=10", as I am using "Minimum Graylog setup." > > > > Thank you in advance for your help, > Lefteris. > -- 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/3e8b6a26-7e55-4d7f-983c-7af0f0f009ec%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
