I'am trying to connect web- application, deployed from one container, to rabbitmq, deployed at another container. By relying on this Connecting to RabbitMQ container with docker-compose , I created the following docker-compose: version: '3' services: webapp: container_name: chat build: context: . depends_on: - broker ports: - "8080:8080" broker: container_name: rabbit_chat image: rabbitmq command: rabbitmq-server expose: - 5672 - 15672 healthcheck: test: ["CMD", "curl", "-f", "http://broker:5672 "] interval: 30s timeout: 10s retries: 5 webapp is a service of web-application, at which I prescribe following rabbitmq-properties: host = broker port = 15672 login = guest password = guest I selected 'broker' as a host, as in documentation recommended to connect containers by default-net, using the name of service in docker-compose. And this does not work.Also I tried to use "localhost" as host for connection. Additionally, inspecting container "rabbit_chat" I see in output: "Log": [ { "Start": "2020-04-11T14:54:25.0988242Z", "End": "2020-04-11T14:54:25.2920557Z", "ExitCode": -1, "Output": "OCI runtime exec failed: exec failed: container_linux.go:346: starting container process caused \"exec: \\\"curl\\\": executable file not found in $PATH\": unknown" }

I have a problem with my SH script, I'm writing a SH script that automates the installation of OpenStack Keystone, and also uses a small configuration file, everything works fine but due to a syntax error on my part OpenStack command, script fails when something has already been created, example RabbitMQ user, Project or OpenStack User The contents of my SH script is this:

#!/usr/bin/env bash

set -e
set -o xtrace

source "$PWD/install-keystone.conf"

conf=/etc/keystone/keystone.conf

if [ "$EUID" -ne 0 ]; then 
  echo "To proceed with the installation of OpenStack Keystone you must be root user"
  echo "Please run as root"
  exit 1
fi


config_mysql()
{
apt install mariadb-server python3-pymysql -y


if ! test -f /etc/mysql/mariadb.conf.d/99-openstack.cnf; then
cat >> /etc/mysql/mariadb.conf.d/99-openstack.cnf > /root/admin-openrc.sh > /root/demo-openrc.sh << EOF
export OS_PROJECT_DOMAIN_NAME=Default
export OS_USER_DOMAIN_NAME=Default
export OS_PROJECT_NAME=demo
export OS_USERNAME=demo
export OS_PASSWORD=$DEMO_PASSWORD
export OS_AUTH_URL=http://$HOST_IP:5000/v3 
export OS_IDENTITY_API_VERSION=3
export OS_IMAGE_API_VERSION=2
EOF
fi

}

config_mysql
config_rabbitmq
install_pkgs
create_keystone_database
conf_keystone
create_projects_users
request_auth_token
create_cli_environment_scripts

echo ""
echo ""
echo ""
echo "This is your host IP address: $HOST_IP"
echo "Keystone URL is available at http://$HOST_IP:5000/ "
echo "The default users are: admin and demo"
echo "The password of administrator is '$ADMIN_PASSWORD'"
echo ""
echo "OpenStack Keystone has been successfully installed!"
echo "Learn more about Keystone in guides and more from : https://docs.openstack.org/keystone/latest/ "
echo ""
echo "Now connect this Keystone installation to other OpenStack services"
echo "It is recommended to subsequently install Glance (Image Service) on your controller node"
exit

My custom config file:

HOST_IP=
ADMIN_PASSWORD=
DEMO_PASSWORD=
DATABASE_PASSWORD=
RABBITMQ_PASSWORD=

I realized that it initially failed because I made a mistake in the

--os-username

section I didn't enter the username and the script failed because of me now as soon as it comes to OpenStack user creation on RabbitMQ it says the user already exists but the script fails without ignoring that message Is there a way to ignore the message? And I use

-e

, to avoid having the script continue due to an error, but even if something exists it still marks it as an error and the script doesn't proceed

