automatic logs cleanup in oxauth component and also in opendj

By: Udaykumar Alwala Account Admin 17 Jan 2025 at 1:30 p.m. CST

4 Responses
Udaykumar Alwala gravatar
We are currently using gluu version 4.2.3 which is running on kubernetes clusters logs files for oxauth is saving in opt/gluu/jetty/oxauth/logs/ location. I can see the logs files are creating automatically. but cleanup of the older logs is not happening. We are able to see the logs of last 2 months as well. Is there any option in gluu to clean the log files which are older than let say 15 days so that we don't need to manually cleanup the log files. sample log output: ``` -rw-r--r-- 1 root root 0 Nov 27 12:15 http_request_response.log -rw-r--r-- 1 root root 67211769 Nov 27 23:59 oxauth-2024-11-27-1.log -rw-r--r-- 1 root root 2383621 Nov 27 23:59 oxauth-2024-11-27-2.log -rw-r--r-- 1 root root 122642664 Nov 28 23:59 oxauth-2024-11-28-1.log -rw-r--r-- 1 root root 4878727 Nov 28 23:59 oxauth-2024-11-28-2.log -rw-r--r-- 1 root root 119305805 Nov 29 23:59 oxauth-2024-11-29-1.log -rw-r--r-- 1 root root 4878727 Nov 29 23:59 oxauth-2024-11-29-2.log -rw-r--r-- 1 root root 68720707 Nov 30 23:59 oxauth-2024-11-30-1.log -rw-r--r-- 1 root root 4878725 Nov 30 23:59 oxauth-2024-11-30-2.log -rw-r--r-- 1 root root 64702231 Dec 1 23:59 oxauth-2024-12-01-1.log -rw-r--r-- 1 root root 4883310 Dec 1 23:59 oxauth-2024-12-01-2.log -rw-r--r-- 1 root root 165326452 Dec 2 23:59 oxauth-2024-12-02-1.log -rw-r--r-- 1 root root 4878743 Dec 2 23:59 oxauth-2024-12-02-2.log -rw-r--r-- 1 root root 131543726 Dec 3 23:59 oxauth-2024-12-03-1.log -rw-r--r-- 1 root root 4878740 Dec 3 23:59 oxauth-2024-12-03-2.log -rw-r--r-- 1 root root 163198023 Dec 4 23:59 oxauth-2024-12-04-1.log -rw-r--r-- 1 root root 4878750 Dec 4 23:59 oxauth-2024-12-04-2.log -rw-r--r-- 1 root root 39981078 Dec 5 23:59 oxauth-2024-12-05-1.log -rw-r--r-- 1 root root 1987030 Dec 5 23:59 oxauth-2024-12-05-2.log -rw-r--r-- 1 root root 3795788 Dec 6 23:59 oxauth-2024-12-06-1.log -rw-r--r-- 1 root root 1085875 Dec 6 23:57 oxauth-2024-12-06-2.log -rw-r--r-- 1 root root 2634757 Dec 7 23:59 oxauth-2024-12-07-1.log -rw-r--r-- 1 root root 1206880 Dec 7 23:59 oxauth-2024-12-07-2.log -rw-r--r-- 1 root root 2912693 Dec 8 23:59 oxauth-2024-12-08-1.log -rw-r--r-- 1 root root 1596018 Dec 8 23:59 oxauth-2024-12-08-2.log -rw-r--r-- 1 root root 92323264 Dec 9 23:59 oxauth-2024-12-09-1.log -rw-r--r-- 1 root root 3452683 Dec 9 23:59 oxauth-2024-12-09-2.log -r--r-- 1 root root 3717067 Jan 11 23:59 oxauth-2025-01-11-2.log -rw-r--r-- 1 root root 3362442 Jan 12 23:59 oxauth-2025-01-12-1.log -rw-r--r-- 1 root root 4100373 Jan 12 23:59 oxauth-2025-01-12-2.log -rw-r--r-- 1 root root 4609746 Jan 13 23:59 oxauth-2025-01-13-1.log -rw-r--r-- 1 root root 4012678 Jan 13 23:59 oxauth-2025-01-13-2.log -rw-r--r-- 1 root root 4844362 Jan 14 23:59 oxauth-2025-01-14-1.log -rw-r--r-- 1 root root 4207432 Jan 14 23:59 oxauth-2025-01-14-2.log -rw-r--r-- 1 root root 5621173 Jan 15 23:59 oxauth-2025-01-15-1.log -rw-r--r-- 1 root root 4344108 Jan 15 23:59 oxauth-2025-01-15-2.log -rw-r--r-- 1 root root 5121612 Jan 16 23:59 oxauth-2025-01-16-1.log -rw-r--r-- 1 root root 4307100 Jan 16 23:59 oxauth-2025-01-16-2.log ``` If there is no such option from gluu, I have created a cronjob which will cleanup the logs automatically for every 15 days. please review it.
Gluu 4.2.3 OS Version : N/A
inprogress

Answers

By Mohib Zico Account Admin 20 Jan 2025 at 7:16 a.m. CST

Copy
Mohib Zico gravatar
In Gluu CE, there is a logrotation script which does that job. @Amro.Misbah: how can we achieve such in CN?

By Amro Misbah staff 21 Jan 2025 at 12:02 p.m. CST

Copy
Amro Misbah gravatar
log4j2.xml doesn't have a rollover strategy to have a time-based deletion. A CronJob is a good approach and it looks good to me. I see the command achieves the intended functionality.

By Amro Misbah staff 06 Feb 2025 at 5:33 a.m. CST

Copy
Amro Misbah gravatar
Btw, we want to let you know that we added a section to the [docs](https://gluu.org/docs/gluu-server/4.5/operation/logs/#cn-setup) showcasing log management with a simpler command in the `CronJob`. It's using the `delete` flag instead of `exec rm -f {} \;`

By Udaykumar Alwala Account Admin 26 Mar 2025 at 4:17 a.m. CDT

Copy
Udaykumar Alwala gravatar
Hello Isman/Alex, How about the script for opendj logs cleanup. ``` apiVersion: batch/v1 kind: CronJob metadata: name: opendj-log-cleanup-cronjob namespace: mysso-sit spec: schedule: "0 1 * * *" # Run daily at 1 AM jobTemplate: spec: template: spec: containers: - name: log-cleanup image: bitnami/kubectl:latest command: - /bin/sh - -c - | POD_NAME=$(kubectl get pod -l app=opendj -n mysso-sit -o jsonpath='{.items[0].metadata.name}') echo "Cleaning up OpenDJ logs older than 15 days..." # Clean rotated logs like access.YYYYMMDD*, audit.YYYYMMDD*, etc. kubectl exec -n mysso-sit $POD_NAME -- find /opt/opendj/logs/ -type f \( -name "access.*" -o -name "audit.*" -o -name "errors.*" -o -name "replication.*" -o -name "ldap-access.audit.json.*" \) -mtime +15 -delete echo "Cleanup completed." env: - name: KUBERNETES_SERVICE_HOST value: "kubernetes.default.svc" - name: KUBERNETES_SERVICE_PORT value: "443" restartPolicy: OnFailure ```
opendj-log.yaml

Post an answer