After setting up the license file in my brand new installation, i have tried to start the broker directly from the command line using "mgxparuntime" and with "startb". In both cases i got the same message in the mgerror.log file:

 

==============================================
PID 9479        26/12/2019 16:54:21
==============================================


 <-1> 26/12/2019 17:04:09.779     [Error  ] - ABNORMAL TERMINATION:  INTERRUPT (11)

Also i have tried to use STRACE to check what going wrong and it seems that it is a segmentation fault error:

 

--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0} ---

 

This is my environment:

• OS: Red Hat Enterprise Linux Server release 7.7 (Maipo)
• Java: java version "1.8.0_231"
• Magic: XPA 4.5a

It looks like all the libraries are OK:

[magicxpa@srv-vmd-ria ~]$ ldd /app/magicxpa4.5a/bin/mgxparuntime
linux-vdso.so.1 =>  (0x00007ffd061f0000)
libxerces-c-3.1.so => /app/magicxpa4.5a/lib/libxerces-c-3.1.so (0x00007f0731c69000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x00007f0731a3f000)
liblber-2.4.so.2 => /lib64/liblber-2.4.so.2 (0x00007f0731830000)
libldap_r-2.4.so.2 => /lib64/libldap_r-2.4.so.2 (0x00007f07315d1000)
libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007f073116e000)
libssl.so.10 => /lib64/libssl.so.10 (0x00007f0730efc000)
libicuio.so.50 => /lib64/libicuio.so.50 (0x00007f0730cee000)
libicui18n.so.50 => /lib64/libicui18n.so.50 (0x00007f07308ef000)
libicuuc.so.50 => /lib64/libicuuc.so.50 (0x00007f0730576000)
libicudata.so.50 => /lib64/libicudata.so.50 (0x00007f072efa2000)
libjvm.so => /usr/java/jre1.8.0_231-amd64/lib/amd64/server/libjvm.so (0x00007f072dfb8000)
libz.so.1 => /lib64/libz.so.1 (0x00007f072dda2000)
libnsl.so.1 => /lib64/libnsl.so.1 (0x00007f072db88000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f072d984000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f072d768000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f072d460000)
libm.so.6 => /lib64/libm.so.6 (0x00007f072d15e000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f072cf48000)
libc.so.6 => /lib64/libc.so.6 (0x00007f072cb7a000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f072c961000)
libsasl2.so.3 => /lib64/libsasl2.so.3 (0x00007f072c744000)
libssl3.so => /lib64/libssl3.so (0x00007f072c4eb000)
libsmime3.so => /lib64/libsmime3.so (0x00007f072c2c3000)
libnss3.so => /lib64/libnss3.so (0x00007f072bf94000)
libnssutil3.so => /lib64/libnssutil3.so (0x00007f072bd64000)
libplds4.so => /lib64/libplds4.so (0x00007f072bb60000)
libplc4.so => /lib64/libplc4.so (0x00007f072b95b000)
libnspr4.so => /lib64/libnspr4.so (0x00007f072b71d000)
libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007f072b4d0000)
libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007f072b1e7000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f072afe3000)
libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f072adb0000)
/lib64/ld-linux-x86-64.so.2 (0x00007f0732202000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f072ab79000)
libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007f072a969000)
librt.so.1 => /lib64/librt.so.1 (0x00007f072a761000)
libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f072a55d000)
libfreebl3.so => /lib64/libfreebl3.so (0x00007f072a35a000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f072a133000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f0729ed1000)
[magicxpa@srv-vmd-ria ~]$

 

I have a Magic XPA 3.3 running smoothly on Linux, and don't have clue what's going on with 4.5a.

Thanks in advance for any help.

Best regards,
Marvin VIDAL

If you run your Magic server in a docker container you can set the MAC address dynamically as a command line parameter for docker run https://docs.docker.com/engine/reference/run/
Maybe helps and works, I dont have Magic Linux (and dont need it when its hardwarebound shit)