<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 28 May 2015, at 19:10, Tim Bell <<a href="mailto:Tim.Bell@cern.ch" class="">Tim.Bell@cern.ch</a>> wrote:</div><div class=""><br class="">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.<br class=""></div></blockquote><div><br class=""></div><div>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).<div class=""><br class=""></div><div class="">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.<br class=""><div class=""><br class=""></div><div class="">[1] <a href="https://github.com/driskell/log-courier" class="">https://github.com/driskell/log-courier</a></div><div class="">[2] <a href="https://github.com/josegonzalez/python-beaver" class="">https://github.com/josegonzalez/python-beaver</a></div></div></div><div><br class=""></div><div>— </div><div><br class=""></div><div>-Nick</div><div><br class=""></div></div></body></html>
<br>
<span style="color:rgb(34,34,34);font-family:arial,sans-serif;background-color:rgb(255,255,255)">DataCentred Limited registered in England and Wales no. 05611763</span>