[rabbitmq-discuss] RabbitMQ broker's death by one cut: robustness problem

Lev Walkin vlm at lionet.info
Mon Apr 27 11:46:19 BST 2009

During evaluation period, our RabbitMQ node has crashed at some point, 
killed by OOM killer. Unfortunately, killing corrupted the log files, so 
RabbitMQ restart did not fix the problem. RabbitMQ just would not start:

[broker at zamq ~]> /usr/local/bin/rabbitmq-server -kernel check_ip true 
-connect_all false
Logging to "/.../rabbitmq/log/rabbit.log"
SASL logging to "/.../rabbitmq/log/rabbit-sasl.log"

starting database             ...done
starting core processes       ...done
starting recovery             ...done
starting persister            ...{"init terminating in 
init terminating in do_boot ()
[broker at zamq ~]>

It turns out, the broker beam was killed during a persister operation, 
so persister logs were broken:

[broker at zamq ...]> ls -al | grep persister
-rw-r--r--  1 broker  wheel          8 Apr 24 18:48 rabbit_persister.LOG
-rw-r--r--  1 broker  wheel  661677171 Apr 24 18:19 
[broker at zamq ~]> hd rabbit_persister.LOG
00000000  01 02 03 04 63 58 4d 0b                           |....cXM.|
[broker at zamq ...]>

I believe there is a way to make such error recovery more robust. Is 
there a solution you'd like to introduce for this kind of problem?

Lev Walkin
vlm at lionet.info

More information about the rabbitmq-discuss mailing list