RabbitMQ Services Does Not Start on a Sysprep'd System

[Mike Compton]

System is a Windows 7 SP1 fully patched.

RabbitMQ Server 3.6.5

When the client system is Sysprep'd on next startup, RabbitMQ service fails to start. manually running the service causes it to 'Unexpectedly terminate'

Q1) How can I determine what is causing the service to terminate/preventing the service from starting? Are there any log files?

Q2) Why is Rabbit Server not tolerant of a Sysprep? This is an extremely common procedure on all Windows systems varients. Has no testing been done on Windows systems?

[Michael Klishin]

Start by inspecting (and posting) server logs.

I'm not a Windows expert and have no idea what a "sysprep" is but the logs typically provide

a starting point.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

MK

Staff Software Engineer, Pivotal/RabbitMQ

[Michael Klishin]

Right, so according to https://technet.microsoft.com/en-us/library/cc721940(v=ws.10).aspx it's a mechanism of

VM (or similar?) duplication.

RabbitMQ is sensitive to hostname changes and node names in a cluster must be unique. Imaging and duplication

tools therefore likely need some help with making sure hostnames are unique, all nodes can resolve itself and their peers,

and that there are no duplicate names.

On Mon, Apr 10, 2017 at 5:59 PM, Michael Klishin <mkli...@pivotal.io> wrote:

Start by inspecting (and posting) server logs.

I'm not a Windows expert and have no idea what a "sysprep" is but the logs typically provide

a starting point.

On Mon, Apr 10, 2017 at 5:00 PM, Mike Compton <mikeyc...@gmail.com> wrote:

System is a Windows 7 SP1 fully patched.

RabbitMQ Server 3.6.5

When the client system is Sysprep'd on next startup, RabbitMQ service fails to start. manually running the service causes it to 'Unexpectedly terminate'

Q1) How can I determine what is causing the service to terminate/preventing the service from starting? Are there any log files?

Q2) Why is Rabbit Server not tolerant of a Sysprep? This is an extremely common procedure on all Windows systems varients. Has no testing been done on Windows systems?

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.

To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

MK

Staff Software Engineer, Pivotal/RabbitMQ

[Mike Compton]

Thanks for replying Michael - Can you please tell me where the logs are located? This is the first time i have been involved with installing RabbitMQ.

SysPrep is a program and built into all Windows OS's since Win 7, which clears all the unique GUIDs/SIDs from a device, Preparing the System for an image of it to be take for deployment to multiple systems.

So yes, the hostname changes not through the SysPrep directly, but as a result of the next startup of the image 'being turn into' a new system (for want of a better way to describe it).

So in order to work around the way that RabbitMQ stamps the hostname into its configuration; what is the procedure for changing a hostname of a system with RabbitMQ already installed?

Once that is addressed, perhaps the service will start.

I can also perform a test here, that will use an identical hostname after SysPrep but that will take a while to prepare.

Thanks for your assistance so far.

Mike.

[Michael Klishin]

See http://www.rabbitmq.com/relocate.html and http://www.rabbitmq.com/configure.html.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.

To post to this group, send email to rabbitmq-users@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Mike Compton]

So I have read the pages you sent links to (Relocate and Configure).

Q1) I have checked the Log folder, as per the File Locations section, and the log folder is empty, despite the Event Log showing that the service is terminating unexpectedly. Why is there no log file recorded? These are my findings whilst searching for a useable log:

C:\Users\%username%\AppData\Roaming\RabbitMQ\Log              = EMPTY

C:\Users\%username%\AppData\Roaming\RabbitMQ\                     = erl_crash.dump  

C:\Users\%username%\AppData\Roaming\RabbitMQ\db\RABBIT~3\LATEST.LOG     =   Unreadable file (binary?)

So directing me to the page listing Rabbit folder has not been userful so far.

Q 2/3) As for investigating whether the hardcoded (??) hostname is the cause; after reading the Configure page, i have read that Rabbit uses the System variable COMPUTERNAME on Windows systems (so not a Rabbit environment variable), this implies the hostname is in fact NOT hardcoded? Can you please confirm, if the hostname really is hardcoded in Rabbit? And if so, where?

Regards

Mike Compton

On Monday, 10 April 2017 15:00:55 UTC+1, Mike Compton wrote:

[Michael Klishin]

If it's empty this means your RabbitMQ node didn't have a chance to create any logs.

The "log" files under the db directory are internal data store operation logs.

erl_crash.dump might provide a bit of information about the state of the node

but ideally we need to capture standard output and standard error of the node.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mike Compton]

OK

How do you suggest I proceed?

What more can I do?

On Monday, 10 April 2017 15:00:55 UTC+1, Mike Compton wrote:

[Michael Klishin]

Locate any Windows logs that could capture standard output and standard error streams

of the process, or further termination details.

Consider posting the erl_crash.dump file here since that's the only piece of information

there is.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.