Re: wierd amandad timeout error
On Wed, Nov 20, 2002 at 07:24:18AM +, John P. Looney wrote: Sounds intriguing. Is this a simple matter in amanda, or do you mean backup root, except /usr in one entry in disklist, then /usr in another entry ? Does this mean there is a max size to filesystems you can backup in amanda? No, not an amanda limitation, but many OS's have a max filesize limit of 2GB. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: wierd amandad timeout error
Jon LaBadie wrote: On Wed, Nov 20, 2002 at 07:24:18AM +, John P. Looney wrote: Sounds intriguing. Is this a simple matter in amanda, or do you mean backup root, except /usr in one entry in disklist, then /usr in another entry ? Does this mean there is a max size to filesystems you can backup in amanda? No, not an amanda limitation, but many OS's have a max filesize limit of 2GB. It might also be pointed out that 'tar' has this 2 Gb limitation, unless they fixed it in 1.13.25. I've run headlong into it before. =G=
Re: wierd amandad timeout error
Hi, Galen Johnson schrieb: Jon LaBadie wrote: [] It might also be pointed out that 'tar' has this 2 Gb limitation, unless they fixed it in 1.13.25. I've run headlong into it before. =G= i think this is not correct. i've handeled archives 2gb with tar 1.12. If you are on a filesystem with a 2 gb limit, your libc has a 2g Limit or the system your tar was compiled on had a 2gb limit, yes then tar too has the 2GB problem when reading/writing from/to hd. This was true for most intel-linux systems until auround the middle of this year. (don't remember exact time when it went away) Christoph
Re: wierd amandad timeout error
This is correct. It depends on what c lib that tar was compiled with. See Tom's Root Boot website for an explanation of this. He distributes 2 versions of dd, one has Large File System support while the other does not. He goes into detail of the differences. http://www.toms.net/rb/ On Wednesday 20 November 2002 11:04 am, Christoph Scheeder wrote: Hi, Galen Johnson schrieb: Jon LaBadie wrote: [] It might also be pointed out that 'tar' has this 2 Gb limitation, unless they fixed it in 1.13.25. I've run headlong into it before. =G= i think this is not correct. i've handeled archives 2gb with tar 1.12. If you are on a filesystem with a 2 gb limit, your libc has a 2g Limit or the system your tar was compiled on had a 2gb limit, yes then tar too has the 2GB problem when reading/writing from/to hd. This was true for most intel-linux systems until auround the middle of this year. (don't remember exact time when it went away) Christoph
wierd amandad timeout error
amcheck -c on the server says that all my clients are fine. However, when I run amdump, one of the clients, which worked fine previously, is now failing. The (rather long) debug file in /tmp/amanda seems to indicate that it was working fine, then timed out. Any idea why this could be ? It's always just this host. It's a very similar problem (with no solution) to the one encountered by; http://www.mail-archive.com/amanda-users@amanda.org/msg14385.html John START included debug log --- [root@jny06 amanda]# cat amandad.20021118020001.debug amandad: debug 1 pid 15690 ruid 33 euid 33 start time Mon Nov 18 02:00:01 2002 amandad: version 2.4.2p2 amandad: build: VERSION=Amanda-2.4.2p2 amandad:BUILT_DATE=Thu Apr 5 09:18:00 EDT 2001 amandad:BUILT_MACH=Linux porky.devel.redhat.com 2.2.17-8smp #1 SMP Fri Nov 17 16:12:17 EST 2000 i686 unknown amandad:CC=gcc amandad: paths: bindir=/usr/bin sbindir=/usr/sbin amandad:libexecdir=/usr/lib/amanda mandir=/usr/share/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 SAMBA_CLIENT=/usr/bin/smbclient amandad:GNUTAR=/bin/tar COMPRESS_PATH=/usr/bin/gzip amandad:UNCOMPRESS_PATH=/usr/bin/gzip MAILER=/usr/bin/Mail amandad:listed_incr_dir=/var/lib/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=localhost 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 got packet: Amanda 2.4 REQ HANDLE 007-F8510608 SEQ 1037584808 SECURITY USER amanda SERVICE sendsize OPTIONS maxdumps=1;hostname=jny06.jinny.ie; bsd security: remote host krusty.jinny.ie user amanda local user amanda amandahosts security check passed amandad: running service /usr/lib/amanda/sendsize amandad: got packet: Amanda 2.4 REQ HANDLE 007-F8510608 SEQ 1037584808 SECURITY USER amanda SERVICE sendsize OPTIONS maxdumps=1;hostname=jny06.jinny.ie; GNUTAR / 0 1970:1:1:0:0:0 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR / 1 2002:10:13:1:45:45 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar amandad: received dup P_REQ packet, ACKing it sending ack: Amanda 2.4 ACK HANDLE 007-F8510608 SEQ 1037584808 amandad: got packet: Amanda 2.4 REQ HANDLE 007-F8510608 SEQ 1037584808 SECURITY USER amanda SERVICE sendsize OPTIONS maxdumps=1;hostname=jny06.jinny.ie; GNUTAR / 0 1970:1:1:0:0:0 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR / 1 2002:10:13:1:45:45 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar amandad: received dup P_REQ packet, ACKing it sending ack: Amanda 2.4 ACK HANDLE 007-F8510608 SEQ 1037584808 amandad: sending REP packet: Amanda 2.4 REP HANDLE 007-F8510608 SEQ 1037584808 OPTIONS maxdumps=1; / 0 SIZE 2615460 / 1 SIZE 1357520 amandad: dgram_recv: timeout after 10 seconds amandad: waiting for ack: timeout, retrying amandad: dgram_recv: timeout after 10 seconds amandad: waiting for ack: timeout, retrying amandad: dgram_recv: timeout after 10 seconds amandad: waiting for ack: timeout, retrying amandad: dgram_recv: timeout after 10 seconds amandad: waiting for ack: timeout, retrying amandad: dgram_recv: timeout after 10 seconds amandad: waiting for ack: timeout, giving up! amandad: pid 15690 finish time Mon Nov 18 05:24:33 2002 END included debug log ---
Re: wierd amandad timeout error
At 12:53 PM 11/19/2002 +, you wrote: amcheck -c on the server says that all my clients are fine. However, when I run amdump, one of the clients, which worked fine previously, is now failing. The (rather long) debug file in /tmp/amanda seems to indicate that it was working fine, then timed out. Any idea why this could be ? It's always just this host. Are you *sure* there aren't any firewalls in between? If the data size on this client got large enough, it could have bumped over to the realm of problem. My problem went like this: server contacts client: sent me estimate client: thinks client: replies inside of link created owned by server - fine. but if client thinks T long, that link dies. Then client has to create a new link for the reply (all done by the lower levels of software) and the firewall may not ALLOW client to initiate a link. So that's where the problem arises -- when the reply takes longer than . some value. You might try splitting the client's tar files into 2 pieces -- see if that makes it work OK again. That would strongly suggest this kind of situtation! Deb Baddorf --- Deb Baddorf [EMAIL PROTECTED] 840-2289 You can't help getting older, but you don't have to get old. - George Burns IXOYE
Re: wierd amandad timeout error
On Tue, Nov 19, 2002 at 05:25:52PM -0600, Deb Baddorf mentioned: Are you *sure* there aren't any firewalls in between? If the data size on this client got large enough, it could have bumped over to the realm of problem. My problem went like this: 1000% sure. I was also trying to backup a machine the far side of our firewall, and haven't quite managed yet. But, this machine, and all the other ones connected to it. You might try splitting the client's tar files into 2 pieces -- see if that makes it work OK again. That would strongly suggest this kind of situtation! Sounds intriguing. Is this a simple matter in amanda, or do you mean backup root, except /usr in one entry in disklist, then /usr in another entry ? Does this mean there is a max size to filesystems you can backup in amanda? John
