amanda-2.5.2p1 on SCO 5.0.4
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
#
Re: amanda-2.5.2p1 on SCO 5.0.4
On Mon, Jul 21, 2008 at 12:24 PM, Michael Reuland <[EMAIL PROTECTED]> wrote: > 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 This is basically a protocol error -- the server connected to the client, expecting a binary-formatted packet in response, but the config parser output an error message over the socket instead. > The client system apd50.coop.com (SCO 5.0.4) shows the following when I try > to run amcheck on that system. Running amcheck on a client doesn't make sense, and won't parse the amanda-client.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" Unless I'm missing something, line 5 is the "conf" line. Try commenting that line out? > 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. Please post suggestions to help others build on SCO on the wiki: http://wiki.zmanda.com/index.php/Installation/OS_Specific_Notes and also please consider becoming a Platform Expert: http://wiki.zmanda.com/index.php/Platform_Experts We don't have anyone else around to test on SCO, so your help is the only way we can continue to compile on this system. Dustin -- Storage Software Engineer http://www.zmanda.com
Re: amanda-2.5.2p1 on SCO 5.0.4
Sent from my iPhone On Jul 21, 2008, at 1:12 PM, "Dustin J. Mitchell" <[EMAIL PROTECTED]> wrote: On Mon, Jul 21, 2008 at 12:24 PM, Michael Reuland <[EMAIL PROTECTED]> wrote: 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 This is basically a protocol error -- the server connected to the client, expecting a binary-formatted packet in response, but the config parser output an error message over the socket instead. The client system apd50.coop.com (SCO 5.0.4) shows the following when I try to run amcheck on that system. Running amcheck on a client doesn't make sense, and won't parse the amanda-client.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" Unless I'm missing something, line 5 is the "conf" line. Try commenting that line out? 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. Please post suggestions to help others build on SCO on the wiki: http://wiki.zmanda.com/index.php/Installation/OS_Specific_Notes and also please consider becoming a Platform Expert: http://wiki.zmanda.com/index.php/Platform_Experts We don't have anyone else around to test on SCO, so your help is the only way we can continue to compile on this system. Dustin -- Storage Software Engineer http://www.zmanda.com Yes please post info regarding SCO. I have needed a working SCO client for a long time. Kenneth Berry
Re: amanda-2.5.2p1 on SCO 5.0.4
I have tried several configuration changes and still end up w/ the same problem. After each change I have returned to the original configuration to try and keep things in order. I'm still getting the same error about "quoted string " I have stripped the ~etc/amanda/amanda-client.conf file to only the actual configuration keywords and options. I still get the similar response reporting the first line of configuration data from the file. Is there a utility that I can run on the client to see if the config file is being read correctly? I'd like to narrow down the problem. Since I have the host server running w/ a different client (not SCO), I'd like to focus on the client platform to start with. Thank you, Michael R_ On Mon, 2008-07-21 at 14:12 -0400, Dustin J. Mitchell wrote: > On Mon, Jul 21, 2008 at 12:24 PM, Michael Reuland > <[EMAIL PROTECTED]> wrote: > > 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 > > This is basically a protocol error -- the server connected to the > client, expecting a binary-formatted packet in response, but the > config parser output an error message over the socket instead. > > > > 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" > > Unless I'm missing something, line 5 is the "conf" line. Try > commenting that line out? > > > 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. > > Please post suggestions to help others build on SCO on the wiki: > http://wiki.zmanda.com/index.php/Installation/OS_Specific_Notes > and also please consider becoming a Platform Expert: > http://wiki.zmanda.com/index.php/Platform_Experts > > We don't have anyone else around to test on SCO, so your help is the > only way we can continue to compile on this system. > > Dustin > _ Michael Reuland Senior Unix Systems Engineer Activant Solutions Inc.™ T: 512.278-5310 F: 512-278-5915 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.
Re: amanda-2.5.2p1 on SCO 5.0.4
If the configuration keywords are shifted into different order, the amcheck still reports the problem at the first line that has any keyword. If I insert an invalid configuration keyword, the amcheck still reports the same error. Running amrecover does connect back to the index_server from the config file entry. If I insert and invalid configuration parameter (w/o any additional data on that line), I get the following response. (line 6 is the invalid keyword): # amrecover "/usr/local/etc/amanda/amanda-client.conf", line 6: configuration keyword expected amrecover: error reading conffile: /usr/local/etc/amanda/amanda- client.conf If I include an invalid parameter and value I get a very similar response to the amcheck output that is complaining about "end of line expected". # amrecover "/usr/local/etc/amanda/amanda-client.conf", line 6: configuration keyword expected "/usr/local/etc/amanda/amanda-client.conf", line 6: end of line is expected amrecover: error reading conffile: /usr/local/etc/amanda/amanda- client.conf The amanda-client.conf file that I am using was pulled from a working amanda client system. The 2.5.2p1 source tarball did not have a device-src module. I do not find any device-src directory anywhere in the source code. There were no files or directories w/ the name "\*device\*". This is a listing of all of the Makefile files in the source code. # pwd /wrk/michaelr/amanda/amanda-2.5.2p1 # find . -name Makefile -print ./amplot/Makefile ./changer-src/Makefile ./client-src/Makefile ./common-src/Makefile ./config/Makefile ./dumper-src/Makefile ./example/Makefile ./server-src/Makefile ./gnulib/Makefile ./amandad-src/Makefile ./tape-src/Makefile ./restore-src/Makefile ./recover-src/Makefile ./oldrecover-src/Makefile ./man/Makefile ./docs/Makefile ./Makefile # find . -type f -name tape\*.c -print ./common-src/tapelist.c ./server-src/tapefile.c ./server-src/taperscan.c ./server-src/taper.c ./tape-src/tapeio.c ./tape-src/tapetype.c The only changes that I have made to the source code to make everything compile are the following: server-src/ and dumper-src/ Makefile.am and Makefile.in - remove the capital "W" option from the perl command options. That option is not supported. perl --version Perl 5.005_03 This is perl, version 5.005_03 built for i386-sco tape-src/ Makefile.in and Makefile.am - added the gnulib/libgnu.$(LIB_EXTENSION) to the list of libraries in order for the libamtape.la to be included in several of the tape-src compiles. ### # Because libamanda includes routines (e.g. regex) provided by some system # libraries, and because of the way libtool sets up the command line, we # need to list libamanda twice here, first to override the system library # routines, and second to pick up any references in the other libraries. ### LDADD = ../common-src/libamanda.$(LIB_EXTENSION) \ libamtape.$(LIB_EXTENSION) \ ../common-src/libamanda.$(LIB_EXTENSION) \ ../gnulib/libgnu.$(LIB_EXTENSION) Michael R_ On Wed, 2008-07-23 at 15:02 -0400, Dustin J. Mitchell wrote: > On Wed, Jul 23, 2008 at 2:38 PM, Michael Reuland > <[EMAIL PROTECTED]> wrote: > > I have stripped the ~etc/amanda/amanda-client.conf file to only the actual > > configuration keywords and options. I still get the similar response > > reporting the first line of configuration data from the file. > > What happens if you switch the order of lines so that the first line > is e.g., the second? > > > Is there a utility that I can run on the client to see if the config file is > > being read correctly? I'd like to narrow down the problem. Since I have > > the host server running w/ a different client (not SCO), I'd like to focus > > on the client platform to start with. > > You can run 'amrecover' on the client. It should give the same error > messages. > > On a completely unrelated topic, I'd like to know whether your SCO > system uses POSIX tapes or the old "uware" driver. Can you run > grep 'tape-.*\.c' device-src/Makefile > and send me the result? I'm considering removing native uware (and > aix and xenix) support, since most systems have POSIX these days, and > since we don't have a way to test these other systems. > > Dustion > _ Michael Reuland Senior Unix Systems Engineer Activant Solutions Inc.™ T: 512.278-5310 F: 512-278-5915 The opinions expressed here aren't even mine... To err is human...to really foul up requires the root password. Not
Re: amanda-2.5.2p1 on SCO 5.0.4
On Wed, Jul 23, 2008 at 2:38 PM, Michael Reuland <[EMAIL PROTECTED]> wrote: > I have stripped the ~etc/amanda/amanda-client.conf file to only the actual > configuration keywords and options. I still get the similar response > reporting the first line of configuration data from the file. What happens if you switch the order of lines so that the first line is e.g., the second? > Is there a utility that I can run on the client to see if the config file is > being read correctly? I'd like to narrow down the problem. Since I have > the host server running w/ a different client (not SCO), I'd like to focus > on the client platform to start with. You can run 'amrecover' on the client. It should give the same error messages. On a completely unrelated topic, I'd like to know whether your SCO system uses POSIX tapes or the old "uware" driver. Can you run grep 'tape-.*\.c' device-src/Makefile and send me the result? I'm considering removing native uware (and aix and xenix) support, since most systems have POSIX these days, and since we don't have a way to test these other systems. Dustion -- Storage Software Engineer http://www.zmanda.com
Re: amanda-2.5.2p1 on SCO 5.0.4
OK, folks, this thread has been a while coming, but I wanted to mention that it's been fixed. We discovered that on Michael's system, in whatever context amandad runs, isspace(0x20) == 0. That is to say, it's not thinking in ASCII for some reason. The fix, in r1310, is to use Glib's g_ascii_isspace(), which (as you might guess) always uses ASCII regardless of any system settings. For the moment, this is appropriate everywhere in Amanda, and it will remain true in the on-wire and on-disk formats. At some point, we'll support Unicode in the configuration file, but that's not a current project. Dustin -- Storage Software Engineer http://www.zmanda.com
