[bareos-users] Storage daemon didn't accept Device "autochanger-0" command.

Sascha Bejer

2018-10-10 08:00:15 UTC

Hello Bareos Users,

Occasionally some jobs are failing on me with âStorage daemon didn't accept
Device "autochanger-0" commandâ.

Most times it recovers with later jobs. The schedule is a simple
full-differential cycle. Superloader3 Library, LTO.

09-Oct 21:00 bareos-dir JobId 385: Start Backup JobId 385,
Job=backup-serverXXX-fd.2018-10-09_21.00.00_33

09-Oct 21:00 bareos-dir JobId 385: Fatal error: Storage daemon didn't
accept Device "autochanger-0" command.

09-Oct 21:00 bareos-dir JobId 385: Error: Bareos bareos-dir 17.2.4
(21Sep17):

09-Oct 21:00 bareos-dir JobId 391: Start Backup JobId 391,
Job=backup-bareos-fd.2018-10-09_21.00.00_39

09-Oct 21:00 bareos-dir JobId 391: Using Device "tapedrive-0" to write.

09-Oct 21:00 bareos-sd JobId 391: 3304 Issuing autochanger "load slot 7,
drive 0" command.

09-Oct 21:01 bareos-sd JobId 391: 3305 Autochanger "load slot 7, drive 0",
status is OK.

Any tips where this may come from or how to debug?

It seems in Bacula they have a logic to show the cause directly with the
error at least for some failures.

Mit freundlichen GrÃŒÃen / with kind regards

Sascha

--
.
--
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 bareos-users+***@googlegroups.com.
To post to this group, send email to bareos-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.