[JIRA] (JENKINS-53924) Jenkins 2.136+ is not restartable with GLIBC 2.5

[gor...@idisagree.org (JIRA)]

Title: Message Title

Gordon Daugherty edited a comment on JENKINS-53924   Re: Jenkins 2.136+ is not restartable with GLIBC 2.5 As info, I had this same issue and found that the cause was that Linux's 'noexec' setting was enabled on the directory that was being used as my JVM's JNI tmpdir. The fix was to use "-Djna.tmpdir=<some path that has execute capability>" in the java command line used to start Jenkins.   Specifically, I added this to my start script: {quote} \ # Java's JNA tmpdir cannot be 'noexec' or Jenkins' restart functionality won't work so we're relocating it. mkdir -p ${JENKINS_HOME}/tmp TMPDIR_ARG=-Djna.tmpdir=${JENKINS_HOME}/tmp nohup $JAVA_HOME/bin/java $TMPDIR_ARG -jar jenkins.war <various other arguments omitted as those will differ for you> & {quote} Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194523.1538752831000.9642.1572996780191%40Atlassian.JIRA.