Hudson builds hang with builds in queue

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

Hudson builds hang with builds in queue

mjparme
For the last few weeks Hudson will no longer build projects. It stacks them all up in a Build Queue but they don't actually build. If I restart Hudson all the projects in the build queue will build but then Hudson will no longer build anymore (until another restart).

I first noticed this after upgrading to 1.249, I kept installing new versions hoping it was just a short-lived bug that would be fixed. I have tried versions all the way up to the newest 1.255 release and experience the same behavior. Presently I have "downgraded" all the way to 1.245 but still experience the same behavior.

Since past known good versions are experiencing the behavior I went hunting around the system log and ran across this:

Oct 14, 2008 10:35:48 AM hudson.node_monitors.DiskSpaceMonitor$1 monitor
WARNING: Making null offline temporarily due to the lack of disk space


All partitions have plenty of space.

Running on:

Linux linux120 2.4.21-40.ELsmp #1 SMP Thu Feb 2 22:22:39 EST 2006 i686 i686 i386 GNU/Linux


Anyone provide any insight? I have been using Hudson since 1.150 or so and this is the first issue we have had with it.
Reply | Threaded
Open this post in threaded view
|

Re: Hudson builds hang with builds in queue

mjparme
I guess my definition of "plenty of space" is different than Hudson's:-) I found another forum thread that mentioned that Hudson logs that message when the partition it is on has less than 1 gig.

Why the 1 gig limit? That seems to odd to shut down the builders when the partition has less than 1 gig. That is plenty of space to keep building.

The other issue I noticed is that all of the builds were being saved even though I have each one of our projects set only save the last 4 builds. Any idea why it wouldn't be honoring that setting?


mjparme wrote
For the last few weeks Hudson will no longer build projects. It stacks them all up in a Build Queue but they don't actually build. If I restart Hudson all the projects in the build queue will build but then Hudson will no longer build anymore (until another restart).

I first noticed this after upgrading to 1.249, I kept installing new versions hoping it was just a short-lived bug that would be fixed. I have tried versions all the way up to the newest 1.255 release and experience the same behavior. Presently I have "downgraded" all the way to 1.245 but still experience the same behavior.

Since past known good versions are experiencing the behavior I went hunting around the system log and ran across this:

Oct 14, 2008 10:35:48 AM hudson.node_monitors.DiskSpaceMonitor$1 monitor
WARNING: Making null offline temporarily due to the lack of disk space


All partitions have plenty of space.

Running on:

Linux linux120 2.4.21-40.ELsmp #1 SMP Thu Feb 2 22:22:39 EST 2006 i686 i686 i386 GNU/Linux


Anyone provide any insight? I have been using Hudson since 1.150 or so and this is the first issue we have had with it.
Reply | Threaded
Open this post in threaded view
|

Re: Hudson builds hang with builds in queue

Rich D
In reply to this post by mjparme
I'm having a similar issue running with;

Hudson 1.260
Java: 1.6.0_06b02
Appserver: Tomcat 6.0.16
OS: Linux version 2.6.18-53.1.21.el5 (mockbuild@builder6.centos.org) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Tue May 20 09:34:18 EDT 2008

df output;
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg00-lvroot
                      2.0G  306M  1.6G  17% /
/dev/mapper/vg00-lvhome
                      992M   46M  896M   5% /home
/dev/mapper/vg00-lvopt
                      496M  103M  368M  22% /opt
/dev/mapper/vg00-lvusr
                      3.9G  1.5G  2.2G  41% /usr
/dev/mapper/vg00-lvtmp
                      992M  198M  743M  22% /tmp
/dev/mapper/vg00-lvvar
                      2.0G  550M  1.4G  30% /var
/dev/mapper/vg00-lvhudson
                      3.0G  2.0G  901M  69% /export/hudson
/dev/sda1              99M   14M   81M  15% /boot
tmpfs                 125M     0  125M   0% /dev/shm

