[rabbitmq-discuss] After weekly log rotatation was done, the command "rabbitmqctl rotate-logs" never stop

Thu May 16 07:36:26 BST 2013

Hi Matthias,

    Bad news, I cannot get the dump file via command "kill -SIGUSR1 8972"
and process still exist. Are there any other method to get the dump file?
Btw, this is first time the rabbitmq-server did the log rotation.
Thanks a lot.

Best Regards,
Nate

2013/5/15 Matthias Radestock-3 [via RabbitMQ] <
ml-node+s1065348n26706h51 at n5.nabble.com>

> Nate,
>
> On 15/05/13 09:51, Nate wrote:
> > 1.  Did logs get rotated successfully in the past or did all log
> > rotations get stuck?
> > Only two of nodes in the cluster get stuck. And two clusters are in the
> > same situation.
>
> My question was whether the logs on these nodes ever got rotated
> successfully in the past.
>
> > 2. Your initial report showed a few more processes, including a
> > beam.smpprocess. Presumably that's still there too, right? If so, please
> > postthe complete command line for that.
> >
> > rabbitmq  8972  0.0  2.8 580024 510588 ?       Ssl  May12   0:00
> > /usr/lib/erlang/erts-5.9/bin/beam.smp -- -root /usr/lib/erlang -progname
> > erl -- -home /var/lib/rabbitmq -- -pa
> > /usr/lib/rabbitmq/lib/rabbitmq_server-3.0.1/sbin/../ebin -noshell
> > -noinput -hidden -sname rabbitmqctl8972 -s rabbit_control_main -nodename
> > rabbit at rabbitmq1 -extra rotate_logs
> >
> > 3. I wanna know the root cause too! Therefore, I prefer to keeping the
> > process and let it telling us the reason.
>
> Unfortunately the rabbitmqctl node is a hidden node, so we cannot
> connect to it. The best we can do is make it crash with
>
>    kill -SIGUSR1 8972
>
> That should produce an erl_crash.dump. Not sure where it will end up
> though. Possibly in the rabbitmq home dir. Anyway, I'm sure you'll
> manage to track it down. Stick that crash dump on something like dropbox
> and post a link.
>
>
> Regards,
>
> Matthias.
> _______________________________________________
> rabbitmq-discuss mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=26706&i=0>
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://rabbitmq.1065348.n5.nabble.com/Re-After-weekly-log-rotatation-was-done-the-command-rabbitmqctl-rotate-logs-never-stop-tp26607p26706.html
>  To unsubscribe from Re: After weekly log rotatation was done, the command
> "rabbitmqctl rotate-logs" never stop, click here<http://rabbitmq.1065348.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=26607&code=bmF0ZXdhbmcwNDI1QGdtYWlsLmNvbXwyNjYwN3w0NTY2Njg2Njk=>
> .
> NAML<http://rabbitmq.1065348.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>

--
View this message in context: http://rabbitmq.1065348.n5.nabble.com/Re-After-weekly-log-rotatation-was-done-the-command-rabbitmqctl-rotate-logs-never-stop-tp26607p26736.html
Sent from the RabbitMQ mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130515/31648cd7/attachment.htm>