You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
backup@sharky5:~$ dpkg-query -l amanda\*|grep ^ii ii amanda-client 1:3.5.1-11+deb12u1 amd64 Advanced Maryland Automatic Network Disk Archiver (Client) ii amanda-common 1:3.5.1-11+deb12u1 amd64 Advanced Maryland Automatic Network Disk Archiver (Libs) ii amanda-server 1:3.5.1-11+deb12u1 amd64 Advanced Maryland Automatic Network Disk Archiver (Server)
And using the stock amanda-S3.conf, with some minor changes, I am get and error from amcheck:
`backup@sharky5:~$ amcheck sharky5
Amanda Tape Server Host Check
NOTE: Holding disk '/var/lib/amanda/holdings/sharky5': 40548 MB disk space available, using 12000 MB as requested
ERROR: amcheck-device terminated with signal 11
NOTE: conf info dir '/var/log/amanda/sharky5curinfo' does not exist
it will be created on the next run
NOTE: index dir '/var/log/amanda/sharky5/index' does not exist
it will be created on the next run
Server check took 0.242 seconds
Amanda Backup Client Hosts Check
Client check: 1 host checked in 2.160 seconds. 0 problems found.
(brought to you by Amanda 3.5.1)`
what am I doing wrong?
The text was updated successfully, but these errors were encountered:
I found the problem, and found the solution in another man page. It appears
that the changer config from 3.3 does not work with 3.5. I needed a more
elaberate value for the change-multi. Amcheck is not crashing now. I think
there is a problem with amcheck-device where it fails to properly report
configuration errors and just crashes without a proper error message.
At Thu, 18 Jul 2024 14:29:00 -0700 zmanda/amanda ***@***.***> wrote:
Hey @RobertPHeller,
I can try to help you. Could you share the `amanda.conf` (redact any secret keys or bucket names) file you have created for the config `sharky5`.
I am using Amanda 3.5.1 from the Debian 12 repo:
backup@sharky5:~$ dpkg-query -l amanda\*|grep ^ii ii amanda-client 1:3.5.1-11+deb12u1 amd64 Advanced Maryland Automatic Network Disk Archiver (Client) ii amanda-common 1:3.5.1-11+deb12u1 amd64 Advanced Maryland Automatic Network Disk Archiver (Libs) ii amanda-server 1:3.5.1-11+deb12u1 amd64 Advanced Maryland Automatic Network Disk Archiver (Server)
And using the stock amanda-S3.conf, with some minor changes, I am get and error from amcheck:
`backup@sharky5:~$ amcheck sharky5
Amanda Tape Server Host Check
NOTE: Holding disk '/var/lib/amanda/holdings/sharky5': 40548 MB disk space available, using 12000 MB as requested
ERROR: amcheck-device terminated with signal 11
NOTE: conf info dir '/var/log/amanda/sharky5curinfo' does not exist
it will be created on the next run
NOTE: index dir '/var/log/amanda/sharky5/index' does not exist
it will be created on the next run
Server check took 0.242 seconds
Amanda Backup Client Hosts Check
Client check: 1 host checked in 2.160 seconds. 0 problems found.
(brought to you by Amanda 3.5.1)`
what am I doing wrong?
The text was updated successfully, but these errors were encountered: