Re: [Bacula-users] MD5 Fatal Error

2024-04-12 Thread Martin Simmons
Maybe the same problem as reported in
https://sourceforge.net/p/bacula/mailman/bacula-users/thread/c3bc9fed-3c84-46d3-2f40-9dd78590a773%40baculasystems.com/#msg37296305
?

I assume the "cycle in their volume list" comment there means it is writing to
a volume that it previous read.

__Martin


> On Mon, 8 Apr 2024 11:27:20 +0200, Mohamed AIT EL HADJ via Bacula-users 
> said:
> 
> Hello,
> My backups were working fine but yesterday I had a problem with one of 
> my jobs which apparently has a problem with MD5.
> 
> Here are the job logs:
> 
> pbckall004-dir JobId 5387: Error: Unable to flush file records!
> pbckall004-dir JobId 5387: Fatal error: Error detected between 
> digest[466172]="zxdWYCUt+beniiSsYO+d6w" and 
> name[466171]="/var/opt/gitlab/gitlab-rails/shared/artifacts/12/53/1253e9373e781b7500266caa55150e08e210bc8cd8cc70d89985e3600155e860/2024_04_01/"
> pbckall004-dir JobId 5387: Fatal error: MD5 digest not same FileIndex=466172 
> as attributes FI=466171
> pbckall004-sd JobId 5387: Sending spooled attrs to the Director. Despooling 
> 237,369,878 bytes ...
> pbckall004-sd JobId 5387: Elapsed time=02:20:45, Transfer rate=7.303 M 
> Bytes/second
> pbckall004-sd JobId 5387: End of Volume "Vol0197" at addr=898996114 on device 
> "DEV-dedup-DRV19" (/zfs/bacula).
> pbckall004-sd JobId 5387: Forward spacing Volume "Vol0197" to addr=893762478
> pbckall004-sd JobId 5387: Ready to read from volume "Vol0197" on Aligned 
> device "DEV-dedup-DRV19" (/zfs/bacula).
> pbckall004-sd JobId 5387: End of Volume "Vol0165" at addr=515616168 on device 
> "DEV-dedup-DRV19" (/zfs/bacula).
> pbckall004-sd JobId 5387: New volume "Vol0159" mounted on device 
> "DEV-dedup-DRV1" (/zfs/bacula) at 07-avril-2024 18:22.
> pbckall004-sd JobId 5387: Recycled volume "Vol0159" on Aligned device 
> "DEV-dedup-DRV1" (/zfs/bacula), all previous data lost.
> pbckall004-dir JobId 5387: Using Volume "Vol0159" from 'Scratch' pool.
> pbckall004-dir JobId 5387: Recycled volume "Vol0159"
> pbckall004-dir JobId 5387: All records pruned from Volume "Vol0131"; marking 
> it "Purged"
> pbckall004-dir JobId 5387: New Pool is: Scratch
> pbckall004-dir JobId 5387: There are no more Jobs associated with Volume 
> "Vol0131". Marking it purged.
> pbckall004-dir JobId 5387: All records pruned from Volume "Vol0124"; marking 
> it "Purged"
> pbckall004-dir JobId 5387: New Pool is: Scratch
> pbckall004-dir JobId 5387: There are no more Jobs associated with Volume 
> "Vol0124". Marking it purged.
> pbckall004-dir JobId 5387: All records pruned from Volume "Vol0184"; marking 
> it "Purged"
> pbckall004-dir JobId 5387: New Pool is: Scratch
> pbckall004-dir JobId 5387: There are no more Jobs associated with Volume 
> "Vol0184". Marking it purged.
> pbckall004-dir JobId 5387: All records pruned from Volume "Vol0186"; marking 
> it "Purged"
> pbckall004-dir JobId 5387: New Pool is: Scratch
> pbckall004-dir JobId 5387: There are no more Jobs associated with Volume 
> "Vol0186". Marking it purged.
> pbckall004-dir JobId 5387: All records pruned from Volume "Vol0159"; marking 
> it "Purged"
> pbckall004-dir JobId 5387: New Pool is: Scratch
> pbckall004-dir JobId 5387: There are no more Jobs associated with Volume 
> "Vol0159". Marking it purged.
> pbckall004-sd JobId 5387: End of medium on Volume "Vol0179" 
> Bytes=53,686,844,017 Blocks=409,600 at 07-avril-2024 18:22.
> pbckall004-sd JobId 5387: User defined maximum volume size 53,687,091,200 
> will be exceeded on device "DEV-dedup-DRV1" (/zfs/bacula).    Marking Volume 
> "Vol0179" as Full.
> 
> I have no idea how this could have happened or how to resolve the error.
> 
> Any helps will be great.
> 
> Regards,
> 
> 
> 
> ___
> 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] Building the S3/Amazon options for Bacula 15

