ANAMDA SERVER
zorn->[48] > uname -a
SunOS zorn.math.purdue.edu 5.10 Generic_120011-14 sun4u sparc
SUNW,Sun-Fire-280R
AMANDA SOFTWARE 2.5.2p1
Last night none of my backups ran on the host zorn, which happens to be
my Amanda server. All my other clients ran with out problems as they
have been for years.
SNIPIT of REPORT
Hostname: zorn.math.purdue.edu
Org : DAILY BACKUP - MATHNET
Config : daily
Date : May 19, 2009
These dumps were to tape D00025.
peano /boot 1 0 0 -- 0:00
79.1 0:03 11.3
pythagoras / 0 13014 13014 -- 36:45
6045.2 6:07 36287.9
pythagoras /boot 1 0 0 -- 0:00
266.1 0:03 10.7
zada / 1 247 247 -- 1:43
2452.4 0:06 44166.2
zada /export/comm 1 7477 7477 -- 43:27
2937.0 2:21 54378.0
zorn / MISSING
----------------------------------------------------
zorn /export/csw MISSING
----------------------------------------------------
zorn /export/jumpstart MISSING
----------------------------------------------------
zorn /export/patchsvr MISSING
----------------------------------------------------
zorn /export/pkgs MISSING
----------------------------------------------------
zorn /export/users-a MISSING
----------------------------------------------------
zorn /export/users-b MISSING
----------------------------------------------------
zorn /export/users-c MISSING
----------------------------------------------------
This morning I ran "amcheck -c daily zorn" and got the following.
zorn->[46] > cat amcheck.20090520091105.debug
amcheck: debug 1 pid 24619 ruid 30002 euid 0: start at Wed May 20
09:11:05 2009
amcheck: debug 1 pid 24619 ruid 30002 euid 30002: rename at Wed May 20
09:11:05 2009
amcheck-clients: time 0.021: security_getdriver(name=BSD) returns
ff258f24
amcheck-clients: time 0.021: security_handleinit(handle=3d558,
driver=ff258f24 (BSD))
amcheck-clients: time 0.049: bind_portrange2: Try port 917: Available
- Success
amcheck-clients: time 0.049: dgram_bind: socket 4 bound to 0.0.0.0.917
amcheck-clients: time 0.050: dgram_send_addr(addr=3d578, dgram=ff2592f4)
amcheck-clients: time 0.050: (sockaddr_in *)3d578 = { 2, 10080,
128.210.3.177 }
amcheck-clients: time 0.050: dgram_send_addr: ff2592f4->socket = 4
amcheck-clients: time 10.060: dgram_send_addr(addr=3d578,
dgram=ff2592f4)
amcheck-clients: time 10.060: (sockaddr_in *)3d578 = { 2, 10080,
128.210.3.177 }
amcheck-clients: time 10.060: dgram_send_addr: ff2592f4->socket = 4
amcheck-clients: time 20.070: dgram_send_addr(addr=3d578,
dgram=ff2592f4)
amcheck-clients: time 20.070: (sockaddr_in *)3d578 = { 2, 10080,
128.210.3.177 }
amcheck-clients: time 20.070: dgram_send_addr: ff2592f4->socket = 4
amcheck-clients: time 30.079: security_seterror(handle=3d558,
driver=ff258f24 (BSD) error=timeout waiting for ACK)
amcheck-clients: time 30.080: security_close(handle=3d558,
driver=ff258f24 (BSD))
amcheck: time 30.084: pid 24619 finish time Wed May 20 09:11:36 2009
Something changed from May 18 to May 19 but I cannot figure out what. To
the best of my knowledge no changes have been made to any of the Amanda
2.5.2pl files.
I ran a " amdump daily -o diskfile=xdisklist " where xdisklist is a
subset of the disklist. I got the same error but not any diagnostic
other than planner says the same thing.
I do not know where to start looking for the problem. Any suggestions.
Thanks
Robert
_____________________________________________________________________
Robert P. McGraw, Jr.
Manager, Computer System EMAIL: rmcgraw AT purdue DOT edu
Purdue University ROOM: MATH-807
Department of Mathematics PHONE: (765) 494-6055
150 N. University Street
West Lafayette, IN 47907-2067
|
