-
Task
-
Resolution: Unresolved
-
Minor
-
None
Hi
ThinBackup process in the Jenkins is failing to complete successfully.
Its taking too much to complete the backup . sometimes it will take exact time to complete .
drwxr-xr-x 3 jenkins jenkins 12K Feb 12 03:00 FULL-2024-02-12_03-00
Actually the jenkins took 3-4 hours to complete the backup process . Now its taking too much time
in logs i found
Cannot perform a backup. Please be sure jenkins/hudson has write privileges in the configured backup path '/jenkins-workspace/backupNow'.
[id=68015] WARNING o.j.h.p.t.ThinBackupPeriodicWork#backupNow: Do not wait until jenkins/hudson is idle to perform backup. This could cause corrupt backups.
root@server:/var/log/jenkins# cat jenkins.log | grep 'ThinBackup'
2024-02-12 11:00:09.380+0000 [id=68015] WARNING o.j.h.p.t.ThinBackupPeriodicWork#backupNow: Do not wait until jenkins/hudson is idle to perform backup. This could cause corrupt backups.
2024-02-12 11:01:09.379+0000 [id=159] WARNING o.j.h.p.t.h.m.AsyncPeriodicWork#doRun: ThinBackup Worker Thread thread is still running. Execution aborted.
2024-02-12 11:02:09.379+0000 [id=158] WARNING o.j.h.p.t.h.m.AsyncPeriodicWork#doRun: ThinBackup Worker Thread thread is still running. Execution aborted.
2024-02-12 11:03:09.379+0000 [id=46] WARNING o.j.h.p.t.h.m.AsyncPeriodicWork#doRun: ThinBackup Worker Thread thread is still running. Execution aborted.
Cannot perform a backup. Please be sure jenkins/hudson has write privileges in the configured backup path '/jenkins-workspace/backupNow'.
Note : Sometimes the Backup is successfully on time and sometimes it takes more than 12-20hrs to complete the backup .