I installed rabbitmq on kali linux. I started the service sudo systemctl start rabbitmq-server Then I tried to enable the management plugin rabbitmq-plugins enable rabbitmq_management But I am getting this error: Error when reading ./.erlang.cookie: eacces Looks like I am not not authorized to read from the cookie. How can I resolve this? I tried this sudo chmod 600 ./.erlang.cookie and sudo chmod 600 /var/lib/rabbitmq/.erlang.cookie but did not help

I want to list available queues on a remote RabbitMQ server with the following command: rabbitmqadmin --host=a.b.c.com --port=443 --username=user --password=pwd list queues But it ends with an error: Traceback (most recent call last): File "/usr/bin/rabbitmqadmin", line 1150, in main() File "/usr/bin/rabbitmqadmin", line 494, in main method() File "/usr/bin/rabbitmqadmin", line 694, in invoke_list format_list(self.get(uri), cols, obj_info, self.options) File "/usr/bin/rabbitmqadmin", line 523, in get return self.http("GET", "%s/api%s" % (self.options.path_prefix, path), "") File "/usr/bin/rabbitmqadmin", line 597, in http die(json.loads(resp.read())['reason']) File "/usr/lib/python3.8/json/__init__.py", line 357, in loads return _default_decoder.decode(s) File "/usr/lib/python3.8/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File "/usr/lib/python3.8/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) I have tried lots of variants of the command: without credentials, with -k option... but without success. The error has always been the same. nmap tells me that the host a.b.c.com is alive and the port 443 is open. The error may indicate a problem with python, but how the workaround may look like? Installing another version of rabbitmqadmin (the current one is 3.8.2) or another python version (the current one is 3.8.10)? I've also downloaded rabbitmqadmin from the remote server as explained here https://www.rabbitmq.com/management-cli.html and used it. The downloaded version was 3.8.19 but it didn't help. Not sure what is going on behind the scenes that causes this error...

I have an issue when trying to install RabbitMQ for my OpenStack infrastructure: I tried to run dnf -y install centos-release-openstack-xena. Everything seems to be OK but when i try to enable my repo and starting an update : dnf -vv --enablerepo=centos-openstack-xena -y upgrade I have this error: CentOS-8 - RabbitMQ 38 171 B/s | 38 B 00:00 Error: Failed to download metadata for repository « centos-rabbitmq-38 » : Cannot prepare internal mirrorlist: No URLs in mirrorlist Here is my file /etc/yum.repos.d/CentOS-Messaging-rabbitmq.repo

[centos-rabbitmq-38]
name=CentOS-8 - RabbitMQ 38
#baseurl=http://mirror.centos.org/centos/$releasever/messaging/$basearch/rabbitmq-38 
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=messaging-rabbitmq-38 
gpgcheck=1
enabled=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Messaging

I tried with the lastest version of CentOS 8 Stream. If someone could help me it will be great. Thank you

