[Maas-devel] Installing maas on new saucy instances seems to fail all the time

Julian Edwards julian.edwards at canonical.com
Thu Nov 14 23:27:03 UTC 2013


Andres, have you seen this below?  It happens as part of apt-get install maas 
but I can't make it work when doing apt-get install -f either.  There's a 
stray epmd process running, and killing it doesn't help at all.

I can start the service manually but then running apt-get install -f will fail 
again.

Help!

-----------

ubuntu at juju-canonistack-machine-1:/tmp$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up rabbitmq-server (3.1.3-1) ...
 * Starting message broker rabbitmq-server                                        
* FAILED - check /var/log/rabbitmq/startup_\{log, _err\}
                                                                          [fail]
invoke-rc.d: initscript rabbitmq-server, action "start" failed.
dpkg: error processing rabbitmq-server (--configure):
 subprocess installed post-installation script returned error exit status 1
No apport report written because MaxReports is reached already
                                                              Errors were 
encountered while processing:
 rabbitmq-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

ubuntu at juju-canonistack-machine-1:~$ cat /var/log/rabbitmq/startup_log 
ERROR: epmd error for host "juju-canonistack-machine-1": address (cannot 
connect to host/port)






More information about the Maas-devel mailing list