Re: [Bacula-users] Getting a LTO8 drive work with Bacula.

2022-04-12 Thread Gary R. Schmidt 

On 13/04/2022 09:46, Hector Barrera wrote:

Hello Gentlemen,

I wonder if any of you had a chance to make an IBM LTO8 Tape Drive work 
with Bacula 11.0.1


Previously we had an IBM LTO7 that worked great, but this new drive is 
not working as expected, the btape test function throws out an error.


I followed the Bacula chapter: "Testing Your Tape Drive With Bacula"

Here's some information about our setup:

*_Tape Drive:_*

[root@bacula02 tmp]# tapeinfo -f /dev/nst0



   ArchiveDevice = "/dev/tape/by-id/scsi-35000e111cc2d8001-nst"


You are referring to things using different names.

What happens if you change them to be consistent?

Cheers,
GaryB-)


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Getting a LTO8 drive work with Bacula.

2022-04-12 Thread Hector Barrera 
Hello Gentlemen,

I wonder if any of you had a chance to make an IBM LTO8 Tape Drive work
with Bacula 11.0.1

Previously we had an IBM LTO7 that worked great, but this new drive is not
working as expected, the btape test function throws out an error.

I followed the Bacula chapter: "Testing Your Tape Drive With Bacula"

Here's some information about our setup:

*Tape Drive:*

[root@bacula02 tmp]# tapeinfo -f /dev/nst0
Product Type: Tape Drive
Vendor ID: 'IBM '
Product ID: 'ULTRIUM-HH8 '
Revision: 'N9M1'
Attached Changer API: No
SerialNumber: '1097012184'
MinBlock: 1
MaxBlock: 8388608
SCSI ID: 1
SCSI LUN: 0
Ready: yes
BufferedMode: yes
Medium Type: 0x78
Density Code: 0x5c
*BlockSize: 0*
DataCompEnabled: yes
DataCompCapable: yes
DataDeCompEnabled: yes
CompType: 0xff
DeCompType: 0xff
BOP: yes
Block Position: 0
Partition 0 Remaining Kbytes: -1
Partition 0 Size in Kbytes: -1
ActivePartition: 0
EarlyWarningSize: 0
NumPartitions: 1
MaxPartitions: 3
Partition0: 1071
Partition1: 57857
Partition2: 0
Partition3: 0

First I thought the problem might be with the block size, but as you can
see above, the drive is already to 0

*Running the btape test function:*

[root@bacula02 tmp]# btape -c /opt/bacula/etc/bacula-sd.conf
/dev/tape/by-id/scsi-35000e111cc2d8001-nst
Tape block granularity is 1024 bytes.
btape: butil.c:295-0 Using device:
"/dev/tape/by-id/scsi-35000e111cc2d8001-nst" for writing.
btape: btape.c:477-0 open device "IBMLTO8"
(/dev/tape/by-id/scsi-35000e111cc2d8001-nst): OK
*test

=== Write, rewind, and re-read test ===

I'm going to write 1 records and an EOF
then write 1 records and an EOF, then rewind,
and re-read the data to verify that it is correct.

This is an *essential* feature ...

12-Apr 15:59 btape JobId 0: Re-read of last block succeeded.
*btape: btape.c:1156-0 Error writing block to device.*
*
--
Attempting to WEOF a second time claims the tape is in read-only mode:

*weof
btape: Fatal Error at tape_dev.c:953 because:
tape_dev.c:952 Attempt to WEOF on non-appendable Volume
12-Apr 16:25 btape: Fatal Error at tape_dev.c:953 because:
tape_dev.c:952 Attempt to WEOF on non-appendable Volume
btape: btape.c:607-0 Bad status from weof. *ERR=tape_dev.c:952 Attempt to
WEOF on non-appendable Volume*


*Our bacula-sd.conf (LTO8 in bold):*

