RabbitMQ node 'rabbit' not running at all - rabbitmq

Some of the commands I've tried running
Some more of the commands I've tried running
I've recently tried installing RabbitMQ version 3.8.2 through chocolatey which in turn installs erlang version 22.3 . I've checked that the erlang cookies match, that the port 4369 is open and listening. I've added an environment variable called "RABBITMQ_NODENAME" with the value "rabbit#localhost". I've tried uninstalling and reinstalling countless times and I've also tried running most cli commands but cannot for the life of me get the node running. I can't get a status out of rabbitmqctl or rabbitmq-diagnostics because the node isn't running and when I try to run the start_app command it doesn't work and returns nothing for the error message. Any help would be greatly appreciated!

Related

How to fix HTTPD (Apache) Error 256 on OSX Monterey 12.5

I have a Apache2 installed with Homebrew on a Mac running OSX Monterey. I haven't done LAMP development for a while, so I'm not sure when the error started, but I've recently updated OSX to 12.5. When I returned to working on a LAMP project, my Apache installation stopped working. Running brew services produced the following output: Name Status User File httpd error 256 root ~/Library/LaunchAgents/homebrew.mxcl.httpd.plist mysql started Nizz0k ~/Library/LaunchAgents/homebrew.mxcl.mysql.plist.
Running the stop, start, and restart commands produces "success" output in the terminal, but Apache doesn't work. I can't navigate to my local vhosts, and of course, running brew services still shows an error.
In running apachectl -e error Apache complains about permissions to the error logs
I have tried:
uninstalling and reinstalling HTTPD
The apr-utilities fix.
confirming Mac installed Apache is stopped.
At this point, I think my problem is that there was conflicting information about how to run Apache on Homebrew. Earlier versions apparently required sudo, but running it this was now produces warnings like this:
Warning: Taking root:admin ownership of some httpd paths:
/usr/local/Cellar/httpd/2.4.54/bin
/usr/local/Cellar/httpd/2.4.54/bin/httpd
/usr/local/opt/httpd
/usr/local/opt/httpd/bin
/usr/local/var/homebrew/linked/httpd
This will require manual removal of these paths using `sudo rm` on
brew upgrade/reinstall/uninstall.
Warning: httpd must be run as non-root to start at user login!
/Library/LaunchDaemons/homebrew.mxcl.httpd.plist: service already bootstrapped
Bootstrap failed: 37: Operation already in progress
Error: Failure while executing; `/bin/launchctl bootstrap system /Library/LaunchDaemons/homebrew.mxcl.httpd.plist` exited with 37.
The issue is even after removing the paths as suggested in the error, a reinstallation brings Root back as the owner.
I do have the same problem with nginx.
Manually unloaded it and then restarting it worked fine.
Try:
sudo launchctl bootout system /Library/LaunchDaemons/homebrew.mxcl.httpd.plist
sudo brew services start httpd

RabbitMQ Boot failed. Getting logger error

I am trying to run rabbitmq server on my mac and i keep getting this error:
Starting broker...Logger - error: {removed_failing_handler,rabbit_log}
BOOT FAILED
I have tried reinstalling it several times and even logged into local host but see the same error.
Managed to fix it. Ran these commands to fully uninstall RabbitMQ (vhosts, users too).
sudo apt-get remove --auto-remove rabbitmq-server
sudo apt-get purge --auto-remove rabbitmq-server
Then after I reinstalled everything worked.
Another possibility is that you are running it on Big Sur- it keeps on giving errors to me that I didn't get previously.
Try pip3 uninstall rabbitmq-server then pip3 install rabbitmq server- that worked for me.

Can't Access newly installed redis(5.0.5) on Ubuntu 19.10

I newly installed Ubuntu 19.10, and installed redis with sudo apt install redis-server(5.0.5).
And started sudo systemctl start redis.
Executed redis-cli, then I got Could not connect to Redis at 127.0.0.1:6379: Y
The last 1 charactor (Y in this case) is different each time.
I just installed with using apt and didn't change any configs.
Is there any bugs or something I missed? please help me.
I tried to install from source code (5.0.7).
It works.

stuck on the first step of ambari 2.7.3 install wizard

