Logrotate - Revision history

Leo: NixOS

2023-10-08T04:16:26Z

NixOS

@@ Line 3: / Line 3: @@
 ==Introduction==
 Logrotate is typically found in your distro's repos as 'logrotate'.
 {{Highlight
 | code = # yum -y install logrotate
 | lang = terminal
-}}
+}}On NixOS, enable Logrotate by setting the <code>services.logrotate.enable = true</code> setting. See the example further down on this page.
 Logrotate is triggered daily via a cronjob and as a result, there is no logrotate daemon. Typically, the cronjob is installed in <code>/etc/cron.daily/</code> but could also be as a <code>@daily</code> job in <code>/etc/crontab</code> on some systems.
 By default, installing Logrotate will also include some standard configuration files that will rotate some common system logs in <code>/var/log</code>.
-=== Cronjob ===
+=== Logrotate is triggered by cronjobs. ===
 <code>/etc/cron.daily/logrotate</code> should have:
 {{Highlight
@@ Line 141: / Line 144: @@
 | lang = text
 }}This will rotate logs daily and will retain up to 7 days worth of logs. Rotated logs are compressed. Verify the logs by running: <code>logrotate -v /etc/logrotate.d/traefik</code>.
 ==See also==

Leo at 17:39, 20 September 2023

2023-09-20T17:39:33Z

