Re: [Bacula-users] Can't see director start up errors with systemd

[Kern Sibbald]

Title: myEMAILsignature

  
  
Yes, I find systemd rather non-satisfactory.  One thing is if
  there is no error printed, it usually means everything went well. 
  A "service bacula-dir status" should tell you if it is running or
  not.  Otherwise service bacula-dir start output gives you two
  commands to use to get more detailed information.  The one I use
  most often is 

journalctl -xe 
Best regards,
Kern


On 05/14/2018 11:18 PM, Tom Plancon
  wrote:


  
  Hello,
  I'm changing some configurations in my bacula-dir.conf on a
CentOS 7 server. Unfortunately it uses the new-fangled systemd
to stop and start the director. I don't get any reports as to
whether it starts or not after "systemctl start bacula-dir". In
the old days, if the director failed to start because of a
configuration error, I would get a fairly comprehensible
explanation why, down to the line number! I don see anything in
/var/log/messages. Any idea where to look for those good old
explanatory errors to see why my director refuses to start?
  Thanks much!
  
  -- 


 Thomas Plancon
CAD/IT MANAGER

E:  tplan...@bkaarchs.com
W: www.bkaarchitects.com


   

  
  
  
  
  --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
  
  
  
  ___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users



  


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 7.4, 7, CentOS 7, and systemd - a cautionary tale

[Jeffrey R. Lang]

Thomas

  I believe that you should have used “restart” instead of “start” in your 
systemctl commands.   Once you make a change in your configs you need to 
totally restart the director, which “systemnctl restart bacula-dir” would not.  
 The start only starts the daemon if it is not already running.

You could have used, bconsole and just done a reload command.  This this does 
the same as shutting down and restarting the daemon.



From: Tom Plancon 
Sent: Tuesday, May 15, 2018 4:09 PM
To: Bacula-users@lists.sourceforge.net
Subject: [Bacula-users] Bacula 7.4, 7, CentOS 7, and systemd - a cautionary tale


Hi folks,

Just spent several frustrating hours trying to get some special backup configs 
into my bacula-dir.conf file. I'd shut down the Director, "sytemctl stop 
bacula-dir", edit the file, then start the Director, "systemctl start 
bacula-dir" and nothing. Did a "bacula-dir -t" and found some syntax errors, 
fixed those and then "systemctl start bacula-dir" and again - nothing. Tried 
"bacula-dir -t", no errors reported! Edited the conf file and commented out all 
my changes, then "systemctl start bacula-dir" and it worked. But I did not have 
the config I wanted.

So piece by piece I un-commented the lines I wanted, did a "bacula-dir -t", no 
errors reported. Tried to start, "systemctl start bacula-dir", nothing. Went 
back and forth this way for a long time finally commenting out again back to 
original file, then "bacula-dir -t", no errors reported. Tried to start, 
"systemctl start bacula-dir", nothing!

Then I rebooted the whole server - when it came up the Director was running!!! 
Stopped the Director, tried adding back in some of the config lines I wanted, 
did a "bacula-dir -t", no errors reported. Tried to start, "systemctl start 
bacula-dir", nothing! Again I rebooted - Director was running with my special 
config!!!

Not sure what was going on, but bottom line - don't trust systemd!
--
Thomas Plancon
CAD/IT MANAGER

E:  tplan...@bkaarchs.com
W: www.bkaarchitects.com

[BKA/LOGO]
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 7.4, 7, CentOS 7, and systemd - a cautionary tale

[Dimitri Maziuk]

On 05/15/2018 05:48 PM, Dimitri Maziuk wrote:
>  -- and that's why systemd's stated goal 

is

> faster boot.


-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu



signature.asc
Description: OpenPGP digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 7.4, 7, CentOS 7, and systemd - a cautionary tale

[Dimitri Maziuk]

On 05/15/2018 04:09 PM, Tom Plancon wrote:

> Not sure what was going on, but bottom line - don't trust systemd!

Read up on shadow mounts and weep. Basically, you now have to reboot
after editing /etc/fstab.
 -- and that's why systemd's stated goal faster boot.
