Master node executors going offline

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Master node executors going offline

Jon Schewe
I just upgraded one of my hudson instances to 1.304 and now I'm noticing
that after most builds the executors become marked offline. I am able to
restart them by going to the master node and click the button "this node
is now online" and then everything is fine. I only have a master node.
When looking at the node I notice that the "Free Temp Space" column is
red with 0.920GB in it. Could that be the problem?

--
Jon Schewe | http://mtu.net/~jpschewe
If you see an attachment named signature.asc, this is my digital
signature. See http://www.gnupg.org for more information.

For I am convinced that neither death nor life, neither angels nor
demons, neither the present nor the future, nor any powers,
neither height nor depth, nor anything else in all creation, will
be able to separate us from the love of God that is in Christ
Jesus our Lord. - Romans 8:38-39


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Master node executors going offline

Michael Donohue
Yes, that's why they're going offline.   But you're in luck - from the 1.301 release notes:

Preventive node monitoring like /tmp size check, swap space size check can be now disabled selectively. (issue 2596, issue 2552)


On Sat, May 9, 2009 at 8:48 PM, Jon Schewe <[hidden email]> wrote:
I just upgraded one of my hudson instances to 1.304 and now I'm noticing
that after most builds the executors become marked offline. I am able to
restart them by going to the master node and click the button "this node
is now online" and then everything is fine. I only have a master node.
When looking at the node I notice that the "Free Temp Space" column is
red with 0.920GB in it. Could that be the problem?

--
Jon Schewe | http://mtu.net/~jpschewe
If you see an attachment named signature.asc, this is my digital
signature. See http://www.gnupg.org for more information.

For I am convinced that neither death nor life, neither angels nor
demons, neither the present nor the future, nor any powers,
neither height nor depth, nor anything else in all creation, will
be able to separate us from the love of God that is in Christ
Jesus our Lord. - Romans 8:38-39


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: Master node executors going offline

Kohsuke Kawaguchi
Administrator

In the "manage Hudson" page it should also tell you that it took the
action to bring the node offline, and shows a hyperlink to the
configuration page.

Was it too subtle? Maybe I shouldn't try to do this at all if it's not a
distributed build environment?


Michael Donohue wrote:

