On 11/15/16 10:07, Douglas K. Rand wrote: > On 10/13/16 03:50, Jörg Steffens wrote: >> Am 12.10.2016 um 17:53 schrieb Douglas K. Rand: >> [...] >>>> it seams, you are not the only one having this problem: >>>> https://bugs.bareos.org/view.php?id=691 >>> >>> Just a "me too": I experienced the same problem as that bug last week. >>> Re-running the job worked fine, and have not seen the error since. >>> Bareos 15.2.2. >> >> Have anybody seen this error using newer versions then bareos-15.2.2? >> Or even better, have someone had this problem and it disappear with >> newer versions? > > I'm seeing the same problem with 16.2.4. (A few newlines added to the > error.) > > 11-Nov 19:30 bareos-sd JobId 3371: > Warning: mount.c:248 Open device "disk-2" > (/local-project/tmp/bareos/backups) Volume "" failed: > ERR=Could not open file device "disk-2" > (/local-project/tmp/bareos/backups). No Volume name given. > > It seems fairly random. Some backups I'll have it happen to 8-10 jobs in > the backup, other times just 1-3. Sometimes the backups work perfectly.
A mildly brute-force work around that at least gets the backups to run is to add something like this to your job definitions: reschedule interval = 10 minutes reschedule on error = yes reschedule times = 3 Which re-tries failed backups 3 times pausing 10 minutes between each re-try. This is working for me in that the backups that fail due to not being able to find a volume named "" get re-started and work just fine the second time. Thanks to Daniel Andratschke for the inadvertent tip on Reschedule On Error. -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
