Thomas Bushnell BSG <[EMAIL PROTECTED]> writes: > Package: openafs-client > Version: 1.4.4.dfsg1-1 > Severity: grave > Justification: renders package unusable
> When I run aklog, I get the following helpful error message: > ~$ aklog -d > Authenticating to cell becket.net (server aquinas.becket.net). > We've deduced that we need to authenticate to realm BECKET.NET. > Getting tickets: afs/[EMAIL PROTECTED] > Principal not found, trying alternate service name: [EMAIL PROTECTED] > Using Kerberos V5 ticket natively > About to resolve name tb to id in cell becket.net. > stackcheck = 66051: stack = 66051 > topstack = 0x3007b034: stackptr = 0x3004b008: stacksize = 0x30000 > Wed Apr 18 08:35:47 2007 LWP: stack overflow in process IO MANAGER! > Aborted > No tokens are reported by the "tokens" program, and klist shows > a correct [EMAIL PROTECTED] ticket. > This makes the package unusuable since the purpose of the package is to > provide AFS file services to users, and without the ability to get > tokens, it is similarly not possible to use AFS effectively in almost > every environment. > Is this related perhaps to the end of linuxthreads in Debian? It's probably related to the fact that glibc 2.5 is not fully compatible with glibc 2.3 on any platform, at least for what OpenAFS is doing in its LWP threading library (which I believe involves using setjmp/longjmp and probably violating an abstraction boundary in the process). I already found that client binaries built with 2.3 won't work with glibc 2.5. On x86 and amd64, rebuilding with glibc 2.5 fixes the problem, but apparently that isn't the case on PowerPC. AFS is slowly moving towards using pthreads everywhere, but not every platform supports them and up until recently the LWP code had been more stable. I'll forward this upstream; this is an area in which there's been some current work and investigation, so I'm hoping that someone else will already have an idea of how to fix it. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
