Re: What does this error mean?

--uCsDZuOxeiZLZ20B
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Aug 01, 2024 at 12:39:46AM -0400, Robert Heller wrote:
>=20
> Any clue as to a "release date"?

The work is done and the new amanda 3.5.4 is on Debian for v13.  My
email of notice did not reach the mailing list.

I can give instructions on how to compile the packages for v12, but I
do not have computers for other CPUs than intel.


Kind regards
Jose M Calhariz




>=20
> At Tue, 23 Jul 2024 03:07:37 +0100 Jose M Calhariz <jose.calhariz@tecnico=
=2Eulisboa.pt> wrote:
>=20
> >
> > Hi,
> >
> > Currently I do not have a setup with S3 at amanda, so this kind of
> > problems are under my radar. I think it broke with the upgrade to
> > Debian v12 and some security updates for Debian v11.  Can anyone
> > confirm or deny?
> >
> > I am currently working on updating amanda for Debian v13 so later I
> > can provide non official packages for Debian v12 of an updated amanda,
> > possibly 3.5.4.
> >
> >
> > Kind regards
> > Jose M Calhariz
> >
> >
> > On Mon, Jul 22, 2024 at 01:49:21PM -0400, Robert Heller wrote:
> > > I opened an issue: https://github.com/zmanda/amanda/issues/259
> > >
> > > I uploaded the *working* configs for Amanda 3.3.3 under CentOS 7.  Th=
e 3.3.3
> > > configuation is not liked by Amanda 3.5.1 under Debian 12 (not suppri=
sing). I
> > > *think* I updated the configs for 3.5.1 correctly (can anyone check?).
> > >
> > > I don't know if this is a bug in Amanda 3.5 or if I have something wr=
ong.
> > >
> > > At Mon, 22 Jul 2024 18:24:28 +0200 Exuvo <[email protected]> wrote:
> > >
> > > >
> > > > You can try enabling the "device-property VERBOSE" and see if the l=
ogs show anything useful.
> > > >
> > > > Anton "exuvo" Olsson
> > > >     [email protected]
> > > >
> > > > On 2024-07-22 18:21, Robert Heller wrote:
> > > > >
> > > > > At Mon, 22 Jul 2024 18:00:16 +0200 Exuvo <[email protected]> wrote:
> > > > >
> > > > >> According to man amanda-changers the device properties can be sp=
ecified in
> > > > >> multiple places so where you have them should also work.
> > > > > I don't think that is the problem.  According to this:
> > > > >
> > > > > https://stackoverflow.com/questions/30518899/amazon-s3-how-to-fix=
-the-request-signature-we-calculated-does-not-match-the-s
> > > > >
> > > > > The problem might be the pathname going to Amazon is bad (leading=
 . or leading
> > > > > /), but *I* am not using either, so I guess Amanda is messing up =
the
> > > > > "signature" somehow.  So this might be a bug?  This used to work =
with Amanda
> > > > > 3.3, so it might be something broke in 3.4 or 3.5.
> > > > >
> > > > > (I've also opened an issue on github.)
> > > > >
> > > > > And I think the "tapedev" is indicated by the
> > > > >      tpchanger "chg-multi:s3:sharky5-backups/slot-{00..40}"
> > > > > line: it is a changer on an Amazon s3 device with with a Bucket of
> > > > > sharky5-backups, with slots slot-00 through slot-40.
> > > > >
> > > > >> Anton "exuvo" Olsson
> > > > >>      [email protected]
> > > > >>
> > > > >> On 2024-07-22 17:19, Robert Heller wrote:
> > > > >>> At Mon, 22 Jul 2024 17:10:23 +0200 Exuvo <[email protected]> wrote:
> > > > >>>
> > > > >>>> Never used S3 but dont you need to use a "tapdev" line and dev=
ice properties on that instead of on the changer?
> > > > >>>> See man amanda-devices S3 Device
> > > > >>> No, that does not work.  Get a config file syntax error...   Th=
e docs are
> > > > >>> somewhat wrong.
> > > > >>>
> > > > >>>> Anton "exuvo" Olsson
> > > > >>>>       [email protected]
> > > > >>>>
> > > > >>>> On 2024-07-22 14:24, Robert Heller wrote:
> > > > >>>>> backup@sharky5:~$ amcheck sharky5
> > > > >>>>> Amanda Tape Server Host Check
> > > > >>>>> -----------------------------
> > > > >>>>> NOTE: tapelist file does not exists
> > > > >>>>>          it will be created on the next run
> > > > >>>>> NOTE: Holding disk '/var/lib/amanda/holdings/sharky5': 38816 =
MB disk space available, using 12000 MB as requested
> > > > >>>>> slot 1: While creating new S3 bucket: The request signature w=
e calculated does not match the signature you provided. Check your key and =
signing method. (SignatureDoesNotMatch) (HTTP 403)
> > > > >>>>> slot 2: While creating new S3 bucket: The request signature w=
e calculated does not match the signature you provided. Check your key and =
signing method. (SignatureDoesNotMatch) (HTTP 403)
> > > > >>>>>
> > > > >>>>> backup@sharky5:~$ cat /etc/amanda/sharky5/amanda.conf
> > > > >>>>> org "Deepwoods Software Sharky5"        # your organization n=
ame for reports
> > > > >>>>> mailto "[email protected]"    # space separated list of ope=
rators at your site
> > > > >>>>> dumpcycle 28 days       # the number of days in the normal du=
mp cycle
> > > > >>>>> runspercycle 28          # the number of amdump runs in dumpc=
ycle days
> > > > >>>>>                            # (1 week * 5 amdump runs per week=
 -- just weekdays)