I have installed the Hortonworks sandbox HDP 2.6.5 (docker install).
After having many issues with Ambari "HeartBeat lost" I decided to upgrade Ambari to the latest version, so I cleanly uninstall ambari and then install 2.7.3 following the instructions from:
https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.7.3
After a long process I managed to complete the installation and start both services successfully: "ambari-server" and "ambari-agent"
Now I am stuck on the install wizard in the fisrt step without getting any error
or any progress. That is, after hitting "Next" it never gets to step 2. (see picture)
screenshot showing the issue
Things done so far to try to work this around:
restarting services (several times)
ambari-server upgrade (once more)
trying with chrome and IE
looking at the log files of ambari-server and ambari-agent
...but without success.
Has anybody come across the same issue?
Any clues?
Thanks for your help!
I have faced the same issue and I have activated the stack as shown below:
sudo sed -i 's|<active>false</active>|<active>true</active>|g' /var/lib/ambari-server/resources/stacks/HDP/2.6/metainfo.xml
sudo sed -i 's|<active>false</active>|<active>true</active>|g' /var/lib/ambari-server/resources/stacks/HDP/2.4/metainfo.xml
cat /var/lib/ambari-server/resources/stacks/HDP/2.6/metainfo.xml
cat /var/lib/ambari-server/resources/stacks/HDP/2.4/metainfo.xml
then I restarted the ambari-server and then it worked.
you have broken stacks for HDP. make sure you fresh build ambari 2.7.3 from source
https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.7.3
https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development
copy folder and contents inside HDP stacks
/root/ambari-release-2.7.3/ambari-server/src/main/resources/stacks/HDP
ambari-release-2.7.3 is folder result build from source
paste to broken ambari-server
/var/lib/ambari-server/src/main/resources/stacks/
restart ambari server

RabbitMQ on Ubuntu 16.04 on Windows Subsystem for Linux

I am running RabbitMQ on Ubuntu 16.04 under the Windows 10 "windows on linux" installation.
I cannot connect using rabbitmqctl. I used su to run as root and also tried to run it under my username with sudo, but everytime I run the command I get:
Diagnostic log
attempted to contact: ['rabbit#SJDEV-JWRIGHT3']
rabbit#SJDEV-JWRIGHT3:
* connected to epmd (port 4369) on SJDEV-JWRIGHT3
* epmd reports node 'rabbit' running on port 25672
* TCP connection succeeded but Erlang distribution failed
* suggestion: hostname mismatch?
* suggestion: is the cookie set correctly?
* suggestion: is the Erlang distribution using TLS?
current node details:
- node name: 'rabbitmq-cli-133#SJDEV-JWRIGHT3'
- home dir: /var/lib/rabbitmq
- cookie hash: iLmkDqwKzDZPxk8ynhqsVw==
I have uninstall and re-installed both Erlang and RabbitMQ. I changed the host names as suggested by someone else, and I still cannot figure out this problem.
I have rebooted the system, and when I tried to run rabbitmq-server restart and got:
ERROR: node with name "rabbit" already running on "SJDEV-[NODE]"
I am new to linux and have been digging in to this for a week and hit my breaking point.
Okay I found out the problem in a round about way. I am running this version of Ubuntu on the Windows Subsystem for Linux application on my windows 10 machine. My windows machine is already running rabbitmq and it happens to be on the same node as the node that I was trying to access using the rabbitmqctl. So there must be a correlation between the Ubuntu and windows system that shows rabbitmq already running. I may try this on a VM and see if I can get a clean break and try again.
Thanks.
I had this issue today.
My config is below:
Have a rabbitmq-server on Windows 10 OS
Have a rabbitmq-server on Ubuntu which was installed on Windows 10 OS (Ubuntu 18.04 app from Windows store)
Now below error makes sense:
ERROR: node with name "rabbit" already running on "MyComputerNamehere"
Another hint was Windows OS firewall has allowed both of them, in other words, they are running on same computer with name (ex: MyComputerNamehere).
Though I know the issue, I didn't fix it by removing rabbitmq-server from Windows 10, as I wanted Windows 10 rabbitmq-server, so gave up on Ubuntu on Windows 10.
Hope this explanation helps someone.