On 2019-09-02 10:53, sruckh--- via Bacula-users wrote:
I am using bacula v9.4.4 community edition on CentOS 7 server.
I am trying to use minio to send backup to backblaze storage.
From the logs it looks like quite a few hiccups occur with messages
similar to this:
msg=S3_put_object ERR=ConnectionFailed
At the very end of the backup log file there is a message like this:
Termination: Backup OK -- Upload to Cloud failed
When looking at the smaller "part" files that make up a volume on the
backblaze server, the parts that had errors in the log message appear
to have 2 revisions of the file and the total file size of that part
to be roughly double of the designated size of the part. I assume
this not to be horribly abnormal as I assume the part is uploaded
twice. Although the bacula log file does not really say that the
volume was re-uploaded, I am just guessing that is what happens.
Anyway, to be safe, I thought it might make sense to use the "cloud"
functions from bconsole to sync the volume to the cloud. When I
choose the "cloud" option and choose the appropriate storage, pool,
and volume, it looks like the upload is unsuccessful and the following
error is given:
3999 Error with the upload: ERR=SignatureDoesNotMatch
As far as I can tell, that may be a minio/aws error, and I can't find
anything necessarily related to bacula with the error.
Is anyone here familiar with this error, and know the resolution?
Thank You.
Not sure if this is helpful, but this is what shows up in the minio
trace log when trying to perform upload function from bacula:
21:48:51.145 [200 OK] s3.ListObjectsV1
localhost:9000/BucketName/?prefix=B2-Vol-1101 127.0.0.1
21:48:51.543 [403 Forbidden] s3.ListObjectsV1
localhost:9000/BucketName/?prefix=B2-Vol-1101&marker=B2-Vol-1101/part.1901%20
127.0.0.1
So I do not know why the [403 Forbidden] message.
That "part" file in question, part.1901, appears to be present on the
remote B2 storage and is the correct file size
[2019-09-02 02:08:40 MST] 10MiB part.1901
I notice the %20 [space] at the end of the filename in the trace
message. I am wondering if that has anything to do with the issue, or
if that is normal.
Also, the part.1901 file is not one of the files that had one of the
"connectionfailed" errors mentioned in earlier post, so not entirely
sure if the 1901 file is relevant to the actual problem or not or just
coincidental.
If I run the same bacula upload test but on a different volume, this is
the result from the trace log:
22:05:52.176 [200 OK] s3.ListObjectsV1
localhost:9000/BucketName/?prefix=B2-Vol-1100 127.0.0.1
22:05:52.691 [403 Forbidden] s3.ListObjectsV1
localhost:9000/BucketName/?prefix=B2-Vol-1100&marker=B2-Vol-1100/part.1907%20
127.0.0.1
So the same [403 Forbidden] error message, with the same %20 at the end
of the file name, but the part file is 1907 as opposed to 1901.
The MD5SUM of the local file and the remote file on the B2 storage
calculate to the same value.
I don't know if this is a bug between bacula<-->minio or if this is an
admin issue.
Any assistance appreciated.
Thank You.
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