← Older revision		Revision as of 17:39, 20 September 2023
Line 15:		Line 15:
	Logrotate is triggered by cronjobs.		Logrotate is triggered by cronjobs.

	<code>/etc/~~corn~~.daily/logrotate</code> should have:		<code>/etc/cron.daily/logrotate</code> should have:
	{{Highlight		{{Highlight
	\| code = /usr/sbin/logrotate -s /var/lib/logrotate/logrotate.status /etc/logrotate.conf		\| code = /usr/sbin/logrotate -s /var/lib/logrotate/logrotate.status /etc/logrotate.conf
Line 75:		Line 75:
	\|Whether to compress the log or not. Uses gzip by default.		\|Whether to compress the log or not. Uses gzip by default.
	\|<code>compress</code>		\|<code>compress</code>
			\|-
			\|Delays compression of the logs by one rotation cycle.
			\|<code>delaycompress</code>
	\|-		\|-
	\|The extension of rotated log files. Eg. '<code>messages-2020-12-26.log</code>' or '<code>messages.0.log</code>'.		\|The extension of rotated log files. Eg. '<code>messages-2020-12-26.log</code>' or '<code>messages.0.log</code>'.
Line 106:		Line 109:

	== Tasks ==		== Tasks ==

			=== Testing logrotate configs ===
			To test a specific log rotate config, run:
			{{Highlight
			\| code = # logrotate -v /etc/logrotate.d/your-new-config
			\| lang = terminal
			}}
			That should print out what logrotate will do. The first time you run logrotate, logrotate will update the status file at <code>/var/lib/logrotate/logrotate.status</code> with the last time that the log files were looked at.

			If you want to have logrotate rotate the logs for you, you will have to edit this status file and change the timestamp to sometime in the past and re-run the logrotate command again.

	===Rotating Traefik access logs===		===Rotating Traefik access logs===

Leo: /* Rotating Traefik access logs */

2023-05-04T23:34:38Z

Rotating Traefik access logs

← Older revision		Revision as of 23:34, 4 May 2023
Line 108:		Line 108:

	===Rotating Traefik access logs===		===Rotating Traefik access logs===
	After configuring Traefik to log to <code>/var/log/traefik</code>, you may want to use this rule to rotate logs and then send <code>USR1</code> to the container running Traefik. Create a configuration file at <code>/etc/logrotate.d/traefik</code> with the following:{{Highlight		After configuring Traefik to log to <code>/var/log/traefik</code>, you may want to use this rule to rotate logs and then send <code>USR1</code> to the container running Traefik.

			Create a configuration file at <code>/etc/logrotate.d/traefik</code> with the following:{{Highlight
	\| code = /var/log/traefik/access.log {		\| code = /var/log/traefik/access.log {
	~~monthly~~		daily
	rotate 60		rotate 7

	create 0644 root root		create 0644 root root
Line 121:		Line 123:

	postrotate		postrotate
	docker kill --signal="USR1" $(docker ps {{!}} grep traefik {{!}} awk '{print $1}')		docker kill --signal="USR1" $(docker ps {{!}} grep traefik: {{!}} awk '{print $1}')
	endscript		endscript
	}		}
	\| lang = text		\| lang = text
	}}		}}This will rotate logs daily and will retain up to 7 days worth of logs. Rotated logs are compressed. Verify the logs by running: <code>logrotate -v /etc/logrotate.d/traefik</code>.

	==See also==		==See also==

Leo: /* Rotating Traefik access logs */

2023-05-04T23:30:15Z

Rotating Traefik access logs

← Older revision		Revision as of 23:30, 4 May 2023
Line 108:		Line 108:

	===Rotating Traefik access logs===		===Rotating Traefik access logs===
	After configuring Traefik to log to <code>/var/log/traefik</code>, you may want to use this rule to rotate logs and then send <code>USR1</code> to the container running Traefik.{{Highlight		After configuring Traefik to log to <code>/var/log/traefik</code>, you may want to use this rule to rotate logs and then send <code>USR1</code> to the container running Traefik. Create a configuration file at <code>/etc/logrotate.d/traefik</code> with the following:{{Highlight
	\| code = /var/log/traefik/access.log {		\| code = /var/log/traefik/access.log {
	monthly		monthly

Leo at 20:53, 8 December 2022

2022-12-08T20:53:01Z

← Older revision		Revision as of 20:53, 8 December 2022
Line 11:		Line 11:

	By default, installing Logrotate will also include some standard configuration files that will rotate some common system logs in <code>/var/log</code>.		By default, installing Logrotate will also include some standard configuration files that will rotate some common system logs in <code>/var/log</code>.

			=== Cronjob ===
			Logrotate is triggered by cronjobs.

			<code>/etc/corn.daily/logrotate</code> should have:
			{{Highlight
			\| code = /usr/sbin/logrotate -s /var/lib/logrotate/logrotate.status /etc/logrotate.conf
			\| lang = bash
			}}
			OR you should have a root crontab entry in <code>/var/spool/cron/root</code> similar to:
			{{Highlight
			\| code = 00 05 * * * /usr/sbin/logrotate -f /etc/logrotate.conf
			\| lang = text
			}}

	===Configuration===		===Configuration===

Leo at 19:27, 18 January 2022

2022-01-18T19:27:43Z

← Older revision		Revision as of 19:27, 18 January 2022
Line 15:		Line 15:
	Configuration is done with <code>/etc/logrotate.conf</code> and additional log rotate definitions can be placed in <code>/etc/logrotate.d/</code>. For example, we could put httpd log rotation rules in <code>/etc/logrotate.d/httpd</code>.		Configuration is done with <code>/etc/logrotate.conf</code> and additional log rotate definitions can be placed in <code>/etc/logrotate.d/</code>. For example, we could put httpd log rotation rules in <code>/etc/logrotate.d/httpd</code>.

	A ~~logrotate entry should contain~~ one or more log files (~~you can use globbing using <code>*</code>~~) ~~followed by some directives~~. ~~For example:~~		Each logrotate configuration file can define global directives, followed by logfiles to rotate. A logfile definition can specify one or more log files and also supports globbing. Each logfile definition can have its own set of local directives that override the global directives (if any exists) defined within its configuration file.
	{{Highlight		{{Highlight
	\| code = /path/to/logs/log1.log {		\| code = Global directives
	Directives		/path/to/logs/log1.log {
			Local Directives
	}		}
	/path/to/logs/log1.log /path/to/logs/*.log {		/path/to/logs/log1.log /path/to/logs/*.log {
	Directives		Local Directives
	}		}
	\| lang = terminal		\| lang = terminal
Line 85:		Line 86:
	}}		}}
	\|-		\|-
	\|Run the ~~postrotate~~ script only once, even if multiple logs were rotated		\|Run the pre/post-rotate script only once, even if multiple logs were rotated
	\|<code>sharedscripts</code>		\|<code>sharedscripts</code>
	\|}		\|}

Leo at 18:34, 18 January 2022

2022-01-18T18:34:25Z

← Older revision		Revision as of 18:34, 18 January 2022
Line 15:		Line 15:
	Configuration is done with <code>/etc/logrotate.conf</code> and additional log rotate definitions can be placed in <code>/etc/logrotate.d/</code>. For example, we could put httpd log rotation rules in <code>/etc/logrotate.d/httpd</code>.		Configuration is done with <code>/etc/logrotate.conf</code> and additional log rotate definitions can be placed in <code>/etc/logrotate.d/</code>. For example, we could put httpd log rotation rules in <code>/etc/logrotate.d/httpd</code>.

	~~Log rotations are defined with the following syntax~~:		A logrotate entry should contain one or more log files (you can use globbing using <code>*</code>) followed by some directives. For example:
	{{Highlight		{{Highlight
	\| code = /path/to/logs/*.log {		\| code = /path/to/logs/log1.log {
			Directives
			}
			/path/to/logs/log1.log /path/to/logs/*.log {
	Directives		Directives
	}		}
Line 81:		Line 84:
	\| lang = terminal		\| lang = terminal
	}}		}}
			\|-
			\|Run the postrotate script only once, even if multiple logs were rotated
			\|<code>sharedscripts</code>
	\|}		\|}
	After defining your new rule, you can test it by running <code>logrotate -v /etc/logrotate.d/your-new-config</code>. If your logs aren't rotating, it's possible you need to tweak the state file in <code>/var/lib/logrotate/logrotate.status</code> for your particular log file in order for the rotate conditions to be fulfilled.		After defining your new rule, you can test it by running <code>logrotate -v /etc/logrotate.d/your-new-config</code>. If your logs aren't rotating, it's possible you need to tweak the state file in <code>/var/lib/logrotate/logrotate.status</code> for your particular log file in order for the rotate conditions to be fulfilled.

Leo at 00:13, 1 January 2022

2022-01-01T00:13:55Z

← Older revision		Revision as of 00:13, 1 January 2022
Line 24:		Line 24:
	It should also have at minimum the following directives:		It should also have at minimum the following directives:
	{\| class="wikitable"		{\| class="wikitable"
	!~~What~~		!style="width:70%"\|Description
	!Directives		!Directives
	\|-		\|-
Line 39:		Line 39:
	You may also optionally add the following directives depending on your needs:		You may also optionally add the following directives depending on your needs:
	{\| class="wikitable"		{\| class="wikitable"
	!		!style="width:70%"\|Description
	!		!Directives
	\|-		\|-
	\|Whether to create a new empty log after rotation is done.		\|Whether to create a new empty log after rotation is done.

Leo: testing logrotate rules

2022-01-01T00:12:32Z

testing logrotate rules

← Older revision		Revision as of 00:12, 1 January 2022
Line 42:		Line 42:
	!		!
	\|-		\|-
	\|Whether to create a new empty log		\|Whether to create a new empty log after rotation is done.
	\|<code>create</code>, <code>nocreate</code>		Optionally, you may specify the new file's mode and ownership.
			\|<code>create</code>, <code>create mode owner group</code>, <code>nocreate</code>
	\|-		\|-
	\|Use date as the suffix for rotated logs using the specified date format.		\|Use date as the suffix for rotated logs using the specified date format.
Line 81:		Line 82:
	}}		}}
	\|}		\|}
	<br />		After defining your new rule, you can test it by running <code>logrotate -v /etc/logrotate.d/your-new-config</code>. If your logs aren't rotating, it's possible you need to tweak the state file in <code>/var/lib/logrotate/logrotate.status</code> for your particular log file in order for the rotate conditions to be fulfilled.

	==Tasks==		== Tasks ==

	===Rotating Traefik logs===		===Rotating Traefik access logs===
	{{Highlight		After configuring Traefik to log to <code>/var/log/traefik</code>, you may want to use this rule to rotate logs and then send <code>USR1</code> to the container running Traefik.{{Highlight
	\| code = /var/log/traefik/*.log {		\| code = /var/log/traefik/access.log {
	~~daily~~		monthly
	rotate 30		rotate 60

			create 0644 root root
	missingok		missingok
	notifempty		notifempty
Line 95:		Line 98:
	dateext		dateext
	dateformat .%Y-%m-%d		dateformat .%Y-%m-%d
	~~create 0644 root root~~

	~~size 10M~~
	~~rotate 50~~
	~~missingok~~
	~~notifempty~~
	postrotate		postrotate
	docker kill --signal="USR1" $(docker ps {{!}} grep traefik {{!}} awk '{print $1}')		docker kill --signal="USR1" $(docker ps {{!}} grep traefik {{!}} awk '{print $1}')
Line 108:		Line 106:
	}}		}}

	== See also ==		==See also==

	* https://linux.die.net/man/8/logrotate		*https://linux.die.net/man/8/logrotate
	{{Navbox Linux}}		{{Navbox Linux}}
	[[Category:Linux]]		[[Category:Linux]]
	[[Category:LinuxUtilities]]		[[Category:LinuxUtilities]]

Leo at 23:58, 31 December 2021

2021-12-31T23:58:34Z

← Older revision		Revision as of 23:58, 31 December 2021
Line 46:		Line 46:
	\|-		\|-
	\|Use date as the suffix for rotated logs using the specified date format.		\|Use date as the suffix for rotated logs using the specified date format.
	Creates logs like 'messages-2020-12-26'		Creates logs like '<code>messages-2020-12-26</code>'
	\|<code>dateext</code>		\|<code>dateext</code>
	<code>dateformat .%Y-%m-%d</code>		<code>dateformat .%Y-%m-%d</code>
Line 57:		Line 57:
	\|<code>compress</code>		\|<code>compress</code>
	\|-		\|-
	\|The extension of rotated log files. Eg. 'messages-2020-12-26.log' or 'messages.0.log'.		\|The extension of rotated log files. Eg. '<code>messages-2020-12-26.log</code>' or '<code>messages.0.log</code>'.
	\|<code>extension log</code>		\|<code>extension log</code>
	\|-		\|-
	\|Send an email when a log is rotated out of existance.		\|Send an email when a log is rotated out of existance.
	\|<code>mail user@domain.com</code>		\|<code>mail user@domain.com</code>
			\|-
			\|Move rotated logs to a different location.
			\|<code>olddir /var/log/rotated</code>
	\|-		\|-
	\|Ignore if file is missing		\|Ignore if file is missing
Line 105:		Line 108:
	}}		}}

			== See also ==

			* https://linux.die.net/man/8/logrotate
	{{Navbox Linux}}		{{Navbox Linux}}
	[[Category:Linux]]		[[Category:Linux]]
	[[Category:LinuxUtilities]]		[[Category:LinuxUtilities]]