RabbitMQ service install logs Unrecognized option {child_type,worker}] on Windows Server 2022 #14683
-
Describe the bugOn a clean installation of RabbitMQ 3.13.2 with Erlang OTP 26.2.5.10 on Windows Server 2022, the RabbitMQ service can be created and started, but during installation/update, the following error is shown: Reproduction steps
cd "C:\Program Files\RabbitMQ Server\rabbitmq_server-3.13.2\sbin"
.\rabbitmq-service.bat install
Expected behaviorThe RabbitMQ Windows service should install and update without any error messages. Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
|
The RabbitMQ 3.13 does not receive community support or updates. If you can reproduce this issue using RabbitMQ 4.1.4, please respond here and I'll re-open this discussion. Do NOT file a new issue until we're certain there is a bug to be fixed. |
Beta Was this translation helpful? Give feedback.
-
|
erlang 26.2.5.14 comes with erls 14.2.5.11 and Rabbitmq 3.13.7 throws the child_type worker error on windows 2022 server 10.0.20348 (64 bit). |
Beta Was this translation helpful? Give feedback.
-
|
@SiaWot you were told that RabbitMQ series older than 4.1.x are out of community support. I don't see why an ERTS version would matter here, in particular on Windows. We need a way to reproduce against |
Beta Was this translation helpful? Give feedback.
-
|
Maybe this can help someone: the $env:HOMEDRIVE and $env:HOMEPATH variables on Windows were set incorrectly, pointing to a network drive. Because of that, erlang couldn't find the cookie and couldn't determine the machine's name. Once I configured the $env:HOMEDRIVE and $env:HOMEPATH to their standard values, everything started working again. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you! This is sort of mentioned in one of the most obscure doc guides we have :) |
Beta Was this translation helpful? Give feedback.
-
|
Thank you Roberto! Worked! 🙂
Kind Regards,
Sebile
…On Mon, 27 Oct 2025 at 20:59, Roberto Basile ***@***.***> wrote:
Maybe this can help someone: the $env:HOMEDRIVE and $env:HOMEPATH
variables on Windows were set incorrectly, pointing to a network drive.
Because of that, erlang couldn't find the cookie and couldn't determine the
machine's name. Once I configured the $env:HOMEDRIVE and $env:HOMEPATH to
their standard values, everything started working again.
—
Reply to this email directly, view it on GitHub
<#14683 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AW2R2ZX5AIN7ALWA2AVHAUL3Z2BTPAVCNFSM6AAAAACIJKRZLWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINZZG43DENQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
FWIW, this Windows-specific issue is mentioned in this doc guide, which I admit is not the easiest thing to discover. |
Beta Was this translation helpful? Give feedback.
Maybe this can help someone: the $env:HOMEDRIVE and $env:HOMEPATH variables on Windows were set incorrectly, pointing to a network drive. Because of that, erlang couldn't find the cookie and couldn't determine the machine's name. Once I configured the $env:HOMEDRIVE and $env:HOMEPATH to their standard values, everything started working again.