2024-04-12 Thread Dan Langille
On Fri, Apr 12, 2024, at 8:27 AM, Martin Simmons wrote:
>> On Thu, 11 Apr 2024 16:34:48 -0400, Dan Langille said:
>> 
>> A problem with building the S3 options on Bacula 15.0.2 has been reported[1] 
>> and I'm trying to figure it out. I'm not an s3 user myself, and I am the 
>> maintainer of the FreeBSD port/package.
>> 
>> When building 13.0.4, see:
>> 
>> src/stored/.libs/bacula-sd-cloud-s3-driver.so
>> src/stored/.libs/bacula-sd-cloud-s3-driver-13.0.4.so
>> 
>> When building 15.0.2, I see
>> 
>> src/stored/.libs/bacula-sd-cloud-driver.so
>> src/stored/.libs/bacula-sd-cloud-driver-15.0.2.so
>> 
>> Of note, the '-s3' part of the name has been removed. That doesn't seem to 
>> be my problem though.
>
> These are different libraries and you need both of them
> (bacula-sd-cloud-driver loads bacula-sd-cloud-s3-driver if required).  I think
> this is the same in 13.0.4.
>
>> The problem is the files do not get installed, and I'm not sure why.
>
> The build log contains:
>
> checking libs3.h usability... no
> checking libs3.h presence... no
> checking for libs3.h... no
>
> so that looke like the problem.  Where is your libs3.h?

First goal, who supplies that?

Searching at https://www.freshports.org by pkg-plist, I find 
sysutils/bacula-libs3

How is that used:

[12:30 pkg01 dvl ~/ports/head/sysutils] % grep -r bacula-libs3 bacula*  

bacula11-server/Makefile:LIB_DEPENDS+=  libs3.so:sysutils/bacula-libs3
bacula13-server/Makefile:LIB_DEPENDS+=  libs3.so:sysutils/bacula-libs3
bacula15-server/Makefile:MS3_LIB_DEPENDS=   libs3.so:sysutils/bacula-libs3

Interesting how it's MS3 for 15, and S3 for 11 and 13. I have only myself to 
blame and I have no idea why it's like that.

It appears to be cruft leftover from my mangled transformation from "if 
${PORT_OPTIONS:MS3}" to modern methods.

compare old and new:

https://cgit.freebsd.org/ports/tree/sysutils/bacula13-server/Makefile#n135
https://cgit.freebsd.org/ports/tree/sysutils/bacula15-server/Makefile#n136

Doing this change allowed the build:

[14:41 pkg01 dvl ~/ports/head/sysutils/bacula15-server] % git diff .
diff --git a/sysutils/bacula15-server/Makefile 
b/sysutils/bacula15-server/Makefile
index 6e7aec421cd7..a9d84c4720a0 100644
--- a/sysutils/bacula15-server/Makefile
+++ b/sysutils/bacula15-server/Makefile
@@ -133,10 +133,10 @@ MTX_RUN_DEPENDS=  ${LOCALBASE}/sbin/mtx:misc/mtx
 
 .endif
 
-.include 
+S3_CONFIGURE_ARGS= --enable-s3
+S3_LIB_DEPENDS=libs3.so:sysutils/bacula-libs3
 
-MS3_CONFIGURE_ARGS=--enable-s3
-MS3_LIB_DEPENDS=   libs3.so:sysutils/bacula-libs3
+.include 
 
 .if defined(WITH_CLIENT_ONLY)
 MP8+=  bacula.8 bacula-fd.8 bconsole.8

Now I find:

root@140amd64-dvl-primary:/wrkdirs/usr/ports/sysutils/bacula15-server/work # 
find . -name bacula-sd-cloud-s3-driver.so
./stage/usr/local/lib/bacula-sd-cloud-s3-driver.so
./bacula-15.0.2/src/stored/.libs/bacula-sd-cloud-s3-driver.so

Thanks for help me find my own error. I'll pass this onto the user for testing.

-- 
  Dan Langille
  d...@langille.org


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


Re: [Bacula-users] Building the S3/Amazon options for Bacula 15

2024-04-12 Thread Martin Simmons
> On Thu, 11 Apr 2024 16:34:48 -0400, Dan Langille said:
> 
> A problem with building the S3 options on Bacula 15.0.2 has been reported[1] 
> and I'm trying to figure it out. I'm not an s3 user myself, and I am the 
> maintainer of the FreeBSD port/package.
> 
> When building 13.0.4, see:
> 
> src/stored/.libs/bacula-sd-cloud-s3-driver.so
> src/stored/.libs/bacula-sd-cloud-s3-driver-13.0.4.so
> 
> When building 15.0.2, I see
> 
> src/stored/.libs/bacula-sd-cloud-driver.so
> src/stored/.libs/bacula-sd-cloud-driver-15.0.2.so
> 
> Of note, the '-s3' part of the name has been removed. That doesn't seem to be 
> my problem though.

These are different libraries and you need both of them
(bacula-sd-cloud-driver loads bacula-sd-cloud-s3-driver if required).  I think
this is the same in 13.0.4.

> The problem is the files do not get installed, and I'm not sure why.

The build log contains:

checking libs3.h usability... no
checking libs3.h presence... no
checking for libs3.h... no

so that looke like the problem.  Where is your libs3.h?

__Martin


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