Problem with upgrading RabbitMQ from 3.3.5 to 3.4.3

[Yury A]

Hi guys!

I've updated my RabbitMQ server on RedHat Linux platform from version 3.3.5 to 3.4.3 and server can't start correctly.

Below you can see messages from different log files:

Linux 2.6.32-358.14.1.el6.x86_64 :/var/log/rabbitmq>cat startup_log

BOOT FAILED

===========

Error description:

   {error,previous_upgrade_failed}

Log files (may contain more information):

   /var/log/rabbitmq/rab...@srv2-4pd-hasg08.log

   /var/log/rabbitmq/rab...@srv2-4pd-hasg08-sasl.log

Stack trace:

   [{rabbit_upgrade,ensure_backup_taken,0,[]},

    {rabbit_upgrade,maybe_upgrade_mnesia,0,[]},

    {rabbit,'-boot/0-fun-0-',0,[]},

    {rabbit,start_it,1,[]},

    {init,start_it,1,[]},

    {init,start_em,1,[]}]

{"init terminating in do_boot",{rabbit,failure_during_boot,{error,previous_upgrade_failed}}}

Linux 2.6.32-358.14.1.el6.x86_64 :/var/log/rabbitmq>cat startup_err

Crash dump was written to: erl_crash.dump

init terminating in do_boot ()

Is it a known bug? And how can I deal with it?

[Michael Klishin]

On 15 January 2015 at 14:49:57, Yury A (haste...@gmail.com) wrote:
> Is it a known bug? And how can I deal with it?

Either you have schema_upgrade_lock in the database directory for some reason, or RabbitMQ
cannot create it. In any case, the upgrade shouldn't have started with this message. Remove the lock
file if any and try again and check permissions on the database directory. 
--
MK

Staff Software Engineer, Pivotal/RabbitMQ

[Michael Klishin]

 On 15 January 2015 at 14:49:57, Yury A (haste...@gmail.com) wrote:

> Log files (may contain more information):
> /var/log/rabbitmq/rab...@srv2-4pd-hasg08.log
> /var/log/rabbitmq/rab...@srv2-4pd-hasg08-sasl.log

This name suggests it may be a cluster member. Are you trying to upgrade one cluster member while other
are running?

[Yury A]

Michael, thanks for reply!

Yep, it was lock file in database directory and I erased it.

After that server started successfully, but when I open management plugin UI there weren't  any queues and exchanges (only old users and vhost were available)

Also when I open Exchanges page I receive an error: ReferenceError: show_column is not defined

[Michael Klishin]

On 15 January 2015 at 15:45:01, Yury A (haste...@gmail.com) wrote:
> Yep, it was lock file in database directory and I erased it.
> After that server started successfully, but when I open management
> plugin UI there weren't any queues and exchanges (only old users
> and vhost were available)

See the logs. I suspect you had a real upgrade failure earlier but I can't know what it might have been.

[Yury A]

Michael, what logs do you mean? 

RabbitMQ?

Now I remove RabbitMQ 3.4.3 packet, after what install back 3.3.5 version, create some queues and exchanges.

Then update it to 3.4.3, so server started but managment plugin still get me errors if I try to open any of Overview, Exchanges or Queues tab

[Michael Klishin]

On 15 January 2015 at 16:48:51, Yury A (haste...@gmail.com) wrote:
> Michael, what logs do you mean?
> RabbitMQ?

Correct.

> Now I remove RabbitMQ 3.4.3 packet, after what install back 3.3.5
> version, create some queues and exchanges.
> Then update it to 3.4.3, so server started but managment plugin
> still get me errors if I try to open any of Overview, Exchanges
> or Queues tab

Try clearing your browser's cache.

[Yury A]

It's a pity but I have cleared log directory after updating RabbitMQ

 

Try clearing your browser's cache.

Thanks, it helps me =)