Re: 2.6.1 client with 2.4.3 server?
Yes, this patch solved the problem. Thank you! Can we anticipate it being integrated into future versions? -Mitch On Tue, 19 May 2009, Jean-Louis Martineau wrote: amanda client 2.6.1p1 is compatible with server 2.4.3b4 and up. But it is not with 2.4.3b3 and previous. Try the attached patch. Jean-Louis Mitch Collinsworth wrote: Hi, Is there any gross imcompatability that would prevent a 2.6.1p1 client from being backed up by a 2.4.3b3 server? I've got it to the point where they are at least talking with each other, using auth bsd. amcheck -c is happy. estimates worked ok. But amstatus is showing this: client-a:/a0 driver: [parse of reply message failed] (10:34:30) client-a:/var 0 driver: [parse of reply message failed] (10:41:15) client-a:/var/log 0 31020k wait for dumping driver: (aborted:[request timeout]) hmm... here's something interesting in the sendbackup.debug file: 1242744076.458012: sendbackup: pid 14788 ruid 501 euid 501 version 2.6.1p1: start a t Tue May 19 10:41:16 2009 1242744076.458089: sendbackup: Version 2.6.1p1 1242744076.458650: sendbackup: sendbackup req: GNUTAR /var 0 1970:1:1:0:0:0 OPTI ONS |;bsd-auth;index; 1242744076.458736: sendbackup: Parsed request as: program `GNUTAR' 1242744076.458749: sendbackup: disk `/var' 1242744076.458760: sendbackup: device `/var' 1242744076.458770: sendbackup: level 0 1242744076.458781: sendbackup: since 1970:1:1:0:0:0 1242744076.458791: sendbackup: options `|;bsd-auth;index;' 1242744076.458998: sendbackup: start: client-a:/var lev 0 1242744076.459129: sendbackup: doing level 0 dump as listed-incremental to '/var/li b/amanda/gnutar-lists/client-a_var_0.new' 1242744076.461334: sendbackup: Started index creator: /bin/tar -tf - 2/dev/null | sed -e 's/^\.//' 1242744076.461537: sendbackup: pipespawnv: stdoutfd is 50 1242744076.461947: sendbackup: Spawning /usr/libexec/amanda/runtar runtar NOCONFIG /bin/tar --create --file - --directory /var --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/client-a_var_0.new --sparse --ignore-failed-read --to tals . in pipeline 1242744076.463151: sendbackup: gnutar: /usr/libexec/amanda/runtar: pid 14792 1242744076.463205: sendbackup: Started backup 1242744166.493587: sendbackup: critical (fatal): index tee cannot write [Broken pip e] /usr/lib64/amanda/libamanda-2.6.1p1.so[0x35834215b2] /lib64/libglib-2.0.so.0(g_logv+0x26f)[0x3af5c34d5f] /lib64/libglib-2.0.so.0(g_log+0x83)[0x3af5c34f33] /usr/libexec/amanda/sendbackup(start_index+0x290)[0x4037f0] /usr/libexec/amanda/sendbackup[0x4075f0] /usr/libexec/amanda/sendbackup(main+0x10a4)[0x405834] /lib64/libc.so.6(__libc_start_main+0xf4)[0x3fe1c1d8b4] /usr/libexec/amanda/sendbackup[0x403139] So it looks like a problem sending the index data. I've set index_server to the correct hostname in /etc/amanda-client.conf. Will this properly override the settings configured at compile time? This client is installed from the redhat rpm, so it has no local compile-time configuration. The /etc/amanda-client.conf looks like this: # # amanda.conf - sample Amanda client configuration file. # # This file normally goes in /etc/amanda/amanda-client.conf. # conf test # your config name index_server amanda-server# your amindexd server tape_server amanda-server# your amidxtaped server tapedev tape:/dev/nst1 # your tape device # if not set, Use configure or ask server. # if set to empty string , ask server # amrecover will use the changer if set to the value # of 'amrecover_changer' in the server amanda.conf. # auth- authentication scheme to use between server and client. # Valid values are bsd, bsdudp, bsdtcp, krb5, local, # rsh and ssh. # Default: [auth bsdtcp] auth bsd ssh_keys # your ssh keys file if you use ssh auth Anyone see anything obvious we're overlooking? (Yeah, besides needing to upgrade the server!) :-) -Mitch
Re: 2.6.1 client with 2.4.3 server?
Mitch Collinsworth wrote: Yes, this patch solved the problem. Thank you! Can we anticipate it being integrated into future versions? I committed the patch to SVN, it will be in the next release. Jean-Louis
2.6.1 client with 2.4.3 server?
Hi, Is there any gross imcompatability that would prevent a 2.6.1p1 client from being backed up by a 2.4.3b3 server? I've got it to the point where they are at least talking with each other, using auth bsd. amcheck -c is happy. estimates worked ok. But amstatus is showing this: client-a:/a0 driver: [parse of reply message failed] (10:34:30) client-a:/var 0 driver: [parse of reply message failed] (10:41:15) client-a:/var/log 0 31020k wait for dumping driver: (aborted:[request timeout]) hmm... here's something interesting in the sendbackup.debug file: 1242744076.458012: sendbackup: pid 14788 ruid 501 euid 501 version 2.6.1p1: start a t Tue May 19 10:41:16 2009 1242744076.458089: sendbackup: Version 2.6.1p1 1242744076.458650: sendbackup: sendbackup req: GNUTAR /var 0 1970:1:1:0:0:0 OPTI ONS |;bsd-auth;index; 1242744076.458736: sendbackup: Parsed request as: program `GNUTAR' 1242744076.458749: sendbackup: disk `/var' 1242744076.458760: sendbackup: device `/var' 1242744076.458770: sendbackup: level 0 1242744076.458781: sendbackup: since 1970:1:1:0:0:0 1242744076.458791: sendbackup: options `|;bsd-auth;index;' 1242744076.458998: sendbackup: start: client-a:/var lev 0 1242744076.459129: sendbackup: doing level 0 dump as listed-incremental to '/var/li b/amanda/gnutar-lists/client-a_var_0.new' 1242744076.461334: sendbackup: Started index creator: /bin/tar -tf - 2/dev/null | sed -e 's/^\.//' 1242744076.461537: sendbackup: pipespawnv: stdoutfd is 50 1242744076.461947: sendbackup: Spawning /usr/libexec/amanda/runtar runtar NOCONFIG /bin/tar --create --file - --directory /var --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/client-a_var_0.new --sparse --ignore-failed-read --to tals . in pipeline 1242744076.463151: sendbackup: gnutar: /usr/libexec/amanda/runtar: pid 14792 1242744076.463205: sendbackup: Started backup 1242744166.493587: sendbackup: critical (fatal): index tee cannot write [Broken pip e] /usr/lib64/amanda/libamanda-2.6.1p1.so[0x35834215b2] /lib64/libglib-2.0.so.0(g_logv+0x26f)[0x3af5c34d5f] /lib64/libglib-2.0.so.0(g_log+0x83)[0x3af5c34f33] /usr/libexec/amanda/sendbackup(start_index+0x290)[0x4037f0] /usr/libexec/amanda/sendbackup[0x4075f0] /usr/libexec/amanda/sendbackup(main+0x10a4)[0x405834] /lib64/libc.so.6(__libc_start_main+0xf4)[0x3fe1c1d8b4] /usr/libexec/amanda/sendbackup[0x403139] So it looks like a problem sending the index data. I've set index_server to the correct hostname in /etc/amanda-client.conf. Will this properly override the settings configured at compile time? This client is installed from the redhat rpm, so it has no local compile-time configuration. The /etc/amanda-client.conf looks like this: # # amanda.conf - sample Amanda client configuration file. # # This file normally goes in /etc/amanda/amanda-client.conf. # conf test # your config name index_server amanda-server# your amindexd server tape_server amanda-server# your amidxtaped server tapedev tape:/dev/nst1 # your tape device # if not set, Use configure or ask server. # if set to empty string , ask server # amrecover will use the changer if set to the value # of 'amrecover_changer' in the server amanda.conf. # auth- authentication scheme to use between server and client. # Valid values are bsd, bsdudp, bsdtcp, krb5, local, # rsh and ssh. # Default: [auth bsdtcp] auth bsd ssh_keys # your ssh keys file if you use ssh auth Anyone see anything obvious we're overlooking? (Yeah, besides needing to upgrade the server!) :-) -Mitch
Re: 2.6.1 client with 2.4.3 server?
I try to keep them compatible, but I don't test with release before 2.4.5. index_server is used only by amrecover. Can you post the amandad.*.debug file from the client? Jean-Louis Mitch Collinsworth wrote: Hi, Is there any gross imcompatability that would prevent a 2.6.1p1 client from being backed up by a 2.4.3b3 server? I've got it to the point where they are at least talking with each other, using auth bsd. amcheck -c is happy. estimates worked ok. But amstatus is showing this: client-a:/a0 driver: [parse of reply message failed] (10:34:30) client-a:/var 0 driver: [parse of reply message failed] (10:41:15) client-a:/var/log 0 31020k wait for dumping driver: (aborted:[request timeout]) hmm... here's something interesting in the sendbackup.debug file: 1242744076.458012: sendbackup: pid 14788 ruid 501 euid 501 version 2.6.1p1: start a t Tue May 19 10:41:16 2009 1242744076.458089: sendbackup: Version 2.6.1p1 1242744076.458650: sendbackup: sendbackup req: GNUTAR /var 0 1970:1:1:0:0:0 OPTI ONS |;bsd-auth;index; 1242744076.458736: sendbackup: Parsed request as: program `GNUTAR' 1242744076.458749: sendbackup: disk `/var' 1242744076.458760: sendbackup: device `/var' 1242744076.458770: sendbackup: level 0 1242744076.458781: sendbackup: since 1970:1:1:0:0:0 1242744076.458791: sendbackup: options `|;bsd-auth;index;' 1242744076.458998: sendbackup: start: client-a:/var lev 0 1242744076.459129: sendbackup: doing level 0 dump as listed-incremental to '/var/li b/amanda/gnutar-lists/client-a_var_0.new' 1242744076.461334: sendbackup: Started index creator: /bin/tar -tf - 2/dev/null | sed -e 's/^\.//' 1242744076.461537: sendbackup: pipespawnv: stdoutfd is 50 1242744076.461947: sendbackup: Spawning /usr/libexec/amanda/runtar runtar NOCONFIG /bin/tar --create --file - --directory /var --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/client-a_var_0.new --sparse --ignore-failed-read --to tals . in pipeline 1242744076.463151: sendbackup: gnutar: /usr/libexec/amanda/runtar: pid 14792 1242744076.463205: sendbackup: Started backup 1242744166.493587: sendbackup: critical (fatal): index tee cannot write [Broken pip e] /usr/lib64/amanda/libamanda-2.6.1p1.so[0x35834215b2] /lib64/libglib-2.0.so.0(g_logv+0x26f)[0x3af5c34d5f] /lib64/libglib-2.0.so.0(g_log+0x83)[0x3af5c34f33] /usr/libexec/amanda/sendbackup(start_index+0x290)[0x4037f0] /usr/libexec/amanda/sendbackup[0x4075f0] /usr/libexec/amanda/sendbackup(main+0x10a4)[0x405834] /lib64/libc.so.6(__libc_start_main+0xf4)[0x3fe1c1d8b4] /usr/libexec/amanda/sendbackup[0x403139] So it looks like a problem sending the index data. I've set index_server to the correct hostname in /etc/amanda-client.conf. Will this properly override the settings configured at compile time? This client is installed from the redhat rpm, so it has no local compile-time configuration. The /etc/amanda-client.conf looks like this: # # amanda.conf - sample Amanda client configuration file. # # This file normally goes in /etc/amanda/amanda-client.conf. # conf test # your config name index_server amanda-server# your amindexd server tape_server amanda-server# your amidxtaped server tapedev tape:/dev/nst1 # your tape device # if not set, Use configure or ask server. # if set to empty string , ask server # amrecover will use the changer if set to the value # of 'amrecover_changer' in the server amanda.conf. # auth- authentication scheme to use between server and client. # Valid values are bsd, bsdudp, bsdtcp, krb5, local, # rsh and ssh. # Default: [auth bsdtcp] auth bsd ssh_keys # your ssh keys file if you use ssh auth Anyone see anything obvious we're overlooking? (Yeah, besides needing to upgrade the server!) :-) -Mitch
Re: 2.6.1 client with 2.4.3 server?
On Tue, 19 May 2009, Jean-Louis Martineau wrote:
I try to keep them compatible, but I don't test with release before 2.4.5.
index_server is used only by amrecover.
Can you post the amandad.*.debug file from the client?
Jean-Louis
Yup, here's a sample below.
-Mitch
1242745188.258722: amandad: pid 14871 ruid 501 euid 501 version 2.6.1p1: start
at Tue May 19 10:59:48 2009
1242745188.259342: amandad: security_getdriver(name=bsd) returns 0x358364e920
1242745188.259373: amandad: version 2.6.1p1
1242745188.259383: amandad: build: VERSION=Amanda-2.6.1p1
1242745188.259393: amandad:BUILT_DATE=Fri Apr 10 16:12:07 PDT 2009
1242745188.259402: amandad:BUILT_MACH=x86_64-unknown-linux-gnu
BUILT_REV=1860
1242745188.259410: amandad:BUILT_BRANCH=amanda-261 CC=gcc
1242745188.259419: amandad: paths: bindir=/usr/bin sbindir=/usr/sbin
1242745188.259428: amandad:libexecdir=/usr/libexec
1242745188.259436: amandad:amlibexecdir=/usr/libexec/amanda
mandir=/usr/share/man
1242745188.259445: amandad:AMANDA_TMPDIR=/tmp/amanda
1242745188.259453: amandad:AMANDA_DBGDIR=/var/log/amanda
CONFIG_DIR=/etc/amanda
1242745188.259462: amandad:DEV_PREFIX=/dev/ RDEV_PREFIX=/dev/r
1242745188.259470: amandad:DUMP=/sbin/dump
RESTORE=/sbin/restore VDUMP=UNDEF
1242745188.259479: amandad:VRESTORE=UNDEF XFSDUMP=UNDEF
XFSRESTORE=UNDEF VXDUMP=UNDEF
1242745188.259489: amandad:VXRESTORE=UNDEF
SAMBA_CLIENT=/usr/bin/smbclient
1242745188.259497: amandad:GNUTAR=/bin/tar
COMPRESS_PATH=/usr/bin/gzip
1242745188.259506: amandad:UNCOMPRESS_PATH=/usr/bin/gzip
LPRCMD=/usr/bin/lpr
1242745188.259515: amandad: MAILER=UNDEF
listed_incr_dir=/var/lib/amanda/gnutar-lists
1242745188.259523: amandad: defs: DEFAULT_SERVER=localhost
DEFAULT_CONFIG=DailySet1
1242745188.259532: amandad:DEFAULT_TAPE_SERVER=localhost
DEFAULT_TAPE_DEVICE=
1242745188.259540: amandad:HAVE_MMAP NEED_STRSTR HAVE_SYSVSHM
AMFLOCK_POSIX AMFLOCK_FLOCK
1242745188.259549: amandad:AMFLOCK_LOCKF AMFLOCK_LNLOCK
SETPGRP_VOID ASSERTIONS
1242745188.259557: amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY
USE_AMANDAHOSTS
1242745188.259566: amandad:CLIENT_LOGIN=amandabackup CHECK_USERID
HAVE_GZIP
1242745188.259574: amandad:COMPRESS_SUFFIX=.gz
COMPRESS_FAST_OPT=--fast
1242745188.259582: amandad:COMPRESS_BEST_OPT=--best
UNCOMPRESS_OPT=-dc
1242745188.259683: amandad: dgram_recv(dgram=0x3583659788, timeout=0,
fromaddr=0x3583669780)
1242745188.259718: amandad: (sockaddr_in *)0x3583669780 = { 2, 769, 11.22.33.44
}
1242745188.259753: amandad: security_handleinit(handle=0xbcf5a30,
driver=0x358364e920 (BSD))
1242745188.262340: amandad: accept recv REQ pkt:
SERVICE sendbackup
OPTIONS hostname=client-a;
GNUTAR / 0 1970:1:1:0:0:0 OPTIONS |;bsd-auth;index;
1242745188.262390: amandad: creating new service: sendbackup
OPTIONS hostname=client-a;
GNUTAR / 0 1970:1:1:0:0:0 OPTIONS |;bsd-auth;index;
1242745188.264233: amandad: sending ACK pkt:
1242745188.264340: amandad: dgram_send_addr(addr=0xbcf5a70, dgram=0x3583659788)
1242745188.264360: amandad: (sockaddr_in *)0xbcf5a70 = { 2, 769, 11.22.33.44 }
1242745188.264374: amandad: dgram_send_addr: 0x3583659788-socket = 0
1242745188.270256: amandad: security_streaminit(stream=0xbd06c60,
driver=0x358364e920 (BSD))
1242745188.270320: amandad: stream_server opening socket with family 2
(requested family was 2)
1242745188.270362: amandad: try_socksize: send buffer size is 65536
1242745188.270378: amandad: try_socksize: receive buffer size is 65536
1242745188.277672: amandad: bind_portrange2: Try port 11039: Available -
Success
1242745188.277744: amandad: stream_server: waiting for connection: 0.0.0.0.11039
1242745188.277769: amandad: security_streaminit(stream=0xbd0f140,
driver=0x358364e920 (BSD))
1242745188.277789: amandad: stream_server opening socket with family 2
(requested family was 2)
1242745188.277817: amandad: try_socksize: send buffer size is 65536
1242745188.277831: amandad: try_socksize: receive buffer size is 65536
1242745188.285066: amandad: bind_portrange2: Try port 11039: Available -
Address already in use
1242745188.292295: amandad: bind_portrange2: Try port 11040: Available -
Success
1242745188.292368: amandad: stream_server: waiting for connection: 0.0.0.0.11040
1242745188.292392: amandad: security_streaminit(stream=0xbd171c0,
driver=0x358364e920 (BSD))
1242745188.292412: amandad: stream_server opening socket with family 2
(requested family was 2)
1242745188.292438: amandad: try_socksize: send buffer size is 65536
1242745188.292452: amandad: try_socksize: receive buffer size is 65536
1242745188.299718: amandad: bind_portrange2: Try port 11039: Available -
Address already in use
1242745188.302654: amandad: bind_portrange2: Try port 11040: Available -
Address already in
Re: 2.6.1 client with 2.4.3 server?
amanda client 2.6.1p1 is compatible with server 2.4.3b4 and up. But it
is not with 2.4.3b3 and previous.
Try the attached patch.
Jean-Louis
Mitch Collinsworth wrote:
Hi,
Is there any gross imcompatability that would prevent a 2.6.1p1 client
from being backed up by a 2.4.3b3 server?
I've got it to the point where they are at least talking with each
other, using auth bsd.
amcheck -c is happy.
estimates worked ok.
But amstatus is showing this:
client-a:/a0 driver: [parse of reply message failed] (10:34:30)
client-a:/var 0 driver: [parse of reply message failed] (10:41:15)
client-a:/var/log 0 31020k wait for dumping driver:
(aborted:[request timeout])
hmm... here's something interesting in the sendbackup.debug file:
1242744076.458012: sendbackup: pid 14788 ruid 501 euid 501 version
2.6.1p1: start a
t Tue May 19 10:41:16 2009
1242744076.458089: sendbackup: Version 2.6.1p1
1242744076.458650: sendbackup: sendbackup req: GNUTAR /var 0
1970:1:1:0:0:0 OPTI
ONS |;bsd-auth;index;
1242744076.458736: sendbackup: Parsed request as: program `GNUTAR'
1242744076.458749: sendbackup: disk `/var'
1242744076.458760: sendbackup: device `/var'
1242744076.458770: sendbackup: level 0
1242744076.458781: sendbackup: since
1970:1:1:0:0:0
1242744076.458791: sendbackup: options
`|;bsd-auth;index;'
1242744076.458998: sendbackup: start: client-a:/var lev 0
1242744076.459129: sendbackup: doing level 0 dump as
listed-incremental to '/var/li
b/amanda/gnutar-lists/client-a_var_0.new'
1242744076.461334: sendbackup: Started index creator: /bin/tar -tf
- 2/dev/null |
sed -e 's/^\.//'
1242744076.461537: sendbackup: pipespawnv: stdoutfd is 50
1242744076.461947: sendbackup: Spawning /usr/libexec/amanda/runtar
runtar NOCONFIG
/bin/tar --create --file - --directory /var --one-file-system
--listed-incremental
/var/lib/amanda/gnutar-lists/client-a_var_0.new --sparse
--ignore-failed-read --to
tals . in pipeline
1242744076.463151: sendbackup: gnutar: /usr/libexec/amanda/runtar:
pid 14792
1242744076.463205: sendbackup: Started backup
1242744166.493587: sendbackup: critical (fatal): index tee cannot
write [Broken pip
e]
/usr/lib64/amanda/libamanda-2.6.1p1.so[0x35834215b2]
/lib64/libglib-2.0.so.0(g_logv+0x26f)[0x3af5c34d5f]
/lib64/libglib-2.0.so.0(g_log+0x83)[0x3af5c34f33]
/usr/libexec/amanda/sendbackup(start_index+0x290)[0x4037f0]
/usr/libexec/amanda/sendbackup[0x4075f0]
/usr/libexec/amanda/sendbackup(main+0x10a4)[0x405834]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x3fe1c1d8b4]
/usr/libexec/amanda/sendbackup[0x403139]
So it looks like a problem sending the index data. I've set index_server
to the correct hostname in /etc/amanda-client.conf. Will this properly
override the settings configured at compile time? This client is
installed
from the redhat rpm, so it has no local compile-time configuration.
The /etc/amanda-client.conf looks like this:
#
# amanda.conf - sample Amanda client configuration file.
#
# This file normally goes in /etc/amanda/amanda-client.conf.
#
conf test # your config name
index_server amanda-server# your amindexd server
tape_server amanda-server# your amidxtaped server
tapedev tape:/dev/nst1 # your tape device
# if not set, Use configure or ask server.
# if set to empty string , ask server
# amrecover will use the changer if set to the
value
# of 'amrecover_changer' in the server
amanda.conf.
# auth- authentication scheme to use between server and
client.
# Valid values are bsd, bsdudp, bsdtcp,
krb5, local,
# rsh and ssh.
# Default: [auth bsdtcp]
auth bsd
ssh_keys # your ssh keys file if you use ssh
auth
Anyone see anything obvious we're overlooking? (Yeah, besides needing to
upgrade the server!) :-)
-Mitch
Index: client-src/sendbackup.c
===
--- client-src/sendbackup.c (revision 17487)
+++ client-src/sendbackup.c (working copy)
@@ -436,6 +436,10 @@
if(am_has_feature(g_options-features, fe_rep_options_hostname)) {
g_printf(hostname=%s;, g_options-hostname);
}
+if (!am_has_feature(g_options-features, fe_rep_options_features)
+ !am_has_feature(g_options-features, fe_rep_options_hostname)) {
+ g_printf(;);
+}
g_printf(\n);
fflush(stdout);
if (freopen(/dev/null, w, stdout) == NULL) {
