> On 28 May 2015, at 19:10, Tim Bell <tim.b...@cern.ch> wrote:
> 
> Using UDP is a great workaround but it does not feel like a fix... can't the 
> daemons realise that the syslog socket is not alive and reconnect. Given it 
> affects most of the OpenStack projects, a fix inside one of the oslo logging 
> libraries (if the error can be detected there) would be great.

We too have been bitten hard by this issue in the past - way before Juno - when 
using rsyslog logging to a remote target (i.e Logstash).  We eventually went 
down the route of using log-courier [1] on x86 and beaver [2] on ARM (due to 
the lack of support for Go).

Both have worked out well for us - if you’re using Logstash it might be worth 
looking into either of these as a solution instead of switching to UDP and 
hoping that you don’t lose any messages that you might care about.

[1] https://github.com/driskell/log-courier 
<https://github.com/driskell/log-courier>
[2] https://github.com/josegonzalez/python-beaver 
<https://github.com/josegonzalez/python-beaver>

— 

-Nick


-- 
DataCentred Limited registered in England and Wales no. 05611763
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Reply via email to