[Openstack-operators] 100% CPU and hangs if syslog is restarted

Abel Lopez alopgeek at gmail.com
Thu May 28 17:19:13 UTC 2015

I bet you can workaround this by switching to UDP remote syslog. You'd loose messages, but your processes *should* "fire and forget"

> On May 28, 2015, at 9:56 AM, George Shuklin <george.shuklin at gmail.com> wrote:
> Hello.
> Today we've discover a very serious bug in juno: https://bugs.launchpad.net/nova/+bug/1459726
> In short: if you're using syslog, and restart rsyslog, all APIs processes will eventually stuck with 100% CPU usage without doing anything.
> Is anyone hits this bug before? It looks like very nasty.
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150528/248dee3b/attachment.pgp>

More information about the OpenStack-operators mailing list