[
https://issues.jenkins-ci.org/browse/JENKINS-12882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162028#comment-162028
]
Marc Günther edited comment on JENKINS-12882 at 4/25/12 4:40 PM:
-----------------------------------------------------------------
This is a duplicate of JENKINS-2548.
BTW, the problem is not that the {{temporaryOfflineCause}} is stored in the
{{config.xml}} (which is correct, as it should survive a restart), but that the
DiskSpaceMonitor never takes the slave back online.
was (Author: marc_guenther):
This is a duplicate of JENKINS-2548.
BTW, the problem is not that the temporaryOfflineCause is stored in the
config.xml (which is correct, as it should survive a restart), but that the
DiskSpaceMonitor never takes the slave back online.
> Master stays offline if once low disk space occured
> ---------------------------------------------------
>
> Key: JENKINS-12882
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12882
> Project: Jenkins
> Issue Type: Bug
> Components: master-slave
> Affects Versions: current
> Reporter: Jan Hoppe
> Priority: Blocker
>
> After deleting files or/and decreasing DiskSpace variables Jenkins master
> stays offline!
> The offline information is permanently stored in config.xml in jenkins
> install dir.
> It's like
> <temporaryOfflineCause
> class="hudson.node_monitors.DiskSpaceMonitorDescriptor$DiskSpace">
> <size>1011720192</size>
> <triggered>true</triggered>
> </temporaryOfflineCause>
> <disabledAdministrativeMonitors>
> <string>hudson.node_monitors.MonitorMarkedNodeOffline</string>
> </disabledAdministrativeMonitors>
> ...
> Delete those lines from the file an start jenkins again, everything is fine!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
