We used Apache Tomcat 6.0 to run the Hudson server. We also run artifactory for local maven2 repository on the same application server.
These few days the problem could be temporarily fixed by restarting the application server. I did it several times, but seems this problem is a chronic problem that keeps recurring every 10-20 builds.
This morning I figured out something new, Hudson seems to complain that the executor was frozen (showing that both executors status is "Offline"). Then I take a look, I discovered that there is a configuration for the executor when you click on the [Build executor status] positioned on the bottom of the left menu.
From here I can see the problem clearly:
Hudson displays the name of the executor nodes (as it supports build on multiple nodes), the response time for each node, free swap space and free disk space and some other stuff.
On my machine Hudson showed a warning that the disk space is low (less than 1GB). So this is the reason why Hudson froze the executors. It prevents itself to bring down the machine buy hogging the disk space.
Then I try to find a solution for this problem. I know that on our Windows server Hudson is running as Default User on the user's home. So, there is high probability to fix this problem by moving Hudson to other user of moving this user's space to location other than C: drive.
The simplest working solution to this problem turned to be:
- specifying Hudson home (other than the default $USER_HOME/.hudson) on the Apache Tomcat service configuration
- specifying Artifactory home (other than the default $USER_HOME/.artifactory) on the Apache Tomcat service configuration
- copy the content of $USER_HOME/.hudson to a new hudson home
- copy the content of $USER_HOME/.artifactory to a new artifactory home
- restart Apache Tomcat service
No comments:
Post a Comment