[rabbitmq-discuss] Mnesia db integrity

[Valentino Volonghi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm doing some deployment testing on EC2 in these days using EBS to  
store
the mnesia directory for rabbitmq and I found a problem that I need to  
solve.

Basically the issue is something that was already discussed an year on  
this
list. After a simulated crash (basically just shutdown the system  
without stopping
services) and a restart rabbitmq reacts by crashing on the mnesia  
directory.

The error is essentially timeout_waiting_for_tables  which I suppose  
means that
the system crashed while everything was in the middle of a transaction  
of some
kind (the server though wasn't hit with any traffic and no messages  
were around).

I thought that by saving rabbitmq log files and removing the mnesia  
files rabbitmq
would have picked up the undelivered messages but apparently all I get  
from
the logs is a:

Rolling persister log to "/mnt/ebs/adrollserver/mnesia/adserverrmq/ 
rabbit_persister.LOG.previous"

Which basically means that it discards my messages that won't be  
transmitted again.

Is there any way to automatically or manually fix this issue or to  
have rabbitmq
not choke on it?

- --
Valentino Volonghi aka Dialtone
Now running MacOS X 10.5
Home Page: http://www.twisted.it
http://www.adroll.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAkmDX2IACgkQ9Llz28widGVj1gCdEwwmKS4Bdx7pDS82yBSWLnJq
CusAn0Nm7s4StRx+kVfaf25hZSiMmcAW
=w0tx
-----END PGP SIGNATURE-----