Hi Jochen, Files were deleted a couple of times while Graylog was stopped. The solution was to drop the Elasticsearch indices (and reflect the changes in MongoDB also). Now Graylog's performance is back to normal and no exceptions in the log.
Thanks for the help, Laszlo On Sunday 15 Feb 2015 10:21:58 Jochen Schalanda wrote: > Hi Laszlo, > > the error message looks like there were still some old and possibly > corrupted files in the spool directory. > > You should shutdown the Graylog server, remove the files from the spool > directory, and then start Graylog again. If you have removed the files > while Graylog was still running, they will be written again on shutdown. > > > Cheers, > Jochen > > On Friday, 13 February 2015 16:07:10 UTC+1, Laszlo Toth wrote: > > Hi Jochen, > > > > I tried deleting those files before but unfortunately that didn't solve > > my problem. > > Everything looks normal until the first input arrives or until I try to > > stop > > the server. If an input message arrives I get the same message. If I stop > > the > > server (even without receiving any input) it logs the following: > > > > 2015-02-13T15:02:59.562Z ERROR [AbstractCacheWorkerThread] Exception > > while working on cache: > > java.lang.IllegalStateException: Error while accessing database > > > > at > > > > org.graylog2.caches.DiskJournalCache.pop(DiskJournalCache.java:191) > > > > at > > > > org.graylog2.periodical.AbstractCacheWorkerThread.drainMessagesEnqueue(Ab > > stractCacheWorkerThread.java:75) > > > > at > > > > org.graylog2.periodical.AbstractCacheWorkerThread.work(AbstractCacheWorke > > rThread.java:58) > > > > at > > > > org.graylog2.periodical.OutputCacheWorkerThread$1.run(OutputCacheWorkerTh > > read.java:60) > > > > at java.lang.Thread.run(Thread.java:745) > > > > Caused by: java.lang.IllegalAccessError: already closed > > > > at org.mapdb.EngineWrapper$1.get(EngineWrapper.java:472) > > at org.mapdb.EngineWrapper.get(EngineWrapper.java:58) > > at org.mapdb.Atomic$Long.get(Atomic.java:315) > > at org.mapdb.Queues$SimpleQueue.poll(Queues.java:127) > > at org.mapdb.Queues$SimpleQueue.take(Queues.java:243) > > at > > > > org.graylog2.caches.DiskJournalCache.pop(DiskJournalCache.java:181) > > > > ... 4 more > > > > 2015-02-13T15:02:59.564Z ERROR [AbstractCacheWorkerThread] Exception > > while working on cache: > > java.lang.IllegalStateException: Error while accessing database > > > > at > > > > org.graylog2.caches.DiskJournalCache.pop(DiskJournalCache.java:191) > > > > at > > > > org.graylog2.periodical.AbstractCacheWorkerThread.drainMessagesEnqueue(Ab > > stractCacheWorkerThread.java:75) > > > > at > > > > org.graylog2.periodical.AbstractCacheWorkerThread.work(AbstractCacheWorke > > rThread.java:58) > > > > at > > > > org.graylog2.periodical.InputCacheWorkerThread$1.run(InputCacheWorkerThre > > ad.java:60) > > > > at java.lang.Thread.run(Thread.java:745) > > > > Caused by: java.lang.IllegalAccessError: already closed > > > > at org.mapdb.EngineWrapper$1.get(EngineWrapper.java:472) > > at org.mapdb.EngineWrapper.get(EngineWrapper.java:58) > > at org.mapdb.Atomic$Long.get(Atomic.java:315) > > at org.mapdb.Queues$SimpleQueue.poll(Queues.java:127) > > at org.mapdb.Queues$SimpleQueue.take(Queues.java:243) > > at > > > > org.graylog2.caches.DiskJournalCache.pop(DiskJournalCache.java:181) > > > > ... 4 more > > > > Thanks, > > Laszlo > > > > On Friday 13 Feb 2015 14:45:28 Jochen Schalanda wrote: > > > Hi Laszlo, > > > > > > you simply have to remove the files inside your spool directory ( > > > *message_cache_spool_dir* in your graylog2.conf, > > > > https://github.com/Graylog2/graylog2-server/blob/0.92.4/misc/graylog2.con > > f# > > > > > L314-315) and restart graylog2-server. > > > > > > > > > Cheers, > > > Jochen > > > > > > On Friday, 13 February 2015 11:42:18 UTC+1, Laszlo Toth wrote: > > > > Hi Kay, > > > > > > > > How can I delete the master cache? > > > > (It's not a big problem if I loose messages even from elasticsearch > > > > as all the logs are archived somewhere else. I use graylog2 to > > > > analyse the logs.) > > > > > > > > Thanks, > > > > Laszlo
