Public bug reported:

Today I performed an upgrade from 1.4+bzr1693+dfsg-0ubuntu2.3~ctools0 to
1.5+bzr2204-0ubuntu1 and got this error from rabbit:

Considering dependency proxy for proxy_http:
Module proxy already enabled
Module proxy_http already enabled
Module expires already enabled
Module wsgi already enabled
 * Restarting message broker rabbitmq-server
   ...done. 
ls: cannot access /etc/rabbitmq/rabbitmq.conf.d: No such file or directory
Error: {'EXIT',
           {terminated,
               [{io,nl,[<0.30.0>],[]},
                {lists,foreach,2,[{file,"lists.erl"},{line,1323}]},
                {rabbit_control_main,display_info_list,2,
                    [{file,"src/rabbit_control_main.erl"},{line,651}]},
                {rabbit_control_main,start,0,
                    [{file,"src/rabbit_control_main.erl"},{line,156}]},
                {init,start_it,1,[]},
                {init,start_em,1,[]}]}}
ls: cannot access /etc/rabbitmq/rabbitmq.conf.d: No such file or directory
Changing password for user "maas_longpoll" ...
...done.        
ls: cannot access /etc/rabbitmq/rabbitmq.conf.d: No such file or directory
ls: cannot access /etc/rabbitmq/rabbitmq.conf.d: No such file or directory
Changing password for user "maas_workers" ...
...done.
Syncing...
Creating tables ...
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)

** Affects: maas (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: upgrade

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1302860

Title:
  cannot access /etc/rabbitmq/rabbitmq.conf.d: No such file or directory
  upgrading from precise maas to trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1302860/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Reply via email to