strange error listed in the daily report
My dumps have been failing right when it seems the dump should complete.
Below is a snippet of information in the amreport that I get every
night. The client and server have no problems communicating so I'm not
sure why I would get this type of message. Does anyone have any ideas?
Thanks
Jeff
I have attached a copy of my amreport below:
snippet
FAILED AND STRANGE DUMP DETAILS:
/-- smtp0 da0s1e lev 0 FAILED [mesg read: Connection reset by peer]
sendbackup: start [smtp0:da0s1e level 0]
sendbackup: info BACKUP=/usr/local/bin/gtar
sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/usr/local/bin/gtar
-f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
\
amreport:
*** A TAPE ERROR OCCURRED: [not an amanda tape].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
smtp0 da0s1e lev 0 FAILED [mesg read: Connection reset by peer]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 2:01
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.10.00.1
Original Size (meg) 0.80.00.8
Avg Compressed Size (%) 8.7-- 8.7 (level:#disks
...)
Filesystems Dumped1 0 1 (1:1)
Avg Dump Rate (k/s)23.5--23.5
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
FAILED AND STRANGE DUMP DETAILS:
/-- smtp0 da0s1e lev 0 FAILED [mesg read: Connection reset by peer]
sendbackup: start [smtp0:da0s1e level 0]
sendbackup: info BACKUP=/usr/local/bin/gtar
sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/usr/local/bin/gtar
-f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
\
NOTES:
planner: Adding new disk smtp0:da0s1e.
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS
KB/s
-- -
smtp0da0s1a 1 870 76 8.7 0:03 23.5 N/A N/A
smtp0da0s1e 0 FAILED
---
(brought to you by Amanda version 2.4.3b2)
Re: Make problem on Solaris 2.8
I suspect that you've got an ld.so path issue. The best way to deal with that is to have the linking invocations of gcc specify -R /where/ever/your/libs/are, with LD_LIBRARY_PATH unset.
Make problem on Solaris 2.8
Hi all: I'm trying to run make for Amanda 2.4.2p2 on a Solaris 2.8 SPARC server with the following configure options: ./configure --with-user=amanda --with-group=amanda During the make process, the following error occurs. Here's the tail end of the error message: rm -f genversion.h genversion.h.new echo '#define CC "gcc"' > genversion.h.new echo '#define BUILT_DATE "'`date`'"' >> genversion.h.new echo '#define BUILT_MACH "'`uname -a || echo UNKNOWN HOST`'"' >> genversion.h.new mv genversion.h.new genversion.h gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c genversion.c gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c versuff.c /bin/sh ../libtool --mode=link gcc -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -o genversion genversion.o versuff.o alloc.o debug.o error.o util.o file.o -lgen -lm -lreadline -ltermcap -lsocket -lnsl -lintl mkdir .libs gcc -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -o genversion genversion.o versuff.o alloc.o debug.o error.o util.o file.o -lgen -lm -lreadline -ltermcap -lsocket -lnsl -lintl rm -f version.c ./genversion > version.c ld.so.1: ./genversion: fatal: libreadline.so.4: open failed: No such file or directory *** Error code 137 make: Fatal error: Command failed for target `version.c' Current working directory /home/amanda/amanda-2.4.2p2/common-src *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Any guidance will be greatly appreciated. =)
Re: Amanda through translated addresses
If, for example, you setup your internal machines to have domains like 'host.private.daily.umn.edu', you would want your resolv.conf to look like this: domain private.daily.umn.edu search private.daily.umn.edu daily.umn.edu nameserver x It all depends how you've setup your internal DNS, since there are a 1000 different ways to do it. And even more opinions as to their correctness. As for tcpdump, I would read the man page, but probably something like this: tcpdump -i -l -n udp | tee tcpdump.output that way you can see the output and also go back to view the file later if you're seeing a ton of udp traffic. If you comment out all entries except the server in the disklist (just to narrow your focus), are you getting anything in /tmp/amanda? -doug On Tue, 19 Mar 2002, Lee Parsons wrote: > Yes. We can run nslookup from the amanda server on the hostnames of any > of the machines with NAT addresses we want it to backup and they resolve > to the proper NAT addresses. > The file /etc/resolv.conf has a domain and a nameserver entry, no search > entry, unless thats a synonymous term with nameserver. Ping and ssh work > fine from the amanda server to other internal machines. > > Whats the proper syntax for running tcpdump on amcheck? Thats not > something that I often need to run. > > --- > Lee Parsons > LAN Administrator > The Minnesota Daily > www.mndaily.com > > > > On Tue, 19 Mar 2002, Doug Silver wrote: > > > Ok, if you run this: > > nslookup `hostname` > > > > on the amanda server, does that resolve? In the resolv.conf file, are > > there 'domain' and 'search' entries? You can ping all the internal > > machines, correct? What about some other service like ssh? > > > > As a last resort, you could run tcpdump while running amcheck to one or > > two clients to see what the packets actually look like. > > > > -- > > ~ > > Doug Silver > > Network Manager > > Quantified Systems, Inc > > ~ > > On Tue, 19 Mar 2002, Lee Parsons wrote: > > > > > Our NAT addresses are class C (192.168.0.xxx). The Amanda server resides > > > at 192.168.0.18. It is unable to back itself up. We have a DNS server > > > set up for the NAT addresses at 192.168.0.10 that is referred to in > > > /etc/resolv.conf as the only DNS server for the Amanda server. However > > > the Amanda server has no difficulties with the machines on the public IPs > > > when it runs amcheck. We also tried to put the IP addresses of the > > > internal machines into the disklist file, and it made no difference. > > > Still the host timeout. > > > > > > --- > > > Lee Parsons > > > LAN Administrator > > > The Minnesota Daily > > > www.mndaily.com > > > > > > On Tue, 19 Mar 2002, Doug Silver wrote: > > > > > > > > > > > Perhaps a bit more detail would let us figure out the problem. For > > > > example, here's my setup: > > > > > > > > Amanda server: 172.16.20.140 (private IP) it's resolv.conf allows it to > > > > resolve both internal and external names since I have an internal DNS > > > > machine. I back up a bunch of private IP's (172.10.x) and external > > > > (public IPs). > > > > > > > > Do you have an internal dns server that the amanda server can use to > > > > resolve all IPs? I'm not sure if Amanda would use /etc/hosts to resolve > > > > IP/names, so that might be a cause too. > > > > > > > > When you said you tried pointing to the internal machines by their NAT > > > > addresses, don't you mean the external machines? Regardless, on the > > > > server, recheck inetd, HUP it, and run 'amcheck -c CONFIG'. There should > > > > be some sort of /tmp/amanda debug files available. > > > > > > > > -- > > > > ~ > > > > Doug Silver > > > > Network Manager > > > > Quantified Systems, Inc > > > > ~
Re: Amanda through translated addresses
Yes. We can run nslookup from the amanda server on the hostnames of any of the machines with NAT addresses we want it to backup and they resolve to the proper NAT addresses. The file /etc/resolv.conf has a domain and a nameserver entry, no search entry, unless thats a synonymous term with nameserver. Ping and ssh work fine from the amanda server to other internal machines. Whats the proper syntax for running tcpdump on amcheck? Thats not something that I often need to run. --- Lee Parsons LAN Administrator The Minnesota Daily www.mndaily.com On Tue, 19 Mar 2002, Doug Silver wrote: > Ok, if you run this: > nslookup `hostname` > > on the amanda server, does that resolve? In the resolv.conf file, are > there 'domain' and 'search' entries? You can ping all the internal > machines, correct? What about some other service like ssh? > > As a last resort, you could run tcpdump while running amcheck to one or > two clients to see what the packets actually look like. > > -- > ~ > Doug Silver > Network Manager > Quantified Systems, Inc > ~ > On Tue, 19 Mar 2002, Lee Parsons wrote: > > > Our NAT addresses are class C (192.168.0.xxx). The Amanda server resides > > at 192.168.0.18. It is unable to back itself up. We have a DNS server > > set up for the NAT addresses at 192.168.0.10 that is referred to in > > /etc/resolv.conf as the only DNS server for the Amanda server. However > > the Amanda server has no difficulties with the machines on the public IPs > > when it runs amcheck. We also tried to put the IP addresses of the > > internal machines into the disklist file, and it made no difference. > > Still the host timeout. > > > > --- > > Lee Parsons > > LAN Administrator > > The Minnesota Daily > > www.mndaily.com > > > > On Tue, 19 Mar 2002, Doug Silver wrote: > > > > > > > > Perhaps a bit more detail would let us figure out the problem. For > > > example, here's my setup: > > > > > > Amanda server: 172.16.20.140 (private IP) it's resolv.conf allows it to > > > resolve both internal and external names since I have an internal DNS > > > machine. I back up a bunch of private IP's (172.10.x) and external > > > (public IPs). > > > > > > Do you have an internal dns server that the amanda server can use to > > > resolve all IPs? I'm not sure if Amanda would use /etc/hosts to resolve > > > IP/names, so that might be a cause too. > > > > > > When you said you tried pointing to the internal machines by their NAT > > > addresses, don't you mean the external machines? Regardless, on the > > > server, recheck inetd, HUP it, and run 'amcheck -c CONFIG'. There should > > > be some sort of /tmp/amanda debug files available. > > > > > > -- > > > ~ > > > Doug Silver > > > Network Manager > > > Quantified Systems, Inc > > > ~ > > > > > > > > > >
Re: Amanda through translated addresses
Ok, if you run this: nslookup `hostname` on the amanda server, does that resolve? In the resolv.conf file, are there 'domain' and 'search' entries? You can ping all the internal machines, correct? What about some other service like ssh? As a last resort, you could run tcpdump while running amcheck to one or two clients to see what the packets actually look like. -- ~ Doug Silver Network Manager Quantified Systems, Inc ~ On Tue, 19 Mar 2002, Lee Parsons wrote: > Our NAT addresses are class C (192.168.0.xxx). The Amanda server resides > at 192.168.0.18. It is unable to back itself up. We have a DNS server > set up for the NAT addresses at 192.168.0.10 that is referred to in > /etc/resolv.conf as the only DNS server for the Amanda server. However > the Amanda server has no difficulties with the machines on the public IPs > when it runs amcheck. We also tried to put the IP addresses of the > internal machines into the disklist file, and it made no difference. > Still the host timeout. > > --- > Lee Parsons > LAN Administrator > The Minnesota Daily > www.mndaily.com > > On Tue, 19 Mar 2002, Doug Silver wrote: > > > > > Perhaps a bit more detail would let us figure out the problem. For > > example, here's my setup: > > > > Amanda server: 172.16.20.140 (private IP) it's resolv.conf allows it to > > resolve both internal and external names since I have an internal DNS > > machine. I back up a bunch of private IP's (172.10.x) and external > > (public IPs). > > > > Do you have an internal dns server that the amanda server can use to > > resolve all IPs? I'm not sure if Amanda would use /etc/hosts to resolve > > IP/names, so that might be a cause too. > > > > When you said you tried pointing to the internal machines by their NAT > > addresses, don't you mean the external machines? Regardless, on the > > server, recheck inetd, HUP it, and run 'amcheck -c CONFIG'. There should > > be some sort of /tmp/amanda debug files available. > > > > -- > > ~ > > Doug Silver > > Network Manager > > Quantified Systems, Inc > > ~ > > > > >
Re: Amanda through translated addresses
Our NAT addresses are class C (192.168.0.xxx). The Amanda server resides at 192.168.0.18. It is unable to back itself up. We have a DNS server set up for the NAT addresses at 192.168.0.10 that is referred to in /etc/resolv.conf as the only DNS server for the Amanda server. However the Amanda server has no difficulties with the machines on the public IPs when it runs amcheck. We also tried to put the IP addresses of the internal machines into the disklist file, and it made no difference. Still the host timeout. --- Lee Parsons LAN Administrator The Minnesota Daily www.mndaily.com On Tue, 19 Mar 2002, Doug Silver wrote: > > Perhaps a bit more detail would let us figure out the problem. For > example, here's my setup: > > Amanda server: 172.16.20.140 (private IP) it's resolv.conf allows it to > resolve both internal and external names since I have an internal DNS > machine. I back up a bunch of private IP's (172.10.x) and external > (public IPs). > > Do you have an internal dns server that the amanda server can use to > resolve all IPs? I'm not sure if Amanda would use /etc/hosts to resolve > IP/names, so that might be a cause too. > > When you said you tried pointing to the internal machines by their NAT > addresses, don't you mean the external machines? Regardless, on the > server, recheck inetd, HUP it, and run 'amcheck -c CONFIG'. There should > be some sort of /tmp/amanda debug files available. > > -- > ~ > Doug Silver > Network Manager > Quantified Systems, Inc > ~ > >
Re: Amanda through translated addresses
On Tue, 19 Mar 2002, Lee Parsons wrote: > We tried it both ways. The backup server actually refers to another > machine on the NAT range for its DNS, so when it pings the names of the > machines with NAT addresses, it will get responses from their NAT IPs. > We also added them manually to the /etc/hosts file on the backup server to > point to their NAT addresses just to avoid confusion. That made no > difference. Then we changed the disklist file to point to the internal > machines by their NAT addresses, which also made no difference. What else > could be causing it? All the machines with translated addresses are > reporting "selfcheck request timed out. Host down?" Including the > backup server itself when running amcheck. What are we not seeing here? > > --- > Lee Parsons > LAN Administrator > The Minnesota Daily > www.mndaily.com > > On Mon, 18 Mar 2002, John Koenig wrote: > > > Do your names refer to external (public) IP addresses while your > > machines behind the NAT actually have internal (private) IP addresses? > > > > > Perhaps a bit more detail would let us figure out the problem. For example, here's my setup: Amanda server: 172.16.20.140 (private IP) it's resolv.conf allows it to resolve both internal and external names since I have an internal DNS machine. I back up a bunch of private IP's (172.10.x) and external (public IPs). Do you have an internal dns server that the amanda server can use to resolve all IPs? I'm not sure if Amanda would use /etc/hosts to resolve IP/names, so that might be a cause too. When you said you tried pointing to the internal machines by their NAT addresses, don't you mean the external machines? Regardless, on the server, recheck inetd, HUP it, and run 'amcheck -c CONFIG'. There should be some sort of /tmp/amanda debug files available. -- ~ Doug Silver Network Manager Quantified Systems, Inc ~
Re: Amanda through translated addresses
If the server can't back up itself, I'd start there. I just checked on my system and IP's seem to work, at least with amcheck, so perhaps that will solve your problem. If you used the FBSD port (/usr/ports) system on your server to build Amanda, I think it automatically required FQDN for the hosts. Check the debug files on the server to confirm what amandad reports for the defaults. I use FQDN for all machines, but that's just me ;) ~ Doug Silver Network Manager Quantified Systems, Inc ~ On Mon, 18 Mar 2002, Lee Parsons wrote: > Can I use IP addresses in the disklist files rather than the FQDNs? If I > could do that then I wouldn't have to worry about DNS to begin with. I > haven't seen anything explicitly say we can or cannot but every disklist > file I've seen always has the FQDN. Although the other thing I notice i > that I can ping the NAT servers from the amanda server by their names > without a problem. I'll try IPs in the disklist file and see what > happens. > > > --- > Lee Parsons > LAN Administrator > The Minnesota Daily > www.mndaily.com > > On Mon, 18 Mar 2002, Doug Silver wrote: > > > On Mon, 18 Mar 2002, Lee Parsons wrote: > > > > > We began using NAT addresses on our network a few months ago, but at first > > > we kept all of our systems that were backed up by amanda outside the NAT > > > range. As time moved on we started bringing some of them inside, and it > > > seemed that the easiest way to get both the inside (translated) and > > > outside (nontranslated) addresses would be to build an amanda server and > > > place it inside. After building a system with FreeBSD 4.5 and amanda, we > > > found that it was able to connect to the machines outside, but none of the > > > machines inside, including itself. Is there something we missed? We > > > enabled the "operator" accounts on all the systems, we used inetd to start > > > amanadad as operator on all the systems, and added the UDP and the two TCP > > > ports into /etc/services. But yet we still cannot get the new amanda > > > server to get anything inside, including itself. When we run amcheck it > > > reports all the systems inside to be "host down?". Any ideas would be > > > much appreciated. > > > > > > --- > > > Lee Parsons > > > LAN Administrator > > > The Minnesota Daily > > > www.mndaily.com > > > > > > > I would check your DNS settings (and /etc/resolv.conf) and if they > > correspond to what you have listed in your disklist file. If the amanda > > server has a problem with the user it will complain about that in > > particular (i.e. root/operator/etc). In your case, start with one machine > > and get that one working -- it's probably the same problem everywhere. > > Perhaps you aren't using the correct FQDN? > > > > Debug files will be in /tmp/amanda. > >
Re: Amanda through translated addresses
We tried it both ways. The backup server actually refers to another machine on the NAT range for its DNS, so when it pings the names of the machines with NAT addresses, it will get responses from their NAT IPs. We also added them manually to the /etc/hosts file on the backup server to point to their NAT addresses just to avoid confusion. That made no difference. Then we changed the disklist file to point to the internal machines by their NAT addresses, which also made no difference. What else could be causing it? All the machines with translated addresses are reporting "selfcheck request timed out. Host down?" Including the backup server itself when running amcheck. What are we not seeing here? --- Lee Parsons LAN Administrator The Minnesota Daily www.mndaily.com On Mon, 18 Mar 2002, John Koenig wrote: > Do your names refer to external (public) IP addresses while your > machines behind the NAT actually have internal (private) IP addresses? > >
Re: samba backup -- spaces in sharenames, windows backup client
"christopher cuse" <[EMAIL PROTECTED]> writes: > Hi All, > > I noticed that attempting to specify a share name containing spaces in > disklist bombs during amcheck. Has anyone worked around this? I am trying to > backup a number of directories on each client machine from the > administrative share created through the windows profile on the samba server > i.e. //pc-client/c$ > > Don't suppose that anyone has developed a hack to use a windows arcserve > client, or developed an amanda windows client?? :) > > Cheers, > > Christopher CUSE > [EMAIL PROTECTED] > Antananarivo, Madagascar Christopher, There is http://sourceforge.net/projects/amanda-win32/ >From the web page: Note that product runs fine for me and for authority who oversaw project, there's just too little feedback to dub it "stable". I just read "NT", what about Win9X as a client? Johannes Nieß
Network Interfaces
I seem to remember someone saying a while ago on this list that it is possible to specify in the disklist what interface on the server an amanda client should use. This is because my backups are taking an age or rather the estimates are taking an age. I thought if I could tell each client to use the interface on that network so nothing is done through the router it might speed things up. My networking is not up to scratch but I don't know if the clients would use the most direct/efficient interface anyway? - David Flood Systems Administrator [EMAIL PROTECTED] Tel: +44 (0)1224 262721 The Robert Gordon University School of Computing St. Andrews Street Aberdeen -
Re: samba backup -- spaces in sharenames, windows backup client
remove the white spaces in the share name. Make 'Documents and Settings' 'docs' or whatever. just remove all spaces... your life will become much more simple. works for me On Tue, 2002-03-19 at 08:38, christopher cuse wrote: > Hi All, > > I noticed that attempting to specify a share name containing spaces in > disklist bombs during amcheck. Has anyone worked around this? I am trying to > backup a number of directories on each client machine from the > administrative share created through the windows profile on the samba server > i.e. //pc-client/c$ > > Don't suppose that anyone has developed a hack to use a windows arcserve > client, or developed an amanda windows client?? :) > > Cheers, > > Christopher CUSE > [EMAIL PROTECTED] > Antananarivo, Madagascar > > -- Brad Tilley, OUB Sys. Admin. http://bursar.vt.edu/rtilley/pgpkey
samba backup -- spaces in sharenames, windows backup client
Hi All, I noticed that attempting to specify a share name containing spaces in disklist bombs during amcheck. Has anyone worked around this? I am trying to backup a number of directories on each client machine from the administrative share created through the windows profile on the samba server i.e. //pc-client/c$ Don't suppose that anyone has developed a hack to use a windows arcserve client, or developed an amanda windows client?? :) Cheers, Christopher CUSE [EMAIL PROTECTED] Antananarivo, Madagascar
Re: Report meaning
On March 19 2002, "Robert SHEN" wrote: > I got the following message in the report sent by amanda, does anyone figure > out the meaning: > > gtar: ./dumps/20020319/host.domain._dev_sda5.0.tmp: file changed as we > read it Just as the message says, that file changed as GNU tar was trying to read it. The messsage is not fatal, but the .tmp file is not likely to be recoverable. However, it looks like you are backing up your Amanda holding area. In fact, the file being read was probably the same file that was being written at the time. It is very counterproductive to backup your holding area since it only contains other backup images. You might try using an exclude list to avoid this problem. Perhaps something like: ./dumps ./dumps/* If you have dedicated the entire /dev/sda5 partition to the holding area, you can just eliminate it from your disklist. I hope this helps, -Ben -- Benjamin Lewis <[EMAIL PROTECTED]> Database Analyst/Programmer Instructional Computing Services - Computing Accounts Purdue University
Report meaning
I got the following message in the report sent by amanda, does anyone figure out the meaning: FAILURE and STRANGE DUMP SUMMARY: host.domain /dev/sda5 lev 0 STRANGE ... FAILED AND STRANGE DUMP DETAILS: /-- host.domain /dev/sda5 lev0 STRANGE sendbackup: start [host.domain:/dev/sda5 level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end > gtar: ./dumps/20020319/host.domain._dev_sda5.0.tmp: file changed as we read it | Total bytes written: 3427215360 (3.2GB, 3.5MB/s) sendbackup: size 3346890 sendbackup: end \
