[Questions] Service won't start when installing via Software Center (SCCM)

[jeditiran]

Community Support Policy

• I have read RabbitMQ's Community Support Policy
• I run RabbitMQ 4.x, the only series currently covered by community support
• I promise to provide all relevant information (versions, logs from all nodes, rabbitmq-diagnostics output, detailed reproduction steps)

RabbitMQ version used

other (please specify)

Erlang version used

26.0.x

Operating system (distribution) used

Windows 10 1809 x64 LTSC

How is RabbitMQ deployed?

Windows binary package

rabbitmq-diagnostics status output

See https://www.rabbitmq.com/docs/cli to learn how to use rabbitmq-diagnostics

# PASTE OUTPUT HERE, BETWEEN BACKTICKS
Not sure what commands I should put here to get a valid output

Logs from node 1 (with sensitive values edited out)

See https://www.rabbitmq.com/docs/logging to learn how to collect logs

# PASTE LOG HERE, BETWEEN BACKTICKS

Logs from node 2 (if applicable, with sensitive values edited out)

See https://www.rabbitmq.com/docs/logging to learn how to collect logs

# PASTE LOG HERE, BETWEEN BACKTICKS

Logs from node 3 (if applicable, with sensitive values edited out)

See https://www.rabbitmq.com/docs/logging to learn how to collect logs

# PASTE LOG HERE, BETWEEN BACKTICKS

rabbitmq.conf

See https://www.rabbitmq.com/docs/configure#config-location to learn how to find rabbitmq.conf file location

# PASTE rabbitmq.conf HERE, BETWEEN BACKTICKS

Steps to deploy RabbitMQ cluster

No needed for this issue.

Steps to reproduce the behavior in question

1. Install Erlang
2. Add the installer for Rabbit to a SCCM server and advertise it to a workstation
3. On the workstation attempt to install Rabbit
4. During the install, when the installer attempts to start the service, it fails

advanced.config

See https://www.rabbitmq.com/docs/configure#config-location to learn how to find advanced.config file location

# PASTE advanced.config HERE, BETWEEN BACKTICKS

Application code

# PASTE CODE HERE, BETWEEN BACKTICKS

Kubernetes deployment file

# Relevant parts of K8S deployment that demonstrate how RabbitMQ is deployed
# PASTE YAML HERE, BETWEEN BACKTICKS

What problem are you trying to solve?

My company has the installers for Erlang and Rabbit encapsulated into a single EXE along with the other applications that are needed for our purpose and when we install the overall application via Software Center the RabbitMQ service fails to start.

Error: "rabbit-service.bat start exited with code 1."

We are installing the following versions:
Erlang: v.25.3.2.4 (13.2.2.2)
RabbitMQ Server v.3.12.2

If we run the EXE manually then everything installs fine and the service starts.
If we add the EXE to a SCCM (MECM) server and install the application then when Rabbit installs it throws an error starting the service failed to start. Erlang is installed before Rabbit.
The service fails no matter how I install the app when using Software Center. If I use "silent" switches, or even if i just trigger the EXE and I manually "next, next, finish" my way through the installer.
I have downloaded a stand-alone version of Erlang and Rabbit and they have the same behavior (fine manual, but service fail via SC). Even if I manually install Erlang and Rabbit (so the service starts fine), then install my EXE, the service breaks and fails.
I have found instructions for using the batch files in the "sbin" folder to uninstall the service, reinstall it and start, and that works as a workaround, but I need a resolution to the issue when installing.

[lukebakken]

During the install, when the installer attempts to start the service, it fails

Unfortunately, my telepathy is not what it used to be 😉

Could you provide logs? Is anything logged to the RabbitMQ log file, or the Event Viewer (Application or System)?

What logs Error: "rabbit-service.bat start exited with code 1."?

Finally, you must install RabbitMQ using a local administrator account, and it's best to ensure that HOMEDRIVE and HOMEPATH are set for that account. SCCM may try to install using LocalSystem and I really don't know what the outcome of that would be.

[jeditiran]

I would be happy to provide logs, if you can tell me how to get them. I looked at the site and it assumes a higher level of programming experience than I have. :(

The Event Viewer has 2 errors:

1. RabbitMQ: Could not start erlang service "RabbitMQ"with commandline ["C:\Program Files\Erlang OTP\erts-13.2.2.2\bin\erl.exe" -service_event ErlSrv_RabbitMQ -nohup -sname rabbit@N-TestVM09 -s "rabbit" boot -boot "start_sasl" +W w +MBas ageffcbf +MHas ageffcbf +MBlmbcs 512 +MHlmbcs 512 +MMmcs 30 +pc unicode +P 1048576 +t 5000000 +stbt db +zdbbl 128000 +sbwt none +sbwtdcpu none +sbwtdio none -kernel inet_dist_listen_min 25672 -kernel inet_dist_listen_max 25672 -syslog logger [] -syslog syslog_error_logger false -kernel prevent_overlapping_partitions false -enable-feature maybe_expr ].
2. RabbitMQ: Could not start erlang machine

[michaelklishin]

Unfortunately that message does not contain any hints.

[jeditiran]

Can you tell me how to pull the logs from Rabbit?

[jeditiran]

Looks like running with the latest version of Erlang (27.3.3) and the latest version of Rabbit (4.1.0) install clean.

Issue resolved.

[lukebakken]

https://www.rabbitmq.com/docs/relocate#windows

@jeditiran you need to figure out which user account is being used to run the RabbitMQ installer.

Then, log in with that account, and look in %APPDATA%\RabbitMQ\log for .log files.

Are you using a non-English language?

Related (maybe):

• Documentation: Installing on Windows emqx/emqx#871
• Recommend way to run emqttd 2.0 on windows emqx/emqx#803

[michaelklishin]

RabbitMQ versions before 4.1.0 are out of community support and Windows 10 reaches EOL in less than six months according to Google but if @lukebakken wants to investigate this, I won't interfere.

[lukebakken]

Ha, I didn't even notice the Windows 10 part of this discussion!

[viasat-ccaf]

Windows 10 1809 LTSC doesn't reach EOL until 2029-01-09.

[jeditiran]

And if it helps, it is happening on Windows 11 24H2 x63 LTSC as well.

[michaelklishin]

@viasat-ccaf we won't support a decade plus old distribution, Microsoft does not pay us a penny to do so. We do not support Windows Server older than 10 years, for example.

@jeditiran I'm pretty sure Windows 11 generally is in the same boat.

In any case, if @lukebakken wants to continue, so be it but any fixes will ship in 4.1.x. Everything older is out of community support.

4.1.x supports upgrades from 3.13.x, upgrading to it won't be any different than to 4.0.9.