richardbenson/YAMS — Issue #50: Cannot set Max DB size, current max fills in just a few hours.
Author: Pendaelose
Created: 2012-02-02 01:54:33+00:00
State: open

I've read the similar bug, and tried purging by setting a scheduled event, however if you set the retention days to 0 it doesn't work. Because the logs fill up in just a few hours It needs a MUCH more narrow log window. I need something like 1 hour of logs. Now it's gotten to the point I can't even launch the service without it crashing immediately. I've re-installed YAMS (and my servers) twice. It works fine for a few hours, then hits max DB and dies.

I have 3 recommendations for this issue.

1) Have an option to auto-purge logs to keep the history at the set size. If it crosses the limit instead of seizing up and dying it needs to just dump the old logs on the spot, even if that means logs made 2 hours ago.

2) Have a field in the settings where you can set the max DB size. the current max is just not nearly high enough.

3) if the service locks up because the log is too full we need a tool to purge the logs without re-installing the app.