rabbitmq logs are not collected

[Serguei Bezverkhi]

with current version of erlang-R16B-03.16.el7.x86_64, rabbitmg process fails to store logging information, the issue is resolved in erlang-R16B-03.17

Error in log handler
====================
Event: {info_report,<0.108.0>,
           {<0.3706.0>,progress,
            [{supervisor,{<0.3706.0>,rabbit_amqqueue_sup}},
             {started,
                 [{pid,<0.3707.0>},
                  {name,rabbit_amqqueue},
                  {mfargs,
                      {rabbit_prequeue,start_link,
                          [{amqqueue,
                               {resource,<<"/">>,queue,
                                   <<"q-agent-notifier"...>>},
                               false,false,none,
                               [{<<"x-expire"...>>,signedint,1800000},
                                {<<"x-ha"...>>,longstr,...}],
                               none,[],[],[],...},
                           declare,<0.3705.0>]}},
                  {restart_type,intrinsic},
                  {shutdown,4294967295},
                  {child_type,worker}]}]}}
Error: function_clause
Stack trace: [{error_logger_file_h,write_event,
               [{<0.69.0>,"/var/log/kolla/rabbitmq/rabbit.log",[]},
                {info_report,<0.108.0>,
                 {<0.3706.0>,progress,
                  [{supervisor,{<0.3706.0>,rabbit_amqqueue_sup}},
                   {started,
                    [{pid,<0.3707.0>},
                     {name,rabbit_amqqueue},
                     {mfargs,
                      {rabbit_prequeue,start_link,
                       [{amqqueue,
                         {resource,<<"/">>,queue,
                          <<"q-agent-notifier-l2population-update_fanout_5d7c713ed32f4801b6532d05ed811559">>},
                         false,false,none,
                         [{<<"x-expires">>,signedint,1800000},
                          {<<"x-ha-policy">>,longstr,<<"all">>}],
                         none,[],[],[],undefined,[],[],live},
                        declare,<0.3705.0>]}},
                     {restart_type,intrinsic},
                     {shutdown,4294967295},
                     {child_type,worker}]}]}}],
               [{file,"error_logger_file_h.erl"},{line,113}]},
              {error_logger_file_h,handle_event,2,
               [{file,"error_logger_file_h.erl"},{line,78}]},
              {rabbit_error_logger_file_h,safe_handle_event,3,[]},
              {gen_event,server_update,4,[{file,"gen_event.erl"},{line,522}]},
              {gen_event,server_notify,4,[{file,"gen_event.erl"},{line,504}]},
              {gen_event,server_notify,4,[{file,"gen_event.erl"},{line,506}]},
              {gen_event,handle_msg,5,[{file,"gen_event.erl"},{line,266}]},
              {proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,239}]}]

[Paul Bourke (pauldbourke)]

sdake, you marked this as confirmed, are you seeing this? RabbitMQ seems to be logging ok for me.

[Hui Kang (huikang27)]

I did not see any error either for centos binary/source deployment

[Paul Bourke (pauldbourke)]

Serguei, please confirm if this is still a problem, and give more info on your setup. Thanks.

[Steven Dake (sdake)]

I was able to confirm this. This is one of the reasons we moved to RDO repos for rabbitmq (to fix the dependency issues of erlang).

[Steven Dake (sdake)]

re comment #4, this bug is a duplicate of another bug. Not sure which one. However, since its marked invalid, that should be good enough for the paper pushing.

Regards
-steve

[Jeffrey Zhang (jeffrey4l)]

@sdake, so it should not affect master branch, too. I saw the rabbitmq logs in my env.

[Jeffrey Zhang (jeffrey4l)]

Sorry, just notice the bug is marked invalid now. please ignore my above comment.