Debra,
The patch created other problems and was later reverted (I don't
remember what was the problem).
You can try it if you want
In common-src/krb5-security.c,function runkrb5,
replace the last argument (0) of stream_client to 1.
Jean-Louis
On 09/22/2014 04:19 PM, Debra S Baddorf wrote:
I seem to recall a patch for this, but I can’t find it now. It’s finally
happened firmly enough that I can reproduce it, on amcheck at least:
amcheck (and sometimes amdump) hang indefinitely is the client is powered down.
amanda v3.3.6 server (happened on 3.3.3 too so I upgraded, but it still
happens)
2 clients - are powered down so version cannot matter!
both are (were) using auth=krb5
other krb5 clients work fine and have done so for more than a year
The server’s log doesn’t have anything useful — I killed the process at about
15:10 .
server/daily/amcheck.20140922150805.debug
::::::::::::::
Mon Sep 22 15:08:05 2014: thd-0x9550330: amcheck: pid 3893 ruid 0 euid 11
version 3.3.6: start at Mon Sep 22 15:08:05 2014
Mon Sep 22 15:08:05 2014: thd-0x9550330: amcheck: pid 3893 ruid 0 euid 11
version 3.3.6: rename at Mon Sep 22 15:08:05 2014
Mon Sep 22 15:08:05 2014: thd-0x9550330: amcheck-clients:
security_getdriver(name=krb5) returns 0x193240
Mon Sep 22 15:08:05 2014: thd-0x9550330: amcheck-clients:
security_handleinit(handle=0x96251c8, driver=0x193240 (KRB5))
Mon Sep 22 15:08:05 2014: thd-0x9550330: amcheck-clients:
security_streaminit(stream=0x9625750, driver=0x193240 (KRB5))
Mon Sep 22 15:08:05 2014: thd-0x9550330: amcheck-clients: make_socket opening
socket with family 2
Mon Sep 22 15:08:05 2014: thd-0x9550330: amcheck-clients: connect_port: Try
port 50000: available - Success
Can somebody point me to the patch I remember hearing about?
Deb Baddorf
Fermilab
