: tempserv1: selfcheck request failed: timeout waiting for ACK
The planner debug file has lines like the following:
planner: time 0.099: connect_portrange: connect to 192.168.52.131.10080 failed:\
Connection refused
planner: stream_client: Could not bind to port in range 5 - 50040.
planner
when running amcheck:
WARNING: tempserv1: selfcheck request failed: timeout waiting for ACK
The planner debug file has lines like the following:
planner: time 0.099: connect_portrange: connect to 192.168.52.131.10080 failed:\
Connection refused
planner: stream_client: Could not bind to port
: it will be created on the next run.
Server check took 0.066 seconds
Amanda Backup Client Hosts Check
WARNING: mother_inner:: selfcheck request failed: timeout waiting for
ACK
Client check: 1 host checked in 30.033 seconds. 1
On Mon, Feb 1, 2010 at 10:32 AM, jo...@msli.com jo...@msli.com wrote:
I am trying to solve an amcheck error.
Amanda Backup Client Hosts Check errors withselfcheck request failed:
timeout waiting for ACK.
You're using BSD authentication, which is notoriously tricky to set up
and debug.
It
This is both the server and client, and eventually I hope to add more
clients.
the man amanda-auth(7) , didn't tell me how to configure 'local'.
Once I change amanda.conf section
define dumptype root-tar {}
to include: auth local
Now:
su amanda -c /usr/sbin/amcheck Monthly_Mother
reports:
On Mon, Feb 1, 2010 at 11:37 AM, jo...@msli.com jo...@msli.com wrote:
Where do I read about why mother_inner isn't local?
You need to use the hostname 'localhost'. If this is a problem, you
should set up BSDTCP instead.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
Perfect. Setting the one entery in /etc/amanda/Monthly_Mother/disklist
to localhost did it. Thank you!
After I follow man amanda-auth(7) carefully, I'll try bsdtcp.
BTW, a quick read through man amanda-auth(7), for more detailed
information, it sends me to
On Mon, Feb 1, 2010 at 12:13 PM, jo...@msli.com jo...@msli.com wrote:
I'm wondering if these circular document loops are helpful or needed.
Yes, we should take them out of the manpage. Thanks!
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
Should I file a bug some place? I'm not finding the bug page.
On Mon, 2010-02-01 at 12:22 -0600, Dustin J. Mitchell wrote:
On Mon, Feb 1, 2010 at 12:13 PM, jo...@msli.com jo...@msli.com wrote:
I'm wondering if these circular document loops are helpful or needed.
Yes, we should take them out
On Mon, Feb 1, 2010 at 12:36 PM, jo...@msli.com jo...@msli.com wrote:
Should I file a bug some place? I'm not finding the bug page.
We don't have a publicly-visible bug page at the moment. I'll take
care of it some time soon. If you'd like to make up a patch and post
it to the list, I can
On Mon, 2010-02-01 at 12:48 -0600, Dustin J. Mitchell wrote:
On Mon, Feb 1, 2010 at 12:36 PM, jo...@msli.com jo...@msli.com wrote:
Should I file a bug some place? I'm not finding the bug page.
We don't have a publicly-visible bug page at the moment. I'll take
care of it some time soon.
Thanks, that did the trick (added bind address)...
Force the listen address in the relevant xinetd.d file. This will do the
trick.
--
Luc Lalonde, analyste
-
Département de génie informatique:
Éole polytechnique de Montréal
::204:23ff:fee0:6546/64 scope link
valid_lft forever preferred_lft forever
When I do an amcheck on the primary addr (192.168.1.23) , all is
fine... However, if I do it with the secondary addr (192.168.1.25), I
get this message:
WARNING: secon-ip: selfcheck request failed: timeout waiting
this message:
WARNING: secon-ip: selfcheck request failed: timeout waiting for ACK
Where, secon-ip is 192.168.1.25. I did a tcpdump -A -v -v udp port
10080 and it confirms that the Amanda server is sending a request from
the secondary address, but getting an answer from the primary address
14 matches
Mail list logo
