Journalctl - Revision history

Ardika Sulistija at 13:40, 18 June 2025

2025-06-18T13:40:53Z

← Older revision		Revision as of 13:40, 18 June 2025
Line 39:		Line 39:
	----		----
	sudo journalctl --no-pager --catalog --boot		sudo journalctl --no-pager --catalog --boot

			sudo journalctl --no-pager --catalog --boot > journalctl_boot-$(date +"%d-%m-%Y").txt

	sudo journalctl -b --since "2025-03-11 07:00:00" --until "2025-03-11 09:00:00"		sudo journalctl -b --since "2025-03-11 07:00:00" --until "2025-03-11 09:00:00"

2025-03-11T18:04:23Z

← Older revision		Revision as of 18:04, 11 March 2025
Line 38:		Line 38:
	====Using Journalctl to Troubleshoot Boot Issues====		====Using Journalctl to Troubleshoot Boot Issues====
	----		----
	journalctl --no-pager --catalog --boot		sudo journalctl --no-pager --catalog --boot

			sudo journalctl -b --since "2025-03-11 07:00:00" --until "2025-03-11 09:00:00"

2025-03-05T16:06:01Z

@@ Line 1: / Line 1: @@
 ====Journalctl Disk Usage====
 ----
@@ Line 37: / Line 34: @@
 Reference: https://unix.stackexchange.com/questions/130786/can-i-remove-files-in-var-log-journal-and-var-cache-abrt-di-usr

2024-09-02T17:09:27Z

← Older revision		Revision as of 17:09, 2 September 2024
Line 24:		Line 24:
	. . .		. . .
	Deleted archived journal /var/log/journal/f77f9567bb70f8e7b5d9a0c95bef5c2a/user-1000@e6ecd2f858d1498b9a445af7bac00bbf-000000000000063a-0005848ac99802b3.journal (8.0M).		Deleted archived journal /var/log/journal/f77f9567bb70f8e7b5d9a0c95bef5c2a/user-1000@e6ecd2f858d1498b9a445af7bac00bbf-000000000000063a-0005848ac99802b3.journal (8.0M).
	Vacuuming done, freed 88.0M of archived journals from		Vacuuming done, freed 88.0M of archived journals from
	/var/log/journal/f77f9567bb70f8e7b5d9a0c95bef5c2a.		/var/log/journal/f77f9567bb70f8e7b5d9a0c95bef5c2a.

2024-09-02T17:09:14Z

← Older revision		Revision as of 17:09, 2 September 2024
Line 14:		Line 14:

	To clean logs after a period of time rather than when they reach a certain size, you can set the parameter MaxRetentionSec instead of SystemMaxUse. See man journald.conf for more details.		To clean logs after a period of time rather than when they reach a certain size, you can set the parameter MaxRetentionSec instead of SystemMaxUse. See man journald.conf for more details.

			You can also clean based on time: journalctl --vacuum-time=10d
			# du -sh /var/log/journal
			113M /var/log/journal
			# journalctl --vacuum-time=10d
			Deleted archived journal
			/var/log/journal/f77f9567bb70f8e7b5d9a0c95bef5c2a/system@36170b4530af4c89ac4d84ac68f8b727- 0000000000000001-00057b09da23eb2c.journal (8.0M).
			Deleted archived journal /var/log/journal/f77f9567bb70f8e7b5d9a0c95bef5c2a/user-1000@54176301a0c74c4698c3b6a549e1b2ed-0000000000000874-00057b0c1a491094.journal (8.0M).
			. . .
			Deleted archived journal /var/log/journal/f77f9567bb70f8e7b5d9a0c95bef5c2a/user-1000@e6ecd2f858d1498b9a445af7bac00bbf-000000000000063a-0005848ac99802b3.journal (8.0M).
			Vacuuming done, freed 88.0M of archived journals from
			/var/log/journal/f77f9567bb70f8e7b5d9a0c95bef5c2a.

			root@monroe:/var/log# du -sh /var/log/journal
			25M /var/log/journal

	You can force a log rotation:		You can force a log rotation:

2024-09-02T17:07:38Z

← Older revision		Revision as of 17:07, 2 September 2024
Line 1:		Line 1:
	journalctl --no-pager --catalog --boot		journalctl --no-pager --catalog --boot


			====Journalctl Disk Usage====
			----
			Check Journalctl disk usage:
			[ec2-user@ringroadlimo ~]$ journalctl --disk-usage
			Archived and active journals take up 1.0G on disk.

			Journalctl will take up space over time in the directory <b>/var/log/journalctl/*</b>. It is safe to delete the contents but do not delete the directory.

			You can control the size of this directory using this parameter in your /etc/systemd/journald.conf:
			SystemMaxUse=50M

			To clean logs after a period of time rather than when they reach a certain size, you can set the parameter MaxRetentionSec instead of SystemMaxUse. See man journald.conf for more details.

			You can force a log rotation:
			$ sudo systemctl kill --kill-who=main --signal=SIGUSR2 systemd-journald.service

			NOTE: You might need to restart the logging service to force a log rotation, if the above signaling method does not do it. You can restart the service like so:
			$ sudo systemctl restart systemd-journald.service

			Reference: https://unix.stackexchange.com/questions/130786/can-i-remove-files-in-var-log-journal-and-var-cache-abrt-di-usr

2024-08-27T00:30:29Z

Created page with "journalctl --no-pager --catalog --boot"

New page

journalctl --no-pager --catalog --boot