Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[r0...@nxlplyx.com]

Hi Martin,

Thank you.  But I got the same result.

---

$ make CFLAGS=-I/usr/include/x86_64-linux-gnu  deb

make: *** No rule to make target 'curl/curl.h', needed by
'build/obj/acl.do'.  Stop.

---

and just for consistency, I ran Radoslaw's command and got the results
below:

=

$ dpkg -S curl.h
libcurl4-openssl-dev:amd64: /usr/include/x86_64-linux-gnu/curl/curl.h

=


Well, if anyone can help I'd appreciate it.

Regards,

Al.


On 5/21/20 12:55 PM, Martin Simmons wrote:
> If you were trying to set CFLAGS to -I/usr/include/x86_64-linux-gnu then you
> must remove the space after CFLAGS=, i.e. use
>
> make CFLAGS=-I/usr/include/x86_64-linux-gnu deb
>
> __Martin
>
>
>> On Wed, 20 May 2020 20:40:23 -0400, r0002@nxlplyx com said:
>> Hi Radoslaw,
>>
>> I still get the same results.  Judging by the error message, I am
>> guessing that it finds them, but doesn't know what to do with them
>> because there is no rule for them.
>>
>> ===
>>
>> $ make CFLAGS= -I/usr/include/x86_64-linux-gnu  deb
>>
>> make: *** No rule to make target 'curl/curl.h', needed by
>> 'build/obj/acl.do'.  Stop.
>>
>> ===
>>
>> Thanks for the attempt to help.
>>
>> Has anyone actually gotten the S3 module  to work in Ubuntu 18.04 that
>> can give a hand?
>>
>> Regards,
>>
>> Al
>>
>> On 5/20/20 4:38 AM, Radosław Korzeniewski wrote:
>>> Hello,
>>>
>>> Hi Radoslaw,
>>>
>>> I believe I have tried every kind of library combination, to no avail.
>>>
>>> Your compilation requires a following header file to be
>>> available: curl/curl.h
>>> In my development machine (Debian) it is available with the following
>>> package:
>>> # dpkg -S curl.h
>>> libcurl4-openssl-dev:amd64: /usr/include/x86_64-linux-gnu/curl/curl.h
>>>
>>> So, I suggested that it should be available in a similar package in
>>> Ubuntu (and it seems it is the exact package).
>>> You have to check where this header file is installed and what package
>>> provides it. If it does not fit then you should alter your compilation
>>> flags, i.e. CFLAGS and CPPFLAGS to provide a correct header file location.
>>>
>>> I hope it helps.
>>>
>>> Radek
>>> -- 
>>> Radosław Korzeniewski
>>> rados...@korzeniewski.net 
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[Martin Simmons]

If you were trying to set CFLAGS to -I/usr/include/x86_64-linux-gnu then you
must remove the space after CFLAGS=, i.e. use

make CFLAGS=-I/usr/include/x86_64-linux-gnu deb

__Martin


> On Wed, 20 May 2020 20:40:23 -0400, r0002@nxlplyx com said:
> 
> Hi Radoslaw,
> 
> I still get the same results.  Judging by the error message, I am
> guessing that it finds them, but doesn't know what to do with them
> because there is no rule for them.
> 
> ===
> 
> $ make CFLAGS= -I/usr/include/x86_64-linux-gnu  deb
> 
> make: *** No rule to make target 'curl/curl.h', needed by
> 'build/obj/acl.do'.  Stop.
> 
> ===
> 
> Thanks for the attempt to help.
> 
> Has anyone actually gotten the S3 module  to work in Ubuntu 18.04 that
> can give a hand?
> 
> Regards,
> 
> Al
> 
> On 5/20/20 4:38 AM, Radosław Korzeniewski wrote:
> > Hello,
> >
> > Hi Radoslaw,
> >
> > I believe I have tried every kind of library combination, to no avail.
> >
> > Your compilation requires a following header file to be
> > available: curl/curl.h
> > In my development machine (Debian) it is available with the following
> > package:
> > # dpkg -S curl.h
> > libcurl4-openssl-dev:amd64: /usr/include/x86_64-linux-gnu/curl/curl.h
> >
> > So, I suggested that it should be available in a similar package in
> > Ubuntu (and it seems it is the exact package).
> > You have to check where this header file is installed and what package
> > provides it. If it does not fit then you should alter your compilation
> > flags, i.e. CFLAGS and CPPFLAGS to provide a correct header file location.
> >
> > I hope it helps.
> >
> > Radek
> > -- 
> > Radosław Korzeniewski
> > rados...@korzeniewski.net 
> 


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

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[r0...@nxlplyx.com]

