We tracked the problem down to the following rsyslog configuration in our test cluster:
*.* @@<log_host>:<log_port> $ActionExecOnlyWhenPreviousIsSuspended on & /var/log/failover.log $ActionExecOnlyWhenPreviousIsSuspended off It seems that the $ActionExecOnlyWhenPreviousIsSuspended directive doesn't work well with the $RepeatedMsgReduction directive we have in our main rsyslog.conf, as the rsyslog documentation warns: http://www.rsyslog.com/doc/rsconf1_actionexeconlywhenpreviousissuspended.html On Wed, Jul 27, 2016 at 12:34 PM, Karsten Heymann <karsten.heym...@gmail.com > wrote: > Hi, > > The syslog socket will block if it can't deliver it's logs. This happens > for example if logs are forwarded to a remote loghost via tcp and the > remote server becomes unavailable. > > Best > Karsten > > _______________________________________________ > ceph-users mailing list > ceph-users@lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > >
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
