Re: planner timeouts
2005-09-05 23:33:31
Charles Sprickman wrote:
h13 (client) debug logs. Note that there is two-way communication, and
everything seems to go correctly. In the debug dir, there are only
"amandad" debug logs, nothing else.
That doesn't sound right to me. There should be a sendbackup log file as
well, a runtar one, and so on. Can you verify your inetd config on that
particular client, to see whether there's something afoul? Have a look at
the system logs as well, while you're at it. amanda might be unable to run
any secondary programs, for instance.
Me neither... Is there any way to increase the verbosity of amandad?
inetd config is good (it's a client, so it's only got the single line for
amandad), nothing in the system logs, all of the stuff in the libexec
directory appears to have correct perms (the proper things are setuid to
my amanda user)...
GETTING ESTIMATES...
planner: time 30.956: error result for host h13.blah.com disk /spool:
Request to h13.blah.com timed out.
planner: time 30.956: error result for host h13.blah.com disk
/var/qmail/bin: Request to h13.blah.com timed out.
planner: time 30.956: error result for host h13.blah.com disk
/var/qmail/control: Request to h13.blah.com timed out.
planner: time 30.956: error result for host h13.blah.com disk /var/db/pkg:
Request to h13.blah.com timed out.
planner: time 30.956: error result for host h13.blah.com disk /usr/local/:
Request to h13.blah.com timed out.
planner: time 30.956: error result for host h13.blah.com disk /home:
Request to h13.blah.com timed out.
planner: time 30.956: error result for host h13.blah.com disk /: Request to
h13.blah.com timed out.
planner: time 30.956: getting estimates took 30.811 secs
Does that spell a 30s timeout somewhere? amanda.conf not taken into account,
perhaps? And the obligatory question, did you double-check that there's no
firewall between that particular client and server? (If you did,
triple-check. :-) )
I have bumped up all the timeouts in amanda.conf to ridiculously large
values. :) There are firewalls, and the tcpdump trace I sent was taken
with each host's firewall software (ipfilter) disabled. Additionally, the
firewall logs blocked traffic and had nothing to say about this.
What else can I look at here?
I'm also including the tcpdump output again at the end of this message.
Thanks,
Charles
The devel2 (server) view:
19:46:23.967162 devel2.937 > h13.blah.com.amanda: udp 117
19:46:24.074337 h13.blah.com.amanda > devel2.937: udp 50
19:46:24.249414 h13.blah.com.amanda > devel2.937: udp 81
19:46:24.249497 devel2.937 > h13.blah.com.amanda: udp 50
19:46:24.489787 devel2.937 > h13.blah.com.amanda: udp 1465
19:46:34.497794 devel2.937 > h13.blah.com.amanda: udp 1465
19:46:44.508815 devel2.937 > h13.blah.com.amanda: udp 1465
The h13 (client) view:
19:46:23.982760 devel2.937 > h13.blah.com.amanda: udp 117
19:46:24.054390 h13.blah.com.amanda > devel2.937: udp 50
19:46:24.230317 h13.blah.com.amanda > devel2.937: udp 81
19:46:24.264200 devel2.937 > h13.blah.com.amanda: udp 50
19:46:24.523791 devel2.937 > h13.blah.com.amanda: udp 1465 (frag
59731:1472@0+)
19:46:34.531821 devel2.937 > h13.blah.com.amanda: udp 1465 (frag
62763:1472@0+)
19:46:44.542471 devel2.937 > h13.blah.com.amanda: udp 1465 (frag
9535:1472@0+)
Alex
--
Alexander Jolk / BUF Compagnie
tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: planner timeouts,
Charles Sprickman <=
|
|
|