Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

slave-agent.jnlp stored in location not served by jenkins #55

Closed
minid33 opened this issue Sep 22, 2014 · 3 comments
Closed

slave-agent.jnlp stored in location not served by jenkins #55

minid33 opened this issue Sep 22, 2014 · 3 comments

Comments

@minid33
Copy link

minid33 commented Sep 22, 2014

Hey, I'm trying to get jenkins-mesos to work with my mesos cluster.
I was also having problems with starting dockers, there seems to be no logs at all for this issue, so I'll skip it for now.

I'm running mesos 0.20.0, Marathon 0.7.0 RC4, Jenkins 1.580 and a mesos-snapshot build (which i was hoping would have some fixes to my problems:) 0.5.0-SNAPSHOT (private-09/21/2014 21:59-minid33)

When I try to create a none-docker mesos task using the default slave info I see the following error:

It appears that the .jnlp is placed in a location that is not served by jenkins. The slave.jar file is placed inside the /tmp/mesos/..././././././...../ directory and I can curl it but I never manage to retrieve the jnlp.

WARNING: Logging before InitGoogleLogging() is written to STDERR
I0922 22:44:17.516777 16240 fetcher.cpp:76] Fetching URI 'http://slavenode:8080/jnlpJars/slave.jar'
I0922 22:44:17.516878 16240 fetcher.cpp:126] Downloading 'http://slavenode:8080/jnlpJars/slave.jar' to '/tmp/mesos/slaves/20140922-160741-16842879-5050-2582-0/frameworks/20140922-160741-16842879-5050-2582-0001/executors/mesos-jenkins-256ecf2c-241f-4ccc-921d-b88e50d530b3/runs/99b6f0ae-dd80-4024-87b9-e70e4ffe6e1a/slave.jar'
I0922 22:44:17.524060 16240 fetcher.cpp:255] Skipped extracting path '/tmp/mesos/slaves/20140922-160741-16842879-5050-2582-0/frameworks/20140922-160741-16842879-5050-2582-0001/executors/mesos-jenkins-256ecf2c-241f-4ccc-921d-b88e50d530b3/runs/99b6f0ae-dd80-4024-87b9-e70e4ffe6e1a/slave.jar'
I0922 22:44:18.529996 16249 exec.cpp:132] Version: 0.20.0
I0922 22:44:18.532008 16251 exec.cpp:206] Executor registered on slave 20140922-160741-16842879-5050-2582-0
Failing to obtain http://slavenode:8080/computer/mesos-jenkins-256ecf2c-241f-4ccc-921d-b88e50d530b3/slave-agent.jnlp
java.io.IOException: Failed to load http://slavenode:8080/computer/mesos-jenkins-256ecf2c-241f-4ccc-921d-b88e50d530b3/slave-agent.jnlp: 403 Forbidden
    at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:274)
    at hudson.remoting.Launcher.run(Launcher.java:218)
    at hudson.remoting.Launcher.main(Launcher.java:192)
Waiting 10 seconds before retry
Failing to obtain http://slavenode:8080/computer/mesos-jenkins-256ecf2c-241f-4ccc-921d-b88e50d530b3/slave-agent.jnlp
java.io.IOException: Failed to load http://slavenode:8080/computer/mesos-jenkins-256ecf2c-241f-4ccc-921d-b88e50d530b3/slave-agent.jnlp: 403 Forbidden
    at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:274)
    at hudson.remoting.Launcher.run(Launcher.java:218)
    at hudson.remoting.Launcher.main(Launcher.java:192)
Waiting 10 seconds before retry
Failing to obtain http://slavenode:8080/computer/mesos-jenkins-256ecf2c-241f-4ccc-921d-b88e50d530b3/slave-agent.jnlp
java.io.IOException: Failed to load http://slavenode:8080/computer/mesos-jenkins-256ecf2c-241f-4ccc-921d-b88e50d530b3/slave-agent.jnlp: 403 Forbidden
    at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:274)
    at hudson.remoting.Launcher.run(Launcher.java:218)
    at hudson.remoting.Launcher.main(Launcher.java:192)
Waiting 10 seconds before retry
@vinodkone
Copy link
Contributor

Looks like the JNLP requires some authentication credentials? You could pass your auth credentials via the JVM args. See #40

@minid33
Copy link
Author

minid33 commented Sep 25, 2014

Yep this is correct, @vinodkone 👍 perhaps this is something that should be documented but otherwise working

@vinodkone
Copy link
Contributor

Would you be up for sending a PR for the README about the authentication credentials?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants