[rabbitmq-discuss] After weekly log rotatation was done, the command "rabbitmqctl rotate-logs" never stop
natewang0425 at gmail.com
Wed May 15 09:51:30 BST 2013
1. Did logs get rotated successfully in the past or did all log rotations get
Only two of nodes in the cluster get stuck. And two clusters are in the
2. Your initial report showed a few more processes, including a
Presumably that's still there too, right? If so, please post the 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.
Thanks for your help!
2013/5/15 Matthias Radestock-3 [via RabbitMQ] <
ml-node+s1065348n26696h41 at n5.nabble.com>
> On 15/05/13 07:52, Nate wrote:
> > After doing the rabbitmqctl rotate_logs, rabbitmq.log.1 show the '
> > Rotating logs with suffix '' ' in the end of log file and rabbitmq start
> > writing the new logs to rabbitmq.log.
> Great. That's good to know. So it appears that everything is well with
> your server and that the problem is with the logrotate initiation.
> > However, the old rotate process were
> > still exist. BTW, my another 3-node cluster has same log rotate issue
> > today.....
> Did logs get rotated successfully in the past or did all log rotations
> get stuck?
> > root 8944 0.0 0.0 8668 1052 ? S May12 0:00 sh -c ?
> > /sbin/service rabbitmq-server rotate-logs > /dev/null? ?
> > /sbin/service rabbitmq-server rotate-logs > /dev/null?
> > /var/log/rabbitmq/*.log
> > root 8946 0.0 0.0 8804 1296 ? S May12 0:00 /bin/sh
> > /sbin/service rabbitmq-server rotate-logs
> > root 8951 0.0 0.0 10896 1392 ? S May12 0:00 /bin/sh
> > /etc/init.d/rabbitmq-server rotate-logs
> Your initial report showed a few more processes, including a beam.smp
> process. Presumably that's still there too, right? If so, please post
> the complete command line for that.
> You could just kill that process, but I am keen to get to the bottom of
> the problem so am hoping that we will be able to get that process to
> tell us where it's stuck.
> rabbitmq-discuss mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=26696&i=0>
> If you reply to this email, your message will be added to the discussion
> 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=>
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-tp26607p26705.html
Sent from the RabbitMQ mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss