[rabbitmq-discuss] After weekly log rotatation was done, the command "rabbitmqctl rotate-logs" never stop
matthias at rabbitmq.com
Tue May 28 11:05:23 BST 2013
On 28/05/13 05:32, Nate wrote:
> I use pstack to dig the erlang procces, The log seems like the
> erlang already crash??!.
Looks like it's stuck writing the crash dump. The crash dump may have
been triggered by the SIGUSR1 - that's what it is supposed to to do - or
perhaps the process was stuck in that code already.
> Are there any other hint can help to track this issue?
As I said...
> I suggest you "walk up the call stack" of the ps output you posted
> initially and manually run the log rotation commands, to check whether
> any of them get stuck, e.g.
> /bin/sh /usr/sbin/rabbitmqctl rotate_logs
> /bin/sh /etc/init.d/rabbitmq-server rotate-logs
> /bin/sh /sbin/service rabbitmq-server rotate-logs
> sh -c ? /sbin/service rabbitmq-server rotate-logs > /dev/null? ?
> (hmm, what's with those question marks? are they placeholders for
> /usr/sbin/logrotate /etc/logrotate.conf
> /bin/sh /etc/cron.daily/logrotate
> /bin/bash /usr/bin/run-parts /etc/cron.daily
More information about the rabbitmq-discuss