RABBITMQ - Applying Plugin Failed - rabbitmq
EDIT: After setting the rabbitmq variables up in System Environment Variables and trying another un/reinstall the issue is resolved.
The following plugins have been enabled: rabbitmq_shovel
Applying plugin configuration to rabbit#MSGTEST01... started 1 plugin.
END EDIT
c:\RabbitMQ\rabbitmq_server-3.6.12\sbin>rabbitmq-plugins enable
rabbitmq_shovel rabbitmq_shovel_management Plugin configuration
unchanged.
Applying plugin configuration to rabbit#M... failed. Error:
{enabled_plugins_mismatch,"c:\Users\\AppData\Roaming\RabbitMQ
\ENABLE~1",
"c:\RabbitMQ\ENABLE~1"}
I set the following then reinstalled the service:
set RABBITMQ_BASE=c:\RabbitMQ
set RABBITMQ_CONFIG_FILE=c:\RabbitMQ\rabbitmq
set RABBITMQ_LOG_BASE=c:\RabbitMQ\logs
set RABBITMQ_MNESIA_BASE=c:\RabbitMQ\db
set RABBITMQ_ENABLED_PLUGINS_FILE=c:\RabbitMQ\enabled_plugins
Why is it still looking in my roaming profile for anything? Moreover, ENABLE~1 doesn't look like a valid filename.
I've tried blowing away my roaming profile data, RabbitMQ recreates the files.
I've tried copying my C:\RabbitMQ\enables_plugins to roaming, same thing.
Tried the reverse, same thing.
I've tried uninstalling and resintalling the service, same thing.
I'm able to enable the management ui after install, but not rabbitmq_shovel and cannot figure out what the issue is.
Again, this works after install:
rabbitmq-plugins enable rabbitmq_management
This fails with the error above:
rabbitmq-plugins enable rabbitmq_shovel
I'm running these commands as Admin in CMD.
Set up the variables in System Environment Variables and perform the following in CMD as Admin:
rabbitmqctl shutdown
rabbitmqctl stop
rabbitmq-service.bat remove
rabbitmq-service.bat install
rabbitmq-service.bat start
rabbitmq-plugins enable rabbitmq_management
rabbitmq-plugins enable rabbitmq_shovel
That worked for me.
I was able to fix the issue without having to uninstall RabbitMQ
Open the files named "enabled_plugins" at the two directory locations int he error your recived. For me, those directories were "C:\Users\UserName\AppData\Roaming\RabbitMQ" and "C:\ProgramData\RabbitMQ".
For me, one file had:
[rabbitmq_management].
while the other was empty. I copied the config snippet above into the empty file and saved it.
Run the commands as ADMIN in Command Prompt:
rabbitmqctl shutdown
rabbitmqctl stop
rabbitmq-service.bat start
rabbitmq-plugins enable rabbitmq_management
I did receive the same "enabled_plugins_mismatch" error; however, when I browsed to my RabbitMQ UI plugin at "http://localhost:15672/#/" the UI showed up and is functioning.
Related
Connection to SSH from a pipeline in Azure DevOps is still not working
I saw few other posts (in particular this one) about it but there are from last year. I still have this issue right now. I opened the Preview features from the User settings but I can't turn off this feature. My pipelines use SSH connection to run some commands on a virtual machine (basically, pull a Docker image). All my pipelines are failing. How can I fix it or update the SSH connections? Update I set up the Service connection and I use it in my pipelines with this YAML code: - task: SSH#0 displayName: 'SSH: stop shinyproxy' inputs: sshEndpoint: $(server) commands: | echo $(pwd) | sudo -S docker stop shinyproxy failOnStdErr: false continueOnError: true All pipelines, new and old, get the same error ##[error]Failed to connect to remote machine. Verify the SSH service connection details. Error: Error: All configured authentication methods failed at doNextAuth (/home/vsts/work/_tasks/SSH_91443475-df55-4874-944b-39253b558790/0.213.0/node_modules/ssh2/lib/client.js:803:21) at tryNextAuth (/home/vsts/work/_tasks/SSH_91443475-df55-4874-944b-39253b558790/0.213.0/node_modules/ssh2/lib/client.js:993:7) at USERAUTH_FAILURE (/home/vsts/work/_tasks/SSH_91443475-df55-4874-944b-39253b558790/0.213.0/node_modules/ssh2/lib/client.js:373:11) at 51 (/home/vsts/work/_tasks/SSH_91443475-df55-4874-944b-39253b558790/0.213.0/node_modules/ssh2/lib/protocol/handlers.misc.js:337:16) at Protocol.onPayload (/home/vsts/work/_tasks/SSH_91443475-df55-4874-944b-39253b558790/0.213.0/node_modules/ssh2/lib/protocol/Protocol.js:2025:10) at AESGCMDecipherNative.decrypt (/home/vsts/work/_tasks/SSH_91443475-df55-4874-944b-39253b558790/0.213.0/node_modules/ssh2/lib/protocol/crypto.js:987:26) at Protocol.parsePacket [as _parse] (/home/vsts/work/_tasks/SSH_91443475-df55-4874-944b-39253b558790/0.213.0/node_modules/ssh2/lib/protocol/Protocol.js:1994:25) at Protocol.parse (/home/vsts/work/_tasks/SSH_91443475-df55-4874-944b-39253b558790/0.213.0/node_modules/ssh2/lib/protocol/Protocol.js:293:16) at Socket. (/home/vsts/work/_tasks/SSH_91443475-df55-4874-944b-39253b558790/0.213.0/node_modules/ssh2/lib/client.js:713:21) at Socket.emit (node:events:527:28) { level: 'client-authentication' I have never had this issue before.
Based on the other post, highlighted by Antonia, the solution has to be applied on the Ubuntu machine. To fix it, open Terminal and edit /etc/ssh/sshd_config and, at the end of it, add this line /etc/ssh/sshd_config After that, restart. It is working for me.
"Directory name is invalid." etc. with rabbitmq-plugins on Windows
I'm trying to get RabbitMQ going on Windows 10 by following these instructions. However, when trying to enable the management plugin via powershell command: ./rabbitmq-plugins enable rabbitmq_management I get the following: The directory name is invalid. The filename, directory name, or volume label syntax is incorrect. Unsupported node name: hostname is invalid (possibly contains unsupported characters). If using FQDN node names, use the -l / --longnames argument. I've tried setting HOMEDRIVE=C: as the blog suggested. What am I doing wrong? EDIT Per the comment below I did the following: PS C:\program files\rabbitmq server\rabbitmq_server-3.7.15\sbin> ./rabbitmq-service.bat stop The directory name is invalid. The filename, directory name, or volume label syntax is incorrect. The RabbitMQ service is stopping. The RabbitMQ service was stopped successfully. PS C:\program files\rabbitmq server\rabbitmq_server-3.7.15\sbin> ./rabbitmq-service.bat uninstall The directory name is invalid. The filename, directory name, or volume label syntax is incorrect. ********************* Service control usage ********************* rabbitmq-service help - Display this help rabbitmq-service install - Install the RabbitMQ service rabbitmq-service remove - Remove the RabbitMQ service The following actions can also be accomplished by using Windows Services Management Console (services.msc): rabbitmq-service start - Start the RabbitMQ service rabbitmq-service stop - Stop the RabbitMQ service rabbitmq-service disable - Disable the RabbitMQ service rabbitmq-service enable - Enable the RabbitMQ service PS C:\program files\rabbitmq server\rabbitmq_server-3.7.15\sbin> set HOMEDRIVE=C: PS C:\program files\rabbitmq server\rabbitmq_server-3.7.15\sbin> ./rabbitmq-service.bat install The directory name is invalid. The filename, directory name, or volume label syntax is incorrect. RabbitMQ service is already present - only updating service parameters "WARNING: Using RABBITMQ_ADVANCED_CONFIG_FILE: C:\Users\Mj\AppData\Roaming\RabbitMQ\advanced.config" 2019-06-14 10:55:09.630000 args: [] format: "Failed to create cookie file 'l:/.erlang.cookie': enoent" label: {error_logger,error_msg} 2019-06-14 10:55:09.630000 crash_report #{label=>{proc_lib,crash},report=>[[{initial_call,{auth,init,['Argument__1']}},{pid,<0.57.0>},{registered_name,[]},{error_info,{error,"Failed to create cookie file 'l:/.erlang.cookie': enoent",[{auth,init_cookie,0,[{file,"auth.erl"},{line,286}]},{auth,init,1,[{file,"auth.erl"},{line,140}]},{gen_server,init_it,2,[{file,"gen_server.erl"},{line,374}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,342}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}},{ancestors,[net_sup,kernel_sup,<0.46.0>]},{message_queue_len,0},{messages,[]},{links,[<0.55.0>]},{dictionary,[]},{trap_exit,true},{status,running},{heap_size,610},{stack_size,27},{reductions,1456}],[]]} 2019-06-14 10:55:09.635000 supervisor_report #{label=>{supervisor,start_error},report=>[{supervisor,{local,net_sup}},{errorContext,start_error},{reason,{"Failed to create cookie file 'l:/.erlang.cookie': enoent",[{auth,init_cookie,0,[{file,"auth.erl"},{line,286}]},{auth,init,1,[{file,"auth.erl"},{line,140}]},{gen_server,init_it,2,[{file,"gen_server.erl"},{line,374}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,342}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}},{offender,[{pid,undefined},{id,auth},{mfargs,{auth,start_link,[]}},{restart_type,permanent},{shutdown,2000},{child_type,worker}]}]} 2019-06-14 10:55:09.704000 supervisor_report #{label=>{supervisor,start_error},report=>[{supervisor,{local,kernel_sup}},{errorContext,start_error},{reason,{shutdown,{failed_to_start_child,auth,{"Failed to create cookie file 'l:/.erlang.cookie': enoent",[{auth,init_cookie,0,[{file,"auth.erl"},{line,286}]},{auth,init,1,[{file,"auth.erl"},{line,140}]},{gen_server,init_it,2,[{file,"gen_server.erl"},{line,374}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,342}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}}}},{offender,[{pid,undefined},{id,net_sup},{mfargs,{erl_distribution,start_link,[]}},{restart_type,permanent},{shutdown,infinity},{child_type,supervisor}]}]} 2019-06-14 10:55:09.742000 crash_report #{label=>{proc_lib,crash},report=>[[{initial_call,{application_master,init,['Argument__1','Argument__2','Argument__3','Argument__4']}},{pid,<0.45.0>},{registered_name,[]},{error_info,{exit,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,auth,{"Failed to create cookie file 'l:/.erlang.cookie': enoent",[{auth,init_cookie,0,[{file,"auth.erl"},{line,286}]},{auth,init,1,[{file,"auth.erl"},{line,140}]},{gen_server,init_it,2,[{file,"gen_server.erl"},{line,374}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,342}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}}}}},{kernel,start,[normal,[]]}},[{application_master,init,4,[{file,"application_master.erl"},{line,138}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}},{ancestors,[<0.44.0>]},{message_queue_len,1},{messages,[{'EXIT',<0.46.0>,normal}]},{links,[<0.44.0>,<0.43.0>]},{dictionary,[]},{trap_exit,true},{status,running},{heap_size,987},{stack_size,27},{reductions,184}],[]]} 2019-06-14 10:55:09.789000 std_info #{label=>{application_controller,exit},report=>[{application,kernel},{exited,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,auth,{"Failed to create cookie file 'l:/.erlang.cookie': enoent",[{auth,init_cookie,0,[{file,"auth.erl"},{line,286}]},{auth,init,1,[{file,"auth.erl"},{line,140}]},{gen_server,init_it,2,[{file,"gen_server.erl"},{line,374}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,342}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}}}}},{kernel,start,[normal,[]]}}},{type,permanent}]} {"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,auth,{\"Failed to create cookie file 'l:/.erlang.cookie': enoent\",[{auth,init_cookie,0,[{file,\"auth.erl\"},{line,286}]},{auth,init,1,[{file,\"auth.erl\"},{line,140}]},{gen_server,init_it,2,[{file,\"gen_server.erl\"},{line,374}]},{gen_server,init_it,6,[{file,\"gen_server.erl\"},{line,342}]},{proc_lib,init_p_do_apply,3,[{file,\"proc_lib.erl\"},{line,249}]}]}}}}},{kernel,start,[normal,[]]}}}"} Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,auth,{"Failed to create cookie file 'l:/.er Crash dump is being written to: C:\Users\Mj\AppData\Roaming\RabbitMQ\log\erl_crash.dump...done
Seems that the Order at which the commands are ran Matters, this worked for me, shuffle them around SET HOMEDRIVE=C: rabbitmq-plugins.bat enable rabbitmq_management rabbitmq-service.bat stop rabbitmq-service.bat install rabbitmq-service.bat start
Based off of the comment #LukeBakken made in the original question, I was able to get around this by creating a local admin user and doing the install under the local admin user. This was after hours of battling by setting the HOMEDRIVE, etc.
I solved this by following way : 1. Opened command prompt using administrative mode 2. Go to sbin directory. Execute command "SET HOMEDRIVE=C:"
Based on the comment from Luke Bakken, this is what worked for me: Almost the same as his comment, but instead of uninstall I had to use remove. uninstall was not recognized. "Log in as the admin user you installed RMQ with; Open the "RabbitMQ Command Prompt (sbin dir)" terminal, run:" .\rabbitmq-service.bat stop .\rabbitmq-service.bat remove set HOMEDRIVE=C: .\rabbitmq-service.bat install .\rabbitmq-plugins.bat enable rabbitmq_management .\rabbitmq-service.bat start
RabbitMQ: Unable to start rabbitmq_management plugin
Version: > sudo rabbitmqctl status | grep '{rabbit,"RabbitMQ",' {rabbit,"RabbitMQ","3.5.6"}, Error: > sudo rabbitmq-plugins enable rabbitmq_management Plugin configuration unchanged. Applying plugin configuration to rabbit#ip-172-31-26-169... failed. * Could not contact node rabbit#ip-172-31-26-169. Changes will take effect at broker restart. * Options: --online - fail if broker cannot be contacted. --offline - do not try to contact broker. Rabbit is running: > sudo service rabbitmq-server status Status of node 'rabbit#ip-172-31-26-169' ... [{pid,22865}, ..
You need not necessary to contact broker if you are on the same machine. so try this command >rabbitmq-plugins.bat enable rabbitmq_management --offline offline indicates that do not try to contact the broker.
I was getting the same error when trying to enable management console. To my suprise I typed http://localhost:15672/#/ in the browser and I could get to setup stuff through the management console. I had checked the availability of all the ports and everything looked good. So I think that error is kind of misleading. Just try to go to the console in browser. refs: http://arcware.net/installing-rabbitmq-on-windows/ Failed to start rabbitmq-management plugin on Windows
How do I stop the RabbitMQ server on localhost
I installed RabbitMQ server on OS X, and started it on command line. Now, it is not obvious that how I should stop it from running? After I did: sudo rabbitmq-server -detached I get: Activating RabbitMQ plugins ... 0 plugins activated: That was it. How should I properly shut it down? In the document, it mentions using rabbitmqctl(1), but it's not clear to me what that means. Thanks. Edit: As per comment below, this is what I get for running sudo rabbitmqctl stop: (project_env)mlstr-1:Package mlstr$ sudo rabbitmqctl stop Password: Stopping and halting node rabbit#h002 ... Error: unable to connect to node rabbit#h002: nodedown DIAGNOSTICS =========== nodes in question: [rabbit#h002] hosts, their running nodes and ports: - h002: [{rabbit,62428},{rabbitmqctl7069,64735}] current node details: - node name: rabbitmqctl7069#h002 - home dir: /opt/local/var/lib/rabbitmq - cookie hash: q7VU0JjCd0VG7jOEF9Hf/g== Why is there still a 'current node'? I have not run any client program but only the RabbitMQ server, does that mean a server is still running?
It turns out that it is related to permissions. Somehow my rabbitmq server was started with user 'rabbitmq' (which is strange), so that I had to do sudo -u rabbitmq rabbitmqctl stop
In my dev environment where I keep it running all the time, I use: launchctl unload ~/Library/LaunchAgents/homebrew.mxcl.rabbitmq.plist and to start it launchctl load ~/Library/LaunchAgents/homebrew.mxcl.rabbitmq.plist Even easier.... brew services stop rabbitmq brew services start rabbitmq
Use rabbitmqctl stop to stop any node. If you need to specify the node giving you trouble, add the -n rabbit#[hostname] option.
You can also use the shortcut RabbitMQ Service - stop if you don't like the commands
stop sudo systemctl stop rabbitmq-server start sudo systemctl start rabbitmq-server
For Windows, use PowerShell as Admin, then run .\rabbitmq-service.bat stop stop Stop the service. The service must be running for this command to have any effect. https://www.rabbitmq.com/man/rabbitmq-service.8.html For OP's answer above, It turns out that it is related to permissions. I have no knowledge on this.
For mac users To Stop brew services stop rabbitmq To Start brew services start rabbitmq To Restart brew services restart rabbitmq To Know the status of the server brew services info rabbitmq
"node with name "rabbit" already running", but also "unable to connect to node 'rabbit'"
Rabbitmq server does not start, saying it's already running: $: rabbitmq-server Activating RabbitMQ plugins ... 0 plugins activated: node with name "rabbit" already running on "android-d1af002161676bee" diagnostics: - nodes and their ports on android-d1af002161676bee: [{rabbit,52176}, {rabbitmqprelaunch2254, 59205}] - current node: 'rabbitmqprelaunch2254#android-d1af002161676bee' - current node home dir: /Users/Jordan - current node cookie hash: ZSx3slRJURGK/nHXDTBRqQ== But, rabbitmqctl seems to think otherwise: rabbitmqctl -n rabbit status Status of node 'rabbit#android-d1af002161676bee' ... Error: unable to connect to node 'rabbit#android-d1af002161676bee': nodedown diagnostics: - nodes and their ports on android-d1af002161676bee: [{rabbit,52176}, {rabbitmqctl2462,59256}] - current node: 'rabbitmqctl2462#android-d1af002161676bee' - current node home dir: /Users/Jordan - current node cookie hash: ZSx3slRJURGK/nHXDTBRqQ== Any takers?
The rabbitmq server was running somewhere but it just couldn't be connected to. One of the following will mention something about rabbits: $: ps aux | grep epmd $: ps aux | grep erl Kill the process with kill -9 {pid of rabbitmq process}
i was having the same problem then I realized I was not issuing the right command. ./rabbitmqctl stop this works everytime, although it does take down erlang runtime too. also mind where your config file.
I used rabbitmqctl stop and then restarted using rabbitmq-server as root.
This issue can be caused by two issues: Rabbit is already running on the server. If that is the case, use the answer you found of killing the currently running process (ps aux | grep rabbit | grep -v grep) You have changed the IP address of your machine but not changed the /etc/hosts file to reflect the new IP address of the machine. The more common of the issues is the first, but the harder to find is the second (especially if you have rabbit running on the other machine. If rabbit is installed on the other machine it will look at the old IP address and would see another machine already running rabbitmq and give you the same error. This has caused me grief in the past.
I was having this same error # Win 7, but the solutions above did not worked for me, what did solved was to remove and reinstall the service. Using a console with admin rights: rabbitmq-service remove rabbitmq-service install I hope this might help someone else too
$CD RabbitMQ Server\rabbitmq_server-3.7.8\sbin rabbitmq-service remove rabbitmq-service install Go : windows Services Find : RabbitMQ and Start it after this Enable plugin : rabbitmq-plugins enable rabbitmq_management
In my case under Ubuntu 11.10 it helped to #rabbitmqctl cluster MASTER SLAVE #rabbitmqctl start_app before I always got this error message...
Using admin console, in Win 2012R2 ver 3.5.5 rabbit, got it to work using the remove and install then rabbitmq-server restart then ctr-c to terminate the job, then I was able to use the windows service console and start the rabbitMq service.
In my case(windows), 1. I just ran the stop service. 2. The started the service.