I have built RabbitMQ 3.7.3 from source on Ubuntu 16.04 using the following steps:
1)Installed Erlang 20.0, Elixir 1.6.1 and hex 0.17.3.
2) git clone https://github.com/rabbitmq/rabbitmq-server.git &&
cd rabbitmq-server/ &&
git checkout v3.7.3 &&
make all
The build was successful and I'm able to start the server using make run-broker and also can see server status using rabbitmqctl status but I can't enable the management plugin as its not found in the source. Is it built/downloaded during the build? How do I get and enable the Management plugin in order to access the UI?
I'm following http://www.rabbitmq.com/build-server.html and https://www.rabbitmq.com/management.html
The RabbitMQ team monitors this mailing list and only sometimes answers questions on StackOverflow.
As theMayer said, you really should be using a package. To build from source and have plugins available, use this project:
https://github.com/rabbitmq/rabbitmq-public-umbrella
The following command will run the broker with the management plugin enabled:
make PLUGINS='rabbitmq_management run-broker
The source for the RabbitMQ Management Plug-in is located on GitHub, at the following location:
https://github.com/rabbitmq/rabbitmq-management
There are guides available as well for building, and I'm not sure about installing it as I've only ever used the pre-packaged builds.
By default RabbitMQ web management console runs on port 15672. So you will need to allow this port through UFW firewall. By default UFW firewall is disabled in Ubuntu 16.04, so you will need to enable it first. You can enable UFW filrewall with the following command:
sudo ufw enable
Once UFW is enabled, allow port 15672 using the following command:
sudo ufw allow 15672
Related
I have created minishift env using comment:
"minishift start --vm-driver=virtualbox -v5 --show-libmachine-logs --alsologtostderr"
Now I have the console for minishift working.
I have to make some changes to master node config files a
To connect to the Minishift VM you can use minishift ssh command which will connect the cmd/Powershell session to the shell on the VM. You can then do whatever changes you want to do using sudo, which is on the VM password-less. However please note that changing the VM directly is not recommended and might cause problems.
To make the changes to the master node you could also use minishift openshift config command which provides way to alter OpenShift's cluster configuration. In general using this command with combination with oc adm is advised for most users as it should be more secure and robust solution than altering the configs directly in the VM.
I have installed Rabbitmq on my server. Suddenly I needed to remove a queue and I could not. I decided to remove and reinstall Rabbitmq but now I can not run it. I user this article https://linoxide.com/ubuntu-how-to/install-setup-rabbitmq-ubuntu-16-04/ and got this error:
https://imgur.com/a/lL0xln6
Problem was related to some DNS and Hostname settings on my server. I just try to use a new server for AMQP as Saas.
There two containers which is running in two physical machines.One container for Ops-center and other is for (datastax Cassandra + Ops-center agent).I have have manually installed Ops-center agent on each Cassandra containers.This setup is working fine.
But Ops-center can not upgrade nodes due to fail ssh connections to nodes. Is there any way create ssh connection between those two containers. ??
In Docker you should NOT run SSH, read HERE why. After reading that and you still want to run SSH you can, but it is not the same as running it on Linux/Unix. This article has several options.
If you still want to SSH into your container read THIS and follow the instructions. It will install OpenSSH. You then configure it and generate a SSH key that you will copy/paste into the Datastax Opscenter Agent upgrade dialog box when prompted for security credentials.
Lastly, upgrading the Agent is as simple as moving the latest Agent JAR or the version of the Agent JAR you want to run into the Datastax-agent Bin directory. You can do that manually and redeploy your container much simpler than using SSH.
Hope that helps,
Pat
I am using arangodb 2.8.5 on ubuntu 14.04 (64bit)
In config file, endpoint = ssl://0.0.0.0:443
fails to start with error msg in log "FATAL failed
to bind to endpoint 'ssl://0.0.0.0:443'. Please check whether another
instance is already running or review your endpoints configuration."
Ran netstat -lnpt. Only port 22 is in use by ssh
Server starts up and binds to port 8530 with ssl when using endpoint = ssl://0.0.0.0:8530. Admin website is accessible https://www.website.com:8530/.../
I want the admin ui to be accessible without the need for additional port 8530 i.e. https://www.website.com/. This was possible to set up in the earlier versions. What am i doing wrong or is this not possible anymore?
Small application so i am trying to avoid running another web server in front to forward requests to arango apps. Thank you very much for any direction.
Regards,
Anjan
The problem occurs in conjunction with ArangoDB dropping its root privileges to the specified user by
[server]
endpoint = ssl://0.0.0.0:443
uid=arangodb
This may become possible with ArangoDB 3.0 again, however currently you have to choose one of the workarounds to allow non-root processes to bind lower ports:
authbind
Using the iptables REDIRECT target to redirect a low port to a high port (the "nat" table is not yet implemented for ip6tables, the IPv6 version of iptables)
SELinux or AppArmor
Use the capabilities system available as of Linux kernel 2.6.24 and CAP_NET_BIND_SERVICE capability:
setcap 'cap_net_bind_service=+ep' /usr/sbin/arangod
And then anytime ArangoDB is executed thereafter it will get the CAP_NET_BIND_SERVICE capability. setcap is in the debian package libcap2-bin.
More details on the capabilities can be found at:
capabilities(7) man page. Read this long and hard if you're going to use capabilities in a production environment. There are some really tricky details of how capabilities are inherited across exec() calls that are detailed here.
setcap man page
"Bind ports below 1024 without root on GNU/Linux"
Does anyone know how to get to the rabbitmq web management console on cloud9?
I see it is running, but bound to 0.0.0.0.
I'm new to RabbitMQ, but after a bit of googling and experimentation, I was able to run the management console.
The problem is that only port 8080 is forwarded from your Cloud9 workspace, and RabbitMQ's default port is explained here:
The web UI is located at: http://server-name:15672/
To fix, we need to modify the configuration to start the web UI at port 8080. Here are the steps I followed to get that working:
Install RabbitMQ (Steps outlined here: http://www.rabbitmq.com/install-debian.html)
Enable the management console: sudo rabbitmq-plugins enable rabbitmq_management
There wasn't a rabbitmq.config file for me in $RABBITMQ_HOME/etc/rabbitmq/, so I copied the example from /usr/share/doc/rabbitmq-server/ (after unzipping it).
Edited $RABBITMQ_HOME/etc/rabbitmq/rabbitmq.config and found the rabbitmq_management key. There's already an existing setup that's commented out. I replaced it with:
{listener, [{port, 8080},
{ip, "0.0.0.0"},
{ssl, false}]}
Then I restarted the RabbitMQ server and visiting my url, i.e.: https://<workspacename>-<username>.c9.io showed me the RabbitMQ management login screen.
Hope this helps!