Re: [Bacula-users] SD stalled?!
Mandi! Josh Fisher In chel di` si favelave... > Try checking vchanger functions directly. Josh, sorry. Bacula and vchanger works as expected. dir and SD communicate correctly, and sd (seems to) work correctly with vchanger. The trouble arose 'sometime', typically when the remote branch user does not change the RDX cassette on scheduled time, or after some weeks of usage of the system, and appear 'spot', sometime on one site, sometime on other. Because i've setup a script that manage and eject the cassette, i'm simply thinking of restarting bacula-sd when there's a cassette change. But this seems strange to me... probably there's something i've missed... For example, what mean that a volume is 'reserved'?! Three's some way to 'unreserve' a volume? Thanks. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] SD stalled?!
On 12/19/22 04:55, Marco Gaiarin wrote: Mandi! Josh Fisher In chel di` si favelave... Does the firewall on sdpve2.sd.lnf.it allow connections on TCP 9103? Is there an SD process on sdpve2.sd.lnf.it listening on port 9103? You can try to 'telnet sdpve2.sd.lnf.it 9103' command from the machine that bacula-dir runs on to see if it is connecting. Check that the SD password set in bacul-dir.conf matches the one in bacula-sd.conf. Something is preventing bacula-dir from connecting to bacula-sd. Comunication between dir and SD works as expected, there's no firewall or other connection troubles in between. I can send mount or umount command, simply they are ignored: Try checking vchanger functions directly. Use the -u and -g flags to run vchanger as the same user and group that bacula-sd runs as. As root, try: vchanger -u bacula -g tape /path/to/vchanger.conf load 5 /dev/null 0 The 3rd positional argument is the slot number, the 5th the drive number. It could be a permission issue. When vchanger is invoked by bacula-sd, it will run as the same user and group as bacula-sd. So the vchanger work directory needs to be writable by that user. Also, the filesystem that the backup is being written to needs to be writable by the user that bacula-sd runs as. Device status: Autochanger "RDXAutochanger" with devices: "RDXStorage0" (/var/spool/vchanger/VIPVE2RDX/0) "RDXStorage1" (/var/spool/vchanger/VIPVE2RDX/1) "RDXStorage2" (/var/spool/vchanger/VIPVE2RDX/2) Device File: "RDXStorage0" (/var/spool/vchanger/VIPVE2RDX/0) is not open. Device is being initialized. Drive 0 is not loaded. == Device File: "RDXStorage1" (/var/spool/vchanger/VIPVE2RDX/1) is not open. Slot 6 was last loaded in drive 1. == Device File: "RDXStorage2" (/var/spool/vchanger/VIPVE2RDX/2) is not open. Drive 2 is not loaded. == Used Volume status: Reserved volume: VIPVE2RDX_0002_0003 on File device "RDXStorage0" (/var/spool/vchanger/VIPVE2RDX/0) Reader=0 writers=0 reserves=2 volinuse=1 worm=0 *umount storage=VIPVE2RDX Automatically selected Catalog: BaculaLNF Using Catalog "BaculaLNF" Enter autochanger drive[0]: 3901 Device ""RDXStorage0" (/var/spool/vchanger/VIPVE2RDX/0)" is already unmounted. Seems that simply the SD is on a 'unknown' state: they pretend to have a volume 'reserved' (what mean?) and do nothing. After a restart of the SD, current (stalling) job got canceled, but if i rerun it, thay work as expected... ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] SD stalled?!
Mandi! Josh Fisher In chel di` si favelave... > Does the firewall on sdpve2.sd.lnf.it allow connections on TCP 9103? Is > there an SD process on sdpve2.sd.lnf.it listening on port 9103? You can try > to 'telnet sdpve2.sd.lnf.it 9103' command from the machine that bacula-dir > runs on to see if it is connecting. Check that the SD password set in > bacul-dir.conf matches the one in bacula-sd.conf. Something is preventing > bacula-dir from connecting to bacula-sd. Comunication between dir and SD works as expected, there's no firewall or other connection troubles in between. I can send mount or umount command, simply they are ignored: Device status: Autochanger "RDXAutochanger" with devices: "RDXStorage0" (/var/spool/vchanger/VIPVE2RDX/0) "RDXStorage1" (/var/spool/vchanger/VIPVE2RDX/1) "RDXStorage2" (/var/spool/vchanger/VIPVE2RDX/2) Device File: "RDXStorage0" (/var/spool/vchanger/VIPVE2RDX/0) is not open. Device is being initialized. Drive 0 is not loaded. == Device File: "RDXStorage1" (/var/spool/vchanger/VIPVE2RDX/1) is not open. Slot 6 was last loaded in drive 1. == Device File: "RDXStorage2" (/var/spool/vchanger/VIPVE2RDX/2) is not open. Drive 2 is not loaded. == Used Volume status: Reserved volume: VIPVE2RDX_0002_0003 on File device "RDXStorage0" (/var/spool/vchanger/VIPVE2RDX/0) Reader=0 writers=0 reserves=2 volinuse=1 worm=0 *umount storage=VIPVE2RDX Automatically selected Catalog: BaculaLNF Using Catalog "BaculaLNF" Enter autochanger drive[0]: 3901 Device ""RDXStorage0" (/var/spool/vchanger/VIPVE2RDX/0)" is already unmounted. Seems that simply the SD is on a 'unknown' state: they pretend to have a volume 'reserved' (what mean?) and do nothing. After a restart of the SD, current (stalling) job got canceled, but if i rerun it, thay work as expected... ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
