RabbitMQ 3.7.7 startup: "bad "MBa" value: ageffcbf"

[in...@habarisoft.com]

On Win 7 Home the broker displays the below message before startup:

bad "MBa" value: ageffcbfUsage: beam.smp.dll [flags] [ -- [init_args] ]
The flags are:

-a size        suggested stack size in kilo words for threads
               in the async-thread pool, valid range is [16-8192]
-A number      set number of threads in async thread pool,
               valid range is [0-1024]
-B[c|d|i]      c to have Ctrl-c interrupt the Erlang shell,
               d (or no extra option) to disable the break
               handler, i to ignore break signals
-c bool        enable or disable time correction
-C mode        set time warp mode; valid modes are:
               no_time_warp|single_time_warp|multi_time_warp
-d             don't write a crash dump for internally detected errors
               (halt(String) will still produce a crash dump)
-fn[u|a|l]     Control how filenames are interpreted
-hms size      set minimum heap size in words (default 233)
-hmbs size     set minimum binary virtual heap size in words (default 32768)
-hmax size     set maximum heap size in words (default 0)
-hmaxk bool    enable or disable kill at max heap size (default true)
-hmaxel bool   enable or disable error_logger report at max heap size (default t
rue)
-hpds size     initial process dictionary size (default 8)
-hmqd  val     set default message queue data flag for processes,
               valid values are: off_heap | on_heap
-K boolean     enable or disable kernel poll
-n[s|a|d]      Control behavior of signals to ports
               Note that this flag is deprecated!
-M<X> <Y>      memory allocator switches,
               see the erts_alloc(3) documentation for more info.
-pc <set>      Control what characters are considered printable (default latin1)

-P number      set maximum number of processes on this node,
               valid range is [1024-134217727]
-Q number      set maximum number of ports on this node,
               valid range is [1024-134217727]
-R number      set compatibility release number,
               valid range [18-20]
-r             force ets memory block to be moved on realloc
-rg amount     set reader groups limit
-sbt type      set scheduler bind type, valid types are:
-stbt type     u|ns|ts|ps|s|nnts|nnps|tnnps|db
-sbwt val      set scheduler busy wait threshold, valid values are:
               none|very_short|short|medium|long|very_long.
-scl bool      enable/disable compaction of scheduler load,
               see the erl(1) documentation for more info.
-sct cput      set cpu topology,
               see the erl(1) documentation for more info.
-secio bool    enable/disable eager check I/O scheduling,
               see the erl(1) documentation for more info.
-sub bool      enable/disable scheduler utilization balancing,
               see the erl(1) documentation for more info.
-sws val       set scheduler wakeup strategy, valid values are:
               default|legacy.
-swct val      set scheduler wake cleanup threshold, valid values are:
               very_lazy|lazy|medium|eager|very_eager.
-swt val       set scheduler wakeup threshold, valid values are:
               very_low|low|medium|high|very_high.
-sss size      suggested stack size in kilo words for scheduler threads,
               valid range is [20-8192] (default 128)
-sssdcpu size  suggested stack size in kilo words for dirty CPU scheduler
               threads, valid range is [20-8192] (default 40)
-sssdio size   suggested stack size in kilo words for dirty IO scheduler
               threads, valid range is [20-8192] (default 40)
-spp Bool      set port parallelism scheduling hint
-S n1:n2       set number of schedulers (n1), and number of
               schedulers online (n2), maximum for both
               numbers is 1024
-SP p1:p2      specify schedulers (p1) and schedulers online (p2)
               as percentages of logical processors configured and logical
               processors available, respectively
-SDcpu n1:n2   set number of dirty CPU schedulers (n1), and number of
               dirty CPU schedulers online (n2), valid range for both
               numbers is [1-1024], and n2 must be less than or equal to n1
-SDPcpu p1:p2  specify dirty CPU schedulers (p1) and dirty CPU schedulers
               online (p2) as percentages of logical processors configured
               and logical processors available, respectively
-SDio n        set number of dirty I/O schedulers, valid range is [0-1024]
-t size        set the maximum number of atoms the emulator can handle
               valid range is [8192-2147483647]
-T number      set modified timing level, valid range is [0-9]
-V             print Erlang version
-v             turn on chatty mode (GCs will be reported etc)
-W<i|w|e>      set error logger warnings mapping,
               see error_logger documentation for details
-zdbbl size    set the distribution buffer busy limit in kilobytes
               valid range is [1-2097151]
-zdntgc time   set delayed node table gc in seconds
               valid values are infinity or intergers in the range [0-100000000]


Note that if the emulator is started with erlexec (typically
from the erl script), these flags should be specified with +.


        1 file(s) copied.

  ##  ##
  ##  ##      RabbitMQ 3.7.7. Copyright (C) 2007-2018 Pivotal Software, Inc.
  ##########  Licensed under the MPL.  See http://www.rabbitmq.com/
  ######  ##
  ##########  Logs: C:/Users/Michael/AppData/Roaming/RabbitMQ/log/RABBIT~1.LOG
                    C:/Users/Michael/AppData/Roaming/RabbitMQ/log/rabbit@Win7Dev
_upgrade.log

              Starting broker...

 completed with 4 plugins.

The version I worked before (3.7.4) does not display this message. Is this something I can fix?

Erlang version is OTP 20 (9.2)

[Michael Klishin]

Your version of Erlang doesn't support some of the runtime allocator flags 3.7.6 and later

versions use. However, there is a different set of flags that is used on Erlang< 20.2.1.

Can there be multiple versions installed on your system at the same time?

The easiest option is to uninstall all Erlang versions there are and then install Erlang 20.3 or 21.0 (for 3.7.7+).

--
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-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

MK

Staff Software Engineer, Pivotal/RabbitMQ

[in...@habarisoft.com]

I removed the installed version, installed 20.3 and updated the erlang home environment variable, the message no longer is shown now.

Many thanks!

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.