[Gluster-users] Bug in log rotation for 3.3.1

Toby Corkindale toby.corkindale at strategicdata.com.au
Mon Feb 25 04:41:51 UTC 2013

I have filed separate bugs for both the missing man pages, and the 
failed log rotations there.

In the meantime, could someone advise me on the correct way to tell 
Glusterfs to rotate the logs for the bricks and mounts?

I mean, it's easy to do a kill -HUP `cat /var/run/glusterd.pid`, but how 
am I supposed to find the PIDs for the gluster mounts on the clients, or 
the individual brick daemons on the server?


On 23/02/13 04:27, Joe Julian wrote:
> Yes, I am aware. Louis' packaging is part of the official debian
> development and bugs against it are tracked at launchpad.
> Toby Corkindale <toby.corkindale at strategicdata.com.au> wrote:
>     On 22/02/13 11:18, Joe Julian wrote:
>         On 02/20/2013 05:05 PM, Toby Corkindale wrote:
>             logrotate.d/glusterfs-common (in the debian package for
>             3.3.1) is faulty.
>             It rotates the log files, but it doesn't tell glusterd to
>             re-open
>             them, so it continues to write to what is now .1 (and then
>             later it
>             gets gziped and corrupted)
>             I also note that the debian packages do not include the man
>             pages for
>             any of the gluster binaries! (gluster, glusterfs, glusterd)
>         Please file a bug report at
>         https://bugs.launchpad.net/ubuntu/+source/glusterfs/+filebug
>     Oh, I think you misunderstand -- I'm talking about the
>     officially-provided-by-glusterfs debian packages here, not the ones
>     created by Debian or Ubuntu themselves.

More information about the Gluster-users mailing list