Unable to change net_ticktime

[Jim]

Hello,

I set net_ticktime to 120 in rabbitmq.conf and advanced.config (Windows) but rabbitmqctl status still shows Cluster heartbeat timeout (net_ticktime): 60.

I know that my config files are effective because I can see it in the log file.

Is there a bug in rabbitmqctl status or am I missing something?

Thanks

[X Guest]

have you tried to restart the cluster? and what are the rabbitmq version?

--

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 view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/83425222-78d0-495f-9fbc-3729a8ca70e3n%40googlegroups.com.

--

  https://xguest.net/

[Jim]

Yes I restarted the whole cluster. I also tried taking it down completely. No luck.

I'm on  RabbitMQ 3.8.13  Erlang 23.2

Thanks

[Jim]

Anyone has an idea why it does that?

[Michal Kuratczyk]

Hi,

Please provide actual commands you are running and the output you see. It works just fine for me (3.8.14 on MacOS):

$ cat net_ticktime.conf
net_ticktime = 120

$ RABBITMQ_CONFIG_FILE=$PWD/net_ticktime.conf rabbitmq-server

$ rabbitmqctl status | grep ticktime
Cluster heartbeat timeout (net_ticktime): 120

Best,

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/49d434bc-2116-4848-874e-8872c0de31f6n%40googlegroups.com.

--

Michał

RabbitMQ team

[Jimmy Poulin]

Hi, I'm on Windows. Here are the commands and configuration.

C:\RabbitMQ>type rabbitmq.conf | find "ticktime"
net_ticktime = 120

RABBITMQ_CONFIG_FILE=C:\RabbitMQ\rabbitmq.conf

C:\RabbitMQ>type advanced.config | find "ticktime"
{kernel, [{net_ticktime,  120}]}

RABBITMQ_ADVANCED_CONFIG_FILE=C:\RabbitMQ\advanced.config

rabbitmqctl status | find "ticktime"
Cluster heartbeat timeout (net_ticktime): 60

I even tried reinstalling the service and no luck.

What am I missing?

Thanks

You received this message because you are subscribed to a topic in the Google Groups "rabbitmq-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rabbitmq-users/Fj16HE_C5sw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/CAA81d0uDe_4fB%2BjPytZeEOZCY60kdS_g%2BL4LGMfmLF1AEAmH1w%40mail.gmail.com.

--

Jimmy Poulin

Solution Architect

Groupe Canam inc. / Canam Group Inc.

T 418 228-8031; 7594 / C (418) 957-5538

F 418 228-1750

jimmy....@groupecanam.com

[Michal Kuratczyk]

You only showed a part of your advanced config file - perhaps this line is in the wrong place of the structure? But if both config files are effective, it should still be set to 120 because of the .conf file...

I also checked with advanced config file like this:

[
    {kernel, [ {net_ticktime,  120} ]}
].

And it works as expected for me. Do you see expected "Config file(s)" lines in the startup banner? I see this:

  Config file(s): /Users/mkuratczyk/workspace/conf/net_ticktime.config
                  /Users/mkuratczyk/workspace/conf/net_ticktime.conf

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/CAExzEG0_fpOGor2J%2BJxVEiu01SWwskXgXxFFkjWYi3rddxMXGA%40mail.gmail.com.

--

Michał

RabbitMQ team

[Jimmy Poulin]

Here is my full advanced.config

[
  {kernel, [{net_ticktime,  600}]}
].

Here is the startup info from the log

 node           : rabbit@nameofserver
 home dir       : C:\WINDOWS\system32\config\systemprofile
 config file(s) : c:/RabbitMQ/advanced.config
                : c:/RabbitMQ/rabbitmq.conf

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/CAA81d0tVscMA4jT3tzX9TNsipQSHNTUKj-rf99P1cnAFNwvY7w%40mail.gmail.com.

[Ching-Yu Tsai]

Hello,

Same issue here.

• OS: windows
• RabbitMQ version: 3.9.11
• Erlang version: 24.3

Here is my config file (C:\Users\User\AppData\Roaming\RabbitMQ\advanced.config):

[{kernel, [{net_ticktime, 600}]}].

After I restart all the nodes, the rabbitmqctl status still shows Cluster heartbeat timeout (net_ticktime): 60.

Any suggestion?

Thanks.

[Luke Bakken]

Hello,

Thank you for your report. I have opened an issue here if you would like to follow along:

https://github.com/rabbitmq/rabbitmq-server/issues/5055

Luke

[Luke Bakken]

Hello,

This is due to how the Erlang VM is run as a service on Windows. Erlang distribution is started at an earlier phase than on Linux, so you must set net_ticktime via a VM argument. To do so, create the %AppData%\RabbitMQ\rabbitmq-env-conf.bat file with the following contents

> cat C:\Users\bakkenl\AppData\Roaming\RabbitMQ\rabbitmq-env-conf.bat
@echo off
set SERVER_ADDITIONAL_ERL_ARGS=-kernel net_ticktime 600

Then, uninstall and install the service again:

cd C:\Program Files\RabbitMQ Server\rabbitmq_server-3.10.5\sbin

.\rabbitmq-service.bat stop

.\rabbitmq-service.bat remove

.\rabbitmq-service.bat install

.\rabbitmq-service.bat start

NOTE: it is generally a bad idea to set net_ticktime to a different value.

Thanks -

Luke