> Yes, that's why they're going offline.   But you're in luck - from the 1.301
> release notes:
>
> Preventive node monitoring like /tmp size check, swap space size check can
> be now disabled selectively. (issue
> 2596<https://hudson.dev.java.net/issues/show_bug.cgi?id=2596>,
> issue 2552 <https://hudson.dev.java.net/issues/show_bug.cgi?id=2552>)
>
>
> On Sat, May 9, 2009 at 8:48 PM, Jon Schewe <[hidden email]> wrote:
>
>> I just upgraded one of my hudson instances to 1.304 and now I'm noticing
>> that after most builds the executors become marked offline. I am able to
>> restart them by going to the master node and click the button "this node
>> is now online" and then everything is fine. I only have a master node.
>> When looking at the node I notice that the "Free Temp Space" column is
>> red with 0.920GB in it. Could that be the problem?
>>
>> --
>> Jon Schewe | http://mtu.net/~jpschewe <http://mtu.net/%7Ejpschewe>
>> If you see an attachment named signature.asc, this is my digital
>> signature. See http://www.gnupg.org for more information.
>>
>> For I am convinced that neither death nor life, neither angels nor
>> demons, neither the present nor the future, nor any powers,
>> neither height nor depth, nor anything else in all creation, will
>> be able to separate us from the love of God that is in Christ
>> Jesus our Lord. - Romans 8:38-39
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>

--
Kohsuke Kawaguchi
Sun Microsystems                   http://weblogs.java.net/blog/kohsuke/

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Master node executors going offline

Jon Schewe
Yeah, I see the error message now. It would probably help if it was
linked to the "build is stuck" message as well. I just thought my job
was broken, not the hudson environment. Is there a way to tell Hudson to
use a different temp directory? Or to pick a lower limit?

Kohsuke Kawaguchi wrote:

>
> In the "manage Hudson" page it should also tell you that it took the
> action to bring the node offline, and shows a hyperlink to the
> configuration page.
>
> Was it too subtle? Maybe I shouldn't try to do this at all if it's not
> a distributed build environment?
>
>
> Michael Donohue wrote:
>> Yes, that's why they're going offline.   But you're in luck - from
>> the 1.301
>> release notes:
>>
>> Preventive node monitoring like /tmp size check, swap space size
>> check can
>> be now disabled selectively. (issue
>> 2596<https://hudson.dev.java.net/issues/show_bug.cgi?id=2596>,
>> issue 2552 <https://hudson.dev.java.net/issues/show_bug.cgi?id=2552>)
>>
>>
>> On Sat, May 9, 2009 at 8:48 PM, Jon Schewe <[hidden email]> wrote:
>>
>>> I just upgraded one of my hudson instances to 1.304 and now I'm
>>> noticing
>>> that after most builds the executors become marked offline. I am
>>> able to
>>> restart them by going to the master node and click the button "this
>>> node
>>> is now online" and then everything is fine. I only have a master node.
>>> When looking at the node I notice that the "Free Temp Space" column is
>>> red with 0.920GB in it. Could that be the problem?
>>>
>>> --
>>> Jon Schewe | http://mtu.net/~jpschewe <http://mtu.net/%7Ejpschewe>
>>> If you see an attachment named signature.asc, this is my digital
>>> signature. See http://www.gnupg.org for more information.
>>>
>>> For I am convinced that neither death nor life, neither angels nor
>>> demons, neither the present nor the future, nor any powers,
>>> neither height nor depth, nor anything else in all creation, will
>>> be able to separate us from the love of God that is in Christ
>>> Jesus our Lord. - Romans 8:38-39
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>
>
>

--
Jon Schewe | http://mtu.net/~jpschewe
If you see an attachment named signature.asc, this is my digital
signature. See http://www.gnupg.org for more information.

For I am convinced that neither death nor life, neither angels nor
demons, neither the present nor the future, nor any powers,
neither height nor depth, nor anything else in all creation, will
be able to separate us from the love of God that is in Christ
Jesus our Lord. - Romans 8:38-39


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Master node executors going offline

Fineinera
I have the same problem (using Hudson 1.313), how can I tell Hudson to
use a different temp directory?


Jon Schewe wrote
Yeah, I see the error message now. It would probably help if it was
linked to the "build is stuck" message as well. I just thought my job
was broken, not the hudson environment. Is there a way to tell Hudson to
use a different temp directory? Or to pick a lower limit?

Kohsuke Kawaguchi wrote:
>
> In the "manage Hudson" page it should also tell you that it took the
> action to bring the node offline, and shows a hyperlink to the
> configuration page.
>
> Was it too subtle? Maybe I shouldn't try to do this at all if it's not
> a distributed build environment?
>
>
> Michael Donohue wrote:
>> Yes, that's why they're going offline.   But you're in luck - from
>> the 1.301
>> release notes:
>>
>> Preventive node monitoring like /tmp size check, swap space size
>> check can
>> be now disabled selectively. (issue
>> 2596<https://hudson.dev.java.net/issues/show_bug.cgi?id=2596>,
>> issue 2552 <https://hudson.dev.java.net/issues/show_bug.cgi?id=2552>)
>>
>>
>> On Sat, May 9, 2009 at 8:48 PM, Jon Schewe <jpschewe@mtu.net> wrote:
>>
>>> I just upgraded one of my hudson instances to 1.304 and now I'm
>>> noticing
>>> that after most builds the executors become marked offline. I am
>>> able to
>>> restart them by going to the master node and click the button "this
>>> node
>>> is now online" and then everything is fine. I only have a master node.
>>> When looking at the node I notice that the "Free Temp Space" column is
>>> red with 0.920GB in it. Could that be the problem?
>>>
>>> --
>>> Jon Schewe | http://mtu.net/~jpschewe <http://mtu.net/%7Ejpschewe>
>>> If you see an attachment named signature.asc, this is my digital
>>> signature. See http://www.gnupg.org for more information.
>>>
>>> For I am convinced that neither death nor life, neither angels nor
>>> demons, neither the present nor the future, nor any powers,
>>> neither height nor depth, nor anything else in all creation, will
>>> be able to separate us from the love of God that is in Christ
>>> Jesus our Lord. - Romans 8:38-39
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@hudson.dev.java.net
>>> For additional commands, e-mail: users-help@hudson.dev.java.net
>>>
>>>
>>
>
>

--
Jon Schewe | http://mtu.net/~jpschewe
If you see an attachment named signature.asc, this is my digital
signature. See http://www.gnupg.org for more information.

For I am convinced that neither death nor life, neither angels nor
demons, neither the present nor the future, nor any powers,
neither height nor depth, nor anything else in all creation, will
be able to separate us from the love of God that is in Christ
Jesus our Lord. - Romans 8:38-39


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@hudson.dev.java.net
For additional commands, e-mail: users-help@hudson.dev.java.net