Hi Radoslaw,

I still get the same results.  Judging by the error message, I am
guessing that it finds them, but doesn't know what to do with them
because there is no rule for them.

===

$ make CFLAGS= -I/usr/include/x86_64-linux-gnu  deb

make: *** No rule to make target 'curl/curl.h', needed by
'build/obj/acl.do'.  Stop.

===

Thanks for the attempt to help.

Has anyone actually gotten the S3 module  to work in Ubuntu 18.04 that
can give a hand?

Regards,

Al

On 5/20/20 4:38 AM, Radosław Korzeniewski wrote:
> Hello,
>
> Hi Radoslaw,
>
> I believe I have tried every kind of library combination, to no avail.
>
> Your compilation requires a following header file to be
> available: curl/curl.h
> In my development machine (Debian) it is available with the following
> package:
> # dpkg -S curl.h
> libcurl4-openssl-dev:amd64: /usr/include/x86_64-linux-gnu/curl/curl.h
>
> So, I suggested that it should be available in a similar package in
> Ubuntu (and it seems it is the exact package).
> You have to check where this header file is installed and what package
> provides it. If it does not fit then you should alter your compilation
> flags, i.e. CFLAGS and CPPFLAGS to provide a correct header file location.
>
> I hope it helps.
>
> Radek
> -- 
> Radosław Korzeniewski
> rados...@korzeniewski.net 
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[Radosław Korzeniewski]

Hello,

wt., 19 maj 2020 o 21:37 r0...@nxlplyx.com  napisał(a):

> Hi Radoslaw,
>
> I believe I have tried every kind of library combination, to no avail.
>
Your compilation requires a following header file to be
available: curl/curl.h
In my development machine (Debian) it is available with the following
package:
# dpkg -S curl.h
libcurl4-openssl-dev:amd64: /usr/include/x86_64-linux-gnu/curl/curl.h

So, I suggested that it should be available in a similar package in Ubuntu
(and it seems it is the exact package).
You have to check where this header file is installed and what package
provides it. If it does not fit then you should alter your compilation
flags, i.e. CFLAGS and CPPFLAGS to provide a correct header file location.

I hope it helps.

Radek
-- 
Radosław Korzeniewski
rados...@korzeniewski.net
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[r0...@nxlplyx.com]

Hi Radoslaw,

I believe I have tried every kind of library combination, to no avail.




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

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[Radosław Korzeniewski]

Hello,

sob., 16 maj 2020 o 18:40 r0...@nxlplyx.com  napisał(a):

> Hi Sven,
>
> I retrieved the S3 module from the link you provided:
> www.bacula.org/downloads/libs3-20181010.tar.gz
>
> However I have been unable to compile the module in Ubuntu 18.04:
>
> 
>
> $ ls
> archlinux  ChangeLog  debianGNUmakefileGNUmakefile.osx
> INSTALL LICENSE  README  test
> build  COPYINGdoxyfile  GNUmakefile.mingw  inc
> libs3.spec  mswinsrc TODO
> $ make deb
> make: *** No rule to make target 'curl/curl.h', needed by
> 'build/obj/acl.do'.  Stop.
>
You should install something like this: libcurl4-openssl-dev (this is a
Debian package name).

best regards
-- 
Radosław Korzeniewski
rados...@korzeniewski.net
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[kern]

Hello Josh,Yes, it can be implemented the way you describe, and in fact Bacula 
has all the necessary code but some needs to write the driver (a bunch of 
scripts).I am sure it will happen in the not too distant future.Best regards, 
KernSent from my Samsung Galaxy smartphone.
 Original message From: Josh Fisher  Date: 
