Though I am "mostly" retired, I thought I might respond to some of your points.
First, I am sorry you are having problems building the S3 plugin.
The Bacula project does test a lot, and puts out source code prior to release in many cases, so that users can test it and report any problems.
The one thing that Bacula does not do is test every build option possible -- there are probably thousands of different OS, library, and build (deb, rpm, ...) permutations, any one of which could have difficulties.
You asked in a previous email why we don't test on Ubuntu. Well all the initial development and testing of the S3 plugin was done on Ubuntu. I can testify to that because I am the Bacula developer who did it -- this message is being written on a Ubuntu 20.-4 system :-)
In your case, I see that you are doing a number of build operations that can lead to minor problems because of OS specific scripting for debs and such. Normally, Bacula developers build and install the libs3 directly. You are creating (apparently) a libs3 debs package -- that is something that Bacula developers never do and have never tested.
Your fundamental problem in making the S3 plugin work is that plugin has the wrong name -- this can be seen from the -D200 debug output you supplied. The Bacula SD is looking for plugins named: xxx-sd.so, and your plugin is named xxx.so, so Bacula is not finding it.
There is a reasonable possibility that if you simply rename your plugin from xxx.so to xxx-sd.so (I am assuming you know how to replace xxx with the correct name), the plugin *might* work.
If you would like to get reasonable answers from this list, it might help if you would remember that this is free software that relies on community participation.
One last thing: I take issue with your statements about Bacula Systems. Bacula Systems binaries are heavily tested, and they do work. In the off chance they don't the company will quickly (usually within a day or two) build new binaries that do work. I do not mean to imply that you or anyone else must buy a Bacula Systems subscription to get working software. However, I do think it likely that at some point a Bacula Systems developer will probably see this problem and fix it or explain the build problem.
Good luck,
Kern
On 5/5/21 3:55 AM, Jim Joyce wrote:
As you can see, nobody except imaginary super admins have been able to load the S3 plug-in. IT DOES NOT WORK. I implore the community to demand the code & package be rescinded from the repo until somebody with magical coding prowess can get it to work. Community users are wasting their time and energy on something that will not work unless you fork the darn thing and start all over again!
bacula.org package versions you are trying to install.9.6.7 debslibs3 version and installation commandscd libs3-20200523
make debcd build/pkgdpkg -i libs3_4.1.bac_amd64.debroot@backup:~/libs3-20200523/build/pkg# apt show libs3Package: libs3Version: 4.1.bacStatus: install ok installedoperating system exact versioncat /etc/debian_version
10.9bacula-sd -d 200 loading debug outputroot@backup:/opt/bacula/bin# ./bacula-sd -d 200root@backup:/opt/bacula/bin# bacula-sd: address_conf.c:274-0 Initaddr 0.0.0.0:9103backup-sd: jcr.c:131-0 read_last_jobs seek to 192backup-sd: jcr.c:138-0 Read num_items=2backup-sd: plugins.c:97-0 load_pluginsbackup-sd: plugins.c:133-0 Rejected plugin: want=-sd.so name=bpipe-fd.so len=11backup-sd: plugins.c:133-0 Rejected plugin: want=-sd.so name=bacula-sd-cloud-driver-9.6.7.so len=31backup-sd: plugins.c:121-0 Failed to find any plugins in /opt/bacula/plugins...
root@backup:/opt/bacula/plugins# ls
bacula-sd-cloud-driver-9.6.7.so bpipe-fd.so
steps to reproduce the error.Install 9.6.7, install S3 lib hack, define a storage device using the S3 driver in bacula-sd.conf. Volia! Get the dreaded "driver not loaded" error.
From: Heitor Faria <hei...@bacula.com.br>
Sent: Monday, May 3, 2021 7:09 PM
To: sruckh <sru...@gemneye.org>
Cc: bacula-users <bacula-users@lists.sourceforge.net>
Subject: Re: [Bacula-users] S3 "Driver" Doesn't Work 11.0.2Hello Sruckh: the error you reported is different from the OP.Despite of the not-working testimonials in this thread, until now I see no related bug reports in the Bacula bug tracker: https://bugs.bacula.org/view_all_bug_page.php
IMHO it would be of great help if you could make the bug reports with the maximum details, such as:- bacula.org package versions you are trying to install.- libs3 version and installation commands- operating system exact version- bacula-sd -d 200 loading debug output- steps to reproduce the error.I believe this is the fastest way of the bacula.org team to address this problem properly.Regards,Problem has been reported.
For everyone also having the: "Apr 27 20:59:59 backup bacula-sd[498]: cloud_dev.c:1001 Could not open Cloud driver type=1 for Device=xxxx.", you are encouraged also to full a bug report.Thank You.
Regards,
--
MSc Heitor Faria (Miami/USA)
Bacula LATAM CEO
mobile1: + 1 909 655-8971
mobile2: + 55 61 98268-4220
América Latina bacula.lat | bacula.com.br
_______________________________________________ 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