Hi Emile,<div> Thanks for the feedback, and the clarifications, if there's anything outstanding that's still relevant to my concern is how a new folder with the name %APPDATA% ended up in the sbin folder. This to me seems to be a bug with the bat scripts and I do believe it played a factor in making the setup on my machine dysfunctional.</div>
<div><br><br><div class="gmail_quote">On Tue, Mar 27, 2012 at 9:41 PM, Emile Joubert <span dir="ltr"><<a href="mailto:emile@rabbitmq.com">emile@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Nick,<br>
<br>
On 27/03/12 03:05, Nick Josevski wrote:<br>
> I tried to enable the management web feature via rabbitmq-plugins, but<br>
> somewhere during the process of enabling, stopping, installing,<br>
> starting the service back up again. A rogue '%APPDATA%' folder was<br>
> created in the sbin folder. In my case C:\Program Files (x86)\RabbitMQ<br>
> Server\rabbitmq_server-2.8.1\sbin<br>
><br>
> I've experienced this issue on versions 2.7.1 and 2.8.1.<br>
<br>
The default script folder for v2.8.1 is<br>
C:\Program Files\RabbitMQ Server\rabbitmq_server-2.8.1\sbin<br>
<br>
If you select a different installation folder (such as C:\Program Files<br>
(x86)) then the scripts will be installed in the folder you quoted.<br>
<br>
> The worst part of this is once that happened, I kept getting nodedown<br>
> errors when trying to do anything even via the reset and force_reset<br>
> commands.<br>
<br>
This is unlikely to be related to the installation path. Have you tried<br>
the advice in the troubleshooting guide?<br>
<a href="http://www.rabbitmq.com/troubleshooting.html" target="_blank">http://www.rabbitmq.com/troubleshooting.html</a><br>
<br>
> My solution was to uninstall RabbitMQ, delete all the folders (in<br>
> AppData and in Program Files), then go further to uninstall and re-<br>
> install Erlang, all with reboots scattered throughout to ensure<br>
> nothing was left behind.<br>
<br>
The uninstaller should do that for you. It should not be necessary to<br>
re-install Erlang.<br>
<br>
> To finally enable the rabbitmq_management plugin I had to just enable<br>
> it via the rabbitmq-plugins, **not** run stop or install or start via<br>
> rabbitmq-service.bat, but instead go into Services and just re-start<br>
> the RabbitMQ service via right click > start.<br>
<br>
This is incorrect. Restarting the broker is not sufficient for enabling<br>
plugins when running as a service. You must reinstall the service.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
-Emile<br>
<br>
<br>
</font></span></blockquote></div><br></div>