maxscale-6.1.1-1.rhel.8.x86_64 crashes and coredumps on first startup after upgrade maxscale-2.5.15-1.rhel.8.x86_64

I have upgraded MaxScale 2.15.5-1 to 6.1.1-1 on a number of my RHEL servers but on a single DELL server the post upgrade startup fails. journalctl -xe reports the following (see attached for full details):
Sep 01 22:07:17 ded101527.smartservers.com.au systemd[1]: Failed to start MariaDB MaxScale Database Proxy.
– Subject: Unit maxscale.service has failed
– Defined-By: systemd
– Support: https://access.redhat.com/support
–
– Unit maxscale.service has failed.
–
– The result is failed.
Sep 01 22:07:17 ded101527.smartservers.com.au systemd-coredump[1247981]: Process 1247979 (maxscale) of user 977 dumped core.

Stack trace of thread 1247979:
#0 0x00007f151db219d9 ZN7maxsimd7simd25617make_ascii_bitmapERKNSt7_cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libmaxscale-common.so.1.0.0)
#1 0x00007f151d9345e6 __static_initialization_and_destruction_0 (libmaxscale-common.so.1.0.0)
#2 0x00007f151ddf78ba call_init.part.0 (ld-linux-x86-64.so.2)
#3 0x00007f151ddf79ba _dl_init (ld-linux-x86-64.so.2)
#4 0x00007f151dde8fda _dl_start_user (ld-linux-x86-64.so.2)
– Subject: Process 1247979 (maxscale) dumped core
– Defined-By: systemd
– Support: https://access.redhat.com/support
– Documentation: man:core(5)
–
– Process 1247979 (maxscale) crashed and dumped core.
–
– This usually indicates a programming error in the crashing program and
– should be reported to its vendor as a bug.