DevOps Zone is brought to you in partnership with:

A friendly Finnish hacker. I am technology consultant, open source advocator and entrepreneur. My expertise areas cover HTML5, Python, Plone, Javascript, WebGL,UNIX and mobile web. Mikko likes sushi, Angry Birds and dislikes winter. Mikko is a DZone MVB and is not an employee of DZone and has posted 42 posts at DZone. You can read more from them at their website. View Full User Profile

Autodiscovering Log Files for Logrotate

12.19.2012
| 1316 views |
  • submit to reddit

Logrotate is the UNIX application responsible for removing old (website) log file entries and preventing your server disk filling up. Logrotate is configured by writing config files where you specify one entry per file/file collection.

When you install applications like Apache or Nginx from your operating system package manager they usually come with a preconfigured logrotate entries. However, when you write your own custom software you need to take care of logrotation set up yourself.

If you are hosting a several website processes on the same server, e.g. Plone CMS sites, writing the log rotate entries for all log files manually can be pain. Below is a simple Python script which will auto discover all log files under a certain folder and its subfolders and generate logrotate entries for them.

The script is easy to adopt for other systems.

With Plone, since Plone uses buildout based installation process, you could alternatively use buildout configuration entries to maintain the log rotation for Plone. However, some sysadmins may prefer the system-wide logrotate configuration.

The script is hosted on Github for internal maintenance.

See also the related superuser.com question.

#!/usr/bin/python
# -*- coding: utf-8 -*-
"""

    Auto-discover log files and generate logrorate config based on it.

    - Find any folders containing log files

    - Add logrotate entry for *.log files in that folder

    - Try to signal Zope application server after log rotation to release the file
      handle and actually release the disk space associated with it

    http://collective-docs.readthedocs.org/en/latest/hosting/zope.html#log-rotate

    http://man.cx/logrotate

    Usage example for Ubuntu / Debian::

        sudo -i -u  # root
        # Generate a log rotate config which is automatically
        # picked up by a log rotate on the next run
        discover-log-rotate /etc/logrotate.d/plone-all /srv/plone

    Confirm that it works by running logrotate manualy.

    Dry run, outputs a lot but doesn't touch the files::

        logrotate -f -d /etc/logrotate.conf

    Test run, rotates the files::

        logrotate -f /etc/logrotate.conf

    Also see that your processes can re-open log files after logrotate run
    by restating a sample process.

"""

__license__ = "Public domain"
__author__ = "Mikko Ohtamaa <http://opensourcehacker.com>"

import sys

import fnmatch
import os

#: Logroate config template applied for each folder.
#: Modify for your own needs.
TEMPLATE = """
%(folder)s/*.log {
        weekly
        missingok
        # How many days to keep logs
        # In our cases 3 months
        rotate 12
        compress
        delaycompress
        notifempty

        # THE FOLLOWING IS ZOPE SPECIFIC BEHAVIOR

        # This signal will tell Zope to reopen the file-system inode for the log file
        # so it doesn't keep reserving the old log file handle for even if the file is deleted
        # We guess some possible process and PID file names.
        # The process here is little wasfeful, but we don't need to try match a log file to a running process name.
        # TODO: Ideas how to get a process name from the log file name?
        postrotate
            [ ! -f %(installation)s/var/instance.pid ] || kill -USR2 `cat %(installation)s/var/instance.pid`
            [ ! -f %(installation)s/var/client1.pid ] || kill -USR2 `cat %(installation)s/var/client1.pid`
            [ ! -f %(installation)s/var/client2.pid ] || kill -USR2 `cat %(installation)s/var/client2.pid`
            [ ! -f %(installation)s/var/client3.pid ] || kill -USR2 `cat %(installation)s/var/client3.pid`
            [ ! -f %(installation)s/var/client4.pid ] || kill -USR2 `cat %(installation)s/var/client4.pid`
        endscript
}

"""

def run():
    """
    Execute the script.
    """
    if len(sys.argv) < 2:
        sys.exit("Usage: discover-log-rotate [generated config file] [directory]")

    config = sys.argv[1]
    folder = sys.argv[2]

    out = open(config, "wt")

    print "Running log rotate discovery on: %s" % folder

    # Find any folders containing log files
    matches = []
    for root, dirnames, filenames in os.walk(folder):
        for filename in fnmatch.filter(filenames, '*.log'):

            full = os.path.join(root, filename)
            dirpath = os.path.dirname(full)

            if not dirpath in matches:
                print "Adding log rotate entry for: %s" % dirpath
                matches.append(dirpath)

    for match in matches:

        folder = os.path.abspath(match)

        # Assume the main Zope installation folder is format /srv/plone/xxx
        # and the underlying log folder /srv/plone/xxx/var/log
        installation = os.path.abspath(os.path.join(folder, "../.."))
        cooked = TEMPLATE % dict(folder=match, installation=installation)
        out.write(cooked)

    out.close()

    print "Wrote %s" % config

if __name__ == "__main__":
    run()


Published at DZone with permission of Mikko Ohtamaa, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)