You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Reid Madsen (Jira)" <ji...@apache.org> on 2022/06/17 23:08:00 UTC
[jira] [Comment Edited] (MNG-7485) Failed To Load JANSI Native Library
[ https://issues.apache.org/jira/browse/MNG-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17555780#comment-17555780 ]
Reid Madsen edited comment on MNG-7485 at 6/17/22 11:07 PM:
------------------------------------------------------------
[~michael-o] – I read through the comments, and having a hard time understanding what the "Fix" is for this Jira. If the fix is to set /tmp to "exec", then the fix is a no-go for us. We have 50 CICD build servers that are tightly controlled, and running with /tmp set to 'exec' is not permitted.
My apologies if I'm wasting your time...
And if it helps this is our filesyste, layout on CentOS 7:
{code:java}
srmadsen@c7cbagent01 :~$ cat /etc/fstab#
# /etc/fstab
# Created by anaconda on Tue Feb 5 15:16:38 2019
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/mapper/rootvg-rootlv / xfs defaults 0 0
UUID=bf01b480-d502-4c85-93b4-232d56885a5d /boot xfs defaults 0 0
UUID=8D22-7C18 /boot/efi vfat defaults,uid=0,gid=0,umask=0077,shortname=winnt 0 0
/dev/mapper/rootvg-homelv /home xfs nodev 0 0
/dev/mapper/rootvg-optlv /opt xfs defaults 0 0
/dev/mapper/rootvg-tmplv /tmp xfs nodev,nosuid,noexec 0 0
/dev/mapper/rootvg-usrlv /usr xfs defaults 0 0
/dev/mapper/rootvg-utillv /util xfs defaults 0 0
/dev/mapper/rootvg-varlv /var xfs defaults 0 0
/dev/mapper/rootvg-varloglv /var/log xfs defaults 0 0
/dev/mapper/rootvg-varaudlv /var/log/audit xfs defaults 0 0
/tmp /var/tmp none bind 0 0
tmpfs /dev/shm tmpfs nodev,nosuid,noexec 0 0
/dev/sdb /builds xfs defaults 0 0
{code}
was (Author: JIRAUSER291151):
[~michael-o] – I read through the comments, and having a hard time understanding what the "Fix" is for this Jira. If the fix is to set /tmp to "exec", then the fix is a no-go for us. We have 50 CICD build servers that are tightly controlled, and running with /tmp set to 'exec' is not permitted.
My apologies if I'm wasting your time...
> Failed To Load JANSI Native Library
> -----------------------------------
>
> Key: MNG-7485
> URL: https://issues.apache.org/jira/browse/MNG-7485
> Project: Maven
> Issue Type: Bug
> Components: Errors
> Affects Versions: 3.8.5
> Reporter: Mark
> Priority: Minor
>
> Hi All
> Wondering if anyone else has experienced a similar issue. I have recently upgraded to JDK 8 and Maven 3.8.5 and when i try mvn --version i get an error as such:
> {color:#505f79}Failed to load native library:jansi-2.4.0-bbb285ac9ffab828-libjansi.so. The native library file at /tmp/jansi-2.4.0-bbb285ac9ffab828-libjansi.so is not executable, make sure that the directory is mounted on a partition without the noexec flag, or set the jansi.tmpdir system property to point to a proper location. osinfo: Linux/x86_64{color}
> {color:#505f79}java.lang.UnsatisfiedLinkError: /tmp/jansi-2.4.0-bbb285ac9ffab828-libjansi.so: /tmp/jansi-2.4.0-bbb285ac9ffab828-libjansi.so: failed to map segment from shared object: Operation not permitted{color}
> {color:#505f79}Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0){color}
> {color:#505f79}Maven home: /opt/apache-maven-3.8.5{color}
> {color:#505f79}Java version: 1.8.0_251, vendor: Oracle Corporation, runtime: /opt/jdk1.8.0_251/jre{color}
> {color:#505f79}Default locale: en_US, platform encoding: UTF-8{color}
> {color:#505f79}OS name: "linux", version: "3.10.0-1160.49.1.el7.x86_64", arch: "amd64", family: "unix"{color}
> {color:#505f79}java version "1.8.0_251"{color}
> {color:#505f79}Java(TM) SE Runtime Environment (build 1.8.0_251-b08){color}
> {color:#505f79}Java HotSpot(TM) 64-Bit Server VM (build 25.251-b08, mixed mode){color}
> I have also tried installing JANSI through yum and that does not seem to resolve it. sudo yum -y install jansi-native
> Any help or guidance on how to resolve this would be greatly appreciated.
> CentOS Linux release 7.9.2009 (Core)
> apache-maven-3.8.5
> jdk1.8.0_251
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)