By running
touch /usr/local/etc/amanda/amanda-client.conf
I was able to eliminate the error on the server (which is also a client).
I may also have pre-empted a flood of emails on this list.
Perhaps an empty amanda-client.conf file is sufficient, though I
imagine amanda-client.conf is supposed to contain something.
[amandabackup@opennms ~]$ amcheck Daily
Amanda Tape Server Host Check
-----------------------------
Holding disk /home/nept/amandabackup/holding-disk: 2118384 MB disk
space available, using 819200 MB as requested
slot 1:read label `Daily01', date `X'.
NOTE: skipping tape-writable test
Tape Daily01 label ok
Server check took 4.483 seconds
Amanda Backup Client Hosts Check
--------------------------------
WARNING: m248.gc.cuny.edu: selfcheck request failed: Connection refused
Client check: 2 hosts checked in 10.247 seconds. 1 problem found.
(brought to you by Amanda 2.6.0p1)
[amandabackup@opennms ~]$
On Sun, Jun 8, 2008 at 8:07 PM, FL <lengyel AT gmail DOT com> wrote:
> Hi,
> Now that I have multiple luns working in RHEL 5 for a Tandberg drive,
> I decided to upgrade
> AMANDA to the latest version Amanda 2.6.0p1. I had bsdudp auth
> working, but I see that in order
> to get the windows client to work (eventually), I needed to use
> bsdtcp. While adding
>
> auth "bsdtcp"
>
> to the global dump-type configuration did not work, adding
>
> auth "bsdtcp"
>
> to each dump-type used in the DLE did for my AMANDA server, which is
> also a client.
>
>
> I've used the source code; i ran make uninstall to get rid of the
> previous installation, and then ran configure with
>
> ./configure --prefix=/usr/local --with-user=amandabackup
> --with-group=disk --with-config=Daily
> --with-smbclient=/usr/bin/smbclient --with-amandahosts --with-bsdtcp-security
>
>
> However, now I have the amanda-client.conf error, which makes a cameo
> appearance in a few amanda threads,
> but either leaves the scene before the role it plays is revealed, or
> else I am now so enfeebled that I lack the energy
> to pursue the threads long enough to find the resolution.
>
> The highly dramatic output of amcheck follows (the other server is
> still using bsdudp; I'll fix this
>
> Amanda Tape Server Host Check
> -----------------------------
> Holding disk /home/nept/amandabackup/holding-disk: 2118384 MB disk
> space available, using 819200 MB as requested
> slot 1:read label `Daily01', date `X'.
> NOTE: skipping tape-writable test
> Tape Daily01 label ok
> Server check took 4.552 seconds
>
> Amanda Backup Client Hosts Check
> --------------------------------
> WARNING: opennms.gc.cuny.edu: selfcheck request failed:
> tcpm_recv_token: invalid size: could not open conf file
> "/usr/local/etc/amanda/amanda-client.conf": No such file or directory
>
> WARNING: m248.gc.cuny.edu: selfcheck request failed: Connection refused
> Client check: 2 hosts checked in 10.135 seconds. 2 problems found.
>
> (brought to you by Amanda 2.6.0p1)
> [amandabackup@opennms Daily]$
>
> Thank you.
>
|
