Re: amanda windows client times out
On 2008-07-10 04:45, FL wrote: Hi. I'm using the latest AMANDA 2.6.0p1 on a Debian Linux box (I compile the source--Debian packages are behind). The Linux clients work (except for an occasional 80 hour dump, as bad as that sounds on many levels, including dump levels). However, the windows client estimates time out. Not being a Windologian, I implore the group for guidance. I'm using bsdtcp, not ssh. My amstatus follows. FL [EMAIL PROTECTED] Daily]$ amstatus Daily Using /var/log/amanda/Daily/amdump From Wed Jul 9 18:05:02 EDT 2008 [...] curdata.gc.cuny.edu:c:0 10405m wait for dumping curdata.gc.cuny.edu:e:0 planner: [disk e:, all estimate timed out] curdata.gc.cuny.edu:e:Applications0 planner: [disk e:Applications, all estimate timed out] So you installed cygwin on those Windows clients, and run some port of Amanda-clients for Cygwin on Windows, right? And you're using gnutar for cygwin on those windows clients? Which version? For at least one windows client you did get an estimate for at least one DLE. Is there any difference in the definition of the DLE's of one that works or one that does not work? On the client, in the client debug files, (wherever those may be located in cygwin) do you see an error message when gnutar does it's estimates on the different drives? Or do they just take too long, and the amanda server has given up waiting for those numbers? -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: amanda windows client times out
On Thu, Jul 10, 2008 at 2:14 AM, Paul Bijnens [EMAIL PROTECTED] wrote: On 2008-07-10 04:45, FL wrote: Hi. I'm using the latest AMANDA 2.6.0p1 on a Debian Linux box (I compile the source--Debian packages are behind). The Linux clients work (except for an occasional 80 hour dump, as bad as that sounds on many levels, including dump levels). However, the windows client estimates time out. Not being a Windologian, I implore the group for guidance. I'm using bsdtcp, not ssh. My amstatus follows. FL [EMAIL PROTECTED] Daily]$ amstatus Daily Using /var/log/amanda/Daily/amdump From Wed Jul 9 18:05:02 EDT 2008 [...] curdata.gc.cuny.edu:c:0 10405m wait for dumping curdata.gc.cuny.edu:e:0 planner: [disk e:, all estimate timed out] curdata.gc.cuny.edu:e:Applications0 planner: [disk e:Applications, all estimate timed out] So you installed cygwin on those Windows clients, and run some port of Amanda-clients for Cygwin on Windows, right? And you're using gnutar for cygwin on those windows clients? Which version? I'll be able to answer these questions specifically when I have access; for now let me say that I installed the latest zmanda windows client using the installation package available on the zmanda download page. This is the version: AmandaBackupClient-2-5-2p1.msi I did not go out of my way to install cygwin or gnutar---I understand that the zmanda windows client does this and that the zmanda wiki advises against installing your own versions; from the zmanda wiki: http://wiki.zmanda.com/index.php/Windows_client The Amanda Windows client package uses the Microsoft Windows installer and includes Amanda client dependencies (Gnu tar, GnuZip, OpenSSH) as part of the package. This Windows client uses Cygwin and will install Cygwin binaries. If you have Cygwin installed, this package may not work. For at least one windows client you did get an estimate for at least one DLE. Is there any difference in the definition of the DLE's of one that works or one that does not work? Here are the DLEs # windows client test curdata.gc.cuny.edu c:\ comp-root-tar curdata.gc.cuny.edu e:\ comp-root-tar curdata.gc.cuny.edu z:\ comp-root-tar curdata.gc.cuny.edu e:\Applications comp-root-tar curdata.gc.cuny.edu e:\ArcIMS comp-root-tar The first worked; the rest didn't On the client, in the client debug files, (wherever those may be located in cygwin) do you see an error message when gnutar does it's estimates on the different drives? Or do they just take too long, and the amanda server has given up waiting for those numbers? -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
amanda windows client times out
Hi. I'm using the latest AMANDA 2.6.0p1 on a Debian Linux box (I compile the source--Debian packages are behind). The Linux clients work (except for an occasional 80 hour dump, as bad as that sounds on many levels, including dump levels). However, the windows client estimates time out. Not being a Windologian, I implore the group for guidance. I'm using bsdtcp, not ssh. My amstatus follows. FL [EMAIL PROTECTED] Daily]$ amstatus Daily Using /var/log/amanda/Daily/amdump From Wed Jul 9 18:05:02 EDT 2008 cml10:/boot 1 0m finished (19:27:34) cml10:/etc010m finished (19:29:25) cml10:/home/ashp/shared 0 1163m finished (20:01:11) cml10:/home/ashp/www 0 5394m finished (21:54:58) cml10:/home/cunydsc 072m finished (19:34:29) cml10:/home/cunywired 0 0m finished (19:28:24) cml10:/home/flengyel 017m finished (19:30:32) cml10:/home/forever 0 0m finished (19:27:53) cml10:/home/greenstone0 0m finished (19:27:15) cml10:/home/hlbll 025m finished (19:30:49) cml10:/home/itcp 072m finished (19:33:51) cml10:/home/jbrown099m finished (19:36:20) cml10:/home/kkeramidas0 0m finished (19:26:57) cml10:/home/lostmuseum0 180m finished (19:41:52) cml10:/home/mathwiki 039m finished (19:26:40) cml10:/home/moodle0 129m finished (19:40:50) cml10:/home/nml 0 296m finished (19:44:20) cml10:/home/projectstretch1 1206m finished (19:53:02) cml10:/home/proust0 122m finished (19:39:11) cml10:/home/sciart031m finished (19:31:35) cml10:/home/usersupport 047m finished (19:32:24) cml10:/home/virtualny 0 3111m finished (21:25:21) cml10:/home/womenstudies 0 2m finished (19:28:46) cml10:/var0 1644m finished (20:52:34) cur10:/boot 027m finished (19:31:06) cur10:/etc010m finished (19:28:11) cur10:/home/dmulcahey 0 0m finished (19:26:51) cur10:/home/oasis 012m finished (19:29:40) cur10:/home/ojs 0 108m finished (19:38:21) cur10:/home/research 096m finished (19:35:36) cur10:/home/sda 0 3030m finished (21:08:57) cur10:/home/tinyboxer 0 452m finished (19:47:49) cur10:/var0 214m finished (19:43:06) curdata.gc.cuny.edu:c:0 10405m wait for dumping curdata.gc.cuny.edu:e:0 planner: [disk e:, all estimate timed out] curdata.gc.cuny.edu:e:Applications0 planner: [disk e:Applications, all estimate timed out] curdata.gc.cuny.edu:e:ArcIMS 0 planner: [disk e:ArcIMS, all estimate timed out] curdata.gc.cuny.edu:z:0 planner: [disk z:, all estimate timed out] curdc1.gc.cuny.edu:c: 0 planner: [disk c:, all estimate timed out] curdc2.gc.cuny.edu:c: 0 planner: [disk c:, all estimate timed out] gccg.gc.cuny.edu:/boot033m finished (19:31:55) gccg.gc.cuny.edu:/etc 016m finished (19:30:17) gccg.gc.cuny.edu:/opt 0 1320m finished (20:09:39) gccg.gc.cuny.edu:/var 073m finished (19:34:59) ldap.gc.cuny.edu:/boot012m finished (19:28:32) ldap.gc.cuny.edu:/etc 015m finished (19:29:53) ldap.gc.cuny.edu:/var 070m finished (19:32:55) m245.gc.cuny.edu:/boot1 0m finished (19:43:12) m245.gc.cuny.edu:/etc 1 0m finished (19:53:07) m245.gc.cuny.edu:/etc/samba 1 0m finished (19:41:57) m245.gc.cuny.edu:/home/bmartin1 0m finished (19:27:03) m245.gc.cuny.edu:/home/m245/LDAPadmin/0 0m finished (19:31:44) m245.gc.cuny.edu:/home/m245/agreer/ 1 2m finished
client times out
We're running amanda-2.4.5p1 server on a white box under debian/sarge. We're backing up from 8 hosts without any problems beyond an occasional client timeout. Working clients are running debian/sarge, RHAS 2.1, and AIX 5, and the same 2.4.5p1 release of amanda. We have a CentOS 4.1 client that is failing consistently with client-side timeouts. The client starts, dumps 35 MB to the server, then times out. The partition being dumped is around 1 GB. The time out occurs when iptables on the client is turned on, and also when it is turned off. Gtar is 1.15.1. Timeout messages in /tmp/amanda/sendbackup.* on the client look like this: --- sendbackup: debug 1 pid 18885 ruid 518 euid 518: start at Fri Feb 10 02:20:02 2006 [snip] sendbackup: time 0.001: got all connections [snip] sendbackup-gnutar: time 0.062: doing level 0 dump from date: 1970-01-01 0:00:00 GMT [snip] sendbackup-gnutar: time 0.064: /usr/local/amanda/2.4.5p1/libexec/runtar: pid 18889 sendbackup: time 958.026: index tee cannot write [Connection timed out] sendbackup: time 958.026: pid 18887 finish time Fri Feb 10 02:36:00 2006 sendbackup: time 958.026: 125: strange(?): sendbackup: index tee cannot write [Connection timed out] sendbackup: time 958.028: error [/usr/local/amanda/2.4.5p1/bin/gtar got signal 13] sendbackup: time 958.028: pid 18885 finish time Fri Feb 10 02:36:00 2006 --- We reduced the keepalive interval on both client and server but didn't see a change. Any suggestions would be welcome. Thanks, Roy Heimbach -- Roy Heimbach [EMAIL PROTECTED] / 505-277-8348 User Services / [EMAIL PROTECTED] / University of New Mexico
Client times out on amcheck after upgrade to 2.4.3
Hi I upgraded to amanda 2.4.3 and now my client times out when running amcheck from the server. Also no selfcheck...debug file is created on client.xinetd starts amanda without errors or warnings. The amandad...debug file looks like this: --- amandad: debug 1 pid 13640 ruid 501 euid 501: start at Mon Jan 6 17:39:28 2003 amandad: version 2.4.3 amandad: build: VERSION=Amanda-2.4.3 amandad:BUILT_DATE=Fri Jan 3 16:57:03 PST 2003 amandad:BUILT_MACH=Linux host 2.4.7-10 #1 Thu Sep 6 17:27:27 E DT 2001 i686 unknown amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--with-user=amanda' '--with-group=amanda' '--with-gnutar-listdir=/var/amanda' '--with-debugging' '--with-portrange=5,50100' '--wit h-configdir=/etc/amanda' '--with-config=daily' '--with-tape-server=host .com' '--with-gnutar=/bin/tar' '--without-server' '--with-index-server=host '--with-amandahosts' amandad: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin amandad:libexecdir=/usr/local/libexec ma ndir=/usr/local/man amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA _DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/etc/amanda DEV_PREFIX=/dev/ amandad:RDEV_PREFIX=/dev/ DUMP=/sbin/dump amandad:RESTORE=/sbin/restore GNUTAR=/bin/tar amandad:COMPRESS_PATH=/usr/bin/gzip amandad:UNCOMPRESS_PATH=/usr/bin/gzip MAILER=/usr/bin/Mail amandad:listed_incr_dir=/var/amanda amandad: defs: DEFAULT_SERVER=host amandad:DEFAULT_CONFIG=daily amandad:DEFAULT_TAPE_SERVER=host amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc amandad: time 0.000: got packet: Amanda 2.4 REQ HANDLE 001-D85C0808 SEQ 1041903629 SECURITY USER amanda SERVICE noop OPTIONS features=feff9f00; amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 001-D85C0808 SEQ 1041903629 amandad: time 0.001: bsd security: remote host goodchild.organicromantic.com user amanda local user amanda amandad: time 0.001: amandahosts security check passed amandad: time 0.001: running service noop amandad: time 0.001: sending REP packet: Amanda 2.4 REP HANDLE 001-D85C0808 SEQ 1041903629 OPTIONS features=feff9f00; amandad: time 9.998: dgram_recv: timeout after 10 seconds amandad: time 9.998: waiting for ack: timeout, retrying amandad: time 10.008: got packet: Amanda 2.4 REQ HANDLE 001-D85C0808 SEQ 1041903629 SECURITY USER amanda SERVICE noop OPTIONS features=feff9f00; amandad: time 10.008: it is not an ack amandad: time 20.007: dgram_recv: timeout after 10 seconds amandad: time 20.008: waiting for ack: timeout, retrying amandad: time 20.009: got packet: Amanda 2.4 REQ HANDLE 001-D85C0808 SEQ 1041903629 SECURITY USER amanda SERVICE noop OPTIONS features=feff9f00; amandad: time 20.009: it is not an ack amandad: time 30.007: dgram_recv: timeout after 10 seconds amandad: time 30.007: waiting for ack: timeout, retrying amandad: time 40.007: dgram_recv: timeout after 10 seconds amandad: time 40.007: waiting for ack: timeout, retrying amandad: time 50.007: dgram_recv: timeout after 10 seconds amandad: time 50.007: waiting for ack: timeout, giving up! amandad: time 50.007: pid 13640 finish time Mon Jan 6 17:40:18 2003 - Is it just me or does it appear that the client is waiting for an ACK and gets a REQ instead? What is going wrong here? Can someone please help?!!! Thanks for any and all help!
