EFS install fails on startup on RHEL 8 - ERROR: Mounted RPM version is incompatible. Exiting
Remove restrictions with pre-depends on python (>= 2.6.6) | python2 (>= 2.6.6)
The following table lists known issues resolved prior to the release of Azul Zulu Prime System Tools (ZST) 5.22.15.
Release Resolved | Description |
---|---|
5.22.14 |
EFS install fails on startup on RHEL 8 - ERROR: Mounted RPM version is incompatible. Exiting Remove restrictions with pre-depends on python (>= 2.6.6) | python2 (>= 2.6.6) |
5.22.13 |
ZST install fails with 5.16.1 kernel ZST install fails on CentOS 8 kernels 4.18.0-358.el8 and higher ZST install fails on kernel 5.18.x kernels |
5.22.12 |
Fixes to allow running Prime System tools on Icelake machines. |
5.22.11 |
ZST support for RHEL/CentOS/CentOS 8 Stream |
5.22.9 |
ZST service start fails on large RAM systems due to init_on_alloc=1 default kernel setting on Ubuntu 20.04 |
5.22.7 |
ZST DKMS build fails on 5.4.x kernels with the following error message:
|
5.22.6 |
ZVM with ZST and cgroups enabled crashes on Virtuozzo Hypervisor. |
5.22.5 |
ZST dkms build fails for 5.0.0-x azure kernels. |
5.22.4 |
Support for OEL6 4.1.12.x kernels is now available with ZST 5.22.4 |
5.22.3 |
zing-licensed does not start after ZST upgrade. |
5.22.2 |
Zing Memory fails to start with ZST 4.18.x kernels. |
5.22.1 |
The |
5.22.0 |
Cgroup support for 4.x kernels. |
5.21.7 |
Improved handling of fragmented memory when starting Azul Zulu Prime JVM in reserve-at-launch mode and when starting zing-memory service in reserve-at-config mode. |
5.21.6 |
Zing Memory fails to start when vormetric agent is enabled. |
5.21.5 |
Temporarily allocate 4k chunks of memory when there are active file mappings in the buffer cache to overcome 2M allocation failure on RHEL7 systems. |
5.21.4 |
A race condition in VMA manipulation leads to zero byte zing cores. |
5.21.3 |
The system service ZST now uses systemd (if available) instead of sysvinit (init.d scripts) on RHEL/CentOS. |
5.21.3 |
Graceful VM Error reporting (hs_err_pid) support for the libc_hooks errors. |
5.21.1 |
insmod error when using ZST 5.21.0.0 or lower version of rheldkms package with dkms 2.5. |
5.21.1 |
Kernel crashes with the following error messages:
|
5.20.7 |
Azul Zulu Prime JVM ignores memory constraints enforced by cgroups in a container environment. |
5.21.1 |
Support for Linux kernel 4.15.*. |
5.21.0 |
ZST 5.21.0 version of |
5.21.0 |
Azul Zulu Prime JVM core bundler can bundle core files without gdb. |
5.21.0 |
Uninstalling ZST on Amazon Linux displays warning messages when rpm is upgraded. Ignore these warning messages.
|
5.20.6 |
Zing Memory crashes with the following error:
|
5.20.3 |
Kernel crash on RHEL 5 systems when running (Error message: |
5.20.3 |
|
5.20.2 |
Linux kernel bug caused by incorrect Zing Memory management at:
|
5.20.2 |
Running a ZVM on a machine with an enabled user-level Non-Uniform Memory Access Daemon (numad) daemon causes unexpected high system load average. |
5.20.2 |
Kernel crash when running
|
5.20.1 |
Long application pause times occur during New-To-Old/Old collections when collecting both the New and Old Generations. |
5.20.1 |
Kernel crashes with the following error messages: BUG: unable to handle kernel NULL pointer dereference |
5.16.0 |
The |
5.15.0 |
Dumping non-Azul Zulu Prime JVM cores causes RHEL 5 systems to panic under certain conditions. |
5.15.0 |
The |
5.15.0 |
Deadlock is detected when trying to preload a third party library |
5.15.0 |
Entering "default" for contingency memory when configuring ZST memory caused 0 size pool. |
5.14.0 |
Unable to shutdown or startup Azul Zulu Prime JVM instances when running incompatible versions of ZVM and ZST. |
5.12.0 |
Kernel may crash when configuring Zing Memory on some SGI systems. |
5.12.0 |
On Ubuntu 16.04,
|
5.12.0 |
On Ubuntu 16.04, when the zing-memory service is stopped, attempting to start a ZVM gives the following error:
|
5.12.0 |
Azul Zulu Prime JVM core bundler deletes Azul Zulu Prime JVM core when no space is left in the current working directory. Also introduces |
5.11.0 |
Server reboots without any info when using custom signal handler with Azul Zulu Prime JVM. This problem appeared because the |
5.11.0 |
Some SIGSEGV backtraces are not accurately reported in |
5.11.0 |
Unable to handle kernel paging request. |
5.7.19 |
|
5.7.19 |
|
5.7.18 |
Allow shut down scripts to uninstall ZST if Azul Zulu Prime JVM services don’t exist or they fail to stop. |
5.7.18 |
The Pool License Server fails to start with JDK 8. |
5.7.17 |
|
5.7.17 |
Not able to dump cores on containers when |
5.7.17 |
Allow cores to be dumped to any configurable location. |
5.7.16 |
Unable to launch Azul Zulu Prime JVM with reserve-at-launch policy even when sufficient memory is available. |
5.7.15 |
Update |
5.7.15 |
|
5.7.14 |
Support browsers updated with the fix for Logjam vulnerability. Upgrade to ZST 5.7.14 or above if you see |
5.7.12 |
Uninstalling ZST 5.7.11 on Amazon Linux displays a message. Ignore this message:
|
5.7.12 |
|
5.7.12 |
|
5.7.12 |
Add support for Oracle Linux- 2.6.39-400.246.2.el6uek.x86_64, 2.6.39-400.249.3.el5uek.x86_64, 2.6.39-400.249.3.el6uek.x86_64 |