Open lukebakken opened 6 years ago
As I recall, this was added on purpose, because the service.bat script is executed on install, while the server.bat script is executed on server start. So we can't assume that rabbitmq.conf
is there, because installation process does not create it.
Considering previous questions from users I start to lean towards no file check solution by default (like with service.bat).
This will allow users to create an advanced.config
file only if they want and make it a bit more consistent. This also allows us to stop using rabbitmq.config
filename, which is too similar to rabbitmq.conf
.
Of course we will have to handle and log the fact that the file is not there.
[159157000]
To reproduce:
%AppData%\RabbitMQ
, remove all configuration files exceptadvanced.config
, which has this content (nothing special, just something simple):rabbitmq.conf
(which isn't there!) andadvanced.config
are listed as config files.The reason is that this code is slightly different than this code.
When you install the Windows service, the presence of
rabbitmq.conf
is NOT checked and just assumed to be present, meaning thatadvanced.config
will be added to the argument list forerl.exe
whenerlsrv.exe
is started via the Windows Service Manager. When you run from the shell viarabbitmq-server.bat
,advanced.config
will only be used if the.conf
-style file is also present. This caused quite a bit of confusion in a recent support case.