I've reached my first tape change on my autochangers, yeah!
But... 24-Jan 17:22 cnpve3-sd JobId 16234: [SI0202] End of Volume "AAJ661L9" at 333:49131 on device "LTO9Storage0" (/dev/nst0). Write of 524288 bytes got -1. 24-Jan 17:22 cnpve3-sd JobId 16234: Re-read of last block succeeded. 24-Jan 17:22 cnpve3-sd JobId 16234: End of medium on Volume "AAJ661L9" Bytes=17,846,022,566,912 Blocks=34,038,588 at 24-Jan-2024 17:22. 24-Jan 17:22 cnpve3-sd JobId 16234: 3307 Issuing autochanger "unload Volume AAJ661L9, Slot 2, Drive 0" command. 24-Jan 17:28 cnpve3-sd JobId 16234: 3995 Bad autochanger "unload Volume AAJ661L9, Slot 2, Drive 0": ERR=Child died from signal 15: Termination Results=Program killed by Bacula (timeout) 24-Jan 17:28 cnpve3-sd JobId 16234: 3304 Issuing autochanger "load Volume AAJ660L9, Slot 1, Drive 0" command. 24-Jan 17:29 cnpve3-sd JobId 16234: 3305 Autochanger "load Volume AAJ660L9, Slot 1, Drive 0", status is OK. So, unload timeout, but subsequent load command works as expected (and backup are continuing...). I can safely ignore this? Better tackle with tiemout parameters on /etc/bacula/scripts/mtx-changer.conf script? Thanks. -- Ci vuole sempre qualcuno da odiare per sentirsi giustificati nella propria miseria. (Umberto Eco) _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users