Why is Jenkins restarting jobs on its own

[Mark Sinclair]

I'm running version 1.594

Jenkins has done this 2 times now.  A job is running for a long time (2 days) and not producing much output, but the job is definitely still running.  At some point, Jenkins starts the job again.  Jenkins does not increment the build number, it overwrites the console log with the new job.

More details:
All jobs are running with master/slave setup.
Build timeout plugin is NOT installed.
Concurrent builds are disabled
The job is configured to run daily, so the job is sitting in the build queue when this problem occurs.
Kicking off the job again actually causes the running job to finish, as some of its files are overwritten.  It finishes in error and Jenkins sends email notification for the first job.
When the job completes for a second time (successfully), Jenkins sends another mail.  The results from the first run are overwritten.

Looking through the jenkins logs, I don't see any indication as to why this job started again.  It just says Job started by timer on the build page.

Here's what I found that was somewhat interesting.  I see this for many (all?) builds though.

Jan 21, 2015 11:37:23 AM jenkins.diagnostics.ooom.Problem$Inspector scan

WARNING: Failed to inspect /XXX/jenkins/home/jobs/XXXXX/builds/2015-01-19_10-41-57: /XXXX/jenkins/home/jobs/XXXXX/builds/2015-01-19_10-41-57/build.xml doesn't exist

Another thing to note is that I am repeatedly seeing out-of-order build warnings.  I usually resolve them by letting Jenkins sweep it into a backup folder.  Again not sure if it's related.  I thought this may be a system time issue from master/slave?

Thanks very much - I can provide more info if anyone is able to help.

Mark

[Mark Sinclair]

Did some further research and it's possible these issues are related to:
JENKINS-24380

This was recently released in 1.597, so I'm giving it a shot.  The changelog and associated wiki have some good details.