Hide Forgot
Starting with erlang-erts-R16B-03.10min.6.el7ost.x86_64, the log handler repeatedly crashes and fills up the rabbitmq startup_log with entries like: Event crashed log handler: {info_msg,<0.1719.0>, {<0.1832.0>,"Mirrored ~s: Adding mirror on node ~p: ~p~n", ["queue 'l3_agent_fanout_0f6bc20f4c54484f9de482cd6d83a15a' in vhost '/'", 'rabbit@overcloud-controller-1',<6192.10668.1>]}} function_clause Meanwhile the rabbitmq log is empty. Looks like a regression introduced in the "Enable error_logger depth fine tuning" patch.
R16B-03.16.el7 is also affected.
I update my environment to 08/04 puddle but couldn't find erlang-R16B-03.10min.9.el7ost, where can I get it or it should be in the latest puddle? [root@overcloud-controller-0 ~]# rpm -qa|grep erlang- erlang-stdlib-R16B-03.10min.8.el7ost.x86_64 erlang-os_mon-R16B-03.10min.8.el7ost.x86_64 erlang-hipe-R16B-03.10min.8.el7ost.x86_64 erlang-snmp-R16B-03.10min.8.el7ost.x86_64 erlang-ssl-R16B-03.10min.8.el7ost.x86_64 erlang-erts-R16B-03.10min.8.el7ost.x86_64 erlang-sasl-R16B-03.10min.8.el7ost.x86_64 erlang-xmerl-R16B-03.10min.8.el7ost.x86_64 erlang-inets-R16B-03.10min.8.el7ost.x86_64 erlang-tools-R16B-03.10min.8.el7ost.x86_64 erlang-crypto-R16B-03.10min.8.el7ost.x86_64 erlang-mnesia-R16B-03.10min.8.el7ost.x86_64 erlang-otp_mibs-R16B-03.10min.8.el7ost.x86_64 erlang-asn1-R16B-03.10min.8.el7ost.x86_64 erlang-syntax_tools-R16B-03.10min.8.el7ost.x86_64 erlang-runtime_tools-R16B-03.10min.8.el7ost.x86_64 erlang-public_key-R16B-03.10min.8.el7ost.x86_64 erlang-kernel-R16B-03.10min.8.el7ost.x86_64 erlang-sd_notify-0.1-2.el7ost.x86_64 erlang-compiler-R16B-03.10min.8.el7ost.x86_64
moved back to modified as not part of a puddle yet.
Looks like it's in puddle 2016-04-11.1 now
Verified using 2016-04-11 puddle. [root@overcloud-controller-0 ~]# rpm -qa|grep erlang erlang-mnesia-R16B-03.10min.9.el7ost.x86_64 erlang-os_mon-R16B-03.10min.9.el7ost.x86_64 erlang-syntax_tools-R16B-03.10min.9.el7ost.x86_64 erlang-xmerl-R16B-03.10min.9.el7ost.x86_64 erlang-stdlib-R16B-03.10min.9.el7ost.x86_64 erlang-runtime_tools-R16B-03.10min.9.el7ost.x86_64 erlang-asn1-R16B-03.10min.9.el7ost.x86_64 erlang-erts-R16B-03.10min.9.el7ost.x86_64 erlang-hipe-R16B-03.10min.9.el7ost.x86_64 erlang-inets-R16B-03.10min.9.el7ost.x86_64 erlang-crypto-R16B-03.10min.9.el7ost.x86_64 erlang-snmp-R16B-03.10min.9.el7ost.x86_64 erlang-compiler-R16B-03.10min.9.el7ost.x86_64 erlang-ssl-R16B-03.10min.9.el7ost.x86_64 erlang-sd_notify-0.1-2.el7ost.x86_64 erlang-kernel-R16B-03.10min.9.el7ost.x86_64 erlang-sasl-R16B-03.10min.9.el7ost.x86_64 erlang-public_key-R16B-03.10min.9.el7ost.x86_64 erlang-otp_mibs-R16B-03.10min.9.el7ost.x86_64 erlang-tools-R16B-03.10min.9.el7ost.x86_64 [root@overcloud-controller-0 ~]# tail -f /var/log/rabbitmq/rabbit\@overcloud-controller-0.log accepting AMQP connection <0.3601.0> (172.17.0.15:58391 -> 172.17.0.14:5672) =INFO REPORT==== 12-Apr-2016::12:34:27 === accepting AMQP connection <0.3612.0> (172.17.0.14:58577 -> 172.17.0.14:5672) =INFO REPORT==== 12-Apr-2016::12:34:28 === accepting AMQP connection <0.3623.0> (172.17.0.14:58616 -> 172.17.0.14:5672) =INFO REPORT==== 12-Apr-2016::12:34:29 === accepting AMQP connection <0.3634.0> (172.17.0.14:58659 -> 172.17.0.14:5672)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0636.html
Hi, I'm here to ask a question. Well it might be stupid. This bug starting with: erlang-erts-R16B-03.10min.6.el7ost.x86_64 (by Description) Fixed In Version: erlang-R16B-03.10min.9.el7ost And by checking the changelog, if this "Looks like a regression introduced in the "Enable error_logger depth fine tuning" patch."(by Description) is the reason, then both "erlang-erts-R16B-03.10min.9.el7ost.x86_64" and "erlang-R16B-03.10min.9.el7ost" got this bug fixed. So I am wondering that what's the connection between erlang and erlang-erts? Why not just say "fixed in version:erlang-erts-R16B-03.10min.9.el7ost"? Could anyone give me a hand?
(In reply to xiaoxwan from comment #11) > Hi, I'm here to ask a question. Well it might be stupid. > This bug starting with: > erlang-erts-R16B-03.10min.6.el7ost.x86_64 (by Description) > Fixed In Version: > erlang-R16B-03.10min.9.el7ost > And by checking the changelog, if this "Looks like a regression introduced > in the "Enable error_logger depth fine tuning" patch."(by Description) is > the reason, then both "erlang-erts-R16B-03.10min.9.el7ost.x86_64" and > "erlang-R16B-03.10min.9.el7ost" got this bug fixed. > So I am wondering that what's the connection between erlang and erlang-erts? > Why not just say "fixed in version:erlang-erts-R16B-03.10min.9.el7ost"? > Could anyone give me a hand? erlang-erts is just a subpackage of the main erlang package. Typically one only refers to the main package when referencing builds in the build system and errata tooling.