hi Eugen, this is tracked in https://tracker.ceph.com/issues/71156, and a fix has merged for the upcoming 19.2.3 release
unfortunately, a mistake was made in backporting some changes related to thread names and the radosgw process gets renamed to "notif-worker0" as a result. so commands like pkill expect that string instead of radosgw On Wed, Jun 25, 2025 at 7:00 AM Eugen Block <ebl...@nde.ag> wrote: > > Interesting, it seems like the pkill command from logrotate doesn't > trigger anything on the RGW daemons in Reef >= 18.2.5. But on 19.2.2 > it does work as expected. Right now an upgrade to Squid is not > possible, and this has the unfortunate side effect of blowing up the > file system until the process is restarted. Is there some workaround > possible until we upgrade? > > > Zitat von Eugen Block <ebl...@nde.ag>: > > > Hi, > > > > after upgrading multiple clusters from 18.2.4. some weeks ago, I > > noticed that the RGWs stop logging to file after the nightly > > logrotate. Other daemons don't seem to be affected, they continue > > logging to file. Restarting an RGW daemon helps until the next > > logrotate. > > > > I could reproduce this in a lab cluster, after upgrading from 18.2.4 > > to 18.2.5, the daemon stops logging to file after a logrotate. > > > > Is this a known issue? I can't seem to find anything on tracker. > > > > Thanks! > > Eugen > > > > ceph config dump | grep log_to_file > > global basic > > log_to_file true > > global advanced > > mon_cluster_log_to_file true > > > _______________________________________________ > ceph-users mailing list -- ceph-users@ceph.io > To unsubscribe send an email to ceph-users-le...@ceph.io > _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
