On 4/9/20 9:48 AM, Paul Gevers wrote:
> Hi Thomas,
> 
> On 08-04-2020 18:04, Thomas Goirand wrote:
>> How may I test installing rabbitmq-server on ARM64 ? I don't have such a
>> hardware...
> 
> Can't you try on a porterbox?
> 
> Paul
> 

Hi Paul,

It took me a long time to do it, but thanks to the help of Steve
McIntyre, I could try installing RabbitMQ on an arm64 machine. A big
thanks to him! (cc him so he sees the thanks)

And it did work perfectly:

# ps axuf | grep erl
root     30007  0.0  0.0   5888   696 ttyAMA0  S+   15:50   0:00      \_
grep erl
rabbitmq 29591 47.7  3.3 1687452 68372 ?       Sl   15:49   0:11  \_
/usr/lib/erlang/erts-10.7/bin/beam.smp -W w -A 64 -MBas ageffcbf -MHas
ageffcbf -MBlmbcs 512 -MHlmbcs 512 -MMmcs 30 -P 1048576 -t 5000000 -stbt
db -zdbbl 128000 -K true -- -root /usr/lib/erlang -progname erl -- -home
/var/lib/rabbitmq -- -pa
/usr/lib/rabbitmq/lib/rabbitmq_server-3.7.18/ebin  -noshell -noinput -s
rabbit boot -sname rabbit@debian -boot start_sasl -kernel
inet_default_connect_options [{nodelay,true}] -sasl errlog_type error
-sasl sasl_error_logger false -rabbit lager_log_root "/var/log/rabbitmq"
-rabbit lager_default_file "/var/log/rabbitmq/rab...@debian.log" -rabbit
lager_upgrade_file "/var/log/rabbitmq/rabbit@debian_upgrade.log" -rabbit
feature_flags_file
"/var/lib/rabbitmq/mnesia/rabbit@debian-feature_flags" -rabbit
enabled_plugins_file "/etc/rabbitmq/enabled_plugins" -rabbit plugins_dir
"/usr/lib/rabbitmq/plugins:/usr/lib/rabbitmq/lib/rabbitmq_server-3.7.18/plugins"
-rabbit plugins_expand_dir
"/var/lib/rabbitmq/mnesia/rabbit@debian-plugins-expand" -os_mon
start_cpu_sup false -os_mon start_disksup false -os_mon start_memsup
false -mnesia dir "/var/lib/rabbitmq/mnesia/rabbit@debian" -kernel
inet_dist_listen_min 25672 -kernel inet_dist_listen_max 25672 --
rabbitmq 29826  0.1  0.0   1912   424 ?        Ss   15:49   0:00      \_
erl_child_setup 65536

It's hard to see (huge command line), but that's the output when
rabbitmq is started, believe me.

I tried stop / start the rabbitmq-server.service a few times, and it did
work for me, no problem (even though it was a bit slow on the arm64 VM I
was using, which is kind of expected with rabbitmq-server).

I'm therefore downgrading this bug to severity: important, until further
investigation can be done on your side. Indeed, this looks like specific
to your environment here.

Cheers,

Thomas Goirand (zigo)

Reply via email to