Only resolution seems to be restarting tomcat. We have 13 projects running on this instance.

Anyone find a resolution other than downgrading yet?

Thanks in advance,

.rich

mjparme wrote
For the last few weeks Hudson will no longer build projects. It stacks them all up in a Build Queue but they don't actually build. If I restart Hudson all the projects in the build queue will build but then Hudson will no longer build anymore (until another restart).

I first noticed this after upgrading to 1.249, I kept installing new versions hoping it was just a short-lived bug that would be fixed. I have tried versions all the way up to the newest 1.255 release and experience the same behavior. Presently I have "downgraded" all the way to 1.245 but still experience the same behavior.

Since past known good versions are experiencing the behavior I went hunting around the system log and ran across this:

Oct 14, 2008 10:35:48 AM hudson.node_monitors.DiskSpaceMonitor$1 monitor
WARNING: Making null offline temporarily due to the lack of disk space


All partitions have plenty of space.

Running on:

Linux linux120 2.4.21-40.ELsmp #1 SMP Thu Feb 2 22:22:39 EST 2006 i686 i686 i386 GNU/Linux


Anyone provide any insight? I have been using Hudson since 1.150 or so and this is the first issue we have had with it.
Reply | Threaded
Open this post in threaded view
|

Re: Hudson builds hang with builds in queue

Joshua McKinnon
You can disable/re-enable the master and any slaves by going to:
http://your-hudson-url/computer/
This page gives the status of all nodes. It is not very clear how to
get to if you are only running a master. From this page, clicking on a
node will bring you to a page that lets you enable/disable it.

If you have slaves, you can just click on the links for "Master" or
the name of each slave from your main Hudson page to get to the page
specific to that node. Once at the page for a given node, there is a
button in the upper right that will either say "Mark this node as
temporarily offline" or "This node is back online" depending on the
status of the node. You can re-enable a node brought offline due to
disk space in this manner, of course...Hudson will disable it again
the next time the disk space monitor runs.

As for why the limit is 1GB I don't know, but in my case it ends up
being a reasonable number. There may be an issue filed on making it
configurable, but there is a workaround. Hudson can only check free
disk space if you are running it with Java 6 - if you run Hudson on
Java 5 (builds can still use Java 6) it will not check free disk
space. Or you could just free up a little space.

If, on the other hand, Hudson isn't getting an accurate disk space
reading - that's cause for filing a bug.

hope that helps - this one puzzled me at first until I found the log message...

Joshua


On Tue, Nov 11, 2008 at 6:37 PM, Rich D
<[hidden email]> wrote:

>
> I'm having a similar issue running with;
>
> Hudson 1.260
> Java: 1.6.0_06b02
> Appserver: Tomcat 6.0.16
> OS: Linux version 2.6.18-53.1.21.el5 ([hidden email]) (gcc
> version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Tue May 20 09:34:18 EDT
> 2008
>
> df output;
> Filesystem            Size  Used Avail Use% Mounted on
> /dev/mapper/vg00-lvroot
>                      2.0G  306M  1.6G  17% /
> /dev/mapper/vg00-lvhome
>                      992M   46M  896M   5% /home
> /dev/mapper/vg00-lvopt
>                      496M  103M  368M  22% /opt
> /dev/mapper/vg00-lvusr
>                      3.9G  1.5G  2.2G  41% /usr
> /dev/mapper/vg00-lvtmp
>                      992M  198M  743M  22% /tmp
> /dev/mapper/vg00-lvvar
>                      2.0G  550M  1.4G  30% /var
> /dev/mapper/vg00-lvhudson
>                      3.0G  2.0G  901M  69% /export/hudson
> /dev/sda1              99M   14M   81M  15% /boot
> tmpfs                 125M     0  125M   0% /dev/shm
>
> Only resolution seems to be restarting tomcat. We have 13 projects running
> on this instance.
>
> Anyone find a resolution other than downgrading yet?
>
> Thanks in advance,
>
> .rich
>
>
> mjparme wrote:
>>
>> For the last few weeks Hudson will no longer build projects. It stacks
>> them all up in a Build Queue but they don't actually build. If I restart
>> Hudson all the projects in the build queue will build but then Hudson will
>> no longer build anymore (until another restart).
>>
>> I first noticed this after upgrading to 1.249, I kept installing new
>> versions hoping it was just a short-lived bug that would be fixed. I have
>> tried versions all the way up to the newest 1.255 release and experience
>> the same behavior. Presently I have "downgraded" all the way to 1.245 but
>> still experience the same behavior.
>>
>> Since past known good versions are experiencing the behavior I went
>> hunting around the system log and ran across this:
>>
>> Oct 14, 2008 10:35:48 AM hudson.node_monitors.DiskSpaceMonitor$1 monitor
>> WARNING: Making null offline temporarily due to the lack of disk space
>>
>>
>> All partitions have plenty of space.
>>
>> Running on:
>>
>> Linux linux120 2.4.21-40.ELsmp #1 SMP Thu Feb 2 22:22:39 EST 2006 i686
>> i686 i386 GNU/Linux
>>
>>
>> Anyone provide any insight? I have been using Hudson since 1.150 or so and
>> this is the first issue we have had with it.
>>
>
> --
> View this message in context: http://www.nabble.com/Hudson-builds-hang-with-builds-in-queue-tp19981433p20450927.html
> Sent from the Hudson users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

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

Reply | Threaded
Open this post in threaded view
|

Re: Hudson builds hang with builds in queue

mjparme
I opened an issue to make the 1GB limit configurable a few weeks back.

I solved the issue by having the admin resize the partition Hudson was on to give it more space.

Joshua McKinnon wrote
As for why the limit is 1GB I don't know, but in my case it ends up
being a reasonable number. There may be an issue filed on making it
configurable, but there is a workaround. Hudson can only check free
disk space if you are running it with Java 6 - if you run Hudson on
Java 5 (builds can still use Java 6) it will not check free disk
space. Or you could just free up a little space.

If, on the other hand, Hudson isn't getting an accurate disk space
reading - that's cause for filing a bug.

Joshua


On Tue, Nov 11, 2008 at 6:37 PM, Rich D
<rdammkoehler@pillartechnology.com> wrote:
>
> I'm having a similar issue running with;
>
> Hudson 1.260
> Java: 1.6.0_06b02
> Appserver: Tomcat 6.0.16
> OS: Linux version 2.6.18-53.1.21.el5 (mockbuild@builder6.centos.org) (gcc
> version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Tue May 20 09:34:18 EDT
> 2008
>
> df output;
> Filesystem            Size  Used Avail Use% Mounted on
> /dev/mapper/vg00-lvroot
>                      2.0G  306M  1.6G  17% /
> /dev/mapper/vg00-lvhome
>                      992M   46M  896M   5% /home
> /dev/mapper/vg00-lvopt
>                      496M  103M  368M  22% /opt
> /dev/mapper/vg00-lvusr
>                      3.9G  1.5G  2.2G  41% /usr
> /dev/mapper/vg00-lvtmp
>                      992M  198M  743M  22% /tmp
> /dev/mapper/vg00-lvvar
>                      2.0G  550M  1.4G  30% /var
> /dev/mapper/vg00-lvhudson
>                      3.0G  2.0G  901M  69% /export/hudson
> /dev/sda1              99M   14M   81M  15% /boot
> tmpfs                 125M     0  125M   0% /dev/shm
>
> Only resolution seems to be restarting tomcat. We have 13 projects running
> on this instance.
>
> Anyone find a resolution other than downgrading yet?
>
> Thanks in advance,
>
> .rich
>
>
> mjparme wrote:
>>
>> For the last few weeks Hudson will no longer build projects. It stacks
>> them all up in a Build Queue but they don't actually build. If I restart
>> Hudson all the projects in the build queue will build but then Hudson will
>> no longer build anymore (until another restart).
>>
>> I first noticed this after upgrading to 1.249, I kept installing new
>> versions hoping it was just a short-lived bug that would be fixed. I have
>> tried versions all the way up to the newest 1.255 release and experience
>> the same behavior. Presently I have "downgraded" all the way to 1.245 but
>> still experience the same behavior.
>>
>> Since past known good versions are experiencing the behavior I went
>> hunting around the system log and ran across this:
>>
>> Oct 14, 2008 10:35:48 AM hudson.node_monitors.DiskSpaceMonitor$1 monitor
>> WARNING: Making null offline temporarily due to the lack of disk space
>>
>>
>> All partitions have plenty of space.
>>
>> Running on:
>>
>> Linux linux120 2.4.21-40.ELsmp #1 SMP Thu Feb 2 22:22:39 EST 2006 i686
>> i686 i386 GNU/Linux
>>
>>
>> Anyone provide any insight? I have been using Hudson since 1.150 or so and
>> this is the first issue we have had with it.
>>
>
> --
> View this message in context: http://www.nabble.com/Hudson-builds-hang-with-builds-in-queue-tp19981433p20450927.html
> Sent from the Hudson users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@hudson.dev.java.net
> For additional commands, e-mail: users-help@hudson.dev.java.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@hudson.dev.java.net
For additional commands, e-mail: users-help@hudson.dev.java.net
Reply | Threaded
Open this post in threaded view
|

Re: Hudson builds hang with builds in queue

rsemburakkiannan
>> I solved the issue by having the admin resize the partition Hudson was on to give it more space.
How to achieve it?


mjparme wrote
I opened an issue to make the 1GB limit configurable a few weeks back.

I solved the issue by having the admin resize the partition Hudson was on to give it more space.

Joshua McKinnon wrote
As for why the limit is 1GB I don't know, but in my case it ends up
being a reasonable number. There may be an issue filed on making it
configurable, but there is a workaround. Hudson can only check free
disk space if you are running it with Java 6 - if you run Hudson on
Java 5 (builds can still use Java 6) it will not check free disk
space. Or you could just free up a little space.

If, on the other hand, Hudson isn't getting an accurate disk space
reading - that's cause for filing a bug.

Joshua


On Tue, Nov 11, 2008 at 6:37 PM, Rich D
<rdammkoehler@pillartechnology.com> wrote:
>
> I'm having a similar issue running with;
>
> Hudson 1.260
> Java: 1.6.0_06b02
> Appserver: Tomcat 6.0.16
> OS: Linux version 2.6.18-53.1.21.el5 (mockbuild@builder6.centos.org) (gcc
> version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Tue May 20 09:34:18 EDT
> 2008
>
> df output;
> Filesystem            Size  Used Avail Use% Mounted on
> /dev/mapper/vg00-lvroot
>                      2.0G  306M  1.6G  17% /
> /dev/mapper/vg00-lvhome
>                      992M   46M  896M   5% /home
> /dev/mapper/vg00-lvopt
>                      496M  103M  368M  22% /opt
> /dev/mapper/vg00-lvusr
>                      3.9G  1.5G  2.2G  41% /usr
> /dev/mapper/vg00-lvtmp
>                      992M  198M  743M  22% /tmp
> /dev/mapper/vg00-lvvar
>                      2.0G  550M  1.4G  30% /var
> /dev/mapper/vg00-lvhudson
>                      3.0G  2.0G  901M  69% /export/hudson
> /dev/sda1              99M   14M   81M  15% /boot
> tmpfs                 125M     0  125M   0% /dev/shm
>
> Only resolution seems to be restarting tomcat. We have 13 projects running
> on this instance.
>
> Anyone find a resolution other than downgrading yet?
>
> Thanks in advance,
>
> .rich
>
>
> mjparme wrote:
>>
>> For the last few weeks Hudson will no longer build projects. It stacks
>> them all up in a Build Queue but they don't actually build. If I restart
>> Hudson all the projects in the build queue will build but then Hudson will
>> no longer build anymore (until another restart).
>>
>> I first noticed this after upgrading to 1.249, I kept installing new
>> versions hoping it was just a short-lived bug that would be fixed. I have
>> tried versions all the way up to the newest 1.255 release and experience
>> the same behavior. Presently I have "downgraded" all the way to 1.245 but
>> still experience the same behavior.
>>
>> Since past known good versions are experiencing the behavior I went
>> hunting around the system log and ran across this:
>>
>> Oct 14, 2008 10:35:48 AM hudson.node_monitors.DiskSpaceMonitor$1 monitor
>> WARNING: Making null offline temporarily due to the lack of disk space
>>
>>
>> All partitions have plenty of space.
>>
>> Running on:
>>
>> Linux linux120 2.4.21-40.ELsmp #1 SMP Thu Feb 2 22:22:39 EST 2006 i686
>> i686 i386 GNU/Linux
>>
>>
>> Anyone provide any insight? I have been using Hudson since 1.150 or so and
>> this is the first issue we have had with it.
>>
>
> --
> View this message in context: http://www.nabble.com/Hudson-builds-hang-with-builds-in-queue-tp19981433p20450927.html
> Sent from the Hudson users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@hudson.dev.java.net
> For additional commands, e-mail: users-help@hudson.dev.java.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@hudson.dev.java.net
For additional commands, e-mail: users-help@hudson.dev.java.net
Reply | Threaded
Open this post in threaded view
|

RE: Re: Hudson builds hang with builds in queue

Molumby, Rich
We run our hudson on a windows machine that has several drives.
The OS is installed on C:
Hudson is running on D:
Java is installed on D:
What disk space drive is Java 6 looking at to determine if there is enough space?

Rich Molumby 

-----Original Message-----
From: rsemburakkiannan [mailto:[hidden email]]
Sent: Friday, April 24, 2009 12:47 PM
To: [hidden email]
Subject: Re: Hudson builds hang with builds in queue


>> I solved the issue by having the admin resize the partition Hudson was on
to give it more space.
How to achieve it?



mjparme wrote:

>
> I opened an issue to make the 1GB limit configurable a few weeks back.
>
> I solved the issue by having the admin resize the partition Hudson was on
> to give it more space.
>
>
> Joshua McKinnon wrote:
>>
>> As for why the limit is 1GB I don't know, but in my case it ends up
>> being a reasonable number. There may be an issue filed on making it
>> configurable, but there is a workaround. Hudson can only check free
>> disk space if you are running it with Java 6 - if you run Hudson on
>> Java 5 (builds can still use Java 6) it will not check free disk
>> space. Or you could just free up a little space.
>>
>> If, on the other hand, Hudson isn't getting an accurate disk space
>> reading - that's cause for filing a bug.
>>
>> Joshua
>>
>>
>> On Tue, Nov 11, 2008 at 6:37 PM, Rich D
>> <[hidden email]> wrote:
>>>
>>> I'm having a similar issue running with;
>>>
>>> Hudson 1.260
>>> Java: 1.6.0_06b02
>>> Appserver: Tomcat 6.0.16
>>> OS: Linux version 2.6.18-53.1.21.el5 ([hidden email])
>>> (gcc
>>> version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Tue May 20 09:34:18
>>> EDT
>>> 2008
>>>
>>> df output;
>>> Filesystem            Size  Used Avail Use% Mounted on
>>> /dev/mapper/vg00-lvroot
>>>                      2.0G  306M  1.6G  17% /
>>> /dev/mapper/vg00-lvhome
>>>                      992M   46M  896M   5% /home
>>> /dev/mapper/vg00-lvopt
>>>                      496M  103M  368M  22% /opt
>>> /dev/mapper/vg00-lvusr
>>>                      3.9G  1.5G  2.2G  41% /usr
>>> /dev/mapper/vg00-lvtmp
>>>                      992M  198M  743M  22% /tmp
>>> /dev/mapper/vg00-lvvar
>>>                      2.0G  550M  1.4G  30% /var
>>> /dev/mapper/vg00-lvhudson
>>>                      3.0G  2.0G  901M  69% /export/hudson
>>> /dev/sda1              99M   14M   81M  15% /boot
>>> tmpfs                 125M     0  125M   0% /dev/shm
>>>
>>> Only resolution seems to be restarting tomcat. We have 13 projects
>>> running
>>> on this instance.
>>>
>>> Anyone find a resolution other than downgrading yet?
>>>
>>> Thanks in advance,
>>>
>>> .rich
>>>
>>>
>>> mjparme wrote:
>>>>
>>>> For the last few weeks Hudson will no longer build projects. It stacks
>>>> them all up in a Build Queue but they don't actually build. If I
>>>> restart
>>>> Hudson all the projects in the build queue will build but then Hudson
>>>> will
>>>> no longer build anymore (until another restart).
>>>>
>>>> I first noticed this after upgrading to 1.249, I kept installing new
>>>> versions hoping it was just a short-lived bug that would be fixed. I
>>>> have
>>>> tried versions all the way up to the newest 1.255 release and
>>>> experience
>>>> the same behavior. Presently I have "downgraded" all the way to 1.245
>>>> but
>>>> still experience the same behavior.
>>>>
>>>> Since past known good versions are experiencing the behavior I went
>>>> hunting around the system log and ran across this:
>>>>
>>>> Oct 14, 2008 10:35:48 AM hudson.node_monitors.DiskSpaceMonitor$1
>>>> monitor
>>>> WARNING: Making null offline temporarily due to the lack of disk space
>>>>
>>>>
>>>> All partitions have plenty of space.
>>>>
>>>> Running on:
>>>>
>>>> Linux linux120 2.4.21-40.ELsmp #1 SMP Thu Feb 2 22:22:39 EST 2006 i686
>>>> i686 i386 GNU/Linux
>>>>
>>>>
>>>> Anyone provide any insight? I have been using Hudson since 1.150 or so
>>>> and
>>>> this is the first issue we have had with it.
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Hudson-builds-hang-with-builds-in-queue-tp19981433p20450927.html
>>> Sent from the Hudson users mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>>
>
>

--
View this message in context: http://www.nabble.com/Hudson-builds-hang-with-builds-in-queue-tp19981433p23221694.html
Sent from the Hudson users mailing list archive at Nabble.com.


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


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

Reply | Threaded
Open this post in threaded view
|

Re: Hudson builds hang with builds in queue

mjparme
In reply to this post by rsemburakkiannan

rsemburakkiannan wrote
>> I solved the issue by having the admin resize the partition Hudson was on to give it more space.
How to achieve it?
I don't know. There is some Linux magic (we are running Hudson on a RedHat linux box) that an admin can perform to resize the partition on the fly.  I think it is called "virtual file systems" or some such that lets you have a single logical partition span multiple physical drives.

I remember reading about it quite a few years ago when support for it was added to Linux. But my memory is pretty fuzzy regarding exactly what it is called. I could just be plain wrong as well:-) I just asked my admin if he could give that partition more space and he said, "sure no problem".
Reply | Threaded
Open this post in threaded view
|

Re: Hudson builds hang with builds in queue

Kohsuke Kawaguchi
Administrator
In reply to this post by mjparme
mjparme wrote:
> I opened an issue to make the 1GB limit configurable a few weeks back.
>
> I solved the issue by having the admin resize the partition Hudson was on to
> give it more space.

In the upcoming 1.301, you can disable these checks.

>
>
> Joshua McKinnon wrote:
>>
>> As for why the limit is 1GB I don't know, but in my case it ends up
>> being a reasonable number. There may be an issue filed on making it
>> configurable, but there is a workaround. Hudson can only check free
>> disk space if you are running it with Java 6 - if you run Hudson on
>> Java 5 (builds can still use Java 6) it will not check free disk
>> space. Or you could just free up a little space.
>>
>> If, on the other hand, Hudson isn't getting an accurate disk space
>> reading - that's cause for filing a bug.
>>
>> Joshua
>>
>>
>> On Tue, Nov 11, 2008 at 6:37 PM, Rich D
>> <[hidden email]> wrote:
>>>
>>> I'm having a similar issue running with;
>>>
>>> Hudson 1.260
>>> Java: 1.6.0_06b02
>>> Appserver: Tomcat 6.0.16
>>> OS: Linux version 2.6.18-53.1.21.el5 ([hidden email]) (gcc
>>> version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Tue May 20 09:34:18 EDT
>>> 2008
>>>
>>> df output;
>>> Filesystem            Size  Used Avail Use% Mounted on
>>> /dev/mapper/vg00-lvroot
>>>                      2.0G  306M  1.6G  17% /
>>> /dev/mapper/vg00-lvhome
>>>                      992M   46M  896M   5% /home
>>> /dev/mapper/vg00-lvopt
>>>                      496M  103M  368M  22% /opt
>>> /dev/mapper/vg00-lvusr
>>>                      3.9G  1.5G  2.2G  41% /usr
>>> /dev/mapper/vg00-lvtmp
>>>                      992M  198M  743M  22% /tmp
>>> /dev/mapper/vg00-lvvar
>>>                      2.0G  550M  1.4G  30% /var
>>> /dev/mapper/vg00-lvhudson
>>>                      3.0G  2.0G  901M  69% /export/hudson
>>> /dev/sda1              99M   14M   81M  15% /boot
>>> tmpfs                 125M     0  125M   0% /dev/shm
>>>
>>> Only resolution seems to be restarting tomcat. We have 13 projects
>>> running
>>> on this instance.
>>>
>>> Anyone find a resolution other than downgrading yet?
>>>
>>> Thanks in advance,
>>>
>>> .rich
>>>
>>>
>>> mjparme wrote:
>>>>
>>>> For the last few weeks Hudson will no longer build projects. It stacks
>>>> them all up in a Build Queue but they don't actually build. If I restart
>>>> Hudson all the projects in the build queue will build but then Hudson
>>>> will
>>>> no longer build anymore (until another restart).
>>>>
>>>> I first noticed this after upgrading to 1.249, I kept installing new
>>>> versions hoping it was just a short-lived bug that would be fixed. I
>>>> have
>>>> tried versions all the way up to the newest 1.255 release and experience
>>>> the same behavior. Presently I have "downgraded" all the way to 1.245
>>>> but
>>>> still experience the same behavior.
>>>>
>>>> Since past known good versions are experiencing the behavior I went
>>>> hunting around the system log and ran across this:
>>>>
>>>> Oct 14, 2008 10:35:48 AM hudson.node_monitors.DiskSpaceMonitor$1 monitor
>>>> WARNING: Making null offline temporarily due to the lack of disk space
>>>>
>>>>
>>>> All partitions have plenty of space.
>>>>
>>>> Running on:
>>>>
>>>> Linux linux120 2.4.21-40.ELsmp #1 SMP Thu Feb 2 22:22:39 EST 2006 i686
>>>> i686 i386 GNU/Linux
>>>>
>>>>
>>>> Anyone provide any insight? I have been using Hudson since 1.150 or so
>>>> and
>>>> this is the first issue we have had with it.
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Hudson-builds-hang-with-builds-in-queue-tp19981433p20450927.html
>>> Sent from the Hudson users mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> 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