New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RabbitMQ exits with error during install #520

frecuencialibre opened this Issue Sep 19, 2018 · 3 comments


None yet
2 participants
Copy link

frecuencialibre commented Sep 19, 2018

hello all, y buenas noches,

today we hit a new snag upon trying to install libretime in a fresh instance of ubuntu 16 running as a virtual machine. From the ./install output:

               * Configuring RabbitMQ *               
Error: unable to connect to node rabbit@libretime: nodedown


attempted to contact: [rabbit@libretime]

  * connected to epmd (port 4369) on libretime
  * epmd reports: node 'rabbit' not running at all
                  no other nodes on libretime
  * suggestion: start the node

current node details:
- node name: 'rabbitmq-cli-8940@libretime'
- home dir: /var/lib/rabbitmq
- cookie hash: 7Y30JTYnxpNxLQwmUmWuPQ==

systemctl status rabbitmq-server.service reports that

● rabbitmq-server.service - RabbitMQ Messaging Server
   Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled)
   Active: failed (Result: timeout) since mar 2018-09-18 17:35:22 CDT; 2s ago
  Process: 28398 ExecStartPost=/usr/lib/rabbitmq/bin/rabbitmq-server-wait (code=killed, signal=TERM)
  Process: 28397 ExecStart=/usr/sbin/rabbitmq-server (code=killed, signal=TERM)
 Main PID: 28397 (code=killed, signal=TERM)

sep 18 17:33:51 libretime systemd[1]: Starting RabbitMQ Messaging Server...
sep 18 17:34:41 libretime rabbitmq[28398]: Waiting for rabbit@localhost ...
sep 18 17:34:41 libretime rabbitmq[28398]: pid is 28417 ...
sep 18 17:35:21 libretime systemd[1]: rabbitmq-server.service: Start-post operation timed out. Stopping.
sep 18 17:35:22 libretime systemd[1]: Failed to start RabbitMQ Messaging Server.
sep 18 17:35:22 libretime systemd[1]: rabbitmq-server.service: Unit entered failed state.
sep 18 17:35:22 libretime systemd[1]: rabbitmq-server.service: Failed with result 'timeout'.

So then I tried to follow the instructions in Preparing the Server to fix the RabbitMQ hostname

Specifically my 2 attempts to configure RabbitMQ were to edit /etc/rabbitmq/rabbitmq-env.conf

Either with


or by adding a snippet from the stack overflow question linked from libretime documentation.

export RABBITMQ_NODENAME=rabbit@localhost

Either of these do appear to change the hostname in the the error message I see when I run sudo service rabbitmq-server start. Now it says says rabbit@localhost instead of rabbit@libretime, but it's the same error and it still won't start, and so will most probably still abort the libretime install script.

The only modifications we've made to the fresh ubuntu 16 server are the following. Details in the documentation we've been writing simultaneously (in spanish) Not sure if any of them could be related.

  • edited hosts file to resolve our custom base_url back to
  • virt-manager virtual machine network set as a br0 from the server
  • VM given fixed ip set in /etc/network/interfaces
  • sshfs loads a shared folder from the server upon VM startup

...and so I could really use some direction. :)

thanks everyone!


This comment has been minimized.

Copy link

Robbt commented Sep 20, 2018

If rabbitMq thinks your hostname is libretime you can edit /etc/hosts and create an entry for libretime that points to and that shoould fix it. basically add libretime

But I'm not an expert on rabbitMq, there is work on a PR with docker and a specific VM for rabbitmq and other services. I haven't messed with it yet but plan to do so soon.

Sorry I can't be of more help. But I can understand enough spanish to get an idea that you are running LibreTime in a machine as a VM, and I think that Docker might work better for this than going through the whole creating mulitple virtual machines as that is what it is designed to do see #517


This comment has been minimized.

Copy link

frecuencialibre commented Sep 20, 2018

Thanks Rob, I'd already tried that fix in ´hosts´, but haven´t yet tried the RabbitMQ "resetting" steps in the S.O. answer you linked in the forum. We are definitely interested in exploring using docker to be able to manage server configuration (these kind of issues), and also to be able to run multiple instances (production, staging) in order to be able to ensure reliability for the station while actively developing and deploying updates.


This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment