Hey June,

I've seen this before when LIBPROCESS_IP wasn't set or was incorrect for
the Jenkins master. Note that, as a Mesos framework, there needs to be
two-way communication between the Mesos master and the Jenkins master,
otherwise you'll see failures like this. As such, if you're trying to run
the Jenkins master in a Docker container, be sure to do so in HOST
networking mode. Anyway, those are the most common issues I've seen in the
past.

You'll also want to be sure to set the Jenkins URL in the MesosCloud
configuration, so that the launched agents know the host and IP address
that the master is running on.

I hope that helps! Otherwise, you might consider posting to the jenkins-mesos
mailing list <https://groups.google.com/forum/#!forum/jenkins-mesos>.

-- Roger

On Fri, Sep 2, 2016 at 12:33 PM, June Taylor <[email protected]> wrote:

> Version 0.28.
>
>
> Thanks,
> June Taylor
> System Administrator, Minnesota Population Center
> University of Minnesota
>
> On Fri, Sep 2, 2016 at 2:24 PM, Gilbert Song <[email protected]>
> wrote:
>
>> Seems like Master::exited() is called for your jenkins frameworkId or
>> PID. Which
>> Mesos version are you using? It may possibly caused by network partition.
>> Are
>> you consistently getting this error?
>>
>> Gilbert
>>
>> On Fri, Sep 2, 2016 at 12:01 PM, June Taylor <[email protected]> wrote:
>>
>>> Greetings,
>>>
>>> We're trying to use the Jenkins CI plugin
>>> <https://wiki.jenkins-ci.org/display/JENKINS/Mesos+Plugin> to start up
>>> tasks on our Mesos cluster.
>>>
>>> We're running into an error where the framework fails to register when
>>> starting up the Jenkins service, and this appears in the logs. Has anyone
>>> run into a similar issue? We are not sure what it means when it says the
>>> framework disconnected immediately after subscribing.
>>>
>>> Thanks!
>>>
>>> I0902 13:53:49.262558 114093 master.cpp:2231] Received SUBSCRIBE call
>>> for framework 'Jenkins Scheduler' at scheduler-fa208659-1cb1-4f7d-a
>>> [email protected]:35121
>>> I0902 13:53:49.262619 114093 master.cpp:2302] Subscribing framework
>>> Jenkins Scheduler with checkpointing disabled and capabilities [  ]
>>> I0902 13:53:49.262933 114093 master.cpp:1212] Framework
>>> 0c540ad0-a050-4c20-82df-7bd14ce95f51-28951 (Jenkins Scheduler) at
>>> [email protected]:35121
>>> disconnected
>>> I0902 13:53:49.262964 114093 master.cpp:2527] Disconnecting framework
>>> 0c540ad0-a050-4c20-82df-7bd14ce95f51-28951 (Jenkins Scheduler) at
>>> [email protected]:35121
>>> I0902 13:53:49.262974 114093 master.cpp:2551] Deactivating framework
>>> 0c540ad0-a050-4c20-82df-7bd14ce95f51-28951 (Jenkins Scheduler) at
>>> [email protected]:35121
>>> I0902 13:53:49.263044 114093 master.cpp:1236] Giving framework
>>> 0c540ad0-a050-4c20-82df-7bd14ce95f51-28951 (Jenkins Scheduler) at
>>> [email protected]:35121 0ns to
>>> failover
>>> I0902 13:53:49.264189 114088 master.cpp:5176] Framework failover
>>> timeout, removing framework 0c540ad0-a050-4c20-82df-7bd14ce95f51-28951
>>> (Jenkins Scheduler) at scheduler-fa208659-1cb1-4f7d-a
>>> [email protected]:35121
>>> I0902 13:53:49.264209 114088 master.cpp:5909] Removing framework
>>> 0c540ad0-a050-4c20-82df-7bd14ce95f51-28951 (Jenkins Scheduler) at
>>> [email protected]:35121
>>>
>>> Thanks,
>>> June Taylor
>>> System Administrator, Minnesota Population Center
>>> University of Minnesota
>>>
>>
>>
>

Reply via email to