Storage {
  Name = "bacula02-sd"
  SdAddress = **.**.**.**
  WorkingDirectory = "/opt/bacula/working"
  PidDirectory = "/opt/bacula/working"
  PluginDirectory = "/opt/bacula/plugins"
  MaximumConcurrentJobs = 20
}
Device {
  Name = "FileChgr1-Dev1"
  MediaType = "File1"
  ArchiveDevice = "/home/bacula/backups"
  RemovableMedia = no
  RandomAccess = yes
  AutomaticMount = yes
  LabelMedia = yes
  AlwaysOpen = no
  MaximumConcurrentJobs = 5
}
Device {
  Name = "IBMLTO7"
  Description = "IBM LTO7 in Library 1 Drive 1"
  MediaType = "LTO-7"
  DeviceType = "Tape"
  ArchiveDevice = "/dev/tape/by-id/scsi-35005076312156b6c-nst"
  RemovableMedia = yes
  RandomAccess = no
  AutomaticMount = yes
  LabelMedia = yes
  AlwaysOpen = yes
  Autochanger = yes
  AutoSelect = yes
  ChangerDevice = "/dev/tape/by-id/scsi-3500e09efff10c86a"
  AlertCommand = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
  MaximumBlockSize = 524288
  MaximumFileSize = 200
  SpoolDirectory = "/home/bacula/spool"
  MaximumSpoolSize = 20
}














*Device {  Name = "IBMLTO8"  Description = "IBM LTO8 in Library 1 Drive 1"
MediaType = "LTO-8"  DeviceType = "Tape"  ArchiveDevice =
"/dev/tape/by-id/scsi-35000e111cc2d8001-nst"  RemovableMedia = yes
RandomAccess = no  AutomaticMount = yes  LabelMedia = yes  AlwaysOpen =
yes  Autochanger = yes  AutoSelect = yes  ChangerDevice =
"/dev/tape/by-id/scsi-1BDT_FlexStor_II_00DE64106938_LL0"  AlertCommand =
"sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"*





*  MaximumBlockSize = 524288  MaximumVolumeSize = 20
MaximumFileSize = 20  SpoolDirectory = "/home/bacula/spool"
MaximumSpoolSize = 20}*
Messages {
  Name = "Standard"
  Director = bacula02-dir = All
}
Autochanger {
  Name = "FileChgr1"
  Device = "FileChgr1-Dev1"
  ChangerDevice = "/dev/null"
  ChangerCommand = ""







*}Autochanger {  Name = "QUALSTAR-LTO-Lib1"  Description = "Qualstar Q24
Tape Library"  Device = "IBMLTO8"  ChangerDevice =
"/dev/tape/by-id/scsi-1BDT_FlexStor_II_00DE64106938_LL0"  ChangerCommand =
"/opt/bacula/scripts/mtx-changer %c %o %S %a %d"}*
Autochanger {
  Name = "QUANTUM-LTO-Lib1"
  Description = "Quantum SuperLoader 3"
  Device = "IBMLTO7"
  ChangerDevice = "/dev/tape/by-id/scsi-3500e09efff10c86a"
  ChangerCommand = "/opt/bacula/scripts/mtx-changer %c %o %S %a %d"
}
---

I should mention that running this actually works:

mt -f /dev/nst0 rewind
tar -cvf /dev/nst0 .
mt -f /dev/nst0 rewind
tar -xvf /dev/nst0

Running the tar directly to the tape drive works.
I was able to tar several files and extract them without a problem.
So the problem seems to be with my bacula configuration.

Please

Re: [Bacula-users] 11.0.6 deb/rpm availability?

2022-04-12 Thread Dirk 


I see the debs are available now, but not the rpms.  ETA on the rpms?

Also, will you be releasing 11.0.6 debs for Debian 11 and Ubuntu 22.04 ???

---


On 4/12/2022 1:15 PM, Dirk wrote:


I see the debs are available now, but not the rpms.  ETA on the rpms?

Also, will you be releasing 11.0.6 debs for Debian 11 and Ubuntu 22.04 ???

---


On 4/9/2022 1:12 AM, Davide F. wrote:

Hello Dirk,

Bacula 11.0.6 packages will be available by tomorrow evening.

Sorry for the delay and thanks for your patience.

Best regards

Davide

On Fri, 8 Apr 2022 at 18:56 Dirk > wrote:



    Bacula version 11.0.6 was announced nearly one month ago, but the deb
    and rpm packages still are not available.

    What is the ETA on them?  A prompt response is greatly appreciated.

    ---



    ___
    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] Compiling v9.6.7 for Raspian 64 bit

2022-04-12 Thread Martin Simmons 
The bug tracker is at https://bugs.bacula.org.