5/11/20  16:52  (GMT+01:00) To: Kern Sibbald , Sven Hartge 
, bacula-users@lists.sourceforge.net Subject: Re: 
[Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04 


On 5/11/2020 7:38 AM, Kern Sibbald
  wrote:


  
  Hello Sven,
  I share your concerns, but here are a few mitigating factors:
  1. I am not aware of any other C/C++ S3 library that will do
the same job and is well maintained.  I have to admit I have not
looked recently, so any suggestions would be welcome.



I'm not aware of other C libraries either, but why not use AWS
  CLI high-level commands in much the same way that tape autochanger
  script commands are implemented? AWS CLI is actively maintained by
  Amazon and so shouldn't  have the maintenance issues. These are
  simple mv, cp, ls, etc. commands somewhat equivalent to their Unix
  command namesakes. They shouldn't change even when/if Amazon
  changes the underlying S3 protocols.




  2. Bacula Systems actively uses libs3 with its customers, and
any corrections that they make will also be in the Bacula
community libs3 git repo (under the same GNU Lesser V3 license)
  3. Amazon (or other s3 supplier's) tools can be used to restore
Bacula S3 Volumes to disk, and once that is done, Bacula can
read those volumes regardless of what S3 library it is linked
with.  This is because when the Volumes are on disk, Bacula
reads them as standard OS files.  libs3 is only used to move
files from a local disk to and from the S3 cloud.
  
  Best regards,
  Kern
  
  On 5/10/20 3:24 PM, Sven Hartge
wrote:
  
  
On 10.05.20 15:01, Kern Sibbald wrote:



  I agree with Sven, libs3 is a big disaster.  It works well but the
author abandoned it, and many things have changed since then.  For the
moment, we have a version that works with AWS (don't expect it to work
with a number of other S3 implementations, which are not compatible with
AWS).


Adding to that: Other than the horrendous possible security flaws
present in libs3 (try to compile with a recent GCC and see for yourself)
the nature of anything cloud-bases is inherently volatile.

The AWS-API may change at any given moment (and it has in the past),
making libs3 incompatible without updates.

And without an upstream author implementing those changes, your backups
are more or less gone.

My very pessimistic view on the situation is: Don't use any backup
solution using libs3 if you value your data.

But: YMMV.

Grüße,
Sven.






___
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


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

[Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[r0...@nxlplyx.com]

Hi Sven,

I retrieved the S3 module from the link you
provided: www.bacula.org/downloads/libs3-20181010.tar.gz

However I have been unable to compile the module in Ubuntu 18.04:



$ ls
archlinux  ChangeLog  debian    GNUmakefile    GNUmakefile.osx 
INSTALL LICENSE  README  test
build  COPYING    doxyfile  GNUmakefile.mingw  inc 
libs3.spec  mswin    src TODO
$ make deb
make: *** No rule to make target 'curl/curl.h', needed by
'build/obj/acl.do'.  Stop.

-

I have also noticed that in the 'libs3.spec' file, there exist the
following lines.  But I have installed everything remotely similar to
these, to no avail.

=

# Want to include curl dependencies, but older Fedora Core uses curl-devel,
# and newer Fedora Core uses libcurl-devel ... have to figure out how to
# handle this problem, but for now, just don't check for any curl libraries
# Buildrequires: curl-devel
Buildrequires: libxml2-devel
Buildrequires: openssl-devel
Buildrequires: make
# Requires: libcurl
Requires: libxml2
Requires: openssl

=

Does anyone have any ideas on how to make this work in Ubuntu 18.04?


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

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[Martin Simmons]

> On Mon, 11 May 2020 10:52:23 -0400, Josh Fisher said:
> 
> This is a multi-part message in MIME format.
> --===2027621642792716715==
> Content-Type: multipart/alternative;
>  boundary="70CDB63220E9E5545F246201"
> Content-Language: en-US
> 
> This is a multi-part message in MIME format.
> --70CDB63220E9E5545F246201
> Content-Type: text/plain; charset=utf-8; format=flowed
> Content-Transfer-Encoding: 8bit
> 
> 
> On 5/11/2020 7:38 AM, Kern Sibbald wrote:
> >
> > Hello Sven,
> >
> > I share your concerns, but here are a few mitigating factors:
> >
> > 1. I am not aware of any other C/C++ S3 library that will do the same 
> > job and is well maintained.  I have to admit I have not looked 
> > recently, so any suggestions would be welcome.
> >
> 
> I'm not aware of other C libraries either, but why not use AWS CLI 
> high-level commands in much the same way that tape autochanger script 
> commands are implemented? AWS CLI is actively maintained by Amazon and 
> so shouldn't  have the maintenance issues. These are simple mv, cp, ls, 
> etc. commands somewhat equivalent to their Unix command namesakes. They 
> shouldn't change even when/if Amazon changes the underlying S3 protocols.

There is also the Amazon's own SDK: https://aws.amazon.com/sdk-for-cpp/

> 
> 
> > 2. Bacula Systems actively uses libs3 with its customers, and any 
> > corrections that they make will also be in the Bacula community libs3 
> > git repo (under the same GNU Lesser V3 license)
> >
> > 3. Amazon (or other s3 supplier's) tools can be used to restore Bacula 
> > S3 Volumes to disk, and once that is done, Bacula can read those 
> > volumes regardless of what S3 library it is linked with.  This is 
> > because when the Volumes are on disk, Bacula reads them as standard OS 
> > files.  libs3 is only used to move files from a local disk to and from 
> > the S3 cloud.
> >
> > Best regards,
> >
> > Kern
> >
> > On 5/10/20 3:24 PM, Sven Hartge wrote:
> >> On 10.05.20 15:01, Kern Sibbald wrote:
> >>
> >>> I agree with Sven, libs3 is a big disaster.  It works well but the
> >>> author abandoned it, and many things have changed since then.  For the
> >>> moment, we have a version that works with AWS (don't expect it to work
> >>> with a number of other S3 implementations, which are not compatible with
> >>> AWS).
> >> Adding to that: Other than the horrendous possible security flaws
> >> present in libs3 (try to compile with a recent GCC and see for yourself)
> >> the nature of anything cloud-bases is inherently volatile.
> >>
> >> The AWS-API may change at any given moment (and it has in the past),
> >> making libs3 incompatible without updates.
> >>
> >> And without an upstream author implementing those changes, your backups
> >> are more or less gone.
> >>
> >> My very pessimistic view on the situation is: Don't use any backup
> >> solution using libs3 if you value your data.
> >>
> >> But: YMMV.
> >>
> >> Grüße,
> >> Sven.
> >>
> >>
> >>
> >> ___
> >> 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
> 


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

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[Josh Fisher]

On 5/11/2020 7:38 AM, Kern Sibbald wrote:


Hello Sven,

I share your concerns, but here are a few mitigating factors:

1. I am not aware of any other C/C++ S3 library that will do the same 
job and is well maintained.  I have to admit I have not looked 
recently, so any suggestions would be welcome.




I'm not aware of other C libraries either, but why not use AWS CLI 
high-level commands in much the same way that tape autochanger script 
commands are implemented? AWS CLI is actively maintained by Amazon and 
so shouldn't  have the maintenance issues. These are simple mv, cp, ls, 
etc. commands somewhat equivalent to their Unix command namesakes. They 
shouldn't change even when/if Amazon changes the underlying S3 protocols.



2. Bacula Systems actively uses libs3 with its customers, and any 
corrections that they make will also be in the Bacula community libs3 
git repo (under the same GNU Lesser V3 license)


3. Amazon (or other s3 supplier's) tools can be used to restore Bacula 
S3 Volumes to disk, and once that is done, Bacula can read those 
volumes regardless of what S3 library it is linked with.  This is 
because when the Volumes are on disk, Bacula reads them as standard OS 
files.  libs3 is only used to move files from a local disk to and from 
the S3 cloud.


Best regards,

Kern

On 5/10/20 3:24 PM, Sven Hartge wrote:

On 10.05.20 15:01, Kern Sibbald wrote:


I agree with Sven, libs3 is a big disaster.  It works well but the
author abandoned it, and many things have changed since then.  For the
moment, we have a version that works with AWS (don't expect it to work
with a number of other S3 implementations, which are not compatible with
AWS).

Adding to that: Other than the horrendous possible security flaws
present in libs3 (try to compile with a recent GCC and see for yourself)
the nature of anything cloud-bases is inherently volatile.

The AWS-API may change at any given moment (and it has in the past),
making libs3 incompatible without updates.

And without an upstream author implementing those changes, your backups
are more or less gone.

My very pessimistic view on the situation is: Don't use any backup
solution using libs3 if you value your data.

But: YMMV.

Grüße,
Sven.



___
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
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[Kern Sibbald]

  
  
Hello Sven,
I share your concerns, but here are a few mitigating factors:
1. I am not aware of any other C/C++ S3 library that will do the
  same job and is well maintained.  I have to admit I have not
  looked recently, so any suggestions would be welcome.
2. Bacula Systems actively uses libs3 with its customers, and any
  corrections that they make will also be in the Bacula community
  libs3 git repo (under the same GNU Lesser V3 license)
3. Amazon (or other s3 supplier's) tools can be used to restore
  Bacula S3 Volumes to disk, and once that is done, Bacula can read
  those volumes regardless of what S3 library it is linked with. 
  This is because when the Volumes are on disk, Bacula reads them as
  standard OS files.  libs3 is only used to move files from a local
  disk to and from the S3 cloud.

Best regards,
Kern

On 5/10/20 3:24 PM, Sven Hartge wrote:


  On 10.05.20 15:01, Kern Sibbald wrote:


  
I agree with Sven, libs3 is a big disaster.  It works well but the
author abandoned it, and many things have changed since then.  For the
moment, we have a version that works with AWS (don't expect it to work
with a number of other S3 implementations, which are not compatible with
AWS).

  
  
Adding to that: Other than the horrendous possible security flaws
present in libs3 (try to compile with a recent GCC and see for yourself)
the nature of anything cloud-bases is inherently volatile.

The AWS-API may change at any given moment (and it has in the past),
making libs3 incompatible without updates.

And without an upstream author implementing those changes, your backups
are more or less gone.

My very pessimistic view on the situation is: Don't use any backup
solution using libs3 if you value your data.

But: YMMV.

Grüße,
Sven.


  
  
  
  
  ___
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] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[Radosław Korzeniewski]

Hello,

niedz., 10 maj 2020 o 00:01 r0...@nxlplyx.com 
napisał(a):

> Hi Radoslaw,
>
> Thank you for the reply.  I disabled AFS in the configuration and avoided
> the AFS variable compilation errors.
>
> Unfortunately, I am now getting S3 driver compilation errors.
>
> It is the S3 modules that I need.  This may help explain why I have not
> been able to get the S3 module of Bacula 9.6.3 to work in for Ubuntu 18.04.
>
> Can anyone help?
>
What s3 library do you use during Bacula build? You have to use the
library provided by Bacula project. Others won't work.

best regards


> -
>
> LT Compiling tape_dev.c
> LT Compiling vtape_dev.c
> Making libbacsd.la ...
> /home/user1/dirNFS/sw/bacula_9.6.3/bacula-9.6.3/libtool --silent --tag=CXX
> --mode=link /usr/bin/g++-o libbacsd.la \
>acquire.lo ansi_label.lo askdir.lo autochanger.lo block.lo
> block_util.lo butil.lo dev.lo device.lo ebcdic.lo init_dev.lo label.lo
> lock.lo match_bsr.lo mount.lo null_dev.lo os.lo parse_bsr.lo read.lo
> read_records.lo record_read.lo record_util.lo record_write.lo reserve.lo
> scan.lo sd_plugins.lo spool.lo tape_alert.lo tape_worm.lo vol_mgr.lo
> wait.lo fifo_dev.lo file_dev.lo tape_dev.lo vtape_dev.lo \
>   -export-dynamic -rpath /opt/bacula/lib -release 9.6.3
> LT Compiling cloud_dev.c
> LT Compiling cloud_parts.c
> LT Compiling cloud_transfer_mgr.c
> LT Compiling s3_driver.c
> s3_driver.c: In member function 'virtual bool s3_driver::init(JCR*,
> cloud_dev*, DEVRES*)':
> s3_driver.c:561:10: error: 'S3BucketContext {aka struct S3BucketContext}'
> has no member named 'authRegion'
> s3ctx.authRegion = cloud->region;
>   ^~
> Makefile:211: recipe for target 's3_driver.lo' failed
> make[1]: *** [s3_driver.lo] Error 1
> make[1]: Leaving directory
> '/home/user1/dirNFS/sw/bacula_9.6.3/bacula-9.6.3/src/stored'
>
>
>   == Error in
> /home/user1/dirNFS/sw/bacula_9.6.3/bacula-9.6.3/src/stored ==
>
> -
>
>
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>


-- 
Radosław Korzeniewski
rados...@korzeniewski.net
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[Sven Hartge]

On 10.05.20 15:01, Kern Sibbald wrote:

> I agree with Sven, libs3 is a big disaster.  It works well but the
> author abandoned it, and many things have changed since then.  For the
> moment, we have a version that works with AWS (don't expect it to work
> with a number of other S3 implementations, which are not compatible with
> AWS).

Adding to that: Other than the horrendous possible security flaws
present in libs3 (try to compile with a recent GCC and see for yourself)
the nature of anything cloud-bases is inherently volatile.

The AWS-API may change at any given moment (and it has in the past),
making libs3 incompatible without updates.

And without an upstream author implementing those changes, your backups
are more or less gone.

My very pessimistic view on the situation is: Don't use any backup
solution using libs3 if you value your data.

But: YMMV.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[Kern Sibbald]

  
  
Hello,
Please permit me to make a small correction to what Sven said. 
  The libs3 that is needed is indeed updated from the version
  released on Debian and Ubuntu, but it supplied by the Bacula
  Community (i.e. Kern) rather than Bacula Systems.  A working
  version can be found on the bacula web site at:
https://www.bacula.org/downloads/libs3-20181010.tar.gz
I have also pushed what is probably a more recent version of this
  library to the public git repo named libs3.git on www.bacula.org. 
  You can access it similarly to the way you access the current
  bacula.git repository.  Note: I have not personally tested this
  version of libs3.
I agree with Sven, libs3 is a big disaster.  It works well but
  the author abandoned it, and many things have changed since then. 
  For the moment, we have a version that works with AWS (don't
  expect it to work with a number of other S3 implementations, which
  are not compatible with AWS).
Best regards,
Kern

On 5/10/20 11:04 AM, Sven Hartge wrote:


  On 09.05.20 22:48, r0...@nxlplyx.com wrote:


  
It is the S3 modules that I need.  This may help explain why I have not
been able to get the S3 module of Bacula 9.6.3 to work in for Ubuntu 18.04.

  
  
To get the S3 driver working, you need the special libs3 provided by
Bacula systems. The libs3 included in Ubuntu (and Debian) will not work.

(This is also why the Debian and Ubuntu packages don't include the S3
driver in the first place, because of the whole disaster that is libs3
to begin with.)

Grüße,
Sven.


  
  
  
  
  ___
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] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[Sven Hartge]

On 09.05.20 22:48, r0...@nxlplyx.com wrote:

> It is the S3 modules that I need.  This may help explain why I have not
> been able to get the S3 module of Bacula 9.6.3 to work in for Ubuntu 18.04.

To get the S3 driver working, you need the special libs3 provided by
Bacula systems. The libs3 included in Ubuntu (and Debian) will not work.

(This is also why the Debian and Ubuntu packages don't include the S3
driver in the first place, because of the whole disaster that is libs3
to begin with.)

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[r0...@nxlplyx.com]

Hi Radoslaw,

Thank you for the reply.  I disabled AFS in the configuration and
avoided the AFS variable compilation errors. 

Unfortunately, I am now getting S3 driver compilation errors.

It is the S3 modules that I need.  This may help explain why I have not
been able to get the S3 module of Bacula 9.6.3 to work in for Ubuntu 18.04.

Can anyone help?

-

LT Compiling tape_dev.c
LT Compiling vtape_dev.c
Making libbacsd.la ...
/home/user1/dirNFS/sw/bacula_9.6.3/bacula-9.6.3/libtool --silent
--tag=CXX --mode=link /usr/bin/g++    -o libbacsd.la \
   acquire.lo ansi_label.lo askdir.lo autochanger.lo block.lo
block_util.lo butil.lo dev.lo device.lo ebcdic.lo init_dev.lo label.lo
lock.lo match_bsr.lo mount.lo null_dev.lo os.lo parse_bsr.lo read.lo
read_records.lo record_read.lo record_util.lo record_write.lo reserve.lo
scan.lo sd_plugins.lo spool.lo tape_alert.lo tape_worm.lo vol_mgr.lo
wait.lo fifo_dev.lo file_dev.lo tape_dev.lo vtape_dev.lo \
  -export-dynamic -rpath /opt/bacula/lib -release 9.6.3
LT Compiling cloud_dev.c
LT Compiling cloud_parts.c
LT Compiling cloud_transfer_mgr.c
LT Compiling s3_driver.c
s3_driver.c: In member function 'virtual bool s3_driver::init(JCR*,
cloud_dev*, DEVRES*)':
s3_driver.c:561:10: error: 'S3BucketContext {aka struct
S3BucketContext}' has no member named 'authRegion'
    s3ctx.authRegion = cloud->region;
  ^~
Makefile:211: recipe for target 's3_driver.lo' failed
make[1]: *** [s3_driver.lo] Error 1
make[1]: Leaving directory
'/home/user1/dirNFS/sw/bacula_9.6.3/bacula-9.6.3/src/stored'


  == Error in
/home/user1/dirNFS/sw/bacula_9.6.3/bacula-9.6.3/src/stored ==

-


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

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[Radosław Korzeniewski]

Hello,

wt., 5 maj 2020 o 02:17 r0...@nxlplyx.com  napisał(a):

> Hi,
>
> I am attempting to compile Bacula 9.6.3 on Ubuntu 18.04, but am getting
> the following errors.  Can anyone help out?
>
Yes!

Just disable AFS support in Bacula as this support was never tested after
core components refactoring. If you really want to use Bacula to AFS backup
support then I can fix compile issues with your help.

Awaiting feedback.
-- 
Radosław Korzeniewski
rados...@korzeniewski.net
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[Gary R. Schmidt]

On 05/05/2020 06:59, r0...@nxlplyx.com wrote:

Hi,

I am attempting to compile Bacula 9.6.3 on Ubuntu 18.04, but am getting 
the following errors.  Can anyone help out?


What options did you configure the build with?  And what was the output 
from configure?


Cheers,
GaryB-)


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

[Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[r0...@nxlplyx.com]

Hi,

I am attempting to compile Bacula 9.6.3 on Ubuntu 18.04, but am getting
the following errors.  Can anyone help out?

---

$ make

..

..

make[1]: Leaving directory
'/home/user1/dirNFS/sw/bacula_9.6.3/bacula-9.6.3/src/findlib'
==>Entering directory
/home/user1/dirNFS/sw/bacula_9.6.3/bacula-9.6.3/src/filed
make[1]: Entering directory
'/home/user1/dirNFS/sw/bacula_9.6.3/bacula-9.6.3/src/filed'
Compiling filed.c
Compiling authenticate.c
Compiling backup.c
Compiling crypto.c
Compiling win_efs.c
Compiling estimate.c
Compiling fdcollect.c
Compiling fd_plugins.c
Compiling accurate.c
Compiling filed_conf.c
Compiling heartbeat.c
Compiling hello.c
Compiling job.c
Compiling fd_snapshot.c
Compiling restore.c
Compiling status.c
Compiling suspend.c
Compiling verify.c
Compiling verify_vol.c
Compiling bacl.c
bacl.c: In member function ‘bRC_BACL BACL::restore_acl(JCR*, int, char*,
u_int32_t)’:
bacl.c:431:15: error: ‘STREAM_BACL_AFS_TEXT’ was not declared in this scope
  case STREAM_BACL_AFS_TEXT:
   ^~~~
bacl.c:431:15: note: suggested alternative: ‘STREAM_XACL_AFS_TEXT’
  case STREAM_BACL_AFS_TEXT:
   ^~~~
   STREAM_XACL_AFS_TEXT
bacl.c: In member function ‘bRC_BACL BACL::afs_backup_acl(JCR*, FF_PKT*)’:
bacl.c:694:19: error: ‘BUFSIZE’ was not declared in this scope
    vip.out_size = BUFSIZE;
   ^~~
bacl.c:694:19: note: suggested alternative: ‘BUFSIZ’
    vip.out_size = BUFSIZE;
   ^~~
   BUFSIZ
bacl.c:705:32: error: ‘STREAM_BACL_AFS_TEXT’ was not declared in this scope
    return send_acl_stream(jcr, STREAM_BACL_AFS_TEXT);
    ^~~~
bacl.c:705:32: note: suggested alternative: ‘STREAM_XACL_AFS_TEXT’
    return send_acl_stream(jcr, STREAM_BACL_AFS_TEXT);
    ^~~~
    STREAM_XACL_AFS_TEXT
bacl.c: In member function ‘bRC_BACL BACL::afs_restore_acl(JCR*, int)’:
bacl.c:724:23: error: ‘ff_pkt’ was not declared in this scope
    if (jcr == NULL || ff_pkt == NULL){
   ^~
bacl.c:724:23: note: suggested alternative: ‘io_pkt’
    if (jcr == NULL || ff_pkt == NULL){
   ^~
   io_pkt
Makefile:177: recipe for target 'bacl.o' failed
make[1]: *** [bacl.o] Error 1
make[1]: Leaving directory
'/home/user1/dirNFS/sw/bacula_9.6.3/bacula-9.6.3/src/filed'


  == Error in
/home/user1/dirNFS/sw/bacula_9.6.3/bacula-9.6.3/src/filed ==


Makefile:148: recipe for target 'all' failed
make: *** [all] Error 1


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