{"id":178,"date":"2024-05-07T10:09:28","date_gmt":"2024-05-07T10:09:28","guid":{"rendered":"https:\/\/www.rajeshkumar.xyz\/blog\/?p=178"},"modified":"2024-06-11T14:32:40","modified_gmt":"2024-06-11T14:32:40","slug":"how-to-install-and-configure-logroate-in-linux","status":"publish","type":"post","link":"https:\/\/www.rajeshkumar.xyz\/blog\/how-to-install-and-configure-logroate-in-linux\/","title":{"rendered":"How to Install and configure Logroate in Linux?"},"content":{"rendered":"\n

almalinux os<\/h2>\n\n\n\n

To configure logrotate in AlmaLinux, you can follow these steps to ensure your system logs are properly managed and rotated. Logrotate is a system utility that manages the automatic rotation and compression of log files. If logrotate isn’t already installed, you can install it using the package manager, and then configure it by creating or editing configuration files.<\/p>\n\n\n\n

Step 1: Install Logrotate<\/h3>\n\n\n\n

First, make sure logrotate is installed on your system. You can install it using the dnf<\/code> package manager:<\/p>\n\n\n

sudo dnf install logrotate<\/code><\/span><\/pre>\n\n\n
Step 2: Create or Edit a Logrotate Configuration File<\/h3>\n\n\n\n
Logrotate configurations are usually stored in \/etc\/logrotate.conf<\/code> for global settings, and additional custom settings can be placed in \/etc\/logrotate.d\/<\/code>.<\/p>\n\n\n\n
    \n
  1. Edit the main configuration file:<\/strong> Open \/etc\/logrotate.conf<\/code> in a text editor:bashCopy codesudo nano \/etc\/logrotate.conf <\/code>This file contains global settings and defaults.<\/li>\n\n\n\n
  2. Create a custom logrotate file:<\/strong> It’s a common practice to create individual configuration files for different applications under \/etc\/logrotate.d\/<\/code>. For example, to create a logrotate configuration for your custom application logs:<\/li>\n<\/ol>\n\n\n
    sudo nano \/etc\/logrotate.d\/myapp<\/code><\/span><\/pre>\n\n\n
    Add configuration options like:<\/p>\n\n\n
    \/var<\/span>\/log\/myapp\/*.log {\n    daily\n    rotate 14\n    compress\n    delaycompress\n    missingok\n    notifempty\n    create 0640 root adm\n    sharedscripts\n    postrotate\n        \/usr\/bin\/systemctl reload myapp.service > \/dev\/null\n    endscript\n}\n<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      \n
    1. Here\u2019s what each directive means:\n
        \n
      • daily<\/strong>: Rotate the logs daily.<\/li>\n\n\n\n
      • rotate 14<\/strong>: Keep 14 copies of the log files.<\/li>\n\n\n\n
      • compress<\/strong>: Compress (gzip) the log files.<\/li>\n\n\n\n
      • delaycompress<\/strong>: Compress the previous day\u2019s log files.<\/li>\n\n\n\n
      • missingok<\/strong>: Do not output an error if the log file is missing.<\/li>\n\n\n\n
      • notifempty<\/strong>: Do not rotate the log if it is empty.<\/li>\n\n\n\n
      • create 0640 root adm<\/strong>: Create new log files with set permissions\/owner\/group.<\/li>\n\n\n\n
      • sharedscripts<\/strong>: Run the scripts at the end only once, not for each log file which is rotated.<\/li>\n\n\n\n
      • postrotate\/end script<\/strong>: Commands inside this block are executed after the log file is rotated.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
        Step 3: Test Your Configuration<\/h3>\n\n\n\n
        To test your logrotate configuration:<\/p>\n\n\n
        sudo logrotate --debug \/etc\/logrotate.conf\n<\/code><\/span><\/pre>\n\n\n
        This command will show you what logrotate will do, but it won\u2019t actually rotate the logs. It's useful for making sure your configurations are set up correctly.<\/pre>\n\n\n\n
        Manually Run Logrotate<\/h3>\n\n\n
        sudo logrotate -vf \/etc\/logrotate.conf\n\n-v (verbose) will give you detailed output.\n-f (force) will force the rotation.<\/code><\/span><\/pre>\n\n\n
        Step 4: Automate Logrotate<\/strong><\/p>\n\n\n\n
        Logrotate is typically automated as a daily cron job. Check the \/etc\/cron.daily\/logrotate<\/code> script to ensure it\u2019s being run automatically by cron.<\/strong><\/p>\n\n\n\n
        The logrotate process typically runs automatically on most Linux distributions, including AlmaLinux, as it is usually set up as a daily cron job during installation. However, if you need to ensure it is set up and running, or if you want to customize its schedule, here\u2019s a step-by-step guide on how to automate logrotate.<\/p>\n\n\n\n
        Verify Logrotate Installation<\/h3>\n\n\n\n
        First, make sure logrotate is installed and check if the cron job is already in place:<\/p>\n\n\n
        rpm -q logrotate\nls -l \/etc\/cron.daily\/logrotate<\/code><\/span><\/pre>\n\n\n
        How to see all the log file which is being rotated with schedule\\<\/h3>\n\n\n
        cat \/etc\/logrotate.conf\ncat \/etc\/logrotate.d\/<file>\n\ngrep -E \"^\\s*[^\\s#]\"<\/span> \/etc\/logrotate.conf\ngrep -E \"^\\s*[^\\s#]\"<\/span> \/etc\/logrotate.d\/*\n\nThis will list all non-commented lines, which typically include the log file paths and rotation settings.<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        Understand the Default Automation<\/h3>\n\n\n\n
        By default, logrotate is run by a script in \/etc\/cron.daily\/<\/code>. This directory contains scripts that are run daily by cron<\/code>. The logrotate<\/code> script in this directory typically looks something like this:<\/p>\n\n\n
        $ vi <span<\/span> style<\/span>=\"background-color: rgba(34, 34, 34, 0.2); font-family: inherit; color: var(--wp--preset--color--body-text); font-size: var(--wp--preset--font-size--normal); font-weight: var(--wp--custom--typography--font-weight--normal);\"<\/span>><\/span>\/etc\/cron.daily\/logrotate<\/span<\/span>><\/span><span<\/span> style<\/span>=\"background-color: rgba(34, 34, 34, 0.2); font-family: inherit; color: var(--wp--preset--color--body-text); font-size: var(--wp--preset--font-size--normal); font-weight: var(--wp--custom--typography--font-weight--normal);\"<\/span>><\/span><\/span<\/span>><\/span> \n\n#!\/bin\/sh\n\n\/usr\/sbin\/logrotate \/etc\/logrotate.conf\nEXITVALUE=$?\nif [ $EXITVALUE != 0 ]; then\n    \/usr\/bin\/logger -t logrotate \"ALERT exited abnormally with [$EXITVALUE]\"\nfi\nexit 0\n<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
        Ensure the Cron Daemon is Running<\/strong><\/p>\n\n\n
        sudo<\/span> systemctl<\/span> status<\/span> crond<\/span>.service<\/span>\nsudo<\/span> systemctl<\/span> restart<\/span> crond<\/span>.service<\/span>\nsudo<\/span> systemctl<\/span> enable<\/span> crond<\/span>.service<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
        Check Logrotate Status and Logs<\/h3>\n\n\n
        sudo grep logrotate \/var<\/span>\/log\/syslog\nsudo grep logrotate \/var<\/span>\/log\/messages\n\ncat \/var<\/span>\/lib\/logrotate\/status\nor\ncat \/var<\/span>\/lib\/logrotate\/logrotate.status\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Check for Errors or Misconfigurations<\/h3>\n\n\n
        Sometimes logrotate may not work due to errors in the configuration files. Validate the syntax:\n\nTest logrotate configuration:\n\nsudo logrotate --debug \/etc\/logrotate.conf\n\nThis command will perform a dry run and<\/span> print<\/span> out what logrotate would do<\/span> without actually rotating the logs.<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        OPTIONAL<\/strong><\/p>\n\n\n
        Customize the Automation (Optional)\nIf you want logrotate to run more frequently than once a day, you can create a custom cron job:\n\nOpen the cron table for<\/span> editing:\n\nsudo crontab -e\nAdd a new<\/span> line for<\/span> your custom schedule:For example, to run logrotate every 12<\/span> hours, you could add:\n\n0<\/span> *\/12 * * * \/u<\/span>sr\/sbin\/logrotate \/etc\/logrotate.conf\nThis cron job runs at minute 0<\/span> every 12<\/span>th hour of<\/span> every day.\nSave and exit the editor.<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Permission Error<\/h2>\n\n\n
        [root@ip-172<\/span>-31<\/span>-14<\/span>-247<\/span> logrotate.d]# sudo grep logrotate \/var\/log\/messages<\/span>\nJun 11<\/span> 00<\/span>:00<\/span>:01<\/span> ip-172<\/span>-31<\/span>-14<\/span>-247<\/span> logrotate[4063447<\/span>]: error: failed to open config file usertracker: Permission denied\nJun 11<\/span> 00<\/span>:00<\/span>:01<\/span> ip-172<\/span>-31<\/span>-14<\/span>-247<\/span> logrotate[4063447<\/span>]: error: found error in file usertracker, skipping\nJun 11<\/span> 00<\/span>:00<\/span>:01<\/span> ip-172<\/span>-31<\/span>-14<\/span>-247<\/span> systemd[1<\/span>]: logrotate.service: Main process exited, code=exited, status=1<\/span>\/FAILURE\nJun 11<\/span> 00<\/span>:00<\/span>:01<\/span> ip-172<\/span>-31<\/span>-14<\/span>-247<\/span> systemd[1<\/span>]: logrotate.service: Failed with result 'exit-code'<\/span>.\nJun  9<\/span> 00<\/span>:00<\/span>:00<\/span> ip-172<\/span>-31<\/span>-14<\/span>-247<\/span> logrotate[3950100<\/span>]: error: failed to open config file usertracker: Permission denied\nJun  9<\/span> 00<\/span>:00<\/span>:00<\/span> ip-172<\/span>-31<\/span>-14<\/span>-247<\/span> logrotate[3950100<\/span>]: error: found error in file usertracker, skipping\nJun  9<\/span> 00<\/span>:00<\/span>:00<\/span> ip-172<\/span>-31<\/span>-14<\/span>-247<\/span> systemd[1<\/span>]: logrotate.service: Main process exited, code=exited, status=1<\/span>\/FAILURE\nJun  9<\/span> 00<\/span>:00<\/span>:00<\/span> ip-172<\/span>-31<\/span>-14<\/span>-247<\/span> systemd[1<\/span>]: logrotate.service: Failed with result 'exit-code'<\/span>.\nJun 10<\/span> 00<\/span>:00<\/span>:00<\/span> ip-172<\/span>-31<\/span>-14<\/span>-247<\/span> logrotate[4007463<\/span>]: error: failed to open config file usertracker: Permission denied\nJun 10<\/span> 00<\/span>:00<\/span>:00<\/span> ip-172<\/span>-31<\/span>-14<\/span>-247<\/span> logrotate[4007463<\/span>]: error: found error in file usertracker, skipping\nJun 10<\/span> 00<\/span>:00<\/span>:00<\/span> ip-172<\/span>-31<\/span>-14<\/span>-247<\/span> systemd[1<\/span>]: logrotate.service: Main process exited, code=exited, status=1<\/span>\/FAILURE\nJun 10<\/span> 00<\/span>:00<\/span>:00<\/span> ip-172<\/span>-31<\/span>-14<\/span>-247<\/span> systemd[1<\/span>]: logrotate.service: Failed with result 'exit-code'<\/span>.\nJun 11<\/span> 00<\/span>:00<\/span>:01<\/span> ip-172<\/span>-31<\/span>-14<\/span>-247<\/span> logrotate[4063447<\/span>]: error: failed to open config file usertracker: Permission denied\nJun 11<\/span> 00<\/span>:00<\/span>:01<\/span> ip-172<\/span>-31<\/span>-14<\/span>-247<\/span> logrotate[4063447<\/span>]: error: found error in file usertracker, skipping\nJun 11<\/span> 00<\/span>:00<\/span>:01<\/span> ip-172<\/span>-31<\/span>-14<\/span>-247<\/span> systemd[1<\/span>]: logrotate.service: Main process exited, code=exited, status=1<\/span>\/FAILURE\nJun 11<\/span> 00<\/span>:00<\/span>:01<\/span> ip-172<\/span>-31<\/span>-14<\/span>-247<\/span> systemd[1<\/span>]: logrotate.service: Failed with result 'exit-code'<\/span>.\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        Ensure that the log files and their directories have the correct permissions for logrotate to read and write.<\/p>\n\n\n\n
        Troubleshooting steps to ensure logrotate is functioning correctly<\/h3>\n\n\n\n
        Step 1: Check Permissions<\/h3>\n\n\n\n
        Ensure that the usertracker<\/code> configuration file has the correct permissions, and logrotate can access it.<\/p>\n\n\n\n
        sudo chmod 644 \/etc\/logrotate.d\/usertracker
        sudo chown root:root \/etc\/logrotate.d\/usertracker
        <\/code><\/pre>\n\n\n\n
        Step 2: Manually Trigger Log Rotation<\/h3>\n\n\n\n
        You can manually trigger the logrotate to see if it works as expected:<\/p>\n\n\n\n
        sudo logrotate -f \/etc\/logrotate.conf
        <\/code><\/pre>\n\n\n\n
        The -f<\/code> flag forces the rotation, even if it would not normally rotate.<\/p>\n\n\n\n
        Step 3: Verify Crontab for Logrotate<\/h3>\n\n\n\n
        Ensure that logrotate is scheduled to run automatically. Check the crontab:<\/p>\n\n\n\n
        sudo crontab -l | grep logrotate
        <\/code><\/pre>\n\n\n\n
        You should see an entry similar to:<\/p>\n\n\n\n
        0 0 * * * \/usr\/sbin\/logrotate \/etc\/logrotate.conf
        <\/code><\/pre>\n\n\n\n
        This entry schedules logrotate to run every day at midnight.<\/p>\n\n\n\n
        Step 4: Check System Logs<\/h3>\n\n\n\n
        After ensuring permissions and running the manual logrotate, check the system logs again to verify there are no errors:<\/p>\n\n\n\n
        sudo grep logrotate \/var\/log\/messages
        <\/code><\/pre>\n\n\n\n
        Step 5: Validate Configuration Files<\/h3>\n\n\n\n
        Ensure all logrotate configuration files are correctly set up and valid:<\/p>\n\n\n\n
        sudo logrotate --debug \/etc\/logrotate.conf
        <\/code><\/pre>\n\n\n\n
        This command will show any potential issues with the logrotate configuration files.<\/p>\n\n\n\n
        Step 6: Confirm Service Status<\/h3>\n\n\n\n
        Make sure the logrotate service is active and running without issues:<\/p>\n\n\n\n
        sudo systemctl status logrotate
        <\/code><\/pre>\n\n\n\n
        If it’s not running, start or restart the service:<\/p>\n\n\n\n
        sudo systemctl start logrotate
        <\/code><\/pre>\n\n\n\n
        or<\/p>\n\n\n\n
        sudo systemctl restart logrotate
        <\/code><\/pre>\n\n\n\n
        Step 7: Review logrotate<\/code> Status and Output<\/h3>\n\n\n\n
        After confirming the service status and manual rotation, ensure no further errors are present in the logs.<\/p>\n","protected":false},"excerpt":{"rendered":"
        almalinux os To configure logrotate in AlmaLinux, you can follow these steps to ensure your system logs are properly managed […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-178","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/posts\/178","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/comments?post=178"}],"version-history":[{"count":6,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/posts\/178\/revisions"}],"predecessor-version":[{"id":260,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/posts\/178\/revisions\/260"}],"wp:attachment":[{"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/media?parent=178"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/categories?post=178"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/tags?post=178"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}