On 2006-05-02 21:46, McGraw, Robert P. wrote:
I still seem to be having a problem getting a good backup. Seems something
always pops up.
planner: build: VERSION="Amanda-2.5.0p1"
planner: BUILT_DATE="Sat Apr 29 15:42:05 EDT 2006"
planner: BUILT_MACH="SunOS zorn.math.purdue.edu 5.10
Generic_118833-03 sun4u sparc SUNW,Sun-Fire-280R"
I noticed that that the four "dumping" jobs seemed to hang.
zorn->[309] > amstatus --config daily --date
Using /var/amanda/daily/amdump from Tue May 2 14:30:35 EDT 2006
20060502 bers:/ 0 4444m finished (14:42:59)
20060502 bessel:/ 0 4592m finished (14:47:27)
20060502 zorn:/export/csw 0 1322m dumping 0m
(14:34:14)
20060502 zorn:/export/users-aar 0 0m finished (14:35:43)
20060502 zorn:/export/users-aduchkov 0 448m finished (14:37:09)
20060502 zorn:/export/users-aedquist 0 59m dumping 0m
(14:33:43)
20060502 zorn:/export/users-aendicot 0 18m finished (14:31:46)
20060502 zorn:/export/users-agabriel 0 777m dumping 0m
(14:34:29)
20060502 zorn:/export/users-nlucier 0 8931m finished (15:10:54)
20060502 zorn:/export/users-rmcgraw 0 1430m dumping 0m
(14:33:59)
What is the OS/version and Amanda version on those clients?
I went to /tmp/amanda and ran
##R##-zorn->[351] ##> grep -i error *
sendbackup.20060502143344.debug:sendbackup: time 0.000: error redirecting
stderr to fd 51: Bad file number
sendbackup.20060502143359.debug:sendbackup: time 0.000: error redirecting
stderr to fd 51: Bad file number
sendbackup.20060502143414.debug:sendbackup: time 0.000: error redirecting
stderr to fd 51: Bad file number
sendbackup.20060502143429.debug:sendbackup: time 0.000: error redirecting
stderr to fd 51: Bad file number
I cat'ed on of the debug files
##R##-zorn->[360] ##> cat sendbackup.20060502143359.debug
sendbackup: debug 1 pid 23380 ruid 30002 euid 30002: start at Tue May 2
14:33:59 2006
sendbackup: version 2.5.0p1
parsed request as: program `GNUTAR'
disk `/export/users-rmcgraw'
device `/export/fssnap/users'
level 0
since 1970:1:1:0:0:0
options `|;auth=BSD;index;include-file=./rmcgraw;'
sendbackup: time 0.000: error redirecting stderr to fd 51: Bad file number
sendbackup: time 0.000: pid 23380 finish time Tue May 2 14:33:59 2006
1) Can anybody tell me what the "error redirecting stderr to fd 51: Bad file
number" means? I googled the message but found nothing.
The program amandad opens data/mesg/index to file descriptor 50/51/52
and then execs sendbackup. And sendbackup connects those
filedescriptors to the needed streams. The message file descriptor
needs to connected to the stderr of gnutar, but when tried, sendbackup
notices that filedescriptor 51 is not valid (not open?).
Really weird.
Locate the amandad.datatime.debug file that contains the "SERVICE
sendbackup" and see if you got any more clues there?
Or are you running into some limit of open files maybe?
2) I do an fssnap of the /export/users directory and mount it on
/export/fssnap/users. This should not be a problem should it?
Not that I am aware of. In fact, I do similar things with snapshots.
3) I also use "estimate calcsize" where possible.
But the above error seems to occur in the sendbackup, which is
started only after all estimates are finished.
--
Paul Bijnens, xplanation Technology Services Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************
|
