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!
Related
I have a java application which is currently deployed in weblogic clustered environment with 2 managed servers. Would like to enable remote debugging for me to investigate further the issue on session data replication. I followed the steps provided here. After restarting the 2 managed servers, it seems the configuration has no effect. I used the same debug config below in my 2 managed servers.
-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8457,server=y,suspend=n
I also tried adding the below line on each managed server startup script.
export debugFlag=true
export DEBUG_PORT=8457
I use telnet command and got this error: Could not open connection to the host, on port 8457: Connect failed.
Linux firewall is already disabled.
Has anyone already encountered this issue? In addition, how to use it for me to enable debug in my IDE (e.g. Eclipse/IntelliJ)
Thanks in advance for the help.
This is already resolved. As advised by #devwebcl, I put the additional script below in my startManagedWebLogic.sh
export JAVA_OPTIONS="${JAVA_OPTIONS} -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8457,server=y,suspend=n"
I put the same argument (e.g. -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8457,server=y,suspend=n) in the Server Start argument section on each managed server in weblogic admin console.
It will make sure that either you start your managed server via weblogic admin console or via shell startup script of each managed server, the same argument will be picked up.
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.
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
I am new to Mesos and just finished setting up mesos and along with zookeeper on my test server.
Unfortunately I keep getting this error message on my mesos console indicating i am unable to connect to mesos on port 5050 and can't seem to figure out why.
I have included the error in the screen shot below
The mesos log files doesn't point to why the error is showing either.
I resolved the problem by this:
./bin/mesos-master.sh --ip=x.x.x.x --work_dir=/var/lib/mesos --hostname=x.x.x.x
We can avoid this problem by starting mesos-master with following option:
--ip=xx.xx.xx.xx --hostname_lookup=false
I have resolved this problem. Open the web page in Chrome, and open the developer tool, you will see the chrome is accessing the web site with domain, in my case the domain name is "mesosphere", as there is no mesosphere in dns, so the accessing was failed.
I solved the problem by adding the mesosphere in the hosts file, C:/windows/system32/etc/hosts/
If you use the domain name for the Mesos cluster you must set the domain name in windows hosts.
There can be multiple issues here.
Is your mesos-master running and healthy ?
Has leader election process completed, if all is good.
Check if you are able to do
ping leader.mesos
If above ping doesn't work, that means leader has not been elected. First fix that.
I had this problem also. Luckily, I have a running mesos server also. So, I can compare the different between my demo and the running mesos server. I captured the packets between client and server in my demo. I found the explorer didn`t resend fresh request, only some keepalive packets.
but, when I catch the packets in the running mesos server, I found the explorer send get request frequently. like the image
I think, if you run some task or add some agent, maybe it will activate the explore to send request frequently. Then the "Failed to connect" will disappeared.
I was having the same issues and what fixed it for me was the zookeeper configuration. In my case I was using the EC2 public IP Address rather than the private one. Once I changed the /etc/mesos/zk file to zk://<private IP>:2181/mesos I was able to connect without the constant error messages. In other words, zookeeper was reporting to be running in one IP and mesos-master was trying to connect using a different IP.
My configuration was correct as suggested. But failed to start mesos-master service. But There is alternative way to start mesos-master node with exact same configuration. Commands to start mesos-master
$ cd /usr/sbin [or mesos_installation directory/bin]
$sudo ./mesos-master --work_dir=/var/lib/mesos --log_dir=/home/rajeev/logs/mesos/
Its start mesos-master service successfully for me.
I am having some issues accessing the rabbitmq_management plugin.
I am running RabbitMQ 3.6.2, where rabbit is installed as a service and the plugin is enabled. Running on Windows Microsoft Server 2012.
Service runs fine, no errors in logs, however when i try and access the management tool via the web browser UI, "This page can't be displayed", I am sure i am going to the right port as the logs show the port it is running on, i have tried adding some rules to the Inbound on the firewall in case it was to do with ports and nothing seems to work. Any ideas?
EDIT
I am able to access the port via another machine on the network but does still not work in local host.