Re: another selfcheck problem
hi... A selfcheck log on the client does not exist. when I compare the logfile on the non working client, to a working client, it looks like amanda does not process the UDP packages it receives.. greetz olli Am Mittwoch, den 16.07.2008, 15:12 -0400 schrieb Dustin J. Mitchell: The debug logs *do* look different, so this was at least a minimal improvement: On Wed, Jul 16, 2008 at 2:26 PM, Mister Olli [EMAIL PROTECTED] wrote: amandad: debug 1 pid 80108 ruid 1002 euid 1002: start at Wed Jul 16 20:21:46 2008 vs. (earlier) -auth=bsd: debug 1 pid 76969 ruid 1002 euid 1002: start at Wed Jul 16 10:33:47 2008 What do the selfcheck logs say? Dustin
Yet another selfcheck problem
I am setting up a new sun server running Solaris 10. I think I have set
things up correctly. I am getting the error: WARNING: xx.yy.zz:
selfcheck request failed: timeout waiting for ACK.
I have searched the archives and tried everything suggested.
2 things I notice:
1. my permissions on /tmp/amanda are not correct and I can't
figure out how to fix it. They rwx-- and should be rwx-S---.
2. I have no amandad folder in /tmp/amanda and no log files
are created under /tmp/amanda/client/Daily.
Here is my amcheck log:
1216332727.879803: amcheck: pid 2977 ruid 1003 euid 1003: start at Thu
Jul 17 17:12:07 2008
1216332727.885875: amcheck: pid 2977 ruid 1003 euid 1003: rename at Thu
Jul 17 17:12:07 2008
1216332727.889261: amcheck-clients: security_getdriver(name=BSD) returns
ff2e82dc
1216332727.889384: amcheck-clients: security_handleinit(handle=3d970,
driver=ff2e82dc (BSD))
1216332727.891235: amcheck-clients: bind_portrange2: Try port 858:
Available - Success
1216332727.891318: amcheck-clients: dgram_bind: socket 5 bound to
0.0.0.0.858
1216332727.891630: amcheck-clients: dgram_send_addr(addr=3d990,
dgram=ff2edbb4)
1216332727.891639: amcheck-clients: (sockaddr_in *)3d990 = { 2, 10080,
198.206.243.14 }
1216332727.891646: amcheck-clients: dgram_send_addr: ff2edbb4-socket =
5
1216332737.900253: amcheck-clients: dgram_send_addr(addr=3d990,
dgram=ff2edbb4)
1216332737.900294: amcheck-clients: (sockaddr_in *)3d990 = { 2, 10080,
198.206.243.14 }
1216332737.900303: amcheck-clients: dgram_send_addr: ff2edbb4-socket =
5
1216332747.910115: amcheck-clients: dgram_send_addr(addr=3d990,
dgram=ff2edbb4)
1216332747.910134: amcheck-clients: (sockaddr_in *)3d990 = { 2, 10080,
198.206.243.14 }
1216332747.910142: amcheck-clients: dgram_send_addr: ff2edbb4-socket =
5
1216332757.920086: amcheck-clients: security_seterror(handle=3d970,
driver=ff2e82dc (BSD) error=timeout waiting for ACK)
1216332757.920125: amcheck-clients: security_close(handle=3d970,
driver=ff2e82dc (BSD))
1216332757.922592: amcheck: pid 2977 finish time Thu Jul 17 17:12:37
2008
It's been a long day but any help would be appreciated.
Thanks,
Paul Crittenden
Computer Systems Manager
Simpson College
Phone: 515-961-1680
Email: [EMAIL PROTECTED]
image001.gif
RE: Yet another selfcheck problem
I figured it out. I looked at the /var/adm/messages logs and it told me to run
the command:
inetconv -i /etc/inet/inet.conf, since I had made changes in the inetd.conf
file. That got rid of the no ACK error. Then amcheck told me what host name was
actually being used so I changed the .amandahosts file. Then I had some
permissions problems that I corrected.
The /tmp/amanda permissions problem I figured out by finding a Unix Guide that
told me it was the set gid bit. The s is lowercase if group has execute
permission and uppercase if it does not.
Taking a break for a couple of hours helped.
From: [EMAIL PROTECTED] on behalf of Paul Crittenden
Sent: Thu 7/17/2008 5:34 PM
To: amanda-users@amanda.org
Subject: Yet another selfcheck problem
I am setting up a new sun server running Solaris 10. I think I have set things
up correctly. I am getting the error: WARNING: xx.yy.zz: selfcheck request
failed: timeout waiting for ACK.
I have searched the archives and tried everything suggested.
2 things I notice:
1. my permissions on /tmp/amanda are not correct and I can't figure
out how to fix it. They rwx-- and should be rwx-S---.
2. I have no amandad folder in /tmp/amanda and no log files are
created under /tmp/amanda/client/Daily.
Here is my amcheck log:
1216332727.879803: amcheck: pid 2977 ruid 1003 euid 1003: start at Thu Jul 17
17:12:07 2008
1216332727.885875: amcheck: pid 2977 ruid 1003 euid 1003: rename at Thu Jul 17
17:12:07 2008
1216332727.889261: amcheck-clients: security_getdriver(name=BSD) returns
ff2e82dc
1216332727.889384: amcheck-clients: security_handleinit(handle=3d970,
driver=ff2e82dc (BSD))
1216332727.891235: amcheck-clients: bind_portrange2: Try port 858: Available -
Success
1216332727.891318: amcheck-clients: dgram_bind: socket 5 bound to 0.0.0.0.858
1216332727.891630: amcheck-clients: dgram_send_addr(addr=3d990, dgram=ff2edbb4)
1216332727.891639: amcheck-clients: (sockaddr_in *)3d990 = { 2, 10080,
198.206.243.14 }
1216332727.891646: amcheck-clients: dgram_send_addr: ff2edbb4-socket = 5
1216332737.900253: amcheck-clients: dgram_send_addr(addr=3d990, dgram=ff2edbb4)
1216332737.900294: amcheck-clients: (sockaddr_in *)3d990 = { 2, 10080,
198.206.243.14 }
1216332737.900303: amcheck-clients: dgram_send_addr: ff2edbb4-socket = 5
1216332747.910115: amcheck-clients: dgram_send_addr(addr=3d990, dgram=ff2edbb4)
1216332747.910134: amcheck-clients: (sockaddr_in *)3d990 = { 2, 10080,
198.206.243.14 }
1216332747.910142: amcheck-clients: dgram_send_addr: ff2edbb4-socket = 5
1216332757.920086: amcheck-clients: security_seterror(handle=3d970,
driver=ff2e82dc (BSD) error=timeout waiting for ACK)
1216332757.920125: amcheck-clients: security_close(handle=3d970,
driver=ff2e82dc (BSD))
1216332757.922592: amcheck: pid 2977 finish time Thu Jul 17 17:12:37 2008
It's been a long day but any help would be appreciated.
Thanks,
Paul Crittenden
Computer Systems Manager
Simpson College
Phone: 515-961-1680
Email: [EMAIL PROTECTED]
image001.gif
another selfcheck problem
Hi...
when I try to do an 'amcheck' on my daily backup jobs I have one system,
that does not pass the selftest.
it's configured identically to some other machines that work like a
charm.
the debug output of 'amandad' on the client side looks like this:
-auth=bsd: debug 1 pid 76969 ruid 1002 euid 1002: start at Wed Jul 16
10:33:47 2008
security_getdriver(name=BSD) returns 0x280a8020
-auth=bsd: version 2.5.1p3
-auth=bsd: build: VERSION=Amanda-2.5.1p3
-auth=bsd:BUILT_DATE=Tue Jul 15 13:36:45 CEST 2008
-auth=bsd:BUILT_MACH=FreeBSD hdb-mail-001.DOMAIN 7.0-RELEASE-p2
FreeBSD 7.0-RELEASE-p2 #4: Thu Jul 10 10:49:56 CEST 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/DOMAIN_CUSTOM_ESX
i386
-auth=bsd:CC=cc CONFIGURE_COMMAND='./configure' 'freebsd7.0'
-auth=bsd: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin
-auth=bsd:libexecdir=/usr/local/libexec/amanda
-auth=bsd:mandir=/usr/local/man AMANDA_TMPDIR=/tmp/amanda
-auth=bsd:AMANDA_DBGDIR=/tmp/amanda
-auth=bsd:CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/
-auth=bsd:RDEV_PREFIX=/dev/ DUMP=/sbin/dump
-auth=bsd:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF
-auth=bsd:XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF
VXRESTORE=UNDEF
-auth=bsd:SAMBA_CLIENT=UNDEF GNUTAR=/usr/local/bin/gtar
-auth=bsd:COMPRESS_PATH=/usr/bin/gzip
-auth=bsd:UNCOMPRESS_PATH=/usr/bin/gzip LPRCMD=UNDEF
-auth=bsd:MAILER=/usr/bin/Mail
-auth=bsd:listed_incr_dir=/usr/local/var/amanda/gnutar-lists
-auth=bsd: defs: DEFAULT_SERVER=hdb-bak-001.DOMAIN
-auth=bsd:DEFAULT_CONFIG=DailySet1
-auth=bsd:DEFAULT_TAPE_SERVER=hdb-bak-001.DOMAIN HAVE_MMAP
-auth=bsd:HAVE_SYSVSHM LOCKING=POSIX_FCNTL DEBUG_CODE
-auth=bsd:AMANDA_DEBUG_DAYS=4 BSD_SECURITY RSH_SECURITY
USE_AMANDAHOSTS
-auth=bsd:CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP
-auth=bsd:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast
-auth=bsd:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc
-auth=bsd: time 0.000: dgram_recv(dgram=0x280a8fe4, timeout=0,
fromaddr=0x280b8fd0)
-auth=bsd: time 0.000: (sockaddr_in *)0x280b8fd0 = { 2, 960,
172.31.5.10 }
-auth=bsd: time 10.089: dgram_recv(dgram=0x280a8fe4, timeout=0,
fromaddr=0x280b8fd0)
-auth=bsd: time 10.089: (sockaddr_in *)0x280b8fd0 = { 2, 960,
172.31.5.10 }
-auth=bsd: time 20.071: dgram_recv(dgram=0x280a8fe4, timeout=0,
fromaddr=0x280b8fd0)
-auth=bsd: time 20.071: (sockaddr_in *)0x280b8fd0 = { 2, 960,
172.31.5.10 }
-auth=bsd: time 30.070: pid 76969 finish time Wed Jul 16 10:34:17 2008
any ideas what the problem is? I've looked over the configuration
several times, and it's ok.
greetz
olli
Re: another selfcheck problem
Mister Olli wrote: Hi... when I try to do an 'amcheck' on my daily backup jobs I have one system, that does not pass the selftest. it's configured identically to some other machines that work like a charm. the debug output of 'amandad' on the client side looks like this: -auth=bsd: debug 1 pid 76969 ruid 1002 euid 1002: start at Wed Jul 16 10:33:47 2008 '-auth=bsd' at the beginning of the line is bogus, check your inetd/xinetd configuration. Jean-Louis
Re: another selfcheck problem
hi... my /etc/inetd.conf looks like this on all of my freebsd 7 systems. amanda dgram udp waitamanda /usr/local/libexec/amandad -auth=bsd amdump amindexd amidxtaped and it works like a charm, except for that one system... gladly I'm only the backup-administrator of that system. I wasn't the one who did the setup, so I'm not quite sure if there's something wrong with the system setup... are there any hints on what to check, or how to trace/ debug this failure in more detail? greetz olli Am Mittwoch, den 16.07.2008, 07:20 -0400 schrieb Jean-Louis Martineau: Mister Olli wrote: Hi... when I try to do an 'amcheck' on my daily backup jobs I have one system, that does not pass the selftest. it's configured identically to some other machines that work like a charm. the debug output of 'amandad' on the client side looks like this: -auth=bsd: debug 1 pid 76969 ruid 1002 euid 1002: start at Wed Jul 16 10:33:47 2008 '-auth=bsd' at the beginning of the line is bogus, check your inetd/xinetd configuration. Jean-Louis
Re: another selfcheck problem
On Wed, Jul 16, 2008 at 9:46 AM, Mister Olli [EMAIL PROTECTED] wrote: amanda dgram udp waitamanda /usr/local/libexec/amandad -auth=bsd amdump amindexd amidxtaped It looks like amandad is thinking that -auth=bsd is its name, which means that it saw that in argv[0] Try amanda dgram udp waitamanda /usr/local/libexec/amandad /usr/local/libexec/amandad -auth=bsd amdump amindexd amidxtaped Dustin -- Storage Software Engineer http://www.zmanda.com
Re: another selfcheck problem
Mister Olli wrote: hi... my /etc/inetd.conf looks like this on all of my freebsd 7 systems. amanda dgram udp waitamanda /usr/local/libexec/amandad -auth=bsd amdump amindexd amidxtaped A 'amandad' is missing, it should be: amanda dgram udp wait amanda /usr/local/libexec/amandad amandad -auth=bsd amdump amindexd amidxtaped Jean-Louis and it works like a charm, except for that one system... gladly I'm only the backup-administrator of that system. I wasn't the one who did the setup, so I'm not quite sure if there's something wrong with the system setup... are there any hints on what to check, or how to trace/ debug this failure in more detail? greetz olli Am Mittwoch, den 16.07.2008, 07:20 -0400 schrieb Jean-Louis Martineau: Mister Olli wrote: Hi... when I try to do an 'amcheck' on my daily backup jobs I have one system, that does not pass the selftest. it's configured identically to some other machines that work like a charm. the debug output of 'amandad' on the client side looks like this: -auth=bsd: debug 1 pid 76969 ruid 1002 euid 1002: start at Wed Jul 16 10:33:47 2008 '-auth=bsd' at the beginning of the line is bogus, check your inetd/xinetd configuration. Jean-Louis
Re: another selfcheck problem
hi...
the problem seems to be related to something different. I fixed the
inetd config and put in a 'amandad' and also replaced that with the
'/usr/local/libexec/amanda/amandad' but still no success.
The debug file looks exactly the same like before:
# cat amandad/amandad.20080716202146.debug
amandad: debug 1 pid 80108 ruid 1002 euid 1002: start at Wed Jul 16
20:21:46 2008
security_getdriver(name=bsd) returns 0x280a8020
amandad: version 2.5.1p3
amandad: build: VERSION=Amanda-2.5.1p3
amandad:BUILT_DATE=Tue Jul 15 13:36:45 CEST 2008
amandad:BUILT_MACH=FreeBSD hdb-mail-001.ernw.de 7.0-RELEASE-p2
FreeBSD 7.0-RELEASE-p2 #4: Thu Jul 10 10:49:56 CEST 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/DOMAIN_CUSTOM_ESX
i386
amandad:CC=cc CONFIGURE_COMMAND='./configure' 'freebsd7.0'
amandad: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin
amandad:libexecdir=/usr/local/libexec/amanda
amandad:mandir=/usr/local/man AMANDA_TMPDIR=/tmp/amanda
amandad:AMANDA_DBGDIR=/tmp/amanda
amandad:CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/
amandad:RDEV_PREFIX=/dev/ DUMP=/sbin/dump
amandad:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF
amandad:XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF
VXRESTORE=UNDEF
amandad:SAMBA_CLIENT=UNDEF GNUTAR=/usr/local/bin/gtar
amandad:COMPRESS_PATH=/usr/bin/gzip
amandad:UNCOMPRESS_PATH=/usr/bin/gzip LPRCMD=UNDEF
amandad:MAILER=/usr/bin/Mail
amandad:listed_incr_dir=/usr/local/var/amanda/gnutar-lists
amandad: defs: DEFAULT_SERVER=hdb-bak-001.DOMAIN
amandad:DEFAULT_CONFIG=DailySet1
amandad:DEFAULT_TAPE_SERVER=hdb-bak-001.DOMAIN HAVE_MMAP
amandad:HAVE_SYSVSHM LOCKING=POSIX_FCNTL DEBUG_CODE
amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY RSH_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: dgram_recv(dgram=0x280a8fe4, timeout=0,
fromaddr=0x280b8fd0)
amandad: time 0.000: (sockaddr_in *)0x280b8fd0 = { 2, 905, 172.31.5.10 }
amandad: time 10.046: dgram_recv(dgram=0x280a8fe4, timeout=0,
fromaddr=0x280b8fd0)
amandad: time 10.046: (sockaddr_in *)0x280b8fd0 = { 2, 905,
172.31.5.10 }
amandad: time 20.037: dgram_recv(dgram=0x280a8fe4, timeout=0,
fromaddr=0x280b8fd0)
amandad: time 20.037: (sockaddr_in *)0x280b8fd0 = { 2, 905,
172.31.5.10 }
amandad: time 30.031: pid 80108 finish time Wed Jul 16 20:22:16 2008
is it possible to set the debug mode to a higher level???
ah, and in my '/var/log/messages' I see the following lines, each time a
execute a 'amcheck daily' on the backup server:
Jul 16 20:21:46 client
inetd[80105]: /usr/local/libexec/amanda/amandad[80107]: exited, status 1
greetz
olli
Am Mittwoch, den 16.07.2008, 11:04 -0400 schrieb Jean-Louis Martineau:
Mister Olli wrote:
hi...
my /etc/inetd.conf looks like this on all of my freebsd 7 systems.
amanda dgram udp waitamanda /usr/local/libexec/amandad
-auth=bsd amdump amindexd amidxtaped
A 'amandad' is missing, it should be:
amanda dgram udp wait amanda /usr/local/libexec/amandad amandad
-auth=bsd amdump amindexd amidxtaped
Jean-Louis
and it works like a charm, except for that one system... gladly I'm only
the backup-administrator of that system. I wasn't the one who did the
setup, so I'm not quite sure if there's something wrong with the system
setup...
are there any hints on what to check, or how to trace/ debug this
failure in more detail?
greetz
olli
Am Mittwoch, den 16.07.2008, 07:20 -0400 schrieb Jean-Louis Martineau:
Mister Olli wrote:
Hi...
when I try to do an 'amcheck' on my daily backup jobs I have one system,
that does not pass the selftest.
it's configured identically to some other machines that work like a
charm.
the debug output of 'amandad' on the client side looks like this:
-auth=bsd: debug 1 pid 76969 ruid 1002 euid 1002: start at Wed Jul 16
10:33:47 2008
'-auth=bsd' at the beginning of the line is bogus, check your inetd/xinetd
configuration.
Jean-Louis
Re: another selfcheck problem
The debug logs *do* look different, so this was at least a minimal improvement: On Wed, Jul 16, 2008 at 2:26 PM, Mister Olli [EMAIL PROTECTED] wrote: amandad: debug 1 pid 80108 ruid 1002 euid 1002: start at Wed Jul 16 20:21:46 2008 vs. (earlier) -auth=bsd: debug 1 pid 76969 ruid 1002 euid 1002: start at Wed Jul 16 10:33:47 2008 What do the selfcheck logs say? Dustin -- Storage Software Engineer http://www.zmanda.com
