Failed to start RabbitMq redentials_obfuscation - rabbitmq
Any one came across this problem?
Rabbitmq:3.8.14
when run:
$ sudo systemctl start rabbitmq-server
got this credentials obfuscation problem:
{"Kernel pid terminated",application_controller,"{application_start_failure,cr
A nel pid terminated",application_controller,"{application_start_failure,credentials_obfuscation,{{shutdown,{failed_to_start_child,credentials_obfu
l redentials_obfuscation,{{shutdown,{failed_to_start_child,credentials_obfuscaton_svc,{undef,[{crypto,cipher_info,[aes_128_cbc],[]},{credentials_ob
ede uscaton_svc,{undef,[{crypto,cipher_info,[aes_128_cbc],[]},{credentials_obfuscation_pbe,iv_length,1,[{file,"src/credentials_obfuscation_pbe.erl"
sca bfuscation_pbe,iv_length,1,[{file,"src/credentials_obfuscation_pbe.erl"},{line,125}]},{credentials_obfuscation_pbe,encrypt,5,[{file,"src/crede
"},{line,125}]},{credentials_obfuscation_pbe,encrypt,5,[{file,"src/credentials_obfuscation_pbe.erl"},{line,75}]},{credentials_obfuscation_svc,c
entials_obfuscation_pbe.erl"},{line,75}]},{credentials_obfuscation_svc,check,3,[{file,"src/credentials_obfuscation_svc.erl"},{line,163}]},{cre
check,3,[{file,"src/credentials_obfuscation_svc.erl"},{line,163}]},{credentials_obfuscation_svc,init_state,0,[{file,"src/credentials_obfuscati
edentials_obfuscation_svc,init_state,0,[{file,"src/credentials_obfuscation_svc.erl"},{line,133}]},{gen_server,init_it,2,[{file,"gen_server.erl"},{line,249}]}]}}},{credentials_obfuscation_app,start,[normal,[]]}}}"}
After few hours spending on this, it turns out to be the Erlang was too old. Upgraded it to latest version Erlang/OTP 23, problem solved!
the problem cause by incompatible between RabbitMQ and Erlang/OTP:
Ubuntu 18.04 provides Erlang 20.2 and RabbitMQ 3.8.14 requires 22.3 or 23.x. See RabbitMQ and Erlang/OTP Compatibility Matrix
Installing latest Erlang version should solve the problem.
$sudo apt-get install erlang
The problem commonly happens when only upgrade rabbitMq without Erlang. (as my case: rabbitMq 3.8.0 -> 3.8.14)
Related
Rabbitmq giving segmentation fault on M1 mac
env.conf" /opt/homebrew/opt/rabbitmq/sbin/rabbitmq-server /opt/homebrew/opt/rabbitmq/sbin/rabbitmq-server: line 155: 1332 Segmentation fault: 11 start_rabbitmq_server "$#" I am getting this error^ I tried reinstalling rabbitmq. I cannot find a solid solution that has worked. I am trying to run it later I will connect it with celery
This error means that the installed version of RabbitMQ is not compatible with arm64 architecture. The solution is to install arm64-compatible version or to use arm64-compatible docker image of RabbitMQ. For example, here it's advised using rabbitmq:3.9.11-management docker image: https://github.com/heidiks/rabbitmq-delayed-message-exchange/issues/4#issuecomment-987206858
OpenVSwitch won't install on my Alma Linux server
When I am attempting to install OpenVSwitch from the RPM generated from the documentation, it spews out an error, the following. I have python2 installed, python3, and python3.6. I generally do not know why it is showing this, but my 9:40 at night brain can't exactly comprehend much. [root#Alma-85-amd64-base x86_64]# yum install python2 Last metadata expiration check: 1:15:52 ago on Tue 08 Mar 2022 02:20:48 AM CET. Package python2-2.7.18-7.module_el8.5.0+2579+77770ab7.x86_64 is already installed. Dependencies resolved. Nothing to do. Complete! [root#Alma-85-amd64-base x86_64]# rpm -i openvswitch-2.17.0-1.el8.x86_64.rpm error: Failed dependencies: python >= 2.7 is needed by openvswitch-2.17.0-1.el8.x86_64 [root#Alma-85-amd64-base x86_64]#
Alright, here's an update. I could not get OpenVSwitch to work on any version of RHEL 8, but it did work on RHEL 7.
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.
Unable to install latest stable Release of Redis on CentOS 7
I followed below steps to install Redis on CentOS. But Redis 3.2.x version got downloaded, I want more recent version (i.e 4.0.11 or 5.0.x) to be downloaded. I need steps how to upgrade the Redis current installation? I used below steps while installation We can use yum to install EPEL: sudo yum install epel-release As soon as we finish installing EPEL, we can use yum once again to install Redis: sudo yum install redis After a few minutes this installation will be completed and then you can start the Redis service: sudo systemctl start redis.service There is always the chance for Redis to start on boot, all you have to do is enable it through the enable command: sudo systemctl enable redis If you want to check Redis`s status you should run the following: sudo systemctl status redis.service
I have found the Remi repository keeps up with the latest binaries. While you can add them to your repos (see https://rpms.remirepo.net), you can just point yum directly at the rpm file there as well (e.g. yum install -y http://rpms.remirepo.net/enterprise/7/remi/x86_64/redis-5.0.0-1.el7.remi.x86_64.rpm). Edit: Regarding an upgrade, I assumed you don't have any data at this point, so I would suggest a quick yum uninstall redis before installing the latest. If you really need to upgrade with data and all, you need to just be sure to preserve your persistent data files and replace them before starting the new version.
Rabbitmq unable to find erl after Mac OS update
After updating high sierra to 10.13.5, rabbitmq can't seem to find erl when i run: /usr/local/Cellar/rabbitmq/3.7.3/sbin/rabbitmq-server I get the error: /usr/local/Cellar/rabbitmq/3.7.3/sbin/rabbitmq-server: line 85: /usr/local/opt/erlang/bin/erl: No such file or directory Running which erl gives me: /usr/local/bin/erl Need help to get it working again, not sure why the path changed as well.
You probably have to install erlang with brew install erlang or reinstall it with: brew reinstall erlang