Re: [Bacula-users] spool directory

[Alan P. <ala...@gm...>]

Bill:


Thanks for getting back so quickly. In my original (non spool file 
inclusion) i get:

tcp    0    0 0.0.0.0:9103 0.0.0.0:*        LISTEN        10177/bacula-sd

Including the spool file directive I get nothing. In all conf files I 
list the host name as slcakware.polinsky.home


In Slackware, software is stored at

/var/bacula

That directory is owned by root:root. All subsidiary directories, 
plugins, scripts, and working are bacula:bacula. (As I mentioned all 
those directories are on the second sdb disc. I have attached sda1 to 
/bacula. that parent direcotry is owned by root:root. the 
/bacula/working directory is owned by bacula:bacula.

For right now I am sticking with the original configuration.


Alan

On 5/29/25 17:15, Bill Arlofski via Bacula-users wrote:
> On 5/29/25 3:02 PM, Alan Polinsky wrote:
>> I've been running Bacula 9.6.7 for many years with an attached LTO3 
>> tape drive. The machine hosting Bacula is an old Dell Optiplex. 
>> Though I am always in Slackware, there is a small 250 gig drive that 
>> had Windows 10 installed on it, even though It was never booted in 
>> that operating system. With the prospective of Microsoft abandoning 
>> Windows 10, I decided to reformat that disc as ext4 and attached it 
>> to /bacula. The directive in /etc/fstab is  /dev/sda1 /bacula        
>> ext4        defaults 0    0.
>>
>> I created a directory under that called working and changed ownership 
>> to bacula:bacula. In the bacula-sd.conf file I added:
>>
>>      Spool Directory /bacula/working
>>
>>
>> I have changed no other directives in the two remaining conf files. I 
>> get the following error
>>
>>
>> Fatal error: bsockcore.c:208 Un
>> able to connect to Storage daemon on slackware151.polinsky.home:9103. 
>> ERR=Connection
>> refused
>>
>> The added disc is sda, Slackware is on sdb. What do I have to 
>> additionally change to allow the spool file to use sda?
>>
>>
>> Thank you.
>>
>>
>> Alan
>
> Hello Alan,
>
> This looks to me like the SD is not starting/running on 
> `slackware151.polinsky.home`
>
> On that system what does this show:
>
> # netstat -tlpn | grep 9103
>
> I suspect a missing permission, or wrong ownership further up the 
> /opt/bacula tree...
>
> You can test the SD in debug and foreground mode:
>
> # sudo -u bacula /opt/bacula/bin/bacula-sd -d100 -f     (adjust the 
> path to where bacula-sd lives on Slackware)
>
>
> ...And should quickly see what the reason is.
>
>
> Hope this helps,
> Bill
>
>
>
> _______________________________________________
> Bacula-users mailing list
> Bac...@li...
> https://lists.sourceforge.net/lists/listinfo/bacula-users