What makes you think it is the statistics database? How large is it? I've never seen it grow very large as it has rotational nature (only keep X number of days and Y number of entries).
If you have a support case open I'd be very curious to find out whats inside the stats db. Don't post it here as it could contain sensitive information.
no there no case opend, i'm now at the beginning of my troubleshooting task and looking for a solution how to regulate the entries, like x days or to find out, what kind of data are in the database.
actually the file is 19 GB large:
[root@mwg-01 ~]# du -h /opt/mwg/lock/statistic/statistics.db
thanks and regards
It was unchecked or you just did it now?
it was unchecked !
If you set the Rotation setting as well, just restart is what you need after all.
That's what I can suggest.
Other case opening the SR# is required.
netman_71 Please let me know the case number when you have it. The statistics database contains all the information from the dashboards as well as counters. The information from the dashboard is retained in a sliding window fashion, where data goes in and data goes out. The stats db also contains counter information, so if you were using counters in a weird way, perhaps this could lead to the problem maybe??.
In any case I would recommend stopping MWG services and moving the file elsewhere:
1. Stop services (this will interupt traffic):
service mwg stop
2. Move the stats db elsewhere:
mv /opt/mwg/lock/statistic/statistics.db /opt/statistics.db
3. Start MWG services
service mwg start
4. Move the stats db off of /opt else where (like the larger cache partition if needed to gzip it):
mv /opt/statistics.db /opt/mwg/cache/statistics.db
gzip -9 statistics.db
5. Use WinSCP or other to get the file off of MWG for checking what's inside.
6. Gather a feedback post it to SR you open(!)
m.bagheryan, your issue with connection tracing and core file generation is unrelated to Hans' issue.
Yeah. I got it already. That's why I suggest to make SR to check directly.