|
Re: planner timeouts
2005-08-31 19:35:11
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.
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. :-) )
Alex
--
Alexander Jolk / BUF Compagnie
tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
|
|
|
