It is designed to watch the queue of the starr apps and unpack what it says needs unpacked. I wouldn't have accepted the change you where suggesting either as that is not what unpackerr was designed to do. It is an issue with your system being slow. The dev is ignorant and refuses to make any improvements, and when i offered to fix the bugs myself, he said he would reject them, highly recommend anyone who is considering this project to look elsewhere I have tried several different versions of the Graylog Docker, currently sat on 4.2.8Īlright, after dumping several hours into "unpackerr" speaking with the dev on discord, i do not recommend unpackerr as a solution. I have no pipelines and I tried removing all extractors, same error. : Invalid message size: 0Īt 09.(FileMessageSet.scala:141) ~Īt 09.(LogSegment.scala:105) ~Īt 09.(LogSegment.scala:148) ~Īt 09.(Log.scala:506) ~Īt .LocalKafkaJournal.read(LocalKafkaJournal.java:677) ~Īt .LocalKafkaJournal.readNext(LocalKafkaJournal.java:617) ~Īt .LocalKafkaJournal.read(LocalKafkaJournal.java:599) ~Īt .(LocalKafkaMessageQueueReader.java:110) ~Īt .concurrent.AbstractExecutionThreadService$1$2.run(AbstractExecutionThreadService.java:67) Īt .concurrent.Callables$4.run(Callables.java:121) Īt (Thread.java:750) Įlasticsearch is fine, according to it's logs. 11:21:57,189 ERROR: .concurrent.ServiceManager - Service LocalKafkaMessageQueueReader has failed in the RUNNING state. If I restart the container, it will process the journal for a time, then stop again. It stopped processing messages and the journal fills up. Since then Graylog stops after a short time. It was working fine, then I upgraded Unraid from 6.8 to 6.10.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |