Persistent Queue Error after hang up

Our Logstash has hung up(not terminated) on the 29.7. 13:55 so that no events where processed.
Curiosly on the 30.7. 14:10 it has started again but threw only Errors(see under config decription) until i restarted it on the 31.7. 7:30.
After the restart it again processed normally the backlogged events.

The logstash config is mostly the default with the following exceptions:
path.data: /var/lib/logstash
path.config: /etc/logstash/conf.d
queue.type: persisted
path.logs: /var/log/logstash
It was installed with yum on CentOS 7 in Version 5.4.3 (upgraded from 5.3.2 on the 17.07.2017).

The hang up occured without an error.
The error that was continuossly thrown(every 5 seconds) on the next day is an IOException (it will not let me post the complete error).

Knows someone what the cause for this error is?

Thanks
Shaoranlaos

We need to see the full error message. If it's too much to post here (because of a long stacktrace) you can make multiple posts, put it on pastebin or in a gist, or worst case truncate the stacktrace(s) to reduce their size.

Here is the Link to the Error on Pastebin
https://pastebin.com/jBXXc14p

it has happend again this weekend with the same error

i have deactivated the persistent queue now and will see if the failure will happen again

ok after deactivating the persistent queue logstash works again without error to date
so there seems to be an error with this feature in our installation?

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.