Rabbitmq crash when boot failed - rabbitmq
I meet a problem when booting rabbitmq which is driving me crazy...
Env:redhat4
erlang version:R16B03 installed from source code
rabbitmq version:rabbitmq-server-3.6.1 from source code
when I ran 'rabbitmq-server start' command, it gave me some error
information, then I ran that again it showed:
RabbitMQ 3.6.1. Copyright (C) 2007-2016 Pivotal Software, Inc.
## ## Licensed under the MPL. See http://www.rabbitmq.com/
## ##
########## Logs: /var/log/rabbitmq/rabbit#bogon.log
###### ## /var/log/rabbitmq/rabbit#bogon-sasl.log
##########
Starting broker...
And it stucked there, I thought may be it had started, so I ran './rabbitmq-plugins enable rabbitmq_management' to enable web plugins, but I got:
The following plugins have been enabled:
mochiweb
webmachine
rabbitmq_web_dispatch
amqp_client
rabbitmq_management_agent
rabbitmq_management
Applying plugin configuration to rabbit#bogon... failed.
Error: {undef,[{crypto,module_info,[attributes],[]},
{rabbit_misc,module_attributes,1,
[{file,"src/rabbit_misc.erl"},{line,805}]},
{rabbit_misc,'-all_module_attributes/1-fun-0-',3,
[{file,"src/rabbit_misc.erl"},{line,825}]},
{lists,foldl,3,[{file,"lists.erl"},{line,1248}]},
{rabbit_boot_steps,find_steps,1,
[{file,"src/rabbit_boot_steps.erl"},
{line,40}]},
{rabbit_boot_steps,run_boot_steps,1,
[{file,"src/rabbit_boot_steps.erl"},
{line,26}]},
{rabbit,start_apps,1,[{file,"src/rabbit.erl"},{line,343}]},
{rabbit_plugins,ensure,1,
[{file,"src/rabbit_plugins.erl"},{line,52}]}]}
I don't know why... so I stopped the rabbitmq server and started it again, and it gave me this:
RabbitMQ 3.6.1. Copyright (C) 2007-2016 Pivotal Software, Inc.
## ## Licensed under the MPL. See http://www.rabbitmq.com/
## ##
########## Logs: /var/log/rabbitmq/rabbit#bogon.log
###### ## /var/log/rabbitmq/rabbit#bogon-sasl.log
##########
Starting broker...
BOOT FAILED
===========
Error description:
{could_not_start,rabbit,
{undef,
[{crypto,module_info,[attributes],[]},
{rabbit_misc,module_attributes,1,
[{file,"src/rabbit_misc.erl"},{line,805}]},
{rabbit_misc,'-all_module_attributes/1-fun-0-',3,
[{file,"src/rabbit_misc.erl"},{line,825}]},
{lists,foldl,3,[{file,"lists.erl"},{line,1248}]},
{rabbit_boot_steps,find_steps,1,
[{file,"src/rabbit_boot_steps.erl"},{line,40}]},
{rabbit_boot_steps,run_boot_steps,1,
[{file,"src/rabbit_boot_steps.erl"},{line,26}]},
{rabbit,start,2,[{file,"src/rabbit.erl"},{line,477}]},
{application_master,start_it_old,4,
[{file,"application_master.erl"},{line,269}]}]}}
Log files (may contain more information):
/var/log/rabbitmq/rabbit#bogon.log
/var/log/rabbitmq/rabbit#bogon-sasl.log
{"init terminating in do_boot",{could_not_start,rabbit,{undef,[{crypto,module_info,[attributes],[]},{rabbit_misc,module_attributes,1,[{file,"src/rabbit_misc.erl"},{line,805}]},{rabbit_misc,'-all_module_attributes/1-fun-0-',3,[{file,"src/rabbit_misc.erl"},{line,825}]},{lists,foldl,3,[{file,"lists.erl"},{line,1248}]},{rabbit_boot_steps,find_steps,1,[{file,"src/rabbit_boot_steps.erl"},{line,40}]},{rabbit_boot_steps,run_boot_steps,1,[{file,"src/rabbit_boot_steps.erl"},{line,26}]},{rabbit,start,2,[{file,"src/rabbit.erl"},{line,477}]},{application_master,start_it_old,4,[{file,"application_master.erl"},{line,269}]}]}}}
Crash dump was written to: erl_crash.dump
init terminating in do_boot ()
I don't understand... Why there are a lot of issues? Is there any procedure that was not correct?
{could_not_start,rabbit,{undef,[{crypto,module_info,[attributes]
means that you need the crypto Erlang.
Check this https://www.rabbitmq.com/which-erlang.html.
use SSL/TLS reliably 17.0
you need the version >= 17.0
I got same issue because of mismatch of RabbitMQ version installed on 3rd node other than two nodes. Install same versions on all nodes of cluster.
Related
RabbitMQ is dead
I don't actually know how to describe my problem in my title well. The issue I'm having is I have a local install of RabbitMQ through Homebrew (Mac), and it suddenly just died. I suddenly became unable to send messages to the queue. Unfortunately I can't post the error message, because I tried a few other steps, including resetting, uninstalling, and reinstalling Rabbit. After the reinstall, I can't start my Rabbit server; it gets stuck after this: sudo rabbitmq-server start Password: 2022-08-05 11:14:17.972308-04:00 [info] <0.221.0> Feature flags: list of feature flags found: 2022-08-05 11:14:17.979492-04:00 [info] <0.221.0> Feature flags: [x] classic_mirrored_queue_version 2022-08-05 11:14:17.979531-04:00 [info] <0.221.0> Feature flags: [x] implicit_default_bindings 2022-08-05 11:14:17.979546-04:00 [info] <0.221.0> Feature flags: [x] maintenance_mode_status 2022-08-05 11:14:17.979568-04:00 [info] <0.221.0> Feature flags: [x] quorum_queue 2022-08-05 11:14:17.979583-04:00 [info] <0.221.0> Feature flags: [x] stream_queue 2022-08-05 11:14:17.979599-04:00 [info] <0.221.0> Feature flags: [x] user_limits 2022-08-05 11:14:17.979611-04:00 [info] <0.221.0> Feature flags: [x] virtual_host_metadata 2022-08-05 11:14:17.979672-04:00 [info] <0.221.0> Feature flags: feature flag states written to disk: yes 2022-08-05 11:14:18.203961-04:00 [notice] <0.44.0> Application syslog exited with reason: stopped 2022-08-05 11:14:18.204012-04:00 [notice] <0.221.0> Logging: switching to configured handler(s); following messages may not be visible in this log output ## ## RabbitMQ 3.10.7 ## ## ########## Copyright (c) 2007-2022 VMware, Inc. or its affiliates. ###### ## ########## Licensed under the MPL 2.0. Website: https://rabbitmq.com Erlang: 25.0.3 [jit] TLS Library: OpenSSL - OpenSSL 1.1.1q 5 Jul 2022 Doc guides: https://rabbitmq.com/documentation.html Support: https://rabbitmq.com/contact.html Tutorials: https://rabbitmq.com/getstarted.html Monitoring: https://rabbitmq.com/monitoring.html Logs: /usr/local/var/log/rabbitmq/rabbit#localhost.log /usr/local/var/log/rabbitmq/rabbit#localhost_upgrade.log <stdout> Config file(s): (none) Starting broker... completed with 7 plugins. After this it just hangs forever. I would like to completely uninstall Rabbit from my computer and reinstall it from fresh; when I first installed it it worked like a charm, but since them somehow something has gone belly-up. Can someone help me with this? Also, yes, the obvious thing to do is brew rm rabbitmq but that's what got me into this situation. It can't be that simple.
I got it working. Some combination of these steps worked: Change the permission of the service: sudo chown -R $(whoami) $(brew --prefix)/* Reload the launchctl config: launchctl unload -w ~/Library/LaunchAgents/homebrew.mxcl.rabbitmq.plist launchctl load -w ~/Library/LaunchAgents/homebrew.mxcl.rabbitmq.plist Restart the service: brew services restart rabbitmq And then it worked.
Unable to provision rabbitmq using chef and testkitchen
I am trying to install an old version of RabbitMQ using Chef (cookbook 'rabbitmq', '~> 5.8.5') and Kitchen, below my configuration: Attributes #Erlang default['erlang']['install_method'] = 'source' default['erlang']['source']['version']='R13B03' default['erlang']['source']['checksum']='e7c46c8b2778f22064a3b369c1a1b572a1cc0e8a2198166858d4b9a1b488d662' #RabbitMQ default['rabbitmq']['erlang']['enabled'] = true default['rabbitmq']['version'] = "3.4.4" default['rabbitmq']['rpm_package'] ='rabbitmq-server-3.4.4-1.noarch.rpm' Recipe: include_recipe 'rabbitmq::default' When I run kitchen converge, I am getting the following exception: Running handlers: [2020-08-22T22:20:07+00:00] ERROR: Running exception handlers Running handlers complete [2020-08-22T22:20:07+00:00] ERROR: Exception handlers complete Chef Infra Client failed. 9 resources updated in 06 minutes 26 seconds [2020-08-22T22:20:07+00:00] FATAL: Stacktrace dumped to /tmp/kitchen/cache/chef-stacktrace.out [2020-08-22T22:20:07+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report [2020-08-22T22:20:07+00:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: rpm_package[/tmp/kitchen/cache/rabbitmq-server-3.4.4-1.noarch.rpm] (rabbitmq::default line 224) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1' ---- Begin output of ["rpm", "-i", "/tmp/kitchen/cache/rabbitmq-server-3.4.4-1.noarch.rpm"] ---- STDOUT: STDERR: warning: /tmp/kitchen/cache/rabbitmq-server-3.4.4-1.noarch.rpm: Header V4 DSA/SHA1 Signature, key ID 056e8e56: NOKEY error: Failed dependencies: erlang >= R13B-03 is needed by rabbitmq-server-3.4.4-1.noarch ---- End output of ["rpm", "-i", "/tmp/kitchen/cache/rabbitmq-server-3.4.4-1.noarch.rpm"] ---- Ran ["rpm", "-i", "/tmp/kitchen/cache/rabbitmq-server-3.4.4-1.noarch.rpm"] returned 1 But when I logged in to the VM, I can see erlang is installed: [vagrant#kitchen-rmq-server-centos-7 ~]$ erl Erlang R13B03 (erts-5.7.4) [source] [64-bit] [rq:1] [async-threads:0] [hipe] [kernel-poll:false] Eshell V5.7.4 (abort with ^G) 1> And it is the same version required by RMQ (R13B03) Any idea how to solve this issue? Edit: to replicate the issue https://github.com/Proximator/chef-rmq
Firstly, we have to make sure erlang is installed by the rabbitmq cookbook, and not by any other means. This is the note found on Chef supermarket for rabbitmq cookbook: The packages are cannot be installed alongside with other Erlang packages, for example, those from standard Debian repositories or Erlang Solutions. To make sure that the Erlang cookbook is not used by rabbitmq::default Also, there is a compatibility matrix of RabbitMQ and Erlang versions. RabbitMQ 3.7.0 being the lowest supported version, for which the lowest compatible Erlang version is 19.3. There are zero dependency Erlang RPMs "just enough to run RabbitMQ" as documented here: https://github.com/rabbitmq/erlang-rpm For example - to install RabbitMQ 3.7.x with the compatible Erlang 19.3.x: You should have these attributes: default['rabbitmq']['erlang']['enabled'] = true default['rabbitmq']['version'] = '3.7.6' default['rabbitmq']['erlang']['yum']['baseurl'] = 'https://dl.bintray.com/rabbitmq-erlang/rpm/erlang/19/el/7' default['rabbitmq']['erlang']['version'] = '19.3.6.13' Then include below recipes: include_recipe 'rabbitmq::erlang_package' include_recipe 'rabbitmq::default'
arch linux intellij core dump
My Intellij wont start anymore, i really dont know why. Heres the Log File: # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f18a8424be0, pid=12079, tid=139743934207744 # # JRE version: Java(TM) SE Runtime Environment (8.0_60-b27) (build 1.8.0_60-b27) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.60-b23 mixed mode linux-amd64 compressed oops) # Problematic frame: # C 0x00007f18a8424be0 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # i tried ulimit -c unlimited but that didint worked aswell. Thanks for the help!
Did you check arch linux forums? I found that: https://bugs.archlinux.org/task/46619 Did downgrading glib2 helped?
Apache segfault with passenger
I have problem installin passenger under Linux. The way I'm doning it is Added repository: deb https://oss-binaries.phusionpassenger.com/apt/passenger trusty main to /etc/apt/sources.list.d/passenger.list Installed it: sudo apt-get install libapache2-mod-passenger Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libev4 Use 'apt-get autoremove' to remove it. The following NEW packages will be installed: libapache2-mod-passenger 0 upgraded, 1 newly installed, 0 to remove and 580 not upgraded. Need to get 0 B/273 kB of archives. After this operation, 1 281 kB of additional disk space will be used. Selecting previously unselected package libapache2-mod-passenger. (Reading database ... 287776 files and directories currently installed.) Preparing to unpack .../libapache2-mod-passenger_1%3a5.0.13-1~trusty1_amd64.deb ... Unpacking libapache2-mod-passenger (1:5.0.13-1~trusty1) ... Setting up libapache2-mod-passenger (1:5.0.13-1~trusty1) ... Then I tried to enable passenger module with sudo a2enmod passenger but for some reason I had /etc/apache2/mods-available/passenger.conf and /etc/apache2/mods-available/passenger.load files missed after installation. (They are not created and also not removed with libapache2-mod-passenger so I suppose this is some kind of a bug). So I created them manually: s set#set:~$ which ruby /home/set/.rvm/rubies/ruby-2.1.5/bin/ruby set#set:~$ which rails /home/set/.rvm/gems/ruby-2.1.5/bin/rails set#set:~$ ll /usr/lib/apache2/modules/ | grep passenger -rw-r--r-- 1 root root 1209112 Jul 3 01:35 mod_passenger.so /etc/apache2/mods-available/passenger.conf: <IfModule passenger_module> PassengerRoot /home/set/.rvm/gems/ruby-2.1.5/bin/passenger PassengerRuby /home/set/.rvm/rubies/ruby-2.1.5/bin/ruby </IfModule> and /etc/apache2/mods-available/passenger.load: LoadModule passenger_module /usr/lib/apache2/modules/mod_passenger.so the module was successfully enabled then but when I was restarting apache it throw me a segfault: a Starting web server apache2 Segmentation fault (core dumped) Action 'start' failed. The Apache error log may have more information. The apache2 instance did not start within 20 seconds. Please read the log files to discover problems and the coredump: GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from apache2...(no debugging symbols found)...done. [New LWP 30116] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/sbin/apache2 -k start'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007faa58b8e37e in std::_Rb_tree<std::string, std::pair<std::string const, std::string>, std::_Select1st<std::pair<std::string const, std::string> >, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > >::_M_begin() const () from /usr/lib/apache2/modules/mod_passenger.so So I stuck at this point and have no idea where to move nex. Reinstalling of libapache2-mod-passenger does not help. How can I fix this problem?
This issue is more like memory issue. I am facing something similar as your issue. But my case is happening with the virtual box VM's. A similar setup for me worked on a typical hardware with more RAM. What I am doing now to fix this issue is to install the latest passenger module. gem install passenger and running passenger-install-apache2-module which comes natively with passenger. and I think the latest module just work. Here is my puppetmaster.conf file entries under apache conf dir. LoadModule passenger_module /usr/local/share/gems/gems/passenger-5.0.26/buildout/apache2/mod_passenger.so PassengerRoot /usr/local/share/gems/gems/passenger-5.0.26
Configuring Erlang to work with SSL
Erlang version: R13B01 Currently I'm struggling trying to make Erlang work with SSL. The programming part was easy, but now starting the system SSL-enabled is not. Following the Erlang SSL documentation: 1 - Made the start_ssl.rel file {release, {"OTP APN 181 01","R13B01"}, {erts, "5.7.2"}, [{kernel,"2.13.2"}, {stdlib,"1.16.2"}, {sasl,"2.1.6"}, {os_mon,"2.2.2"}, {ssl,"3.10.3"}]}. 2 - Executed the following command 1> systools:make_script("start_ssl",[]). According to the documentation, running the shell would output this (this output is from docs, not mine): $ erl -boot /home/me/ssl/start_ssl Erlang (BEAM) emulator version 5.0 Eshell V5.0 (abort with ^G) 1> whereis(ssl_server). <0.32.0> But, I'm receiving this instead: erl -boot start_ssl Erlang R13B01 (erts-5.7.2) [source] [smp:2:2] [rq:2] [async-threads:0] [kernel-poll:false] 1> whereis(ssl_server). undefined 2> So, for now, the remaining steps are failing too. Sadly, there is no documentation nor forum threads around the web with the same issue. Any tips?
Well, after some try and error, I've managed to start the system: application:start(ssl) and passing all certificates when creating the listening socket ssl:listen(Port, ?TCP_OPTIONS ++ [{ip, Host},{verify, 0}, {depth, 0}, {cacertfile, Cacertfile}, {certfile, Certfile}, {keyfile, Keyfile}]) It worked :)