Skip to content

badarith error for "rabbitmqctl await_startup" #2158

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sergey-safarov opened this issue Nov 6, 2019 · 9 comments · Fixed by #2159
Closed

badarith error for "rabbitmqctl await_startup" #2158

sergey-safarov opened this issue Nov 6, 2019 · 9 comments · Fixed by #2159
Assignees
Milestone

Comments

@sergey-safarov
Copy link

I automating rabbitmq initialization in cloud installation.
And found error

[root@rmq-a-1 ~]# rabbitmqctl await_startup
warning: the VM is running with native name encoding of latin1 which may cause Elixir to malfunction as it expects utf8. Please ensure your locale is set to UTF-8 (which can be verified by running "locale" in your shell)
Error:
{:badarith, [{:erlang, :div, [:infinity, 100], []}, {:rabbit, :wait_for_boot_to_start, 2, [file: 'src/rabbit.erl', line: 769]}, {:rabbit, :await_startup, 3, [file: 'src/rabbit.erl', line: 760]}, {:rpc, :"-handle_call_call/6-fun-0-", 5, [file: 'rpc.erl', line: 197]}]}

To reproduce need execute

rabbitmqctl stop_app
@lukebakken
Copy link
Collaborator

Thanks for using RabbitMQ and for reporting this issue. It has already been fixed in #2144

@sergey-safarov
Copy link
Author

Looks as issue not fixed on 3.8.1
Could you reopen.

OS PID: 6188
OS: Linux
Uptime (seconds): 11466
RabbitMQ version: 3.8.1
Node name: [email protected]
Erlang configuration: Erlang/OTP 21 [erts-10.3.5.6] [source] [64-bit] [smp:2:2] [ds:2:2:10] [async-threads:64] [hipe]
Erlang processes: 250 used, 1048576 limit
Scheduler run queue: 1
Cluster heartbeat timeout (net_ticktime): 60

According referenced PR 2144 fix merged into 3.8.x branch and not help.

@lukebakken lukebakken reopened this Nov 6, 2019
@lukebakken
Copy link
Collaborator

Thanks for letting us know what version you're using. Yes, I can reproduce this issue using the steps you provide.

@lukebakken lukebakken self-assigned this Nov 6, 2019
@lukebakken lukebakken added this to the 3.7.22 milestone Nov 6, 2019
lukebakken added a commit that referenced this issue Nov 6, 2019
@michaelklishin
Copy link
Collaborator

Once this change makes it through the pipeline we will produce a 3.8.2 preview for you to use in your automation work.

@sergey-safarov
Copy link
Author

Where i can download preview rpm build?
Thanks

@michaelklishin
Copy link
Collaborator

We will post a link here once Concourse produces a new alpha (development) build.

@michaelklishin
Copy link
Collaborator

I posted an alpha that did not contain this commit, we have to wait a bit more.

@michaelklishin
Copy link
Collaborator

3.7.22-alpha.5 contains this PR. Thanks again.

@antoinetran
Copy link

Hi, this is just a workaround script for people like me that cannot upgrade Rabbitmq immediately (but in the future yes):

            rabbitmq_await() {
              # Workaround of https://github.com/rabbitmq/rabbitmq-server/issues/2158
              # TODO: remove this sleep if rabbitmq >= 3.8.2.
              while ! rabbitmqctl cluster_status &>/dev/null ; do
                sleep 2
              done
              echo "Rabbitmq ready!"
            }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants