Application terminated due to some permission error on

Hi Experts.,

Need your kind help on below issue that we are experiencing in our product with Alma Linux 8.5 environment.

Java Application terminated with some access error on
When application crashed, it created hs_err_pid805779.log file (also attached the same file).
In this log, we can see below line
“siginfo: si_signo: 11 (SIGSEGV), si_code: 2 (SEGV_ACCERR)”

Here SEGV_ACCERR means “Invalid permissions for mapped object.” (this is from man pages)

In the same file under stack info, we can see below lines
“Stack: [0x00007fc0d17da000,0x00007fc0d18db000], sp=0x00007fc0d18d5828, free space=1006k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C []”.

Considering both things we can assume that the reason for restart is access restriction for library.

Also, below is the result of ‘ls -ltr’ on the file from the same VM.
-rwxr-xr-x. 1 root root 144568 May 11 2019 /usr/lib64/
lrwxrwxrwx. 1 root root 17 May 11 2019 /usr/lib64/ →

Could you please help us understand the reason why access is restricted for this library.


SELinux or buffer overflow?

what does sestatus return? what about ls -lZ /usr/lib64/ ?

have you tried setenforce 0 then running the program? maybe using strace?

what user is the program running as - and what java version/vendor?

have you tried upgrading to 8.7?

log doesn’t seem to be attached.

PFA error log, Please remove .pdf from the extension. It’s a log file.

hs_err_pid805779.log.pdf (155.9 KB)

Here is the output of ls -lZ /usr/lib64/
[root@lb01 ~]# ls -lZ /usr/lib64/
-rwxr-xr-x. 1 root root system_u:object_r:lib_t:s0 144568 May 11 2019 /usr/lib64/
[root@lb01 ~]#

On the note of SELinux, we don’t have SELinux enabled, and hence we cannot use setenforce 0

[root@lb01 ~]# setenforce 0
setenforce: SELinux is disabled
[root@lb01 ~]#

Iqbal Singh

Please let me know if any other info is required or have any further queries.

looks like you’re not using the almalinux supported openjdk package, you’re using some commercially supported “zulu” build, so i’d go back to them in the first instance.

in the meantime see if you get a similar problem with the almalinux openjdk packages.

also the log says you’re running centos 8.1…?