You should send a SIGHUP to all glusterfs processes. Your logrotate configuration is just sending a SIGHUP to the GlusterD process. That's why the other processes are still logging to the old files.
You can use the `pkill` command to send a signal to all Gluster processes; `pkill -HUP gluster` .
Or you can use `killall`; `killall -HUP glusterd glusterfs glusterfsd`
~kaushal
On Sat, Mar 28, 2015 at 2:38 PM, Roman <romeo.r@xxxxxxxxx> wrote:
Anyone?--2015-03-13 10:42 GMT+02:00 Roman <romeo.r@xxxxxxxxx>:Hi,Running glusterfs 3.5.3 built on Nov 17 2014 15:48:54 on two servers and one client. And all have same issue: they are loging to the wrong place.They should log to:/var/log/glusterfs/cli.log/var/log/glusterfs/nfs.log/var/log/glusterfs/glustershd.log/var/log/glusterfs/glfsheal-vol-name.logAfter I start gluster it's ok, but after first rotate gluster wirtes to.1 files only:/var/log/glusterfs/cli.log.1/var/log/glusterfs/nfs.log.1/var/log/glusterfs/glustershd.log.1/var/log/glusterfs/glfsheal-vol-name.log.1same applies to /var/log/bricks/*.log files.on client machineinstead of /var/log/glusterfs/srv-volname.log logging goes to /var/log/glusterfs/srv-volname.log.1 after first rotate.client uses glusterfs 3.5.2, but soon will be updated also.Any help?logrotate.d conf files/var/log/glusterfs/*/*.log {dailyrotate 7delaycompresscompressnotifemptymissingokcopytruncatepostrotate[ ! -f /var/run/glusterd.pid ] || kill -HUP `cat /var/run/glusterd.pid`endscript}root@stor1:~# cat /etc/logrotate.d/glusterfs-common/var/log/glusterfs/*.log {dailyrotate 7delaycompresscompressnotifemptymissingokpostrotate[ ! -f /var/run/glusterd.pid ] || kill -HUP `cat /var/run/glusterd.pid`endscript}--Best regards,
Roman.Best regards,
Roman.
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
