I trying to run Amanda-2.5.2p1 on an SCO OpenServer 5.0.4 system
compiled with gcc-3.4.4
I've worked out the dependencies and syntax errors in the builds to get
the binary files compiled.
My problem now is that the amcheck does not succeed due to
misinterpretation of the amanda-client.conf file on the SCO client
system.
I have the amanda-2.5.2p1 code compiled and configured between two Linux
systems w/in our group. The host system is a RedHat EL4 Update 6, the
first client is a Fedora Core 9 running a localy compiled
amanda-2.5.2p1. These two systems work nicely together.
After I compiled and configured the SCO 5.0.4 system and ran the amcheck
on the host (RHEL4) system, I get the output:
$ amcheck DailySet1
Amanda Tape Server Host Check
-----------------------------
{this sections is resolved and is not part of the problem}
Amanda Backup Client Hosts Check
--------------------------------
WARNING: apd50.coop.com: selfcheck request failed:
tcpm_recv_token: invalid size: "/usr/local/etc/amanda/amanda-
client.conf", line 5: a quoted string is expected
"/usr/local/etc/aman
Client check: 2 hosts checked in 0.161 seconds, 1 problem found
(brought to you by Amanda 2.5.2p1)
-sh-3.00$
The client system apd50.coop.com (SCO 5.0.4) shows the following when I
try to run amcheck on that system.
amcheck DailySet1
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 18:
configuration keyword expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 18: end of
line is expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 24:
configuration keyword expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 24: end of
line is expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 33:
configuration keyword expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 33: end of
line is expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 36:
configuration keyword expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 36: end of
line is expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 0: default
tapetype EXABYTE not defined
amcheck: errors processing config file
"/usr/local/etc/amanda/DailySet1/amanda.conf"
$
The ~etc/amanda/amanda-client.conf file is as follows:
# amanda.conf - sample Amanda client configuration file.
#
# This file normally goes in /etc/amanda/amanda-client.conf.
#
conf "DailySet1" # your config name
#index_server "myserver.mydomain.net" # your amindexd server
index_server "myserver" # your amindexd server
#tape_server "myserver.mydomain.net" # your amidxtaped server
tape_server "myserver" # your amidxtaped server
#tapedev "/dev/null" # your tape device
# auth - authentication scheme to use between server and client.
# Valid values are "bsd", "bsdudp", "bsdtcp" and "ssh".
# Default: [auth "bsdtcp"]
auth "ssh"
# your ssh keys file if you use ssh auth
ssh_keys "/usr/amanda/.ssh/id_rsa_amrecover"
The ~etc/amanda/DailySet1/amanda-client.conf file is as follows:
### !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! !!!
WARNING !!! ###
###
###
### This file is not meant to be installed "as is", and in
fact, it ###
### WILL NOT WORK! You must go through it and make changes
appropriate ###
### to your own situation. See the documentation in this file,
in the ###
### "man amanda" man page, in the "docs" directory and at the
Amanda ###
### web page (www.amanda.org).
###
###
###
### !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! !!!
WARNING !!! ###
#
# amanda.conf - sample Amanda client configuration file.
#
# This file normally goes in /etc/amanda/amanda-client.conf.
#
# your config name
conf "DailySet1"
# your amindexd server
#index_server "myserver.mydomain.net"
index_server "myserver"
# your tape device
tapedev "/dev/null"
# auth - authentication scheme to use between server
and client.
# Valid values are "bsd", "krb4", "krb5" and
"ssh".
# Default: [auth "bsd"]
auth "ssh"
ssh_keys "/usr/amanda/.ssh/authorized_keys" # your ssh keys file
if you use ssh auth
# You may include other amanda configuration files, so you can
share
# dumptypes, tapetypes and interface definitions among several
# configurations.
#includefile "/usr/local/etc/amanda/amanda-client.conf.main"
If I run the amgetconf DailySet1 conf on the client system I get the
following
$ amgetconf DailySet1 conf
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 18:
configuration keyword expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 18: end of
line is expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 19:
configuration keyword expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 24:
configuration keyword expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 24: end of
line is expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 25:
configuration keyword expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 28: a quoted
string is expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 28: end of
line is expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 29:
configuration keyword expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 29: end of
line is expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 30:
configuration keyword expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 30: end of
line is expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 31:
configuration keyword expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 36:
configuration keyword expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 36: end of
line is expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 37:
configuration keyword expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 39:
configuration keyword expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 39: end of
line is expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 40:
configuration keyword expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 40: end of
line is expected
"/usr/local/etc/amanda/DailySet1/amanda.conf", line 0: default
tapetype EXABYTE not defined
amgetconf: errors processing config file
"/usr/local/etc/amanda/DailySet1/amanda.conf"
$
The configure line that I used for the SCO build was:
configure --program-prefix= --bindir=/usr/local/bin \
--includedir=/usr/include --libdir=/usr/lib --
libexecdir=/usr/lib/amanda \
--localstatedir=/var/lib --with-gnutar-
listdir=/usr/local/bin/gtar \
--with-user=amandabk --with-group=backup --with-
tmpdir=/var/log/amanda \
--enable-shared --enable-static --enable-threads --without-ipv6
I've check all the files and directories and confirmed that all they are
all owned and writable by amandabk w/ the few exceptions of the files
that have SUID root.
Can anyone guide me to the area that would possible cause the files to
be read wrong like this?
Thank you.
Michael R_
_________________________
Michael Reuland
Senior Unix Systems Engineer
Activant Solutions Inc.™
The opinions expressed here aren't even mine...
To err is human...to really foul up requires the root password.
Notice: This transmission is for the sole use of the intended recipient(s) and
may contain information that is confidential and/or privileged. If you are not
the intended recipient, please delete this transmission and any attachments and
notify the sender by return email immediately. Any unauthorized review, use,
disclosure or distribution is prohibited.
