Replies: 1 comment
-
You should use I'm assuming you can't consistently reproduce this issue, which means it's environment or server specific. If I have time, I will ensure that RabbitMQ 4.0.7 and Erlang 27.3 install successfully on a clean Windows Server 2022 VM. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Community Support Policy
RabbitMQ version used
4.0.6
Erlang version used
26.2.x
Operating system (distribution) used
Windows Server 2022
How is RabbitMQ deployed?
Windows installer
rabbitmq-diagnostics status output
See https://www.rabbitmq.com/docs/cli to learn how to use rabbitmq-diagnostics
Logs from node 1 (with sensitive values edited out)
See https://www.rabbitmq.com/docs/logging to learn how to collect logs
Logs from node 2 (if applicable, with sensitive values edited out)
See https://www.rabbitmq.com/docs/logging to learn how to collect logs
Logs from node 3 (if applicable, with sensitive values edited out)
See https://www.rabbitmq.com/docs/logging to learn how to collect logs
rabbitmq.conf
See https://www.rabbitmq.com/docs/configure#config-location to learn how to find rabbitmq.conf file location
Steps to deploy RabbitMQ cluster
Steps were to install the OTP software using the .exe and then the RabbitMQ .exe files
Steps to reproduce the behavior in question
I can uninstall and reinstall the OTP and RabbitMQ to get the same results.
advanced.config
See https://www.rabbitmq.com/docs/configure#config-location to learn how to find advanced.config file location
Application code
# PASTE CODE HERE, BETWEEN BACKTICKS
Kubernetes deployment file
What problem are you trying to solve?
During the windows installer and/or Chocolatey I'm getting an error message 'rabbitmq-service.bat install exited with code 1'. The installation is failing to install at the service. The log shows this error message 'C:\Program Files\Erlang OTP\erts-14.2.5.6\bin\erlsrv: Unrecognized option {child_type,worker}].' I've encountered this several times over the past two years at different customer environments across multiple versions. Typically a workaround is to add the 'set HOMEDRIVE=C:\Program Files\RabbitMQ Server' line in the rabbitmq-env.bat file and manually recreate the service. I have two servers in this current environment and this workaround worked on one server but is not working on the other. I'm limited to what I can/cannot copy from the environment.
Beta Was this translation helpful? Give feedback.
All reactions