SSH bus error after upgrade to 10.1.1

L

loekjehe

Registered
Hello all,

Maybe some of you have this same problem. I always use SSH as ordinary user to login as root user to work in the Terminal on root level. Since the 10.1.1 upgrade I always get a "bus error" while exiting as root user in the Terminal. I run OpenSSH_2.9.9p2, OpenSSL 0x0090602f. The console error message (reporting always the same error) follows below. I would appreciate any help. Or is this a real OS 10.1.1 bug?

Loek

Console error report:

Date/Time: 2001-11-17 21:10:10 +0100
OS Version: 10.1.1 (Build 5M28)

Command: klist
PID: 542

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

Thread 0:
#0 0x73f06e3c in initCGDisplayMappings
#1 0x73e0d330 in _CGSDisplayInitialize
#2 0x73e10a14 in CGSInitialize
#3 0x73e04458 in _CGSDefaultConnection
#4 0x731c2478 in RegisterProcess
#5 0x7319dd88 in INIT_Processes
#6 0x7319ae88 in _InitHLTB
#7 0x41108ac0 in call_image_init_routines
#8 0x41112b0c in _dyld_make_delayed_module_initializer_calls
#9 0x00004108 in 0x4108
#10 0x00003f88 in 0x3f88
#11 0x00003efc in 0x3efc


PPC Thread State:
srr0: 0x73f06e3c srr1: 0x0000f030 vrsave: 0x00000000
xer: 0x00000020 lr: 0x73f06e14 ctr: 0x70497044 mq: 0x00000000
r0: 0x00000000 r1: 0xbffff500 r2: 0xbfffe3aa r3: 0x00000000
r4: 0x00000020 r5: 0x00000001 r6: 0x706c6179 r7: 0x20696e74
r8: 0x65726c6f r9: 0x00000000 r10: 0x00000000 r11: 0x83da367c
r12: 0x70497044 r13: 0x00000000 r14: 0x00000036 r15: 0x0004a010
r16: 0xbfffee70 r17: 0x00000000 r18: 0x00504d58 r19: 0x00002803
r20: 0x00000000 r21: 0x0000001c r22: 0x70004bc4 r23: 0x70004c58
r24: 0x706bab4c r25: 0x000006eb r26: 0x8081ab5c r27: 0x003be3a0
r28: 0x00000000 r29: 0xbfffef00 r30: 0x00000000 r31: 0x00000001

**********
 
So you are running something like ssh -l root localhost to do this? If so, is there any more interesting information from adding a couple of -v options to that? I can use that command just fine on my system without any crashes.
 
I always could ssh to my own ip number as the admin user without any problem. I can also work now without problems, but immediately after logout or exit I receive a notification "bus error" and a crash report. Doing ssh -v -v -v produces a lot of output that I can send you if you with but to me there is no interesting info, esp. immediately after logout there is this "bus error" before any verbose message appears.

What might be interesting is that I noticed in the system.log the following message that happens every time shortly after logout from ssh as other user:

WindowServer[68]: _CGXGetDisplayShmem: Unauthorized user
/usr/libexec/CrashReporter: Succeeded writing crash report: /Users/loek/Library/Logs/klist.crash.log

The bus error not only occurs after logout from ssh as admin user, but also after logout from ssh having logged in as other ordinary user. Strangely enough there are no problems while logging out after having logged in as myself (i.e. the user currently logged in). Could be a file permissions problem.
 
That makes it sound as if the program experiencing a bus error is klist which has something to do with Kerberos. Why it's running, I have no idea, but I have noticed on my own machine some processes Kerberos-related running for no reason (specifically, CCacheServer, right now, there are two, but I don't even use Kerberos)...

Does simply running klist cause a bus error as well? If so, it's probably just an annoying problem which doesn't impact, but you might want to report it anyway.

A quick look tells me running klist seems to kick of the CCacheServer process, so that looks to be why it runs in the first place...
 
To followup: klist is being run from /usr/share/init/tcsh/logout when you logout as root. If you comment out the line which calls klist (looks like

Code: 
  if ({ (klist -s >& /dev/null) }) kdestroy

), then I'd bet your bus errors will go away. CCacheServer stopped popping up on my system. Of course, this is more of a workaround than a true fix, but that's better than nothing...
 
After applying your workaround my problems have gone! Your replies are completely correct and very helpful. Thank you! Indeed I also wondered what this CCacheServer was doing. Strange, in the /usr/share/init/tcsh/logout file it is mentioned that this should NOT be run from the Terminal.......

After running "klist" as ordinary user I get the following error:

klist: Unknown error while initializing krb5

After running "klist" as root user I get the following error:

kCGErrorFailure : initCGDisplayState: No display interlock
Bus error

Here we are!! So: a real bug. I will report it. Thank you very much for your help!

Loek
 
You must log in or register to reply here.
Back
Top