Cannot run installed software via plugin, error=2, No such file or directory

1,527 views
Skip to first unread message

Luis Tiago Rico

unread,
Apr 5, 2017, 10:38:48 AM4/5/17
to jenkins...@googlegroups.com
Hi group, 

I'm developing a Angular/Java project and this is the first time I'm configuring jenkins from the start and I'm having some problems to run jobs on jenkins:alpine docker image.

So the problem I'm facing is that I cannot run a maven job with a specific JDK besides the system default (openJDK). Also I cannot run the FE job because it cannot run the installed nodejs.

So what I did was, after complete installation, I've installed the node.js plugin.
After that I went to jenkins configuration and choose a automatic installation of a Oracle JDK, Maven I'm using the default one and also choose a automatic installation of nodejs.
When I first run the Maven job it downloaded the oracle JDK, but then:
ERROR: Failed to parse POMs
java.io.IOException: Cannot run program "/var/jenkins_home/tools/hudson.model.JDK/oracle_8/bin/java" (in directory "/var/jenkins_home/workspace/jam-api"): error=2, No such file or directory

Same thing with Node.js 
[FATAL: command execution failed
java.io.IOException: Cannot run program "/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_7.8.0/bin/node" (in directory "/var/jenkins_home/workspace/jam-fe"): error=2, No such file or directory

Next thing I did was to check if installation was properly done on jenkins home.
Open a bash to my container and I've confirmed that installation was there, but I could not run either java or node from those specific paths. I only could run maven.

Trying to debug what was wrong I did some changes on jenkins JDK/node config, since installation was already done, I've change the automatic to specifying a path to installation, but problem still persists.

What am I missing here?
Adding some relevant screenshots to help you guys (and me) on debug







Thanks in advance

--
Luís Tiago Barreto Rico

Mark Waite

unread,
Apr 5, 2017, 11:36:05 AM4/5/17
to jenkins...@googlegroups.com
I've seen a "No such file or directory" message when I was trying to run a 32 bit version of cmake on a 64 bit operating system.  Is the downloaded JDK you're using a 32 bit JDK or a 64 bit JDK, and how does that compare to the operating system that is hosting it?

Mark Waite

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CALviG7pkwDhnPnvLLeeUgdXDsR5Ahi%2BQYjRhywkePjrCaKamLg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Luis Tiago Rico

unread,
Apr 5, 2017, 6:01:31 PM4/5/17
to Jenkins Users
Hi, OS is x86_64 GNU/Linux and downloader was jdk-8u121-linux-x64.tar.gz (from logs).
I've also checked permissions, ownership etc. for those installations (jdk and nodejs), also I've started from the ground with latest version of jenkins and the same happens. I've been struggling with this for a while now :(

Some other thoughts? This should be out of the box no? Maybe I'm missing something here...

Thanks

Luis Tiago Rico

unread,
Apr 5, 2017, 7:50:54 PM4/5/17
to Jenkins Users
just for clarification,

$ file java
java: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.9, BuildID[sha1]=c90f19ee0af98c47ccaa7181853cfd14867bc931, not stripped

$ uname -a
Linux c1873e406561 4.4.0-71-generic #92-Ubuntu SMP Fri Mar 24 12:59:01 UTC 2017 x86_64 GNU/Linux

Luis Tiago Rico

unread,
Apr 6, 2017, 6:18:26 AM4/6/17
to Jenkins Users
Hi,
moved from Alpine docker image to Ubuntu one and problems were gone. 

That "No such file or directory" message, has references all over the internet for the problem Mark states 32 vs 64bit Arch. incompatibilities, but I could not find the right solution for it! I suspect that some installation package is missing from Alpine that is causing the problem.

Thanks
Reply all
Reply to author
Forward
0 new messages