I am playing over with replication and fail-over scenarios with RabbitMQ. So I copied over the database directory<br>of production RabbitMQ server to a different machine and tried to restart the RabbitMQ server with the database <br>
of the production server. The production machine is running Linux and the destination machines are Linux + MacOSX.<br><br>The startup fails on both server...isn't the database portable across different machine?<br>Or is there some other way for moving a production database directory from one server to another?<br>
<br>Andreas<br><br>-----------<br><br>AMQP 8-0<br>Copyright (C) 2007-2010 LShift Ltd., Cohesive Financial Technologies LLC., and Rabbit Technologies Ltd.<br>Licensed under the MPL. See <a href="http://www.rabbitmq.com/">http://www.rabbitmq.com/</a><br>
<br>node : rabbit@db01<br>app descriptor : /home/ajung/occ/parts/rabbitmq/ebin/rabbit.app<br>home dir : /home/ajung<br>cookie hash : OdO1XbpYQTCCD1J+eBaKtQ==<br>log : /home/ajung/occ/data/logs/rabbit/rabbit.log<br>
sasl log : /home/ajung/occ/data/logs/rabbit/rabbit-sasl.log<br>database dir : /home/ajung/occ/data/db/rabbit<br>erlang version : 5.6.5<br><br>starting file handle cache server ...done<br>
starting worker pool ...done<br>starting database ...Erlang has closed<br>{"init terminating in do_boot",{{nocatch,{error,{cannot_start_application,rabbit,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{{case_clause,{error,{timeout_waiting_for_tables,[rabbit_user,rabbit_user_permission,rabbit_vhost,rabbit_config,rabbit_listener,rabbit_durable_route,rabbit_route,rabbit_reverse_route,rabbit_durable_exchange,rabbit_exchange,rabbit_durable_queue,rabbit_queue]}}},[{rabbit,'-run_boot_step/1-lc$^1/1-1-',1},{rabbit,run_boot_step,1},{rabbit,'-start/2-lc$^0/1-0-',1},{rabbit,start,2},{application_master,start_it_old,4}]}}}}}}},[{init,start_it,1},{init,start_em,1}]}}<br>
<br>Crash dump was written to: erl_crash.dump<br>init terminating in do_boot ()<br><br>