Hello Martin, Thanks! I should have mentioned that earlier. All my tests were using the bacula.org packages. I don't have to build packages from source anymore. Thanks, bacula.org. 😆
Rgds. -- MSc Heitor Faria (Miami/USA) CEO Bacula LatAm mobile1: + 1 909 655-8971 mobile2: + 55 61 98268-4220 América Latina [ http://bacula.lat/] -------- Original Message -------- From: Martin Simmons <mar...@lispworks.com> Sent: Friday, May 7, 2021 06:35 AM To: Heitor Faria <hei...@bacula.com.br> Subject: Re: [Bacula-users] S3 "Driver" Doesn't Work 11.0.2 CC: k...@sibbald.com,jim joyce <jim.jo...@vecna.com>,sru...@gemneye.org,bacula-users@lists.sourceforge.net >That failure to find BaculaCloudDriver is not surprising. The >bacula-sd-cloud-driver-11.0.2.so is a "SD" driver, but the code in cloud_dev.c >is looking for a "Cloud" driver. You need both to make S3 work. > >I suggest checking bacula/src/stored/Makefile in your build to see the value >of CLOUD_INSTALL_TARGETS. If it is empty then you have not configured the S3 >driver. > >__Martin > > >>>>>> On Thu, 6 May 2021 20:22:15 -0300 (BRT), Heitor Faria said: >> >> Hello Kern, >> >> Move is not enough because the SD is looking for the plugin with both >> different names (don't ask me why). >> However, I was able to load the driver and receive a different message >> before the "not loaded message": >> >> cp /opt/bacula/plugins/bacula-sd-cloud-driver-11.0.2.so >> /opt/bacula/plugins/bacula-sd-cloud-s3-driver-11.0.2.so >> >> And the debug: >> >> baculacommunity-sd: init_dev.c:481-0 Open SD driver at >> /opt/bacula/plugins/bacula-sd-cloud-driver-11.0.2.so >> baculacommunity-sd: init_dev.c:484-0 Driver=cloud handle=7fd6d400ba20 >> baculacommunity-sd: init_dev.c:486-0 Lookup "BaculaSDdriver" in driver=cloud >> baculacommunity-sd: init_dev.c:488-0 Driver=cloud entry point=7fd6e062c4d0 >> baculacommunity-sd: cloud_dev.c:876-0 Open SD driver at >> /opt/bacula/plugins/bacula-sd-cloud-s3-driver-11.0.2.so >> baculacommunity-sd: cloud_dev.c:879-0 Driver=s3 handle=7fd6d400cec0 >> baculacommunity-sd: cloud_dev.c:881-0 Lookup "BaculaCloudDriver" in >> driver=s3 >> baculacommunity-sd: cloud_dev.c:883-0 Driver=s3 entry point=0 >> baculacommunity-sd: cloud_dev.c:889-0 Lookup of symbol "BaculaCloudDriver" >> driver=/opt/bacula/plugins/bacula-sd-cloud-s3-driver-11.0.2.so failed: >> ERR=/opt/bacula/plugins/bacula-sd-cloud-s3-driver-11.0.2.so: undefined >> symbol: BaculaCloudDriver >> baculacommunity-sd: message.c:1831-0 cloud_dev.c:1001 Could not open Cloud >> driver type=1 for Device=AWS-Drive-0. >> baculacommunity-sd: message.c:1831-0 cloud_dev.c:1032 Cloud driver >> initialization error Cloud driver not properly loaded >> >> Ref.: [ https://bugs.bacula.org/view.php?id=2615 | >> https://bugs.bacula.org/view.php?id=2615 ] >> >> Regards, >> >> > From: "kern" <k...@sibbald.com> >> > To: "Jim Joyce" <jim.jo...@vecna.com>, "Heitor Faria" >> > <hei...@bacula.com.br>, >> > "sruckh" <sru...@gemneye.org> >> > Cc: "bacula-users" <bacula-users@lists.sourceforge.net> >> > Sent: Thursday, May 6, 2021 12:01:41 PM >> > Subject: Re: [Bacula-users] S3 "Driver" Doesn't Work 11.0.2 >> >> > Hello, >> >> > 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 debs >> >> libs3 version and installation commands >> >> cd libs3-20200523 >> >> make deb >> >> cd build/pkg >> >> dpkg -i libs3_4.1.bac_amd64.deb >> >> root@backup:~/libs3-20200523/build/pkg# apt show libs3 >> >> Package: libs3 >> >> Version: 4.1.bac >> >> Status: install ok installed >> >> operating system exact version >> >> cat /etc/debian_version >> >> 10.9 >> >> bacula-sd -d 200 loading debug output >> >> root@backup:/opt/bacula/bin# ./bacula-sd -d 200 >> >> root@backup:/opt/bacula/bin# bacula-sd: address_conf.c:274-0 Initaddr >> >> 0.0.0.0:9103 >> >> backup-sd: jcr.c:131-0 read_last_jobs seek to 192 >> >> backup-sd: jcr.c:138-0 Read num_items=2 >> >> backup-sd: plugins.c:97-0 load_plugins >> >> backup-sd: plugins.c:133-0 Rejected plugin: want=-sd.so name=bpipe-fd.so >> >> len=11 >> >> backup-sd: plugins.c:133-0 Rejected plugin: want=-sd.so >> >> name=bacula-sd-cloud-driver-9.6.7.so len=31 >> >> backup-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 [ mailto:hei...@bacula.com.br | <hei...@bacula.com.br> >> >> ] >> >> Sent: Monday, May 3, 2021 7:09 PM >> >> To: sruckh [ mailto:sru...@gemneye.org | <sru...@gemneye.org> ] >> >> Cc: bacula-users [ mailto:bacula-users@lists.sourceforge.net | >> >> <bacula-users@lists.sourceforge.net> ] >> >> Subject: Re: [Bacula-users] S3 "Driver" Doesn't Work 11.0.2 >> >> >>>> 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 | >> >>>> 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. >> >> Hello Sruckh: the error you reported is different from the OP. >> >> 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 >> >> [ https://www.linkedin.com/in/msc-heitor-faria-5ba51b3 ] >> >> [ http://www.bacula.com.br/ ] >> >> >> América Latina >> >> [ http://bacula.lat/ | bacula.lat ] | [ http://www.bacula.com.br/ | >> >> bacula.com.br ] >> >> >> _______________________________________________ >> >> Bacula-users mailing list [ mailto:Bacula-users@lists.sourceforge.net | >> >> Bacula-users@lists.sourceforge.net ] [ >> >> https://lists.sourceforge.net/lists/listinfo/bacula-users | >> >> https://lists.sourceforge.net/lists/listinfo/bacula-users ] >> >> -- >> >> MSc Heitor Faria (Miami/USA) >> Bacula LATAM CEO >> >> mobile1: + 1 909 655-8971 >> mobile2: + 55 61 98268-4220 >> [ https://www.linkedin.com/in/msc-heitor-faria-5ba51b3 ] >> [ http://www.bacula.com.br/ ] >> >> América Latina >> [ http://bacula.lat/ | bacula.lat ] | [ http://www.bacula.com.br/ | >> bacula.com.br ] >>
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users