[JIRA] (JENKINS-16319) Failure to delete old config files during rekeying on Windows

Tue, 15 Jan 2013 05:43:01 -0800

I am seeing an even bigger problem with this issue. I have Jenkins running on several 2k3 servers as window services. After my original upgrade to 1.499 (from 1.489), I was unable to get jenkins to recognize/start any of the slaves which all where running as windows services. There is a bug report already for this issue: https://issues.jenkins-ci.org/browse/JENKINS-16346.

I had unfortunately started the re-keying process already when it became necessary to revert to the older version of Jenkins to get things back up and running. The revert worked fine, and I was able to trouble shoot the issue on a different machine. The answer seemed to be to give Anonymous users conenction capability in the Global Security settings in the Project-based Matrix Authorization Strategy for a system using AD.

I re-upgraded my main system to 1.499, applied the security setting, got my slaves running, triggered the re-keying process, and was on my marry way. However, once that completed, any attempt to view the log created results in Jenkins crashing and the windows service it runs on being terminated. I manually looked at the log files and see many of the failed conversion steps as mentioned in this bug report.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to