>From the master's perspective, the framework disconnected immediately after
registering.
You can bump up the logging on the jenkins scheduler by ensuring that
GLOG_v=3 is in your environment when our plugin is initialized.
On Thu, Nov 7, 2013 at 3:17 PM, Whitney Sorenson wrote:
> Sure (https://
Sure (https://github.com/jenkinsci/mesos-plugin/issues/4) but I'm actually
running into another issue which I've seen before with other frameworks:
I added the plugin to a separate Jenkins cluster and the framework doesn't
seem to be able to maintain the connection successfully.
The jenkins maste
We should fix that so that it reconnects with Mesos after a restart of
Jenkins!
Can you file an issue for this?
On Thu, Nov 7, 2013 at 12:31 PM, Whitney Sorenson wrote:
> I should also point out the scheduler didn't seem to survive a reboot of
> Jenkins - I had to delete the mesos cloud and ree
I should also point out the scheduler didn't seem to survive a reboot of
Jenkins - I had to delete the mesos cloud and reenter the parameters.
On Thu, Nov 7, 2013 at 3:26 PM, Whitney Sorenson wrote:
> Looks like we're using authentication on our slaves. So you either need to
> pass
>
> -jnlpCred
Looks like we're using authentication on our slaves. So you either need to
pass
-jnlpCredentials user:pass
on the command line, or change around the permissions in Jenkins to allow
anonymous users to connect/run jobs.
I'm not sure if it would make sense or not to add the user/pass in the
Jenkins
Great. Let us know once you figure it out. Maybe I can add a FAQ to the
plugin's README to help others (or you can contribute too :)).
On Thu, Nov 7, 2013 at 11:40 AM, Whitney Sorenson wrote:
> I added the jenkins user on the slave - this was the missing piece. I'll
> add this to my PR for the r
I added the jenkins user on the slave - this was the missing piece. I'll
add this to my PR for the readme. Got much further now; now I'm getting a
403 on the fetch:
/jenkins/computer/mesos-jenkins-6f4719c8-1c61-4b28-b5ab-ba298e846840/slave-agent.jnlp:
403 Forbidden at
hudson.remoting.Launcher.pars
I looked at the code and it looks there are few places the executor might
fail before it fetches the URI. Most of them have to do with incorrect
permissions. The code was written to have any errors reported either in
slave log or console or executor logs (there might be a bug here if we are
in fact
The gist was compiled from that log. Here is the complete log from toggling
the jenkins plugin on / off (you see the ping statements inbetween):
https://gist.github.com/wsorenson/8bf64e44fd42da354fa0
On Thu, Nov 7, 2013 at 1:57 PM, Vinod Kone wrote:
> What does mesos-slave.err say?
>
>
> On
What does mesos-slave.err say?
On Thu, Nov 7, 2013 at 10:49 AM, Whitney Sorenson wrote:
> Hi Vinod,
>
> It's 0.14.0-rc4 in both.
>
> I believe we have logging working:
>
> -rw-r--r-- 1 root root 0 Oct 22 23:48 mesos-slave.out
> lrwxrwxrwx 1 root root63 Oct 22 23:48 mesos-slave.IN
Hi Vinod,
It's 0.14.0-rc4 in both.
I believe we have logging working:
-rw-r--r-- 1 root root 0 Oct 22 23:48 mesos-slave.out
lrwxrwxrwx 1 root root63 Oct 22 23:48 mesos-slave.INFO ->
mesos-slave.carousel.invalid-user.log.INFO.20131022-234823.5797
lrwxrwxrwx 1 root root66 O
Hey Whitney,
What version of mesos are you using (both in the cluster and the plugin)?
The slave should print stuff to console when it is launching executor
(e.g., "Fetching resources..."). I don't see that in the gist you pasted.
Are you capturing stdout/stderr of the slave?
On Thu, Nov 7, 201
The logs that really helped me sort out what was happening where the
jenkins logs so you may want to check those first. Also when your slave is
trying to run the jenkins job you should check to see if it's actually able
to start the slave.jar java process. Looks something like this:
sh -c java -
Thanks Ray.
I have very similar issue (empty executor directories) - but don't have any
issues curling the slave.jar URI - and I don't have any existing JNLP
process running. I don't have a jenkins user - is that the only setup you
did on the slave?
-Whitney
On Thu, Nov 7, 2013 at 1:16 PM, Ray
Hi Whitney I would have a look at this github issue where I work through
some of my jenkins mesos-plugin issues with Vinod. Might be some of the
same issues you are seeing.
https://github.com/jenkinsci/mesos-plugin/issues/2
Ray
On Thu, Nov 7, 2013 at 1:07 PM, Whitney Sorenson wrote:
> Hi all!
Hi all!
I am trying to get the Jenkins Mesos plugin functioning. I was able to get
it installed on our Jenkins master.
However, it's unclear if there are any required steps for setting up the
slaves. When a framework task is launched, it fails instantly and there are
no logs in the runs folder.
16 matches
Mail list logo