-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu



signature.asc
Description: OpenPGP digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 7.4, 7, CentOS 7, and systemd - a cautionary tale

[Alan Brown]

hint: groups in the startup scripts



On 15/05/18 22:09, Tom Plancon wrote:
>
> Hi folks,
>
> Just spent several frustrating hours trying to get some special backup
> configs into my bacula-dir.conf file. I'd shut down the Director,
> "sytemctl stop bacula-dir", edit the file, then start the Director,
> "systemctl start bacula-dir" and nothing. Did a "bacula-dir -t" and
> found some syntax errors, fixed those and then "systemctl start
> bacula-dir" and again - nothing. Tried "bacula-dir -t", no errors
> reported! Edited the conf file and commented out all my changes, then
> "systemctl start bacula-dir" and it worked. But I did not have the
> config I wanted.
>
> So piece by piece I un-commented the lines I wanted, did a "bacula-dir
> -t", no errors reported. Tried to start, "systemctl start bacula-dir",
> nothing. Went back and forth this way for a long time finally
> commenting out again back to original file, then "bacula-dir -t", no
> errors reported. Tried to start, "systemctl start bacula-dir", nothing!
>
> Then I rebooted the whole server - when it came up the Director was
> running!!! Stopped the Director, tried adding back in some of the
> config lines I wanted, did a "bacula-dir -t", no errors reported.
> Tried to start, "systemctl start bacula-dir", nothing! Again I
> rebooted - Director was running with my special config!!!
>
> Not sure what was going on, but bottom line - don't trust systemd!
>
> -- 
> myEMAILsignature Thomas Plancon
> CAD/IT MANAGER
>
> E:  tplan...@bkaarchs.com
> W: www.bkaarchitects.com 
>
> BKA/LOGO
>
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Bacula 7.4, 7, CentOS 7, and systemd - a cautionary tale

[Tom Plancon]

Hi folks,

Just spent several frustrating hours trying to get some special backup 
configs into my bacula-dir.conf file. I'd shut down the Director, 
"sytemctl stop bacula-dir", edit the file, then start the Director, 
"systemctl start bacula-dir" and nothing. Did a "bacula-dir -t" and 
found some syntax errors, fixed those and then "systemctl start 
bacula-dir" and again - nothing. Tried "bacula-dir -t", no errors 
reported! Edited the conf file and commented out all my changes, then 
"systemctl start bacula-dir" and it worked. But I did not have the 
config I wanted.


So piece by piece I un-commented the lines I wanted, did a "bacula-dir 
-t", no errors reported. Tried to start, "systemctl start bacula-dir", 
nothing. Went back and forth this way for a long time finally commenting 
out again back to original file, then "bacula-dir -t", no errors 
reported. Tried to start, "systemctl start bacula-dir", nothing!


Then I rebooted the whole server - when it came up the Director was 
running!!! Stopped the Director, tried adding back in some of the config 
lines I wanted, did a "bacula-dir -t", no errors reported. Tried to 
start, "systemctl start bacula-dir", nothing! Again I rebooted - 
Director was running with my special config!!!


Not sure what was going on, but bottom line - don't trust systemd!

--
myEMAILsignature Thomas Plancon
CAD/IT MANAGER

E:  tplan...@bkaarchs.com
W: www.bkaarchitects.com 

BKA/LOGO

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Baculum - Grouping error: 7 ERROR: column "media.volumename" ...

[Marcin Haba]

Hello Rasmus,

Thanks for reporting this problem.

It is a bug that will be fixed in the next Baculum version.

In attachment I added patch that fixes it.

Best regards.
Marcin Haba (gani)