> > > > >>>>> tapecycle 40 tapes      # the number of tapes in rotation
> > > > >>>>>                            # 1 week (dumpcycle) times 5 tapes=
 per week (just
> > > > >>>>>                            # the weekdays) plus a few to hand=
le errors that
> > > > >>>>>                            # need amflush and so we do not ov=
erwrite the full
> > > > >>>>>                            # backups performed at the beginni=
ng of the previous
> > > > >>>>>                            # cycle
> > > > >>>>> runtapes 3              # number of tapes to be used in a sin=
gle run of amdump
> > > > >>>>>
> > > > >>>>> define changer my_s3 {
> > > > >>>>>        tpchanger "chg-multi:s3:sharky5-backups/slot-{00..40}"
> > > > >>>>>        device-property "S3_ACCESS_KEY" "XXXXXXXXXXXXXXXXXXXXX=
X"
> > > > >>>>>        device-property "S3_SECRET_KEY" 'xxxxxxxxxxxxxxxxxxxxx=
xxxxx"
> > > > >>>>>        device-property "NB_THREADS_BACKUP" "3"
> > > > >>>>> #    changerfile "/etc/amanda/sharky5/changer.conf"
> > > > >>>>> }
> > > > >>>>> tpchanger "my_s3"
> > > > >>>>> tapetype S3     # what kind of tape it is (see tapetypes belo=
w)
> > > > >>>>>
> > > > >>>>>
> > > > >>>>> I am sure the S3_ACCESS_KEY and S3_SECRET_KEY are correct.
> > > > >>>>>
> > > > >>>>
> > > > >>>>
> > > > >>
> > > > >>
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
>=20

--=20
--
	Todos somos iguais perante a lei, mas n=E3o perante os
	encarregados de faz=EA-las cumprir.
		-- S. Jerzy Lec

--uCsDZuOxeiZLZ20B
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEERkvHzUOf7l6LQJigNIp3jWiF748FAmasNFEACgkQNIp3jWiF
749Dpw/+K2ZVG/1E+MqYfRfZh5JDigiq1NHIjPLiWu+qW3q5CcGYIBtqlFS9sH1I
T8Hg5h4UC3Dw6XS6G8iZJW/rR0lfXC39ENKBtRHoNIfrTPllHSe1ghK/5jB6vMo3
TgzluBX08t4Xo5vvGfved0tgIj8VBFWC1G+neWcT1DAUrC6pEp014TIr4gwoyLnO
aiXl1MSMcv+Mh+8B5QWug9412qJMHzWTljHaUO/pUg93YWsXGu0830kRPoVhl+Z0
ug7LegUC4zYMmw/sHhlTbdQUTxW5U9Dg5J8NDOhCvx3hQWILup9zDEQbhcWHvHw2
xJg57dIcheUEmIxMeY41ID7grTVtLpY4LqlEamuDY8/Ny5eaN/31Cj1fAs0LVWn4
eZu+68FkZSThSuNN9S4kYHct/3l4up0N3sH02r8maMYfl4kL7MOAywdbd0gveI3q
QUPAJ0H+GBzItQB2mKTVCR4e0OqbNoaOcLz0Qwd5OEdwV0fWy9fhDnLnU5B7Hjkf
fvTHsCVaOpqCLpZUWLSWm3dRC7mmk+u/UyConuZUNsciFlj4Vvx39UOXEmuIrRkO
KN6E92fHQHey45vCmEvuzgMPCQNZ89/ZKRRM+A+d7vWZOeSO6y7/KNZ9ihGTaRI4
APP6XoBDvahnwL4vij8o55RKzERF8DGRzHnd26xZA39vhVPMUAA=
=pW2Z
-----END PGP SIGNATURE-----

--uCsDZuOxeiZLZ20B--