Hi Thomas,

I'm still experiencing this issue with Jenkins 1.511 and ThinBackup 1.7.2

logs:

==> /var/log/jenkins/jenkins.log <==
Jul 17, 2013 12:42:02 PM org.jvnet.hudson.plugins.thinbackup.ThinBackupMgmtLink doBackupManual
INFO: Starting manual backup.
Jul 17, 2013 12:42:03 PM org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup <init>
INFO: No previous full backup found, thus creating one.
Jul 17, 2013 12:42:03 PM org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup backupJobsDirectory
INFO: Found 53 jobs to back up.
Jul 17, 2013 12:42:03 PM org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork backupNow
SEVERE: Cannot perform a backup. Please be sure jenkins/hudson has write privileges in the configured backup path '/var/lib/jenkins/backups'.
java.io.FileNotFoundException: Source '/var/lib/jenkins/jobs/nationalvoices-INTEGRATION_LAMORAK/builds/lastUnstableBuild' does not exist
        at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:866)
        at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:814)
        at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupBuildFiles(HudsonBackup.java:302)
        at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupBuildsFor(HudsonBackup.java:270)
        at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJob(HudsonBackup.java:208)
        at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobsDirectory(HudsonBackup.java:196)
        at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobs(HudsonBackup.java:175)
        at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backup(HudsonBackup.java:142)
        at org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork.backupNow(ThinBackupPeriodicWork.java:87)
        at org.jvnet.hudson.plugins.thinbackup.ThinBackupMgmtLink$1.execute(ThinBackupMgmtLink.java:76)
        at org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:54)
        at java.lang.Thread.run(Thread.java:722)

I think the write privileges error is a red herring because jenkins does have the correct privs access to the dir.

Cheers
Ben

Change By: Ben Poole (17/Jul/13 11:44 AM)
Resolution: Fixed
Status: Resolved Reopened
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/groups/opt_out.
 
 

Reply via email to