Opened 10 years ago

Last modified 10 years ago

#48 new defect

Locations that don't exist on first run are never tried again

Reported by: chris Owned by: chris
Priority: normal Milestone: 0.12
Component: bbackupd Version: 0.11rc1
Keywords: backup location not available retry backup-ok notification Cc: [email protected]

Description (last modified by chris)

Torsten reports:

If i have a location not existing locally and not existing on the store but activated as a location in bbackupd.conf. With this configuration box backup throws this errors on start.

ERROR: Failed to stat file: '/test-': No such file or directory (2)
WARNING: Exception thrown: CommonException(OSFileError) at BackupClientFileAttributes.cpp(309)
ERROR: Failed to get attributes for path '/test-', skipping location 'test-'
WARNING: Failed to access directory: /test- No such file or directory
NOTICE: About to notify administrator about event backup-ok, running
script '/root/exobackup/boxbackup/ backup-ok'
  • this errors are only printed once. The next backup runs do not consider to backup this location. That is not good for me. I have locations on remote storage mounted via samba. So only one mount error and i will never again be notified that this location is not backed up.
  • is this the right behavior, that backup-ok is called even though there was this error?

I attached a little patch that makes box backup to retry this location. But i dont think that this is a clean way.

Attachments (1)

bb_retry_dir_not_existing.diff (417 bytes) - added by chris 10 years ago.

Download all attachments as: .zip

Change History (2)

Changed 10 years ago by chris

comment:1 Changed 10 years ago by chris

Description: modified (diff)
Note: See TracTickets for help on using tickets.