-
Suggestion
-
Resolution: Answered
-
None
-
None
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
Sometimes Confluence can render a known error when he wants to save a backup and the backup path doesn't have permission or doesn't exist.
This is an example of stack trace today:
2012-10-18 08:53:14,998 ERROR [scheduler_Worker-5] [confluence.importexport.impl.BackupJob] executeJob Error while running the scheduled backup
java.io.IOException: No such file or directory
Confluence should place in the stack trace the exact path he's trying ton reach so the debug process would be way easier.
- relates to
-
CONFCLOUD-26943 Confluence backup path error message should inform the path in the stack trace
- Closed
[CONFSERVER-26943] Confluence backup path error message should inform the path in the stack trace
Workflow | Original: JAC Suggestion Workflow 4 [ 3566305 ] | New: JAC Suggestion Workflow 3 [ 4332291 ] |
Workflow | Original: JAC Suggestion Workflow 2 [ 3181727 ] | New: JAC Suggestion Workflow 4 [ 3566305 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Suggestion Workflow [ 3026576 ] | New: JAC Suggestion Workflow 2 [ 3181727 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2526605 ] | New: JAC Suggestion Workflow [ 3026576 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 2257019 ] | New: Confluence Workflow - Public Facing v4 [ 2526605 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 - TEMP [ 2189045 ] | New: Confluence Workflow - Public Facing v3 [ 2257019 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 1918879 ] | New: Confluence Workflow - Public Facing v3 - TEMP [ 2189045 ] |
Workflow | Original: Confluence Workflow - Public Facing v2 [ 1752623 ] | New: Confluence Workflow - Public Facing v3 [ 1918879 ] |
Description |
Original:
Sometimes Confluence can render a known error when he wants to save a backup and the backup path doesn't have permission or doesn't exist.
This is an example of stack trace today: {code} 2012-10-18 08:53:14,998 ERROR [scheduler_Worker-5] [confluence.importexport.impl.BackupJob] executeJob Error while running the scheduled backup java.io.IOException: No such file or directory {code} Confluence should place in the stack trace the exact path he's trying ton reach so the debug process would be way easier. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-26943]. {panel} Sometimes Confluence can render a known error when he wants to save a backup and the backup path doesn't have permission or doesn't exist. This is an example of stack trace today: {code} 2012-10-18 08:53:14,998 ERROR [scheduler_Worker-5] [confluence.importexport.impl.BackupJob] executeJob Error while running the scheduled backup java.io.IOException: No such file or directory {code} Confluence should place in the stack trace the exact path he's trying ton reach so the debug process would be way easier. |
it has been resolved but i've faced this issue(actually https://jira.atlassian.com/browse/CONFCLOUD-28575) and comments on this issue have saved me.
exception callstack didn't show any clue and even backup admin.
Configured backup path on backup administration page is normal but actual confluence setting in db is wrong.
thanks @mym@ciklum.com, @Mark Symons