Skip to content
This repository has been archived by the owner on Jul 19, 2019. It is now read-only.

Ensure That JNA lib Can Work On Hardened Host #33

Open
ferricoxide opened this issue Nov 9, 2018 · 0 comments
Open

Ensure That JNA lib Can Work On Hardened Host #33

ferricoxide opened this issue Nov 9, 2018 · 0 comments
Labels
bug Something isn't working

Comments

@ferricoxide
Copy link
Member

ferricoxide commented Nov 9, 2018

Problem Description:

When deploying on a fully-hardened system, Jenkins jobs that rely on JNA lib may fail

Expected Behavior:

Jobs reliant on JNA lib function

Actual Behavior:

Jobs reliant on JNA lib may fail with errors similar to:

18:10:02.095 [ERROR] [system.err] Caused by: java.lang.UnsatisfiedLinkError: 
  /tmp/libjunixsocket-native-2.0.47627608075125696391.so: 
  /tmp/libjunixsocket-native-2.0.47627608075125696391.so: failed to map segment
  from shared object: Operation not permitted

Fix recommendation:

Ensure that that JVM starts with:

-Djava.io.tmpdir=${JENKINS_HOME}/tmp

(or similar) via an appropriate JENKINS_JAVA_OPTIONS setting in the /etc/sysconfig/jenkins file.

See CloudBess Support #215281717

@ferricoxide ferricoxide added the bug Something isn't working label Nov 9, 2018
ferricoxide added a commit to ferricoxide/cfn-jenkins that referenced this issue Nov 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant