Time Based Retention: Fails to Point Deflector Due To Division by Zero #871
Comments
Hi! This was previously fixed in #836 but hasn't been backported to 0.92, not even to the 0.92.4 that's being released right now. |
I've pulled the fix into the 0.92 branch (commit 2f27895). |
Does your advice to select a time period that does not include a zero apply to both |
It is stranger than you think. It tries to find an anchor time, based on For example 1h would anchor on the last full hour, not on the time you
|
After enabling Time Based retention graylog2-server starts throwing mad errors and requires that I move the configuration back to index count based retention. I'm running a two graylog2-server node cluster and make sure to make the configuration change on both nodes.
The
java.lang.ArithmeticException: / by zero
error messages continue to fill the logs for as long as the service runs. Changing the retention back to the max_indices model results in the service operating normally.My relevant graylog2-server config items are
The full, redacted, output of
/var/log/graylog2-server/server.log
The text was updated successfully, but these errors were encountered: