RE: amandad failure on Sun box
Brian, What does your amanda /etc/inetd.conf entries look like? should look like... amanda dgram udp waitamanda /usr/local/libexec/amandad amandad ./Ben I was getting a selfcheck error on one of my sun boxes I just built amanda on and this is what I found in /var/adm/messages: jupiter inetd[179]: amanda/udp server failing (looping), service terminated Any ideas on what I need to fix here? Also on my MP-RAS box I'm getting this error running selfcheck: ERROR: edaf6.irs.sat NAK: amandad busy Brian Davidson 11710 Plaza America Drive Reston, Virginia 20190 703.261.4694 703.261.5086 Fax
RE: Linus Torvald's opinion on Dump.
Lately he's been making some interesting comments... mach kernel is crap, dump is stupid blah blah blah Seems to me that if he didn't create it, er steal it it's automatically 'crap' or 'stupid'. Maybe he's still upset at Andrew S. Tanenbaum for giving him 2 f's on operating system design way back when ;o) In my opinion I would continue with what you have. Hopefully others will chime in with their opinions. -Ben
upgraded tape server a few clients to 2.4.2p2
having some problems with amcheck (amandapass and amandates) output from amcheck ERROR: atsun01: [cannot find password for //atdell01/d$] ERROR: atsun01: [cannot find password for //atdell01/c$] ERROR: atsun01: [can not read/write /etc/amandates: No such file or directory] ERROR: atsun01: [unable to open /etc/amandapass: No such file or directory] I upgraded atsun01 to 2.4.2p2 (client only). I don't understand why it's looking for an amandapass, amandates locally when these exist on the tape server. I know it's something small, and I probably have overlooked something. Any help is appreciated. Thanks, -Ben
RE: upgraded tape server a few clients to 2.4.2p2
Because these files are looked at by client programs, not by server
programs. So they must exist on clients that need them.
Ugh... that was extremely dumb of me - had that server defined in the disklist
unixhost //samba/share
Thanks,
-Ben
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
amanda archive config
Hello, Just wanted to double check my configuration here. What I want to do aside from my production backups is to have a separate config for archival purposes. I've checked the list archives and have done the following: a)Made a separate config for archive b)edited amanda.conf //dumpcycle dumpcycle 1 days runspercycle 1 days tapecycle 1000 tapes //on all dumptypes record no c) created separate directories for log,index,info Any pointers/corrections are appreciated. Thanks, -Ben
RE: FreeBSD pkgadd failure
I created the user group and home dir for amanda also. Modified the /etc/services /etc/inetd.conf , and HUP'd the inetd. What does your inetd.conf look like? (amanda entries) On the BSD boxes I get: On the bsd boxes, what does /tmp/amanda/amanda/selfcheck*debug say? Apr 11 11:18:38 bsd_system2 inetd[147]: /usr/local/libexec/amanda/amandad[18259]: exit status 0x100 Apr 11 11:18:38 bsd_system2 inetd[147]: /usr/local/libexec/amanda/amandad[18260]: exit status 0x100 Apr 11 11:18:38 bsd_system2 inetd[147]: amanda/udp server failing (looping), service terminated Apr 11 11:18:38 bsd_system2 inetd[147]: amanda/udp server failing (looping), service terminated (With the server name changing on the corresponding system, of course). Why would the services be failing? I'd verify the services and inetd.conf amanda entries. netstat -an |grep 10080 - is it listening on your tape server? Should I have just downloaded amanda and run the the configure and makes myself? Forgive me if I'm mistaken here, but I believe Amanda is part of the latest ports collection - I'd do a cvsupdate on your ports tree just to make sure. Should be in /usr/ports/misc/amanda - Edit the Makefile to your liking and 'make install'. TIA William -Ben
RE: amanda issue
Error: Autoconf requires GNU m4 1.1 or later make: *** [autoconf.m4f] Error 1 You need GNU make ftp://ftp.gnu.org/gnu/make/ -Ben anurag
Re: amanda issue
amanda issueHi, I'm installing amanda software on Sun Solaris box. I make userand as amanda. i logged in as amanda and run ./configure --with-user=amanda --with-group=amanda . works fine after that i logeed in as root and give a command make it gives me an error:- ../libtool: ar: not found ^^^ add /usr/ccs/bin to your path - re-run make -Ben
RE: amanda issue
kindly let me know now what will i do. I want to make this Sun box make as a Backup Server because this box contain a Tape Drive. Waiting for you reply I would highly suggest you read the documentation in the DOCS directory. Also the amanda website has a faq-o-matic page that answers some frequently asked questions. anurag -Ben
RE: GNUTAR
Is ther any second entry to make in amanda.conf or anywhere? Make sure gtar is in your path before running 'configure' - assuming you're building from source. Add gtar to your path, re-run configure, make and make install. -Ben
RE: Unable to install Amanda
configure: error: *** --with-user=USER is missing Any corrective suggestions are welcomed. Read the documentation that comes with source - docs/INSTALL. Amanda needs a user defined, ie --with-user=amanda. -Ben
RE: amanda mail report size
create /usr/local/src/amanda/2.4.2p1/Makefile (attached) create /usr/local/src/amanda/2.4.2p1/config.site (attached) create /usr/local/src/amanda/2.4.2p1/amanda-2.4.2p1.tar.gz (distribution) cd /usr/local/src/amanda/2.4.2p1 make ! 0-make-log Thank you very much Todd. then you have a record of exactly how you configured and built amanda-X in the Makefile and config.site. to rebuild at any time, just make again. it's a very easy way to maintain local builds of software packages. Makes a lot of sense I will have to start doing this for other software packages regards, -Ben Todd Pfaff \ Email: [EMAIL PROTECTED]
amanda mail report size
Ever since I rebuilt Amanda and moved it over to another box, I have noticed that the email report size wise is huge (9 MB). Didn't recall the report's to be that big on the old amanda instance I had running. Had an amanda alias pointing to my corp email address, but now that the message size is so big, it's getting rejected at the mail server (not under my control) I've since pointed the amanda alias to my local account(plenty of control ;)) and get the reports fine... just takes forever to load the report up (mutt) ;) Is there any options on amreport, like setting a verbose level? I'm really only interested in dump summary. Thanks, -Ben
RE: amanda mail report size
Doesn't this mean that there is something wrong with backup ? I have 8 samba shares which get backed up - due to open files I get a lot of errors from samba. I added 2 samba shares to the disklist (previous instance had 6 samba shares defined) my previous reports were never this big. -Ben Yuri Pismerov, TUCOWS.COM INC.(416) 535-0123 ext. 1352
RE: NT Backup's - Web Interface?
Please don't flame me for asking this but the NT admins onsite here would like something simpler than the UNIX command line. Is there a Web front available for Amanda or for amrecover in particular. If your NT admins need a gui, I'd suggest having them look at other solutions, i.e Veritas backup. This will give them that pretty gui they want. RLE -Ben
RE:
Can anybody tell me what is going on? What is this taper: FATAL shmget: Cannot allocate memory message mean? use ipcs to list resources allocated by user 'amanda' ; ipcrm to remove. -Ben
RE: forcing level 0 backups
Is there any easy way to force a level 0 backup of every disk in the disklist? man amadmin force hostname [ disks ] Force the disks on hostname to do a full level 0 backup during the next Amanda run. EXAMPLES Request three specific file systems on machine-a get a full level 0 backup during the next Amanda run. Note the use of "^/$" to get the root file system. Without the extra regular expression characters, just "/" would have matched all the file systems on machine-a. $ amadmin config force machine-a "^/$" /var /usr amadmin: machine-a:/ is set to a forced level 0 tonight. amadmin: machine-a:/var is set to a forced level 0 tonight. amadmin: machine-a:/usr is set to a forced level 0 tonight. Ben -Ben
RE: Missing e-mail reports
and in your /etc aliases put this: backup: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED] and you get what you want.. at least, thats the way we do it. Christoph don't forget to run 'newaliases' -Ben
RE: amanda 2.4.2
I am runing it on a freebsd 4.2-Release On my openbsd box I see gmake in my ports tree here. (bhyatt)@kawasaki:/usr/ports/devel/gmake:[115] HTH -Ben Clem Kumah [EMAIL PROTECTED] System Administrator / Teamleader www.worldonline.co.uk World Online UK+44 (0) 870 748
RE: self check request timed out
What does common-src/version.c look like?
/* version.c - generated by genversion.c - DO NOT EDIT! */
char *version_info[] = {
"build: VERSION=\"Amanda-2.4.1p1\"\n",
" BUILT_DATE=\"Thu Jan 25 10:04:03 PST 2001\"\n",
" BUILT_MACH=\"SunOS atsun01 5.7 Generic_106541-14 sun4u sparc
SUNW,Ultr
a-4\"\n",
" CC=\"/usr/local/bin/gcc\"\n",
"paths: bindir=\"/usr/local/bin\" sbindir=\"/usr/local/sbin\"\n",
" libexecdir=\"/usr/local/libexec\" mandir=\"/usr/local/man\"\n",
" CONFIG_DIR=\"/usr/local/etc/amanda\" DEV_PREFIX=\"/dev/dsk/\"\n",
" RDEV_PREFIX=\"/dev/rdsk/\" DUMP=\"/usr/sbin/ufsdump\"\n",
" RESTORE=\"/usr/sbin/ufsrestore\"\n",
" SAMBA_CLIENT=\"/usr/local/samba/bin/smbclient\"\n",
" GNUTAR=\"/usr/local/bin/tar\"\n",
" COMPRESS_PATH=\"/usr/local/bin/gzip\"\n",
" UNCOMPRESS_PATH=\"/usr/local/bin/gzip\"\n",
" MAILER=\"/usr/ucb/Mail\"\n",
" listed_incr_dir=\"/usr/local/var/amanda/gnutar-lists\"\n",
"defs: DEFAULT_SERVER=\"atsun01\" DEFAULT_CONFIG=\"DailySet1\"\n",
" DEFAULT_TAPE_SERVER=\"atsun01\"\n",
" DEFAULT_TAPE_DEVICE=\"/dev/rmt/0hn\" HAVE_MMAP HAVE_SYSVSHM\n",
" LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY\n",
" USE_AMANDAHOSTS CLIENT_LOGIN=\"amanda\" FORCE_USERID HAVE_GZIP\n",
" COMPRESS_SUFFIX=\".gz\" COMPRESS_FAST_OPT=\"--fast\"\n",
" COMPRESS_BEST_OPT=\"--best\" UNCOMPRESS_OPT=\"-dc\"\n",
0
};
Did you try --disable-shared?
Nope... but I'll give it a shot.
thanks,
-Ben
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
RE: self check request timed out (good ending)
Well... I decided to move the sun dlt7000 over to another e450 sun solaris 2.7 and give that a shot. Configure, make make install. Things are working now... very strange?!? Anyways, I'm back up and running. Now THIS is what I like seeing :) (*insecure*)amanda@atsun04:/tmp/amanda$ amcheck atlab Amanda Tape Server Host Check - /apps/backup/amanda: 16798969 KB disk space available, using 16594169 KB. NOTE: skipping tape-writable test. Tape atlab01 label ok. Server check took 5.636 seconds. Amanda Backup Client Hosts Check Client check: 5 hosts checked in 1.882 seconds, 0 problems found. (brought to you by Amanda 2.4.1p1) Thanks again for everyone's help in troubleshooting this. regards, -Ben
RE: self check request timed out
I could be smoking something here, but I seem to recall seeing this (*insecure*) crap on my Solaris 2.6 box here, and my amchecks failed until I got rid of the (*insecure*) by fixing my hostname lookups for my own host. The (*insecure*) bit is just part of amanda's .bashrc... if [ $SHLVL -eq 1 ] ; then if printenv | egrep '^SSH' 21 /dev/null ; then PS1='(8-n)\u@\h:\w\$ ' else PS1='(*insecure*)\u@\h:\w\$ ' fi else if printenv | egrep '^SSH' 21 /dev/null ; then PS1="(8-n)($SHLVL)\\u@\\h:\\w\\$ " else PS1="(*insecure*)($SHLVL)\\u@\\h:\\w\\$ " fi fi I didn't anyone mention that (*insecure*) flag. I think Solaris doesn't like its hostname and it's being pissy about launching amandad or something. Hostname lookups are working fine :) -Ben
RE: selfcheck permission weirdness (Linux ok, but not Solaris)
checking disk /home: device /dev/rdsk/c0t0d0s7: Permission denied what does ls -la on c0t0d0s7 look like? For example: ls -la ../../devices/pci@1f,4000/scsi@3/sd@0,0:h,raw crw-r- 1 root sys 32, 7 Jan 22 14:15 ../../devices/pci@1f,4000/scsi@3/sd@0,0:h,raw Make sure the user amanda runs as has read permission on the raw device. Luc Lalonde, Responsable du reseau GIREF -Ben
RE: selfcheck permission weirdness (Linux ok, but not Solaris)
Make sure the user amanda runs as has read permission on the raw device. Oops... make sure the group of the user that amanda runs as has read permission. -Ben
Re: self check request timed out
On Solaris 7? IIRC, GCC 2.8.1 needed some patches to support Solaris 7.
Yes. I built the latest ( I believe ) 2.95.2 and tried compling, making and
install again (fresh build dir)
No luck. Still get amandad looping, and ending up with a segmentation fault
So my next alternative is to find a decent 2.6 box in the lab somewhere,
transplant the sun dlt7000, and hopefully do a successful amanda build there
:)
-Ben
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: self check request timed out
We need the stack traceback. Please do this again and enter "where" before "quit". Sorry bout that. (gdb) run Starting program: /usr/local/libexec/amandad warning: Lowest section in /usr/lib/libintl.so.1 is .hash at 0074 Program received signal SIGSEGV, Segmentation fault. 0xff0b6e94 in strlen () from /usr/lib/libc.so.1 (gdb) where #0 0xff0b6e94 in strlen () from /usr/lib/libc.so.1 #1 0xff0fff08 in _doprnt () from /usr/lib/libc.so.1 #2 0xff101d30 in vfprintf () from /usr/lib/libc.so.1 #3 0xff1b3bb0 in debug_printf (format=0x13f10 "%s: %s") at debug.c:62 #4 0x11c54 in main (argc=1, argv=0xffbefc04) at amandad.c:174 (gdb) John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -Ben
Re: self check request timed out
frame 4# this should put you at "main"
#4 0x11c54 in main (argc=1, argv=0xffbefc04) at amandad.c:174
174 dbprintf(("%s: %s", argv[0], *vp));
print argv[0]
$1 = 0xffbefcd0 "/usr/local/libexec/amandad"
print vp
$2 = (char **) 0x24974
print *vp
$3 = 0x2 Address 0x2 out of bounds
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
-Ben
RE: self check request timed out
What happens if you run "amadmin xx version"?
(*insecure*)amanda@atsun01:~$ amadmin atlab version
build: VERSION="Amanda-2.4.1p1"
BUILT_DATE="Tue Jan 23 21:41:04 PST 2001"
BUILT_MACH="SunOS atsun01 5.7 Generic_106541-14 sun4u sparc
SUNW,Ultra-4"
CC="gcc"
paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin"
libexecdir="/usr/local/libexec" mandir="/usr/local/man"
CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/dsk/"
RDEV_PREFIX="/dev/rdsk/" DUMP="/usr/sbin/ufsdump"
RESTORE="/usr/sbin/ufsrestore"
SAMBA_CLIENT="/usr/local/samba/bin/smbclient"
GNUTAR="/usr/local/bin/tar"
COMPRESS_PATH="/usr/local/bin/gzip"
UNCOMPRESS_PATH="/usr/local/bin/gzip"
MAILER="/usr/bin/mailx"
listed_incr_dir="/usr/local/var/amanda/gnutar-lists"
defs: DEFAULT_SERVER="atsun01" DEFAULT_CONFIG="atlab"
DEFAULT_TAPE_SERVER="atsun01"
DEFAULT_TAPE_DEVICE="/dev/rmt/0hn" HAVE_MMAP HAVE_SYSVSHM
LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY
USE_AMANDAHOSTS CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP
COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
What about:
and so on until you get to the end of the strings (there should be about
25 of them) or the address is 0x24974 (*vp).
(gdb) frame 4
#4 0x11c54 in main (argc=1, argv=0xffbefc34) at amandad.c:174
174 dbprintf(("%s: %s", argv[0], *vp));
(gdb) print version_info
$4 = 0x24920
(gdb) print version_info[0]
$5 = 0xff1cb278 "build: VERSION=\"Amanda-2.4.1p1\"\n"
(gdb) print version_info[1]
$6 = 0xff1cb240 " BUILT_DATE=\"Tue Jan 23 21:41:04 PST 2001\"\n"
(gdb) print version_info[2]
$7 = 0xff1cb1e8 " BUILT_MACH=\"SunOS atsun01 5.7 Generic_106541-14
sun4u sparc SUNW,Ultra-4\"\n"
(gdb) print version_info[3]
$8 = 0xff1cb1d0 " CC=\"gcc\"\n"
(gdb) print version_info[4]
$9 = 0xff1cb190 "paths: bindir=\"/usr/local/bin\"
sbindir=\"/usr/local/sbin\"\n"
(gdb) print version_info[5]
$10 = 0xff1cb150 " libexecdir=\"/usr/local/libexec\"
mandir=\"/usr/local/man\"\n"
(gdb) print version_info[6]
$11 = 0xff1cb108 " CONFIG_DIR=\"/usr/local/etc/amanda\"
DEV_PREFIX=\"/dev/dsk/\"\n"
(gdb) print version_info [7]
$12 = 0xff1cb0c8 " RDEV_PREFIX=\"/dev/rdsk/\"
DUMP=\"/usr/sbin/ufsdump\"\n"
(gdb) print version_info[8]
$13 = 0xff1cb0a0 " RESTORE=\"/usr/sbin/ufsrestore\"\n"
(gdb) print version_info[9]
$14 = 0xff1cb068 " SAMBA_CLIENT=\"/usr/local/samba/bin/smbclient\"\n"
(gdb) print version_info[10]
$15 = 0xff1cb040 " GNUTAR=\"/usr/local/bin/tar\"\n"
(gdb) print version_info[11]
$16 = 0xff1cb010 " COMPRESS_PATH=\"/usr/local/bin/gzip\"\n"
(gdb) print version_info[12]
$17 = 0xff1cafe0 " UNCOMPRESS_PATH=\"/usr/local/bin/gzip\"\n"
(gdb) print version_info[13]
$18 = 0xff1cafc0 " MAILER=\"/usr/bin/mailx\"\n"
(gdb) print version_info[14]
$19 = 0xff1caf80 "
listed_incr_dir=\"/usr/local/var/amanda/gnutar-lists\"\n"
(gdb) print version_info[15]
$20 = 0xff1caf48 "defs: DEFAULT_SERVER=\"atsun01\"
DEFAULT_CONFIG=\"atlab\"\n"
(gdb) print version_info[16]
$21 = 0xff1caf20 " DEFAULT_TAPE_SERVER=\"atsun01\"\n"
(gdb) print version_info[17]
$22 = 0xff1caed8 " DEFAULT_TAPE_DEVICE=\"/dev/rmt/0hn\" HAVE_MMAP
HAVE_SYSVSHM\n"
(gdb) print version_info[18]
$23 = 0xff1cae90 " LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
BSD_SECURITY\n"
(gdb) print version_info[19]
$24 = 0xff1cae48 " USE_AMANDAHOSTS CLIENT_LOGIN=\"amanda\"
FORCE_USERID HAVE_GZIP\n"
(gdb) print version_info[20]
$25 = 0xff1cae08 " COMPRESS_SUFFIX=\".gz\"
COMPRESS_FAST_OPT=\"--fast\"\n"
How familiar are you with debugging C code? For instance, if I asked
you to set a breakpoint at the start of main and examine version_info
before much else had happened to see if it's getting clobbered or it's
just plain bad coming in, is that do-able?
Not that familiar with it at all, _however_ I'm reading the doc's as we
type.
Looks pretty straight forward to me as far as setting breakpoints in gdb.
I'd say it's do-able :)
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
thanks,
-Ben
RE: self check request timed out
One more test: break main run print version_info[20] # just to make sure we're looking at # the right stuff print version_info[21] gdb) break main Breakpoint 1 at 0x11a78: file amandad.c, line 116. (gdb) run Starting program: /usr/local/libexec/amandad warning: Lowest section in /usr/lib/libintl.so.1 is .hash at 0074 Breakpoint 1, main (argc=1, argv=0xffbefc34) at amandad.c:116 116 char *errstr = NULL; (gdb) print version_info[20] $1 = 0xff1cae08 " COMPRESS_SUFFIX=\".gz\" COMPRESS_FAST_OPT=\"--fast\"\n" (gdb) print version_info[21] $2 = 0x2 Address 0x2 out of bounds Ack! If it shows a value of 2 at this point, which is before any Amanda code is run, then it almost has to be a compiler or loader error. H, gcc version 2.8.1 is what I am using... John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] thanks, -Ben
RE: self check request timed out
I don't think this would matter, but what do you get when you run "gcc -v"? Was it built for the OS version you have (2.7, as I recall)? atsun01:/# gcc -v Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.8.1/specs gcc version 2.8.1 I might add that this was a package, courtesy of sunfreeware.com. I didn't really have a choice as Sun doesn't supply a compiler with the solaris install ;). I've built amanda on 2.6 with the same gcc 2.8.1 package before, however this is the _first_ time building/installing on a 2.7 box. The only things I can think of to try at this point are a complete rebuild of Amanda (blow away all traces of the build area you used before), or upgrading to the latest gcc and building that for the specific host, or making sure you have all the latest Solaris patches. I'll blow away my /usr/local/src/amanda2.4.1p1 dir and rebuild with the latest gcc tomorrow morning. As far as Solaris patches I am up to date... sunsolve 2.7 recommeded. You didn't do anything odd during the "make install" that would cause it to get an incorrect shared library copy, did you (again, based on output you've sent, I doubt this)? No, nothing seemed out of the ordinary. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] thanks for your help troubleshooting this... I'll post my results of building in a clean build dir, with updated gcc. regards, -Ben
RE: self check request timed out
OK, but I have to ask a few questions anyway to make sure something wasn't lost in translation. Sure Is /tmp/amanda/amandad*debug getting updated on atsun01? Yes, ls -lu /tmp/amanda/amandad.debug confirms this. What happens if you run .../amandad by hand **as the Amanda user** (the one listed in inetd.conf)? It should sit for 30 seconds and then terminate, but /tmp/amanda/amandad*debug will be updated. /tmp/amanda/amandad.debug gets updated as you say. Is /tmp/amanda/selfcheck*debug getting updated on atsun01? What's in it? amandad: debug 1 pid 11289 ruid 101 euid 101 start time Tue Jan 23 13:58:41 2001 ./amandad: version 2.4.1p1 ./amandad: build: VERSION="Amanda-2.4.1p1" ./amandad:BUILT_DATE="Mon Jan 22 16:32:45 PST 2001" ./amandad:BUILT_MACH="SunOS atsun01 5.7 Generic_106541-08 sun4u sparc SUNW,Ultra-4" ./amandad:CC="gcc" ./amandad: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" ./amandad:libexecdir="/usr/local/libexec" mandir="/usr/local/man" ./amandad:CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/dsk/" ./amandad:RDEV_PREFIX="/dev/rdsk/" DUMP="/usr/sbin/ufsdump" ./amandad:RESTORE="/usr/sbin/ufsrestore" GNUTAR="/usr/local/bin/tar" ./amandad:COMPRESS_PATH="/usr/local/bin/gzip" ./amandad:UNCOMPRESS_PATH="/usr/local/bin/gzip" ./amandad:MAILER="/usr/ucb/Mail" ./amandad:listed_incr_dir="/usr/local/var/amanda/gnutar-lists" ./amandad: defs: DEFAULT_SERVER="atsun01" DEFAULT_CONFIG="atlab" ./amandad:DEFAULT_TAPE_SERVER="atsun01" ./amandad:DEFAULT_TAPE_DEVICE="/dev/rmt/0hn" HAVE_MMAP HAVE_SYSVSHM ./amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY ./amandad:USE_AMANDAHOSTS CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP ./amandad:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" ./amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" amandad: error receiving message: timeout John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] Thanks, -Ben
RE: self check request timed out
OK, that's all normal. But I asked what was in selfcheck*debug, not amandad*debug. Ugh, sorry about that. * I ran this manually as user amanda - it does not get updated on amcheck * selfcheck: debug 1 pid 11368 ruid 101 euid 101 start time Tue Jan 23 14:15:54 2001 ./selfcheck: version 2.4.1p1 REQ packet is bogus selfcheck: pid 11368 finish time Tue Jan 23 14:16:25 2001 REQ packet is bogus? grep 'amanda' /etc/inetd.conf # Advanced Maryland Automatic Network Disk Archiver amandaidx stream tcp nowait amanda /usr/local/libexec/amindexd amindexd amidxtape stream tcp nowait amanda /usr/local/libexec/amidxtaped amidxtaped amanda dgram udp waitamanda /usr/local/libexec/amandad amandad grep 'amanda' /etc/services # Advanced Maryland Automatic Network Disk Archiver amanda 10080/udp # Amanda backup server amandaidx 10082/tcp # Amanda backup server amidxtape 10083/tcp # Amanda backup server John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] Thanks, -Ben
RE: self check request timed out
What's in the matching amandad*debug file? It's not being updated by amcheck :( When run manually as user amanda /usr/local/libexec/./amandad I get the following in /tmp/amanda/amandad.debug amandad: debug 1 pid 11289 ruid 101 euid 101 start time Tue Jan 23 13:58:41 2001 ./amandad: version 2.4.1p1 ./amandad: build: VERSION="Amanda-2.4.1p1" ./amandad:BUILT_DATE="Mon Jan 22 16:32:45 PST 2001" ./amandad:BUILT_MACH="SunOS atsun01 5.7 Generic_106541-08 sun4u sparc SUNW,Ultra-4" ./amandad:CC="gcc" ./amandad: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" ./amandad:libexecdir="/usr/local/libexec" mandir="/usr/local/man" ./amandad:CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/dsk/" ./amandad:RDEV_PREFIX="/dev/rdsk/" DUMP="/usr/sbin/ufsdump" ./amandad:RESTORE="/usr/sbin/ufsrestore" GNUTAR="/usr/local/bin/tar" ./amandad:COMPRESS_PATH="/usr/local/bin/gzip" ./amandad:UNCOMPRESS_PATH="/usr/local/bin/gzip" ./amandad:MAILER="/usr/ucb/Mail" ./amandad:listed_incr_dir="/usr/local/var/amanda/gnutar-lists" ./amandad: defs: DEFAULT_SERVER="atsun01" DEFAULT_CONFIG="atlab" ./amandad:DEFAULT_TAPE_SERVER="atsun01" ./amandad:DEFAULT_TAPE_DEVICE="/dev/rmt/0hn" HAVE_MMAP HAVE_SYSVSHM ./amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY ./amandad:USE_AMANDAHOSTS CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP ./amandad:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" ./amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" amandad: error receiving message: timeout Would it be worth a try to configure/install the new version 2.4.2? John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -Ben
RE: self check request timed out
I'd suggest blowing away /tmp/amanda, doing the amcheck, and then seeing what's in there. There should be an amandad*debug and selfcheck*debug, both recently updated (as of the time of the amcheck). Take a look at the first few lines of each (assuming they are both there) and an "ls -l" to verify they are brand new. I removed everything from the /tmp/amanda dir and re-ran amcheck. Nothing, absolutely nothing shows up in the /tmp/amanda dir - it's mode 0775 amanda:sys Is /usr/local/libexec/amandad the exact same thing you have in inetd.conf? Here's the line for amandad in my /etc/inetd.conf amanda dgram udp waitamanda /usr/local/libexec/amandad amandad Let's keep tracking this for the moment. Okay John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -Ben
RE: self check request timed out
Okay, A reboot seemed to fix things - weird. I enabled the original amadad entry in /etc/inetd.conf and restarted. Went ahead and ran amcheck atlab as user amanda and it is now creating amandad.debug selfcheck.debug in /tmp/amanda. Ahhh.. now this is much better :) cat /tmp/amanda/selfcheck.debug selfcheck: debug 1 pid 323 ruid 101 euid 101 start time Tue Jan 23 18:15:41 2001 /usr/local/libexec/selfcheck: version 2.4.1p1 checking disk /apps: device /dev/md/rdsk/d0: OK checking disk /opt: device /dev/rdsk/c0t1d0s1: OK checking disk /export/home: device /dev/rdsk/c0t0d0s3: OK checking disk /usr: device /dev/rdsk/c0t1d0s3: OK checking disk /: device /dev/rdsk/c0t0d0s0: OK Thanks for your help troubleshooting this John. Regards, -Ben
help on restore
Hello, Ran into some difficulties attempting to upgrade a e450 (2.6 2.7). This server, unfortunately was my amanda backup server. I am trying to restore using dd, as my preserved data (thanks sun for the painless upgrade)is next to useless, and I'm running into some problems. Following http://www.backupcentral.com/amanda-24.html 'Restoring without Amanda' I'm able to get a description of the image on tape (good). However I'm not able to find the particuliar host|disk I'm looking for. I have loaded tape atlab02, but I only see one image... // output from dd # mt -f /dev/rmt/0 rewind # mt -f /dev/rmt/0 fsf # dd if=/dev/rmt/0 bs=32k count=1 AMANDA: FILE 20010112 web6 / lev 1 comp .gz program /usr/sbin/ufsdump To restore, position tape at start of file and run: dd if=tape bs=32k skip=1 | /usr/local/bin/gzip -dc | usr/sbin/ufsrestore -f... - 1+0 records in 1+0 records out I had a seven tape rotation. The last email I received from amanda on january 15th shows a dump level 0 for the particuliar host and disk. These dumps were to tape atlab02 DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- -- -- atsun01 /apps 0 12109311 3067264 25.3 60:25 846.1 60:25 846.1 Amanda version 2.4.1p1 (solaris 2.6) Any ideas are greatly appreciated. Thanks, -Ben