Maybe the best fix is to use $(INSTALL_PROGRAM_ALL) for the tools instead of
$(INSTALL_PROGRAM)?

__Martin


> On Tue, 12 Apr 2022 14:32:34 +0100, Chris Wilkinson said:
> 
> It seemed to me like a bug in the makefile. How should I report it? Or
> perhaps one of the devs could pick it up?
> 
> dbcheck is also affected. This prevents the dir startup script from running.
> 
> It all seems to be working now with these changes made.
> 
> Chris.
> 
> On Tue, 12 Apr 2022, 11:37 am Martin Simmons,  wrote:
> 
> > That sounds like a bug.  The Makefile actually contains comments about
> > this,
> > so someone was thinking about it:
> >
> > # Allow non-root execution of bsmtp for non-root Directors
> > install: $(INSTOOLS)
> > @for tool in ${INSTOOLS} ; do \
> >$(LIBTOOL_INSTALL) $(INSTALL_PROGRAM) $$tool
> > $(DESTDIR)$(sbindir)/$$tool ; \
> > done
> > #   chattr +i $(DESTDIR)$(sbindir)/bsmtp
> > #   chmod 755 $(DESTDIR)$(sbindir)/bsmtp
> >
> > __Martin
> >
> >
> > > On Tue, 12 Apr 2022 10:10:38 +0100, Chris Wilkinson said:
> > >
> > > Just a final note on this. I found that bsmtp was installed with
> > root:root
> > > 750 permissions. The effect of this was that emails were not sent,
> > > presumably because dir runs as user bacula. There were no errors shown or
> > > logged in any of the logs so it was tricky to track down. Once I changed
> > > bsmtp to 755, mail began to work.
> > >
> > > The other bacula utility programs are also installed as root:root, 750.
> > >
> > > Regards
> > > Chris Wilkinson
> > >
> > > On Sat, 2 Apr 2022, 8:49 am Chris Wilkinson, 
> > wrote:
> > >
> > > > Scripts are installed in /etc/init.d but no unit files for systemd were
> > > > installed. Consequently, I can start everything with the
> > /usr/sbin/bacula
> > > > script but "systemctl start bacula-xxx.service" won't work. These
> > service
> > > > files seem to be in the source tar but don't get installed.
> > > >
> > > > I had added user bacula to sudoers and as a member of the sudo group
> > > > whilst trying to debug this but that was dead end which I should undo
> > now.
> > > >
> > > > Best
> > > > Chris
> > > >
> > > >
> > > > On Fri, 1 Apr 2022, 11:19 pm Martin Simmons, 
> > wrote:
> > > >
> > > >> That looks OK, but how are you running the startup scripts?  You
> > mentioned
> > > >> sudo before, but they should be run directly as root.
> > > >>
> > > >> __Martin
> > > >>
> > > >>
> > > >> > On Fri, 1 Apr 2022 15:40:04 +0100, Chris Wilkinson said:
> > > >> >
> > > >> > These are the ./configure flags I used. This puts the desired daemon
> > > >> > user/group in the startup scripts. I didn't find a --with option to
> > set
> > > >> the
> > > >> > daemon executable permissions that defaults to 750.
> > > >> >
> > > >> > #compile
> > > >> > cd $target/bacula-$ver
> > > >> > PREFIX=/usr/sbin
> > > >> > CFLAGS="-g -O2 -Wall" \
> > > >> > ./configure \
> > > >> >   --bindir=/usr/bin \
> > > >> >   --sbindir=/usr/sbin \
> > > >> >   --docdir=/usr/html \
> > > >> >   --htmldir=/usr/html \
> > > >> >   --enable-smartalloc \
> > > >> >   --with-scriptdir=/etc/bacula/scripts \
> > > >> >   --with-working-dir=/var/lib/bacula \
> > > >> >   --with-pid-dir=/var/run/bacula \
> > > >> >   --with-logdir=/var/log/bacula \
> > > >> >   --with-postgresql \
> > > >> >   --with-archivedir=/mnt/usb \
> > > >> >   --with-job-email=root@localhost \
> > > >> >   --with-dump-email=root@localhost \
> > > >> >   --with-hostname=pi-b \
> > > >> >   --with-db-name=bacula \
> > > >> >   --with-db-user=bacula \
> > > >> >   --with-db-password= \
> > > >> >   --with-dir-user=bacula \
> > > >> >   --with-dir-group=bacula \
> > > >> >   --with-fd-user=root \
> > > >> >   --with-fd-group=root \
> > > >> >   --with-sd-user=bacula \
> > > >> >   --with-sd-group=tape
> > > >> >
> > > >> >
> > > >> > Regards
> > > >> > Chris Wilkinson
> > > >> >
> > > >> > On Fri, 1 Apr 2022, 12:47 pm Martin Simmons, 
> > > >> wrote:
> > > >> >
> > > >> > > > On Fri, 1 Apr 2022 21:29:56 +1100, Gary R Schmidt said:
> > > >> > > >
> > > >> > > > On 01/04/2022 21:13, Chris Wilkinson wrote:
> > > >> > > > > I built this from source and found it would not run due to a
> > > >> > > permissions
> > > >> > > > > error with the daemons bacula-* and dbcheck. It seems the make
> > > >> builds
> > > >> > > > > them with permissions 750, root:root. I run the director as
> > > >> > > > > bacula:bacula, the fd as root:root and sd as bacula:tape. User
> > > >> bacula
> > > >> > > is
> > > >> > > > > a member of the sudo group. Changing the daemons and dbcheck
> > to
> > > >> 755
> > > >> > > > > fixed this.
> > > >> > > > >
> > > >> > > > > Does that suggest the make is in error or maybe my choices of
> > what
> > > >> > > user
> > > >> > > > > to run the daemons as is incorrect?
> > > >> > > > >
> > > >> > > > NOTE: I've not built on Raspian, but it looks like you've
> > missed the
> > > >> >

