|
RESOLVED Re: Estimate timeouts after upgrade and easy way to test just one backup target
2006-04-20 12:06:26
-Major- rookie user error. You'd think I'd been using Amanda for 3
minutes, not 3 years. :-/
I have installed Fedora a million times. Apparently, a million times
minus one, I remembered to disable the freakin' firewall at install
time. I was so focused on the client side issues and making sure
selinux wasn't running on the server, I forgot to do a simple
verification of iptables on the server. Son of a.... It's so obvious
now in hindsight! I currently have that same feeling you get when you
accidentally rm -rf in the wrong place. :-/
Well, glad it's resolved, anyway.
-Fran
Fran Fabrizio wrote:
I have been running tests all afternoon to try to pinpoint the
problem. First issue I am having is with the amcheck timing out.
I have ctimeout set to 150, but amcheck appears to be ignoring that...
-bash-3.1$ /usr/sbin/amcheck -c CIS monkey.cis.uab.edu
Amanda Backup Client Hosts Check
--------------------------------
WARNING: monkey.cis.uab.edu: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.002 seconds, 1 problem found
(brought to you by Amanda 2.4.5p1)
-bash-3.1$
The amandad debug on monkey sees this:
[root@monkey amanda]# tail -f amandad.20060419165330.debug
OPTIONS features=fffffeff9ffe7f;
----
amandad: time 9.994: it is not an ack
amandad: time 9.994: sending REP packet:
----
Amanda 2.4 REP HANDLE 000-08961608 SEQ 1145483693
OPTIONS features=fffffeff9ffe7f;
----
amandad: time 19.985: dgram_recv: timeout after 10 seconds
amandad: time 19.986: waiting for ack: timeout, retrying
amandad: time 19.992: got packet:
----
Amanda 2.4 REQ HANDLE 000-08961608 SEQ 1145483693
SECURITY USER amanda
SERVICE noop
OPTIONS features=fffffeff9ffe7f;
----
amandad: time 19.992: it is not an ack
amandad: time 29.986: dgram_recv: timeout after 10 seconds
amandad: time 29.986: waiting for ack: timeout, retrying
amandad: time 39.986: dgram_recv: timeout after 10 seconds
amandad: time 39.986: waiting for ack: timeout, retrying
amandad: time 49.986: dgram_recv: timeout after 10 seconds
amandad: time 49.986: waiting for ack: timeout, retrying
amandad: time 59.987: dgram_recv: timeout after 10 seconds
amandad: time 59.987: waiting for ack: timeout, giving up!
amandad: time 59.987: pid 31419 finish time Wed Apr 19 16:54:30 2006
So that's the first problem. Any thoughts on this one?
--
Fran Fabrizio
Senior Systems Analyst
Department of Computer and Information Sciences
University of Alabama at Birmingham
http://www.cis.uab.edu/
205.934.0653
|
|
|
