Q We are a school who have been running PaperCut for approximately one year. We would like to clear out the database of print jobs prior to this school year. How do I perform a partial clear?
PaperCut has unlimited log sizes and has a smart log rotation procedure for text based system and print logs. Rotation is not usually required as disks are so large these days. You can however configure the system to delete older data either:
- Automatically via the options under Options → Backup → Delete old log data
- Manually using the command-line option
db-tools delete-old-logs as explained in detail in Appendix A. A value of
0 will delete all logs from today onwards.
In line with print management best practice, PaperCut recommends that all sites keep print log data as long as possible. Historical print usage data allows organizations to look at printing trends and conduct audits over long periods of time. PaperCut is designed in a way where large databases with historical log data will not slow down day-to-day use of the system.
Q I am seeing the error shown below when trying to delete old logs. What can I do about it?
Error occurred running db-tools, command:
delete-old-logs. GC overhead limit exceeded
We have seen this error at a few busy sites. (Sites printing couple of thousands of pages every day) By default, db-tools application uses 256M of memory which can be increased by making the following changes.
- Open db-tools file using a text editor.
- Find the line
- Try adding more amount by doubling it. E.g.
- Save the file.
- Test it if that works and change the memory parameter accordingly to your needs.
Hopefully, this should resolve the issue. If you still see issue, please contact support. If you can include the Application server logs, that would be super helpful.
Keywords: clearing logs, clear database, rotate log data, clear, remove, purge, data, logs, history