Re: [Bacula-users] Compiling v9.6.7 for Raspian 64 bit

2022-04-12 Thread Chris Wilkinson 
It seemed to me like a bug in the makefile. How should I report it? Or
perhaps one of the devs could pick it up?

dbcheck is also affected. This prevents the dir startup script from running.

It all seems to be working now with these changes made.

Chris.

On Tue, 12 Apr 2022, 11:37 am Martin Simmons,  wrote:

> That sounds like a bug.  The Makefile actually contains comments about
> this,
> so someone was thinking about it:
>
> # Allow non-root execution of bsmtp for non-root Directors
> install: $(INSTOOLS)
> @for tool in ${INSTOOLS} ; do \
>$(LIBTOOL_INSTALL) $(INSTALL_PROGRAM) $$tool
> $(DESTDIR)$(sbindir)/$$tool ; \
> done
> #   chattr +i $(DESTDIR)$(sbindir)/bsmtp
> #   chmod 755 $(DESTDIR)$(sbindir)/bsmtp
>
> __Martin
>
>
> > On Tue, 12 Apr 2022 10:10:38 +0100, Chris Wilkinson said:
> >
> > Just a final note on this. I found that bsmtp was installed with
> root:root
> > 750 permissions. The effect of this was that emails were not sent,
> > presumably because dir runs as user bacula. There were no errors shown or
> > logged in any of the logs so it was tricky to track down. Once I changed
> > bsmtp to 755, mail began to work.
> >
> > The other bacula utility programs are also installed as root:root, 750.
> >
> > Regards
> > Chris Wilkinson
> >
> > On Sat, 2 Apr 2022, 8:49 am Chris Wilkinson, 
> wrote:
> >
> > > Scripts are installed in /etc/init.d but no unit files for systemd were
> > > installed. Consequently, I can start everything with the
> /usr/sbin/bacula
> > > script but "systemctl start bacula-xxx.service" won't work. These
> service
> > > files seem to be in the source tar but don't get installed.
> > >
> > > I had added user bacula to sudoers and as a member of the sudo group
> > > whilst trying to debug this but that was dead end which I should undo
> now.
> > >
> > > Best
> > > Chris
> > >
> > >
> > > On Fri, 1 Apr 2022, 11:19 pm Martin Simmons, 
> wrote:
> > >
> > >> That looks OK, but how are you running the startup scripts?  You
> mentioned
> > >> sudo before, but they should be run directly as root.
> > >>
> > >> __Martin
> > >>
> > >>
> > >> > On Fri, 1 Apr 2022 15:40:04 +0100, Chris Wilkinson said:
> > >> >
> > >> > These are the ./configure flags I used. This puts the desired daemon
> > >> > user/group in the startup scripts. I didn't find a --with option to
> set
> > >> the
> > >> > daemon executable permissions that defaults to 750.
> > >> >
> > >> > #compile
> > >> > cd $target/bacula-$ver
> > >> > PREFIX=/usr/sbin
> > >> > CFLAGS="-g -O2 -Wall" \
> > >> > ./configure \
> > >> >   --bindir=/usr/bin \
> > >> >   --sbindir=/usr/sbin \
> > >> >   --docdir=/usr/html \
> > >> >   --htmldir=/usr/html \
> > >> >   --enable-smartalloc \
> > >> >   --with-scriptdir=/etc/bacula/scripts \
> > >> >   --with-working-dir=/var/lib/bacula \
> > >> >   --with-pid-dir=/var/run/bacula \
> > >> >   --with-logdir=/var/log/bacula \
> > >> >   --with-postgresql \
> > >> >   --with-archivedir=/mnt/usb \
> > >> >   --with-job-email=root@localhost \
> > >> >   --with-dump-email=root@localhost \
> > >> >   --with-hostname=pi-b \
> > >> >   --with-db-name=bacula \
> > >> >   --with-db-user=bacula \
> > >> >   --with-db-password= \
> > >> >   --with-dir-user=bacula \
> > >> >   --with-dir-group=bacula \
> > >> >   --with-fd-user=root \
> > >> >   --with-fd-group=root \
> > >> >   --with-sd-user=bacula \
> > >> >   --with-sd-group=tape
> > >> >
> > >> >
> > >> > Regards
> > >> > Chris Wilkinson
> > >> >
> > >> > On Fri, 1 Apr 2022, 12:47 pm Martin Simmons, 
> > >> wrote:
> > >> >
> > >> > > > On Fri, 1 Apr 2022 21:29:56 +1100, Gary R Schmidt said:
> > >> > > >
> > >> > > > On 01/04/2022 21:13, Chris Wilkinson wrote:
> > >> > > > > I built this from source and found it would not run due to a
> > >> > > permissions
> > >> > > > > error with the daemons bacula-* and dbcheck. It seems the make
> > >> builds
> > >> > > > > them with permissions 750, root:root. I run the director as
> > >> > > > > bacula:bacula, the fd as root:root and sd as bacula:tape. User
> > >> bacula
> > >> > > is
> > >> > > > > a member of the sudo group. Changing the daemons and dbcheck
> to
> > >> 755
> > >> > > > > fixed this.
> > >> > > > >
> > >> > > > > Does that suggest the make is in error or maybe my choices of
> what
> > >> > > user
> > >> > > > > to run the daemons as is incorrect?
> > >> > > > >
> > >> > > > NOTE: I've not built on Raspian, but it looks like you've
> missed the
> > >> > > > "--with-XXX-user=" options to configure.
> > >> > >
> > >> > > In particular, the permissions are designed for the daemons to be
> > >> started
> > >> > > as
> > >> > > root, with the -u and -g options controlling the user and group.
> The
> > >> > > default
> > >> > > startup scripts do this using information from the configure.
> > >> > >
> > >> > > __Martin
> > >> > >
> > >> > >
> > >> > > ___
> > >> > > Bacula-users mailing list
> > >> > >

