On 8/2/24 19:50, Robert Heller wrote:
One missed build dep: yacc. Otherwise chugging along.
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset="us-ascii"
At Fri, 2 Aug 2024 05:50:28 +0100 Jose M Calhariz
<[email protected]> wrote:
On Thu, Aug 01, 2024 at 10:52:48PM -0400, Robert Heller wrote:
At Fri, 2 Aug 2024 02:20:26 +0100 Jose M Calhariz
<[email protected]> wrote:
On Thu, Aug 01, 2024 at 12:39:46AM -0400, Robert Heller wrote:
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.
Yes, please do!
To compile amanda 3.5.4 for Debian v12 with the Debian defaults and
not zmanda defaults, do:
sudo apt install build-essential
sudo apt build-dep amanda
sudo apt install devscripts
mkdir -p ~/src/amanda
cd ~/src/amanda
dget http://deb.debian.org/debian/pool/main/a/amanda/amanda_3.5.4-1.dsc
cd amanda-3.5.4
debuild -uc -us
THis instructions were made by memory and are incomplete. Please try
and explain what does not work.
Tomorrow if the creek doesn't get too high. Thanks. Robert. Build
might be on armbian jammie, thats whats running klipper etc for my
printers. If that blows up, I'll pull the latest bookworm for arm64.
Kind regards
Jose M Calhariz
Kind regards
Jose M Calhariz
At Tue, 23 Jul 2024 03:07:37 +0100 Jose M Calhariz
<[email protected]> wrote:
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. The 3.3.3
configuation is not liked by Amanda 3.5.1 under Debian 12 (not supprising). 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 wrong.
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 logs 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 specified 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 device 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... The 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 we 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 we 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 name for reports
mailto "[email protected]" # space separated list of operators at your site
dumpcycle 28 days # the number of days in the normal dump cycle
runspercycle 28 # the number of amdump runs in dumpcycle 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 handle errors that
# need amflush and so we do not overwrite the full
# backups performed at the beginning of the previous
# cycle
runtapes 3 # number of tapes to be used in a single run of amdump
define changer my_s3 {
tpchanger "chg-multi:s3:sharky5-backups/slot-{00..40}"
device-property "S3_ACCESS_KEY" "XXXXXXXXXXXXXXXXXXXXXX"
device-property "S3_SECRET_KEY" 'xxxxxxxxxxxxxxxxxxxxxxxxxx"
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 below)
I am sure the S3_ACCESS_KEY and S3_SECRET_KEY are correct.
Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
