RabbitMQ remote powershell install

296 views
Skip to first unread message

AMartin

unread,
Aug 18, 2016, 4:19:38 PM8/18/16
to rabbitmq-users
I am trying to deploy RabbitMQ via Windows Release Management. This means I have a PowerShell script that opens a remote session, sets environment variables, then uses Start-Process to call rabbitmq-service.bat to install and start the service. This works cosmetically in that the service technically installs and starts, however RabbitMQ does not actually run. This produces no log files, not even empty ones. 

When I restart from Services or via rabbitmq-service.bat it still doesn't work. When I subsequently remove, install and start the service from a local PS session everything works. Environment variables in the local and remote session match exactly. 

Interesting note: when installed via remote session, the service does not have a description, so something is behaving badly in rabbitmq-service.bat. What dependencies does this script have besides the environment variables? Are there any other considerations for a remote install scenario?

Joseph Casale

unread,
Aug 18, 2016, 6:37:14 PM8/18/16
to rabbitm...@googlegroups.com
Why use start-process to run the batch file? There is nothing you are
doing asynchronously and I am not sure if start-process inherits the
parents environment which may be why you are getting mixed results. I
would check the resulting service definition in the Ericcson key and
look at what the batch files generated for arguments, that will likely
explain went wrong.
> --
> 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-user...@googlegroups.com.
> To post to this group, send email to rabbitm...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

AMartin

unread,
Aug 19, 2016, 3:41:45 PM8/19/16
to rabbitmq-users
You nailed it. The registry entries are being created but most of them, including Args and Env, are blank. I can create the registry entries from powershell code in the same script, which would point to erlang behavior and not registry permissions. Not sure if there's anything that can realistically be done about this/
Reply all
Reply to author
Forward
0 new messages