Re: [Bacula-users] Compiling v9.6.7 for Raspian 64 bit

2022-04-12 Thread Martin Simmons 
That sounds like a bug.  The Makefile actually contains comments about this,
so someone was thinking about it:

# Allow non-root execution of bsmtp for non-root Directors
install: $(INSTOOLS)
@for tool in ${INSTOOLS} ; do \
   $(LIBTOOL_INSTALL) $(INSTALL_PROGRAM) $$tool 
$(DESTDIR)$(sbindir)/$$tool ; \
done
#   chattr +i $(DESTDIR)$(sbindir)/bsmtp
#   chmod 755 $(DESTDIR)$(sbindir)/bsmtp

__Martin


> On Tue, 12 Apr 2022 10:10:38 +0100, Chris Wilkinson said:
> 
> Just a final note on this. I found that bsmtp was installed with root:root
> 750 permissions. The effect of this was that emails were not sent,
> presumably because dir runs as user bacula. There were no errors shown or
> logged in any of the logs so it was tricky to track down. Once I changed
> bsmtp to 755, mail began to work.
> 
> The other bacula utility programs are also installed as root:root, 750.
> 
> Regards
> Chris Wilkinson
> 
> On Sat, 2 Apr 2022, 8:49 am Chris Wilkinson,  wrote:
> 
> > Scripts are installed in /etc/init.d but no unit files for systemd were
> > installed. Consequently, I can start everything with the /usr/sbin/bacula
> > script but "systemctl start bacula-xxx.service" won't work. These service
> > files seem to be in the source tar but don't get installed.
> >
> > I had added user bacula to sudoers and as a member of the sudo group
> > whilst trying to debug this but that was dead end which I should undo now.
> >
> > Best
> > Chris
> >
> >
> > On Fri, 1 Apr 2022, 11:19 pm Martin Simmons,  wrote:
> >
> >> That looks OK, but how are you running the startup scripts?  You mentioned
> >> sudo before, but they should be run directly as root.
> >>
> >> __Martin
> >>
> >>
> >> > On Fri, 1 Apr 2022 15:40:04 +0100, Chris Wilkinson said:
> >> >
> >> > These are the ./configure flags I used. This puts the desired daemon
> >> > user/group in the startup scripts. I didn't find a --with option to set
> >> the
> >> > daemon executable permissions that defaults to 750.
> >> >
> >> > #compile
> >> > cd $target/bacula-$ver
> >> > PREFIX=/usr/sbin
> >> > CFLAGS="-g -O2 -Wall" \
> >> > ./configure \
> >> >   --bindir=/usr/bin \
> >> >   --sbindir=/usr/sbin \
> >> >   --docdir=/usr/html \
> >> >   --htmldir=/usr/html \
> >> >   --enable-smartalloc \
> >> >   --with-scriptdir=/etc/bacula/scripts \
> >> >   --with-working-dir=/var/lib/bacula \
> >> >   --with-pid-dir=/var/run/bacula \
> >> >   --with-logdir=/var/log/bacula \
> >> >   --with-postgresql \
> >> >   --with-archivedir=/mnt/usb \
> >> >   --with-job-email=root@localhost \
> >> >   --with-dump-email=root@localhost \
> >> >   --with-hostname=pi-b \
> >> >   --with-db-name=bacula \
> >> >   --with-db-user=bacula \
> >> >   --with-db-password= \
> >> >   --with-dir-user=bacula \
> >> >   --with-dir-group=bacula \
> >> >   --with-fd-user=root \
> >> >   --with-fd-group=root \
> >> >   --with-sd-user=bacula \
> >> >   --with-sd-group=tape
> >> >
> >> >
> >> > Regards
> >> > Chris Wilkinson
> >> >
> >> > On Fri, 1 Apr 2022, 12:47 pm Martin Simmons, 
> >> wrote:
> >> >
> >> > > > On Fri, 1 Apr 2022 21:29:56 +1100, Gary R Schmidt said:
> >> > > >
> >> > > > On 01/04/2022 21:13, Chris Wilkinson wrote:
> >> > > > > I built this from source and found it would not run due to a
> >> > > permissions
> >> > > > > error with the daemons bacula-* and dbcheck. It seems the make
> >> builds
> >> > > > > them with permissions 750, root:root. I run the director as
> >> > > > > bacula:bacula, the fd as root:root and sd as bacula:tape. User
> >> bacula
> >> > > is
> >> > > > > a member of the sudo group. Changing the daemons and dbcheck to
> >> 755
> >> > > > > fixed this.
> >> > > > >
> >> > > > > Does that suggest the make is in error or maybe my choices of what
> >> > > user
> >> > > > > to run the daemons as is incorrect?
> >> > > > >
> >> > > > NOTE: I've not built on Raspian, but it looks like you've missed the
> >> > > > "--with-XXX-user=" options to configure.
> >> > >
> >> > > In particular, the permissions are designed for the daemons to be
> >> started
> >> > > as
> >> > > root, with the -u and -g options controlling the user and group.  The
> >> > > default
> >> > > startup scripts do this using information from the configure.
> >> > >
> >> > > __Martin
> >> > >
> >> > >
> >> > > ___
> >> > > 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] Compiling v9.6.7 for Raspian 64 bit