On 14 May 2018 at 15:07, Rasmus Linden  wrote:
> Hey All!
> Im a long time bacula user, and finally got myself updated to v9.0.7, and i
> have run into a issue with baculum i just cannot figure out how to solve.
> I have everything working, except restoring using baculm. -bat and bconsole
> works with no issues.
>
> When i have chosen files to restore, and click next, i get a sql error :
>
> Baculum problem
> Error 100 - Problem with connection to remote host. cURL error 0: .
>
> SQLSTATE[42803]: Grouping error: 7 ERROR: column "media.volumename" must
> appear in the GROUP BY clause or be used in an aggregate function LINE 2:
> SELECT VolumeName, InChanger, MIN(FirstIndex) as first_in... ^
>
>
> 0083: $connection = VolumeRecord::finder()->getDbConnection();
> 0084: $connection->setActive(true);
> 0085: $sql = sprintf('SELECT first_index, last_index, VolumeName AS
> volname, InChanger AS inchanger FROM (
> 0086:  SELECT VolumeName, InChanger, MIN(FirstIndex) as first_index,
> MAX(LastIndex) as last_index
> 0087:  FROM JobMedia JOIN Media ON (JobMedia.MediaId =
> Media.MediaId)
> 0088:  WHERE JobId = %d GROUP BY (VolumeName, InChanger)
> 0089: ) AS gv, File
> 0090:  WHERE FileIndex >= first_index
> 0091:  AND FileIndex <= last_index
> 0092:  AND File.FileId = %d', $jobid, $fileid);
> 0093: $pdo = $connection->getPdoInstance();
> 0094: $result = $pdo->query($sql);
> 0095: $ret = $result->fetchAll();
> 0096: $pdo = null;
> 0097: $volumes = array();
> 0098: if (is_array($ret)) {
> 0099: for ($i = 0; $i < count($ret); $i  ) {
> 0100: $volumes[] = array(
> 0101: 'first_index' => $ret[$i]['first_index'],
> 0102: 'last_index' => $ret[$i]['last_index'],
> 0103: 'volume' => $ret[$i]['volname'],
> 0104: 'inchanger' => $ret[$i]['inchanger']
> 0105: );
> 0106: }
>
>
> I started out with a quite large MySql database, but for troubleshooting, i
> am running a clean posgress database.
> Os is CentOS Linux release 7.5.1804 (Core)
>
> Anybody got any good ideas ??
>
> All the best
>
> Ras
>
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>



-- 
"Greater love hath no man than this, that a man lay down his life for
his friends." Jesus Christ

"Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie
za przyjaciół swoich." Jezus Chrystus
diff --git a/gui/baculum/protected/API/Class/VolumeManager.php b/gui/baculum/protected/API/Class/VolumeManager.php
index 35265beb97..48b25d74d2 100644
--- a/gui/baculum/protected/API/Class/VolumeManager.php
+++ b/gui/baculum/protected/API/Class/VolumeManager.php
@@ -85,7 +85,7 @@ class VolumeManager extends APIModule {
 		$sql = sprintf('SELECT first_index, last_index, VolumeName AS volname, InChanger AS inchanger FROM (
 		 SELECT VolumeName, InChanger, MIN(FirstIndex) as first_index, MAX(LastIndex) as last_index
 		 FROM JobMedia JOIN Media ON (JobMedia.MediaId = Media.MediaId)
-		 WHERE JobId = %d GROUP BY (VolumeName, InChanger)
+		 WHERE JobId = %d GROUP BY VolumeName, InChanger
 		) AS gv, File
 		 WHERE FileIndex >= first_index
 		 AND FileIndex <= last_index
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Can't see director start up errors with systemd

[Tom Plancon]

Thing,

Thanks very much! This is exactly what I need! BTW, I am running Bacula 
7 on CentOS 7.


myEMAILsignature Thomas Plancon
CAD/IT MANAGER

E:  tplan...@bkaarchs.com
W: www.bkaarchitects.com 

BKA/LOGO

On 5/14/2018 6:14 PM, Thing wrote:

You can run a config check on the conf file, please do so.

/
/bacula-dir -tc /etc/bacula/bacula-dir.conf/
/(or similar)/
/

systemctl status bacula-director should tell you its status.  
Otherwise if you get no return from,


systemctl start bacula.director

that should mean its started OK.

From memory the bacula on Centos 7.4 is version 5 you should be able 
to run version 7 instead.


/http://www.chriscouture.com/installing-bacula-webmin-bacula-webon-centos-7//

/
/

/For my Centos 7 clients talking to my Debian 9 Bacula 7 director this 
is what I did, a full setup should be similar./


//

 *

//vi///*/etc/yum.repos.d/epel-bacula7.repo*/

/
 o

/Add the following to a new repo file,/

/

/



/[epel-bacula7]/

/name=Bacula backports from rawhide/
/baseurl=http://repos.fedorapeople.org/repos/slaanesh/bacula7/epel-$releasever/$basearch//
/enabled=1/
/skip_if_unavailable=1/
/gpgkey=http://repos.fedorapeople.org/repos/slaanesh/bacula7/RPM-GPG-KEY-slaanesh/
/gpgcheck=1/

/[epel-bacula7-source]/
/name=Bacula backports from rawhide - Source/
/baseurl=http://repos.fedorapeople.org/repos/slaanesh/bacula7/epel-$releasever/SRPMS/
/enabled=0/
/skip_if_unavailable=1/
/gpgkey=http://repos.fedorapeople.org/repos/slaanesh/bacula7/RPM-GPG-KEY-slaanesh/
/gpgcheck=1/



 *

/yum repolist/

 *

/yum list bacula*/

 o

/check the output is listed as 7.0X/



root@glustep1 ~]# yum list bacula*

Loaded plugins: fastestmirror, langpacks

Loading mirror speeds from cached hostfile

* base: ucmirror.canterbury.ac.nz 

* epel: epel.mirror.digitalpacific.com.au 



* extras: ucmirror.canterbury.ac.nz 

* updates: centos.mirror.digitalpacific.com.au 



Available Packages

bacula-client.x86_64 7.0.5-7.el7 epel-bacula7

bacula-common.x86_64 7.0.5-7.el7 epel-bacula7

bacula-console.x86_64 7.0.5-7.el7 epel-bacula7

bacula-console-bat.x86_64 7.0.5-7.el7 epel-bacula7

bacula-devel.i686 5.2.13-23.1.el7 base

bacula-devel.x86_64 7.0.5-7.el7 epel-bacula7

bacula-director.x86_64 7.0.5-7.el7 epel-bacula7

bacula-docs.noarch 7.0.5-1.el7 epel-bacula7

bacula-libs.x86_64 7.0.5-7.el7 epel-bacula7

bacula-libs-sql.x86_64 7.0.5-7.el7 epel-bacula7

bacula-logwatch.noarch 7.0.5-7.el7 epel-bacula7

bacula-storage.x86_64 7.0.5-7.el7 epel-bacula7

bacula-traymonitor.x86_64 7.0.5-7.el7 epel-bacula7



 *

/yum -y install bacula-client/

 *

/set firewall to allow 9102 in/

 o
/firewall-cmd --add-port=9102/tcp --permanent/
 o
/firewall-cmd --reload/
 *
/Copy a bacula-fd.conf over and/
 o
///edit name and IP/
 o
/Change working directories as Centos 7 differs to Debian,/

///#WorkingDirectory = /var/lib/bacula/
///WorkingDirectory = /var/spool/bacula/
///#Pid Directory = /run/bacula/
///Pid Directory = /var/run/

 *
/check all Ok with,/

/bacula-fd -tc /etc/bacula/bacula-fd.conf/

 *
/If need be stop the client and delete the pid and state file from
the 2 directories above and start/
 *
/Run bconsole on the bacula server and status → client → clientname
to check all is OK./

/Restoring/

 *
/mkdir -p /bacula/restore/
 *
/chown -R bacula: /bacula/
 *
/Selinux policy will interfere with the restore./
 o
/setenforce 0/
 o
/setenforce 1 when restore is complete/


/

/(if anyone has a better way please let me know)/

/
/

/So I am only installing the client /


On 15 May 2018 at 09:18, Tom Plancon > wrote:


Hello,

I'm changing some configurations in my bacula-dir.conf on a CentOS
7 server. Unfortunately it uses the new-fangled systemd to stop
and start the director. I don't get any reports as to whether it
starts or not after "systemctl start bacula-dir". In the old days,
if the director failed to start because of a configuration error,
I would get a fairly comprehensible explanation why, down to the
line number! I don see anything in /var/log/messages. Any idea
where to look for those good old explanatory errors to see why my
director refuses to start?

Thanks much!

-- 
Thomas Plancon

CAD/IT MANAGER

E: tplan...@bkaarchs.com 
W: www.bkaarchitects.com 

BKA/LOGO



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
  

Re: [Bacula-users] Bacula director crashes while labelling tapes with their barcodes.

[Gary R. Schmidt]

On 15/05/2018 22:01, Charles Nadeau wrote:

Hello!

I just got a used Dell TL2000 tape library to use with Bacula (9.0.4 for 
the director on Ubuntu 16.04, 9.0.6 for the storage director on Ubuntu 
18.04).


I tested it with btape and mtx-changer and it passes all tests (strongly 
inspired by Dan Langille's 
https://dan.langille.org/2016/02/04/dell-tl4000-tape-library-running-btape-and-configuring-baculas-mtx-changer/).
Once defined/integrated in Bacula, I can't label the tapes, 
bacula-director crashes.


Here is what the session is at bconsole:


[SNIP]


Could anybody tell me where the problem could be? Could it be about the 
versions mismatch? I saw on the list that Dan Langille wrote 
(https://sourceforge.net/p/bacula/mailman/message/36187800/): 
"bacula-dir = bacula-sd >= bacula-fd" How close should the versions of 
-dir and -sd be? In my case they are 0.0.2 apart.


It's =.

Not ~, or ~=, or "just a smidge like".

Dir and SD have to be the same version.

I repeat, DIR AND SD HAVE TO BE THE SAME VERSION.

Got it?

That's what "=" means.  (Except when it mean "assignment", which makes 
no sense in this context.)


Cheers,
GaryB-)

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Bacula director crashes while labelling tapes with their barcodes.

[Charles Nadeau]

Hello!

I just got a used Dell TL2000 tape library to use with Bacula (9.0.4 for
the director on Ubuntu 16.04, 9.0.6 for the storage director on Ubuntu
18.04).

I tested it with btape and mtx-changer and it passes all tests (strongly
inspired by Dan Langille's
https://dan.langille.org/2016/02/04/dell-tl4000-tape-library-running-btape-and-configuring-baculas-mtx-changer/
).
Once defined/integrated in Bacula, I can't label the tapes, bacula-director
crashes.

Here is what the session is at bconsole:

charles@bigzilla:/mnt/data/toburn/archive$ bconsole
Connecting to Director 192.168.0.53:9101
1000 OK: 103 bigzilla-dir Version: 9.0.4 (06 September 2017)
Enter a period to cancel a command.
*label barcodes
Automatically selected Catalog: MyCatalog
Using Catalog "MyCatalog"
The defined Storage resources are:
 1: File3
 2: TL2000
Select Storage resource (1-2): 2
Connecting to Storage daemon TL2000 at 192.168.0.17:9103 ...
Connecting to Storage daemon TL2000 at 192.168.0.17:9103 ...
3306 Issuing autochanger "slots" command.
Device "Autochanger" has 24 slots.
Connecting to Storage daemon TL2000 at 192.168.0.17:9103 ...
3301 Issuing autochanger "loaded? drive 0" command.
3302 Autochanger "loaded? drive 0", result: nothing loaded.
3306 Issuing autochanger "list" command.
The following Volumes will be labeled:
Slot  Volume
==
   1  000151L3
   2  000133L3
   3  000128L3
   4  000126L3
   5  000122L3
   6  000125L3
   7  000124L3
   8  000137L3
   9  000129L3
  10  000134L3
  11  000131L3
  12  000140L3
  14  000153L3
  15  000152L3
  16  000132L3
  17  000121L3
  18  000127L3
  19  000130L3
Do you want to label these Volumes? (yes|no): yes
Defined Pools:
 1: Default
 2: Default3
 3: DefaultTape
 4: Differential-File3
 5: Differential-Tape
 6: File
 7: Full-File3
 8: Full-Tape
 9: Incremental-File3
10: Incremental-Tape
11: Photo-File
12: Scratch
Select the Pool (1-12): 12


Here are some details of my configuration:

charles@superbackup:/etc/bacula$ sudo lsscsi -g
[sudo] password for charles:
[3:0:0:0]diskATA  WDC WD20EARS-00M AB51  /dev/sda   /dev/sg0
[7:0:0:0]cd/dvd  HL-DT-ST DVDRAM GSA-H62L  DL00  /dev/sr0   /dev/sg1
[8:0:0:0]diskATA  WDC WD20EARS-00M AB51  /dev/sdb   /dev/sg2
[9:0:0:0]diskATA  WDC WD20EARX-00P AB51  /dev/sdc   /dev/sg3
[10:0:0:0]   diskATA  WDC WD20EARX-008 AB51  /dev/sdd   /dev/sg4
[14:0:0:0]   tapeIBM  ULT3580-TD3  73P5  /dev/st0   /dev/sg7
[14:0:0:1]   mediumx IBM  3573-TL  8.40  /dev/sch0  /dev/sg8
[15:0:0:0]   diskATA  WDC WD20EFRX-68E 0A82  /dev/sde   /dev/sg5
[16:0:0:0]   diskATA  WDC WD20EARS-00M AB51  /dev/sdf   /dev/sg6
charles@superbackup:~$ sudo tapeinfo -f /dev/sg7
Product Type: Tape Drive
Vendor ID: 'IBM '
Product ID: 'ULT3580-TD3 '
Revision: '73P5'
Attached Changer API: No
SerialNumber: '1210306523'
MinBlock: 1
MaxBlock: 16777215
SCSI ID: 0
SCSI LUN: 0
Ready: no


Here is the relevant part of my bacula-sd.conf:

Autochanger {
  Name = Autochanger
  Device = Drive-1
  Changer Command = "/etc/bacula/scripts/mtx-changer %c %o %S %a %d"
  Changer Device = /dev/sg8
}


Device {
  Name = Drive-1
  Media Type = LTO-3
  Device Type = Tape
  Archive Device = /dev/nst0
  AutomaticMount = yes   # when device opened, read it
  AlwaysOpen = yes
  RemovableMedia = yes
  RandomAccess = no
  AutoChanger = yes
  Drive Index = 0
# Enable the Alert command only if you have the mtx package loaded
  Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
# If you have smartctl, enable this, it has more info than tapeinfo
# Alert Command = "sh -c 'smartctl -H -l error %c'"
  Maximum Spool Size = 1024GB
  Maximum Job Spool Size = 800GB
  Spool Directory = /baculatmp
  Maximum Concurrent Jobs = 1
  Maximum Block Size = 1024K
  Maximum File Size = 8GB
  Hardware End of Medium = no
  Fast Forward Space File = yes
}


And the relevant part of my bacula-dir.conf

Storage {
  Name = TL2000
  Address = 192.168.0.17
  SDPort = 9103
  Password = "xxx"
  Device = Autochanger
  Media Type = LTO-3
  Maximum Concurrent Jobs = 1
  Autochanger = yes
  AllowCompression = yes
}


To further investigate the issue, I started bacula-sd and bacula-dir
manually in debug mode and captured below the messages it printed to the
console:

Messages generated by "sudo /usr/sbin/bacula-dir -d 999 -v -c
/etc/bacula/bacula-dir.conf -f -m"

bigzilla-dir: msgchan.c:120-0 Connect to Storage daemon 192.168.0.17:9103
bigzilla-dir: watchdog.c:197-0 Registered watchdog 7f0ec801cf08, interval
1800 one shot
bigzilla-dir: btimers.c:145-0 Start thread timer 7f0ec8021ab8 tid
7f0ed5d27700 for 1800 secs.
bigzilla-dir: bsock.c:237-0 Current 192.168.0.17:9103 All 192.168.0.17:9103
bigzilla-dir: bsock.c:166-0 who=Storage daemon host=192.168.0.17 port=9103
bigzilla-dir: bsock.c:349-0 OK connected to server  Storage daemon
192.168.0.17:9103.
bigzilla-dir: