On 2021-04-30 09:23, Heitor Faria wrote:
Hello,
If you read the email thread, I was not asking for technical help. I
was simply asking if anyone has had success with the S3 plugin. With
the lack of responses, I can only assume nobody has got it working.
Of course. After less than 20 hours from the original post that was the
only possible assumption. I guess everyone have to, voluntarily and
promptly, provide the answers that you need.
Which means the plugin does not work, so it should be removed from the
repo.
I personally know at least 10 administrators that use the CBacula 9/11
version Cloud driver in different sectors. It also works in one of my
lab machines:
I am running bacula 9.6.7 on CentOS 7 where the packages came from
https://bacula.org/packages/xxxxxxxxxxxxx/rpms/9.6.7/el7/x86_64/ . In
my case the S3 drivers seemed to stop working after 9.6.5 (if I remember
correctly. It was a couple of versions ago when it stopped working).
With the current packages, bacula-mysql-9.6.7-1.el7.x86_64,
bacula-aligned-9.6.7-1.el7.x86_64,
bacula-cloud-storage-9.6.7-1.el7.x86_64, and
bacula-libs-9.6.7-1.el7.x86_64, the S3LIB files (discussed in this
thread earlier) are provided by package bacula-cloud-storage. The
libs3.so.4 file gets installed in /opt/bacula/lib64/. The problem being
that if you do a ldd on
/opt/bacula/plugins/bacula-sd-cloud-driver-9.6.7.so it shows it uses,
libs3.so.4, but that it is missing. So I tried to create the file
/etc/ld.so.conf.d/bacula.conf and added /opt/bacula/lib64 path to the
file and ran ldconfig to rebuild the cache. By doing this, running ldd
on bacula-sd-cloud-driver-9.6.7.so now shows libs3.so.4 coming from
/opt/bacula/lib64.
Unfortunately, even with this change, a configuration that used to work
fine in older versions of bacula, no longer work in the current version
installed. The S3 drivers seems to load, but I ultimately end up with
this error: 3999 Error with the upload: ERR=RequestTorrentOfBucketError
.
On a hunch, I went ahead and built an RPM package from the link provided
earlier in the thread for the libs3 library. I went ahead and installed
this RPM after building it and the libs3.so.4 file is now in /usr/lib/ .
I went ahead and removed the /etc/ld.so.conf.d/bacula.conf, and again
rebuilt the cache with ldconfig. Now when running ldd on
bacula-sd-cloud-driver-9.6.7.so the libs3.so.4 now shows to be coming
from /usr/lib/ .
Unfortunately, I get the same error as before. This time, I just went
into bconsole, and tried to use the cloud command to upload the volume.
After a few minutes the bconsole command times out with the exact error
mentioned above that is received when trying to perform a backup.
This exact configuration used to work going straight to S3 cloud bucket,
and also when using minio as a middle-man to go to Backblaze storage
before they supported native S3 commands.
So, in my experience, the S3 cloud plugin has not worked for me after
something changed from an older version._______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
