Bug ID 867253: Systemd not deleting user journals

Last Modified: Jul 23, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0

Opened: Jan 08, 2020
Severity: 3-Major

Symptoms

When setting 'SystemMaxUse' to any value, systemd does not honor this limit, and the specified size is exceeded.

Impact

Journald filling up the file system. These journals are allocated with a minimum size of 4MiB and are not removed when the log entries age-out.

Conditions

Using a non-TMOS user account with external authentication permission. Note: Systemd-journald is configured to create a user journal for every remote user that logs into the BIG-IP system.

Workaround

Option 1: To immediately free up space, manually remove per-user journal logs from the following location: /var/log/journal/*/user-* Option 2: To prevent the system from creating these journal files going forward: 1. Edit /etc/systemd/journald.conf and add the following at the bottom of the file: SplitMode=none 2. Restart systemd-journal service # systemctl restart systemd-journald 3. Delete the existing user journal files from /var/log # rm /var/log/journal/*/user-* Note: -- You must apply this workaround separately to each blade of a VIPRION or vCMP guest running on a VIPRION. -- You must reapply this workaround after performing software installations.

Fix Information

None

Behavior Change