2022-04-12 Thread Chris Wilkinson 
Just a final note on this. I found that bsmtp was installed with root:root
750 permissions. The effect of this was that emails were not sent,
presumably because dir runs as user bacula. There were no errors shown or
logged in any of the logs so it was tricky to track down. Once I changed
bsmtp to 755, mail began to work.

The other bacula utility programs are also installed as root:root, 750.

Regards
Chris Wilkinson

On Sat, 2 Apr 2022, 8:49 am Chris Wilkinson,  wrote:

> Scripts are installed in /etc/init.d but no unit files for systemd were
> installed. Consequently, I can start everything with the /usr/sbin/bacula
> script but "systemctl start bacula-xxx.service" won't work. These service
> files seem to be in the source tar but don't get installed.
>
> I had added user bacula to sudoers and as a member of the sudo group
> whilst trying to debug this but that was dead end which I should undo now.
>
> Best
> Chris
>
>
> On Fri, 1 Apr 2022, 11:19 pm Martin Simmons,  wrote:
>
>> That looks OK, but how are you running the startup scripts?  You mentioned
>> sudo before, but they should be run directly as root.
>>
>> __Martin
>>
>>
>> > On Fri, 1 Apr 2022 15:40:04 +0100, Chris Wilkinson said:
>> >
>> > These are the ./configure flags I used. This puts the desired daemon
>> > user/group in the startup scripts. I didn't find a --with option to set
>> the
>> > daemon executable permissions that defaults to 750.
>> >
>> > #compile
>> > cd $target/bacula-$ver
>> > PREFIX=/usr/sbin
>> > CFLAGS="-g -O2 -Wall" \
>> > ./configure \
>> >   --bindir=/usr/bin \
>> >   --sbindir=/usr/sbin \
>> >   --docdir=/usr/html \
>> >   --htmldir=/usr/html \
>> >   --enable-smartalloc \
>> >   --with-scriptdir=/etc/bacula/scripts \
>> >   --with-working-dir=/var/lib/bacula \
>> >   --with-pid-dir=/var/run/bacula \
>> >   --with-logdir=/var/log/bacula \
>> >   --with-postgresql \
>> >   --with-archivedir=/mnt/usb \
>> >   --with-job-email=root@localhost \
>> >   --with-dump-email=root@localhost \
>> >   --with-hostname=pi-b \
>> >   --with-db-name=bacula \
>> >   --with-db-user=bacula \
>> >   --with-db-password= \
>> >   --with-dir-user=bacula \
>> >   --with-dir-group=bacula \
>> >   --with-fd-user=root \
>> >   --with-fd-group=root \
>> >   --with-sd-user=bacula \
>> >   --with-sd-group=tape
>> >
>> >
>> > Regards
>> > Chris Wilkinson
>> >
>> > On Fri, 1 Apr 2022, 12:47 pm Martin Simmons, 
>> wrote:
>> >
>> > > > On Fri, 1 Apr 2022 21:29:56 +1100, Gary R Schmidt said:
>> > > >
>> > > > On 01/04/2022 21:13, Chris Wilkinson wrote:
>> > > > > I built this from source and found it would not run due to a
>> > > permissions
>> > > > > error with the daemons bacula-* and dbcheck. It seems the make
>> builds
>> > > > > them with permissions 750, root:root. I run the director as
>> > > > > bacula:bacula, the fd as root:root and sd as bacula:tape. User
>> bacula
>> > > is
>> > > > > a member of the sudo group. Changing the daemons and dbcheck to
>> 755
>> > > > > fixed this.
>> > > > >
>> > > > > Does that suggest the make is in error or maybe my choices of what
>> > > user
>> > > > > to run the daemons as is incorrect?
>> > > > >
>> > > > NOTE: I've not built on Raspian, but it looks like you've missed the
>> > > > "--with-XXX-user=" options to configure.
>> > >
>> > > In particular, the permissions are designed for the daemons to be
>> started
>> > > as
>> > > root, with the -u and -g options controlling the user and group.  The
>> > > default
>> > > startup scripts do this using information from the configure.
>> > >
>> > > __Martin
>> > >
>> > >
>> > > ___
>> > > 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