Bug 2356533 - [GSS][Logging] RGW and Ceph-exporter do not resume writing to the log file after being rotated by logrotate.
Summary: [GSS][Logging] RGW and Ceph-exporter do not resume writing to the log file af...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 7.1
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: 7.1z5
Assignee: Matt Benjamin (redhat)
QA Contact: Madhavi Kasturi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-04-01 10:25 UTC by José Enrique
Modified: 2025-12-20 04:25 UTC (History)
16 users (show)

Fixed In Version: ceph-18.2.1-340
Doc Type: Bug Fix
Doc Text:
Thread names for bucket logging threads are now set correctly Previously, unsafe thread naming logic added with bucket logging changes allowed well-known threads to have incorrect names. As a result, programs relying on the name of specific threads saw invalid names, and in the special case where an external program (logrotate) was relying on a thread name as a selector, log rotation was disrupted. With this fix, thread names for bucket logging threads are set correctly.
Clone Of:
Environment:
Last Closed: 2025-06-23 02:51:55 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-11008 0 None None None 2025-04-01 10:27:20 UTC
Red Hat Product Errata RHBA-2025:9335 0 None None None 2025-06-23 02:52:00 UTC

Description José Enrique 2025-04-01 10:25:29 UTC
Description of problem:
Rados Gateway and ceph-exporter loggin doesn't resume after log file are rotated through logrotate.

Version-Release number of selected component (if applicable):

Red Hat Ceph 7.1z3

How reproducible:
execute logrotate --force /etc/logrotate.d/ceph-{fs_id}


Actual results:

The log file is rotated, but the processes do not write to the new log file.

Expected results:

Resume log activity for the mentioned daemons.

Additional info:

The logging activity comes back if the daemons are restarted, but it's not a solution because it's disturb the usual daemon behaviour.

Comment 1 José Enrique 2025-04-04 12:05:32 UTC
New findings,

Using the podman kill function to send the SIGHUP signal, the logging activity comes back, here is the logrotate config used,

# cat /etc/logrotate.d/ceph-0a63c783-54a3-4759-85e9-4b459d3036b4
/var/log/ceph/0a63c783-54a3-4759-85e9-4b459d3036b4/*.log {
    rotate 7
    daily
    compress
    sharedscripts
    postrotate
        podman kill --signal SIGHUP $(podman ps --filter "label=ceph=True" --format "{{.Names}}" | grep -E "^ceph-0a63c783-54a3-4759-85e9-4b459d3036b4") || true
    endscript
    missingok
    notifempty
    su root root
}

Comment 38 errata-xmlrpc 2025-06-23 02:51:55 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat Ceph Storage 7.1 security and bug fix updates), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2025:9335

Comment 39 Red Hat Bugzilla 2025-12-20 04:25:03 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


Note You need to log in before you can comment on or make changes to this bug.