|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Back up the files identity.key and/or identity.key.enc in the Jenkins home directory on the master node, and then delete them. Restart.
From the documentation, it doesn't look like it's really used that much:
https://wiki.jenkins-ci.org/display/JENKINS/Instance+Identity
Still, make sure that e.g. SCM credentials (or any other passwords stored in Jenkins) still work with the newly generated instance identity.
If you could search older jenkins.logs for errors related to instance_identity to help identify the cause of the broken key file that would be great.
Related: https://groups.google.com/d/msg/jenkinsci-users/q9C1m8O0ruE/lrlSllwH-T8J