This morning I found this joyful message greeting me when I started working and tried to ssh to a remote server: Bus Error
Same thing even with verbose mode. The system log (/var/log/system.log) told me that a file containing the full dump of the error was created in my home directory. This is what it said
….(Some gibberish)
Date/Time: 2008-04-18 09:26:28.195 +0100
OS Version: Mac OS X 10.5.2 (9C7010)
Report Version: 6Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0×0000000000001014
Crashed Thread: 0… (More gibberish)
Ouch, kernel protection failure. I found all over Apple forum people whinging about it and posting their full dump without a definite answer. They all seemed to blame the last security update, which is really strange since it worked fine for me after I ran it.
The software causing the error was an additional module of “Audio Hijack Pro” called “Instant Hijack“. You can install it or uninstall it from from “Install Extras” inside the Audio Hijack menu.
Uninstalled it and everything started working again.
Audio Hijack people, get your game straight, don’t mess with my kernel unless you know what you’re doing!
Tags: Apple, Audio, Audio Hijack, Bus, Bus Error, Error, Exception, Failure, Hijack, Instant Hijack, Kernel, Mac, MacOSx, ssh
April 18, 2008 at 8:50 am |
You also could have just upgraded to the latest version of Instant Hijack. They fixed the problem on March 19: http://www.rogueamoeba.com/utm/2008/03/19/security-update-2008-002-compatibility-fix/
April 18, 2008 at 9:03 am |
Oh cool, I didn’t know that. Thanks for the tip!
April 18, 2008 at 12:03 pm |
[...] Gib mir ein Google, das lang genug ist und ich hebe damit die Welt aus den Angeln: Die Lösung fand sich hier. [...]
May 9, 2008 at 6:56 pm |
[...] message greeting me when I started working and tried to ssh to a remote server: Bus Error…. Solvedhttp://thebigdeal.wordpress.com/2008/04/18/mac-os-x-ssh-bus-error/SensocardE-5 error message: Strong electromagnetic field eg. mobile phone or high intensity [...]
May 14, 2008 at 10:45 pm |
Thank you very much for your post, I’ve spent the last 3 hours of my life trying to understand why my SSH clients didn’t connect to my iPhone using OpenSSH…
After the last ~/.ssh/ chmod I’ve found your post…!
I just fogot I’ve installed that Audio Hijack plug-in yesterday…
Working fine now I’ve uninstalled it
Cheers
May 28, 2008 at 2:55 am |
THANK YOU! Solved a very big problem for me with minimal hassle. Much obliged!
June 23, 2008 at 4:28 am |
They have fixed the error. If you update to the nest version of audio hijack or the plugin I forgot which, but it fixes the ssh problem. I had it too!
February 12, 2009 at 1:01 am |
Greetings new friends
I just joined this forum and see that it is very active and full of people with great ideas. It seems like you all support each other well here too. I am looking for advice as I got laid off from my job 3 months ago and it looks like the mortgage company is going to foreclose on my home.
Do any of you have any advice or are you in a similar position?
I know this is a bit off topic for this forum so maybe you can please join me at LayOffRant.com and we can talk through what’s going on with me and the economy in the USA.
June 8, 2009 at 2:14 pm |
This is crazy!
Here I am, a year later, with the same symptoms as described above, but no Audio Hijack installed (at least I don’t think so, and don’t see that in the error log). I did, however, just do an OSX “up”grade, and I did recently install Remote Desktop and VPN. I was thinking that maybe the IP# appearing on both the airport and VPN interfaces might be a problem (although I’ve never had troubles running the same IP on both airport and ethernet simultaneously), but I checked and VPN is disconnected. ifconfig reports only one interface active.
I am very confused now. Did VPN hose my ssh? Did the lamest, I mean latest, upgrade from God, I mean Apple, strike me down? Anyone have any ideas? Thanks!