Bobcares

Nginx access log logrotate

by | Apr 13, 2023

Learn how to set up Nginx access log logrotate. Our Nginx Support team is here to help you with your questions and concerns.

Nginx access log logrotate

The log files for the NGINX web server can grow significantly over time. Fortunately, NGINX lets us rotate log files so that new log files are automatically created and old log files are archived. Today, we are going to discuss how to set up NGINX’s log rotation.

Before we begin let’s take a look at log rotation. When we run a web server, the log files tend to grow over time which leads to large files that are difficult to manage. As a result, we will run out of server space. Furthermore, it affects application performance and increases technology costs as well.

This is where Log rotation comes in handy. It allows us to automatically create new empty log files, archive current log file, and delete old archives conditionally.

How to set up NGINX Log Rotation

  1. First, we have to install the Logrotate utility by opening a terminal and running the following command:
    • For Ubuntu or Debian

      $ sudo apt-get install logrotate

    • For CentOS, Redhat, or Fedora

      #yum install logrotate -y

  2. Next, we have to open the default config file for NGINX server which s located at /etc/logrotate.d/nginx, and add the following lines:

    How to set up NGINX Log RotationWhere,

    • weekly – logs are rotated once a week
    • missingok – does not throw an error if a log file is missing
    • rotate 52 – keeps 52 log files, where one is for each week of the year. Furthermore, it deletes old files only after keeping 52 log files.
    • compress – it compresses old log files to save space
    • notifempty – it ensures that logrotate only writes to new files
    • create – it creates a new empty log file after each rotation
    • sharedscripts – it ensures logrotate runs only once
    • postrotate/prerotate – it ensures the postrotate script is run after log rotation or the prerotate script is run before log rotation depending on which option we include.
  3. Finally, place the config files for each app at /etc/logrotate.d/, and the log files will be taken care of by logrotate automatically.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In summary, our Support Techs demonstrated how to set up and access Nginx logrotate log files.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF