Managing RGW container logs filling up disk space
Hi all, I am running a Ceph Octopus cluster deployed with cephadm. I have three RGW nodes, the RGW containers are writing their logs to /var/lib/docker/containers/<container_id>/<container_id>-json.log Over time this causes the mount point to become 100% utilized. What is the recommended way to manage or limit these logs? - Should I configure a log driver in /etc/docker/daemon.json? If so, can this be done through Ceph/cephadm, or should it be configured manually on each node? - Would setting up a logrotate for /var/lib/docker/containers/*/*-json.log be appropriate? - Are there other best practices to control container log growth in this setup? Any advice or examples from others managing this would be greatly appreciated. Thanks! Sinan
Hi, personally, I like to have the daemon logs as files in /var/log/ceph/{FSID}/ and propose that to every customer as well. The docs [0] have some guidance how to do that. Regards, Eugen [0] https://docs.ceph.com/en/latest/cephadm/operations/#logging-to-files Zitat von Sinan Polat <sinan86polat@gmail.com>:
Hi all,
I am running a Ceph Octopus cluster deployed with cephadm. I have three RGW nodes, the RGW containers are writing their logs to /var/lib/docker/containers/<container_id>/<container_id>-json.log
Over time this causes the mount point to become 100% utilized. What is the recommended way to manage or limit these logs? - Should I configure a log driver in /etc/docker/daemon.json? If so, can this be done through Ceph/cephadm, or should it be configured manually on each node? - Would setting up a logrotate for /var/lib/docker/containers/*/*-json.log be appropriate? - Are there other best practices to control container log growth in this setup?
Any advice or examples from others managing this would be greatly appreciated.
Thanks!
Sinan _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
participants (2)
-
Eugen Block
-
Sinan Polat