Re: What is this log file trying to tell me?
On Wed, Jan 13, 2010 at 07:49:28AM -0500, Jean-Louis Martineau wrote: > What is the error you get from amcheck? timed out waiting for ACK. > > The '229.046' time is high for amcheck, try increasing ctimeout. > ONce upon a time amchek would complete in a matter of seconds. Now it takes tens of minutes. All this without adding significantly to the number of DLE's. Given that, still think it's worth tweaking ctimeout? What phase of the handshaking is it for? -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: What is this log file trying to tell me?
What is the error you get from amcheck? The '229.046' time is high for amcheck, try increasing ctimeout. Jean-Louis stan wrote: WE are still having major issues with our Amanda backups. Most of the machines that are failing still use UDP, and we recognize the need to get newer version of Amanda compiled on those clients. But in addition some machines using bsd_auth are failing. Here is some data from one of those machines, I have extrated what I think are the important peices ehre, but if more are needed, let me know. amandad: debug 1 pid 16548 ruid 404 euid 404: start at Mon Jan 11 12:51:29 2010 security_getdriver(name=bsdtcp) returns ff341ea0 amandad: version 2.5.1p2 amandad: build: VERSION="Amanda-2.5.1p2" amandad:BUILT_DATE="Sun Jul 12 14:09:31 GMT 2009" amandad:BUILT_MACH="SunOS AW0550 5.8 Generic_108528-13 sun4u sparc SUNW, Sun-Blade-100" amandad:CC="gcc" OK /tmp/amanda has more than 64 KB available. OK /tmp/amanda has more than 64 KB available. OK /etc has more than 64 KB available. amandad: time 229.046: received ACK pkt: < security_close(handle=2b3c0, driver=ff341ea0 (BSDTCP)) security_stream_close(350a8) security_stream_seterr(350a8, write error to : Broken pipe) amandad: time 229.046: pid 16548 finish time Mon Jan 11 12:55:18 2010 So, it looks like the clentrecived the reqyest, checked thigs, adn decided they wer OK, but did not suced in telling the master machine things were OK. Am I reading this corectly?
What is this log file trying to tell me?
WE are still having major issues with our Amanda backups. Most of the machines that are failing still use UDP, and we recognize the need to get newer version of Amanda compiled on those clients. But in addition some machines using bsd_auth are failing. Here is some data from one of those machines, I have extrated what I think are the important peices ehre, but if more are needed, let me know. amandad: debug 1 pid 16548 ruid 404 euid 404: start at Mon Jan 11 12:51:29 2010 security_getdriver(name=bsdtcp) returns ff341ea0 amandad: version 2.5.1p2 amandad: build: VERSION="Amanda-2.5.1p2" amandad:BUILT_DATE="Sun Jul 12 14:09:31 GMT 2009" amandad:BUILT_MACH="SunOS AW0550 5.8 Generic_108528-13 sun4u sparc SUNW, Sun-Blade-100" amandad:CC="gcc" OK /tmp/amanda has more than 64 KB available. OK /tmp/amanda has more than 64 KB available. OK /etc has more than 64 KB available. > amandad: time 229.046: received ACK pkt: < > security_close(handle=2b3c0, driver=ff341ea0 (BSDTCP)) security_stream_close(350a8) security_stream_seterr(350a8, write error to : Broken pipe) amandad: time 229.046: pid 16548 finish time Mon Jan 11 12:55:18 2010 So, it looks like the clentrecived the reqyest, checked thigs, adn decided they wer OK, but did not suced in telling the master machine things were OK. Am I reading this corectly? -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
