Not sure if this is your issue, but...
I've had some funny issues when I've been unable to resolve
client names, or clients not properly resolving amanda server
names, as in when the amanda client is a solaris zone or in
an odd segement of my network.
I never rely on "localhost" and always use proper host names,
if I continue to have failure issues, which I recognize as
DNS rather than amanda issues, I'll add the requisit name to
the local /etc/hosts file.
On Tue, Jul 07, 2009 at 11:55:27AM -0700, aminukapon wrote:
> Hello all,
>
> I ran across a problem when I tried to run amcheck on my setup of amanda
> using a new machine.. On our old setup I had the same problem and figured it
> was the permissions on the amandahosts file which I fixed. But now I tried
> the same fix on the new setup but I still get the same errors. I have seached
> the zmanda forums for any form of help but none soo far.
>
> Here is the actually error when I run amcheck
>
> bac...@guass:~$ amcheck DailySet1
> Amanda Tape Server Host Check
> -----------------------------
> Holding disk /home1_backup_usb/dumps/amanda: 1149387776 KB disk space
> available, using 1044530176 KB
> slot 1: read label `DailySet1-01', date `X'
> NOTE: skipping tape-writable test
> Tape DailySet1-01 label ok
> NOTE: conf info dir /etc/amanda/DailySet1/curinfo does not exist
> NOTE: it will be created on the next run.
> NOTE: index dir /etc/amanda/DailySet1/index does not exist
> NOTE: it will be created on the next run.
> Server check took 0.128 seconds
>
> Amanda Backup Client Hosts Check
> --------------------------------
> WARNING: Usage of fully qualified hostname recommended for Client localhost.
> WARNING: localhost: selfcheck request failed: timeout waiting for ACK
> Client check: 1 host checked in 30.024 seconds, 1 problem found
>
> (brought to you by Amanda 2.5.2p1)
>
>
>
> Also when I check the log file /var/log/amanda/server/DailySet1/
>
> amcheck: debug 1 pid 12972 ruid 34 euid 0: start at Tue Jul 7 14:52:58 2009
> amcheck: debug 1 pid 12972 ruid 34 euid 34: rename at Tue Jul 7 14:52:58 2009
> amcheck-clients: time 0.003: security_getdriver(name=BSD) returns 0xb7f19c00
> amcheck-clients: time 0.003: security_handleinit(handle=0x8cd37c8,
> driver=0xb7f19c00$
> amcheck-clients: time 0.005: bind_portrange2: Try port 846: Available -
> Success
> amcheck-clients: time 0.005: dgram_bind: socket 4 bound to ::.846
> amcheck-clients: time 0.005: dgram_send_addr(addr=0x8cd37e8, dgram=0xb7f2ba84)
> amcheck-clients: time 0.005: (sockaddr_in6 *)0x8cd37e8 = { 10, 10080, ::1 }
> amcheck-clients: time 0.005: dgram_send_addr: 0xb7f2ba84->socket = 4
> changer_query: changer return was 25 1
> changer_query: searchable = 0
> changer_find: looking for NULL changer is searchable = 0
> amcheck-clients: time 10.015: dgram_send_addr(addr=0x8cd37e8,
> dgram=0xb7f2ba84)
> amcheck-clients: time 10.015: (sockaddr_in6 *)0x8cd37e8 = { 10, 10080, ::1 }
> amcheck-clients: time 10.015: dgram_send_addr: 0xb7f2ba84->socket = 4
> amcheck-clients: time 20.025: dgram_send_addr(addr=0x8cd37e8,
> dgram=0xb7f2ba84)
> amcheck-clients: time 20.025: (sockaddr_in6 *)0x8cd37e8 = { 10, 10080, ::1 }
> amcheck-clients: time 20.026: dgram_send_addr: 0xb7f2ba84->socket = 4
> amcheck-clients: time 30.036: security_seterror(handle=0x8cd37c8,
> driver=0xb7f19c00 $
> amcheck-clients: time 30.036: security_close(handle=0x8cd37c8,
> driver=0xb7f19c00 (BS$
> amcheck: time 30.036: pid 12972 finish time Tue Jul 7 14:53:28 2009
>
>
> Can anyone help?
>
> Thanks
>
>
>
>
> ---
Brian R Cuttler brian.cutt...@wadsworth.org
Computer Systems Support (v) 518 486-1697
Wadsworth Center (f) 518 473-6384
NYS Department of Health Help Desk 518 473-0773
IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure. It
is intended only for the addressee. If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments. Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.