In GNU/Linux I have an issue with an application I have made. It works in my development environment, most of the components running in dockers or natively, but it randomly (often, but not always) fails in the server environment where it needs to be deployed. Infrastructure: [App in Ubuntu Server 20.04 host-1] [router+firewall] [Ubuntu Server 20.04 host-2] Both servers seem to have enough resources -4 CPUs, 4 GB RAM. The machine running the app has to connect to a RabbitMQ running in that host2, and both publish (I haven't seen failure here) and subscribe (which tends to fail) in different queues there. The issue: sometimes it works (there's a router + firewall, but the problem seems not to be there), but many other times, for some reason, both connections randomly fail. I checked MTU (1500, it works in other deployments), ulimit seems OK, etc. but I am not finding the issue... Many times Rabbit connections start, but then, eventually, I get Rabbit error messages: - AMQPConnector - reporting failure: AMQPConnectorAMQPHandshakeError: ProbableAuthenticationError [..]("ConnectionClosedByBroker: (403) 'ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.'" Which is not true, as the credentials I am 100% sure are OK, in fact, they work sometimes. The connection is retried, but no success. From Rabbit logs: [info] Closing all channels from connection 'xxx.yyy.zzz.kkk:41426 -> yyy.zzz.kkk.zzz:5672' because it has been closed [info] accepting AMQP connection (xxx.yyy.zzz.kkk:41430 -> yyy.zzz.kkk.zzz:5672) [error] Error on AMQP connection (xxx.yyy.zzz.kkk:41430 -> yyy.zzz.kkk.zzz:5672, state: starting): PLAIN login refused: user 'someuser' - invalid credentials I tried with a heartbeat of 500 and 90, and a blocked connection timeout of 300... For me, it seems that the heartbeats are not being received sometimes. I am pretty lost, I imagine it could be a performance or network issue, as in other controlled environments this works, so, what could I check?

I tried starting rabbitmq-server when installing rabbitmq on Ubuntu and I get the following Error:

Job for rabbitmq-server.service failed because the control process exited with error code.
See "systemctl status rabbitmq-server.service" and "journalctl -xe" for details.

rabbitmq-server.service - RabbitMQ Messaging Server
     Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Mon 2021-08-30 18:31:15 CEST; 5s ago
    Process: 89134 ExecStart=/usr/sbin/rabbitmq-server (code=exited, status=1/FAILURE)
   Main PID: 89134 (code=exited, status=1/FAILURE)

I already tried rm /var/lib/rabbitmq/.erlang.cookie, but permission was denied. Restarting doesn't work too. I would really appreciate it, if you could help me solve this problem :)

There is a rabbitmq running on docker on my ubuntu aws server, which I connect to from my local pc app. After setting up https domain on nginx, it broke up (I am not sure if it the reason). I tried to connect via telnet ip port which shows Connection closed by foreign host. Docker logs after above command: 2020-10-02 17:20:57.873 [info] Resetting node maintenance status 2020-10-02 17:31:23.071 [info] accepting AMQP connection (84.54.87.17:58935 -> private_ip:5672) 2020-10-02 17:31:23.071 [error] closing AMQP connection (84.54.87.17:58935 -> private_ip:5672): {handshake_timeout,handshake} Interestingly, the same error occurs when I connect to rabbit_management plugin via telnet. But, i am able to access rabbit_management from browser. Aws bounding rules and ufw ports are open When run my app (python and aio_pika lib for rabbitmq client) following error occurs: Could not get addresses to use: [Errno -2] Name or service not known (http) How to fix this? P.S. I use elastic ip to connect to rabbit, not domain name. But it should work in any case.

I would like to have systemd start up a number of processing servers for a RabbitMQ RPC queue. I tried to follow the example in [Have SystemD spawn N processes?](https://unix.stackexchange.com/questions/288236/have-systemd-spawn-n-processes) to have a single systemctl command to start/stop the servers. Here are my unit file and template file. ansiblepbserver@.service:

[Unit]
Description=RabbitMQ rpc queue server instance %i for ansiblePB_rpc_queue
Requires=rabbitmq-server.servic
After=multi-user.target rabbitmq-server.service
StopWhenUnneeded=yes

[Service]
PermissionsStartOnly=true
Type=idle
User=secretuser
ExecStart=/usr/bin/python /app/bin/ansibleplaybookserver.py
Restart=always
RestartSec=10

[Install]
WantedBy=ansiblePB.servers.service

ansiblePB.servers.service:

[Unit]
Description=Controlling service for the multiple ansiblePB servers

[Install]
WantedBy=multi-user.target

Workflow: 1. Enable servers: sudo systemctl enable ansibleserver@{1..2}.service 2. Start everything for the first time sudo systemctl start ansiblePB.servers.service It fails with:

Failed to start ansiblePB.servers.service: Unit is not loaded properly: Invalid argument.
See system logs and 'systemctl status ansiblePB.servers.service' for details.

Status gives me:

ansiblePB.servers.service lacks both ExecStart= and ExecStop= setting. Refusing.

The docs say have to have at least ExecStart or ExecStop, but the example in the weblink above does not include either and I don't know what I would set them to. Any ideas?

I had a rabbit-mq service running and I suddenly see that the service is not running and that I cannot start it. I have checked other existing questions regarding this kind of problems, and most of them point to problems in /etc/hosts configuration The result of restart is: /etc/init.d/rabbitmq-server restart [....] Restarting rabbitmq-server (via systemctl): rabbitmq-server.serviceJob for rabbitmq-server.service failed because the control process exited with error code. See "systemctl status rabbitmq-server.service" and "journalctl -xe" for details. failed! And the detail in systemctl is: systemctl status rabbitmq-server.service rabbitmq-server.service - RabbitMQ Messaging Server Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since mié 2018-10-03 13:07:32 CEST; 42s ago Process: 5545 ExecStop=/usr/sbin/rabbitmqctl stop (code=exited, status=2) Process: 4564 ExecStartPost=/usr/lib/rabbitmq/bin/rabbitmq-server-wait (code=exited, status=2) Process: 4563 ExecStart=/usr/sbin/rabbitmq-server (code=exited, status=1/FAILURE) Main PID: 4563 (code=exited, status=1/FAILURE) systemd: Starting RabbitMQ Messaging Server... rabbitmq: Waiting for rabbit@edr ... rabbitmq: pid is 4571 ... systemd: rabbitmq-server.service: Main process exited, code=exited, status=1/FAILURE rabbitmq: Error: process_not_running systemd: rabbitmq-server.service: Control process exited, code=exited status=2 systemd: Failed to start RabbitMQ Messaging Server. systemd: rabbitmq-server.service: Unit entered failed state. systemd: rabbitmq-server.service: Failed with result 'exit-code'. The result of journalctl -xe gives not much more info. And the file /var/log/rabbitmq/startup_err shows a message truncated like this: Crash dump is being written to: erl_crash.dump...done Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,auth,{"Cookie file /var/lib/rabbitmq/.erl tail: /var/log/rabbitmq/startup_err: file truncated Is there another way to find the exact error when rabbit-mq fails to start?

I'm trying to install RabbitMQ on Redhat Linux 7 (RHEL7). I followed the instructions on the RabbitMQ site, and it installed fine. However, it won't run because SELinux is preventing Erlang from binding to port 25672. I've found the SELinux policy files in the SELinux repository on github, but I don't know how to build them and apply them. My google-searching has been unsuccessful as I keep coming up with references to other linux distributions, or the use of audit2allow. How do I apply the rabbitmq policy files from https://github.com/selinux-policy/selinux-policy/tree/f21-contrib to my RHEL7 box?

I've been having a problem connecting to my rabbitmq server when I start it on my local machine. Apparently the erlang cookie of the server, running on my local machine, does not match the cookie on my local machine. I found an old post on the internet explaining that such a problem when running on a local machine can be caused by the fact that I'm not running rabbitmq as a rabbitmq user which is created for you by the installer. So I did just that and started rabbitmq as rabbitmq user, with the following command. sudo -H -u rabbitmq bash /usr/lib/rabbitmq/bin/rabbitmq-server How does it really work? Since I don't have a dedicated folder for the user rabbitmq I want to understand where erlang cookie can be saved for the mentioned user, so that it does not match the cookie inside MY home folder (it IS there). Also I would like to know how the command --set-home would work in the context of the given command given such user does not (to my understanding) have a home directory.

I want to install sensu-server and sensu-client both on single node(ubuntu 14.04) for practical purpose. when i am using redis as transport it's working fine. but when i am trying to configure rabbitmq as transport than it's give me error. my configuration structure is: ├── conf.d │   ├── api.json │   ├── check_apache.json │   ├── client.json │   ├── default_handler.json │   ├── rabbitmq.json │   ├── redis.json │   └── transport.json ├── config.json.example ├── dashboard.d ├── extensions ├── plugins │   └── check-apache.rb ├── ssl │   ├── cert.pem │   └── key.pem └── uchiwa.json /etc/sensu/uchiwa.json { "sensu": [ { "name": "Sensu", "host": "localhost", "ssl": false, "port": 4567, "path": "", "timeout": 5000 } ], "uchiwa": { "port": 3000, "stats": 10, "refresh": 10000 } } /etc/sensu/conf.d/api.json { "api": { "host": "localhost", "port": 4567 } } /etc/sensu/conf.d/client.json { "client": { "name": "server", "address": "localhost", "subscriptions": [ "ALL" ] } } /etc/sensu/conf.d/rabbitmq.json { "rabbitmq": { "host": "127.0.0.1", "port": 5671, "vhost": "/sensu", "user": "sensu", "password": "pass", "heartbeat": 30, "prefetch": 50, "ssl": { "cert_chain_file": "/etc/sensu/ssl/cert.pem", "private_key_file": "/etc/sensu/ssl/key.pem" } } } /etc/sensu/conf.d/redis.json { "redis": { "host": "localhost", "port": 6379 } } /etc/sensu/conf.d/transport.json { "transport": { "name": "rabbitmq", "reconnect_on_error": true } } when i replce rabbitmq to redis in transport.json file my setup working fine but in case of rabbitmq its not working. in logs we get this error but username and password is correct that is provide in configuration file. {"timestamp":"2017-03-21T18:44:28.167638+0000","level":"warn","message":"transport connection error","reason":"possible authentication failure. wrong credentials?","user":"sensu"}

So this client has a lot of internal regulations and has issues getting root access. While RabbitMQ has a "generix Linux" install that doesn't require root access, it still relies on ErLang Is there a "generic" or non-root intall or Erlang ? It would be for a Centos/RHEL type Linux Thanks a lot

Is RabbitMQ, for inter process communication, like pipes and named pipes? How does RabbitMQ compare to named pipes? Except distributed systems. ([RabbitMQ](http://www.rabbitmq.org) , for those who haven't encountered it, is an open source, middleware, enterprise message broker that speaks AMQP.)

I am trying to install rabbitmq server from rabbitmq-server-3.6.10-1.e17.noarch.rpm on an EC2 instance running Amazon Linux. I understand that Amazon Linux evolved from CentOS and RHEL Linux, so I looked for install packages intended for those. RMQ has an erlang dependency. I installed erlang from erlang-19.3.6-1.e17.centos.src.rpm. That install ran successfully. The rabbitmq install from the rpm mentioned above via /bin/rpm -Uvh /local/downloads/rabbitmq-server-3.6.10-1.el7.noarch.rpm resulted in several dependency errors. One requires socat. The second requires systemd. That error is: systemd is needed by rabbitmq-server-3.6.10-1.el7.noarch I resolved the first dependency with yum install socat. I've done research but have as yet been unable to overcome that second dependency on systemd so that I can install rabbitmq in this environment. I suspect that Amazon Linux may lock me in to System V init, and may preclude me from using systemd. In which case my only option will be to abandon all the work I've done on this server and re-establish it with another operating system option - CentOS, for example. How can I resolve this?

I need rabbitmq-server installed on Ubuntu. Rabbitmq-server tries to start itself on install, and on many dpkg and apt-get commands thereafter. (Having it run on install is intentional, according to the [instructions](https://www.rabbitmq.com/install-debian.html#running-debian).) On this box, rabbitmq server can't start, and it takes about a minute to give up. I don't want to fix that. I want to make it not try to start whenever I run, say apt-get install something-not-related-to-rabbitmq When I do that, not only does it take an extraordinarily long time to install the package, but it also exits with 100, even if the package itself installed fine. Here's a snippet of what happens: $ sudo apt-get install fortune Reading package lists... Done -- SNIP -- Unpacking fortunes-min (1:1.99.1-7) ... Processing triggers for man-db (2.6.7.1-1ubuntu1) ... Setting up rabbitmq-server (3.6.0-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 package rabbitmq-server (--configure): subprocess installed post-installation script returned error exit status 1 Setting up librecode0:amd64 (3.6-21) ... Setting up fortune-mod (1:1.99.1-7) ... Setting up fortunes-min (1:1.99.1-7) ... Processing triggers for libc-bin (2.19-0ubuntu6.6) ... Errors were encountered while processing: rabbitmq-server E: Sub-process /usr/bin/dpkg returned an error code (1) $ echo $? 100 I'd rather not uninstall it, as I do eventually plan to get around to using it. But frankly, I think it's a little bit nuts that it hijacks my dpkg, and I would appreciate some help killing that little misfeature with fire.