Is logKextDaemon running?

[Langfordjoey]

I have uninstalled, reinstalled, and rebooted. Keep getting this same issue. I am not proficient by any means concerning using terminal and coding but I can usually figure it out. This is stumped me.

[gallowstree]

Same thing happening to me, please let me know if you find a solution. I am running Lion and installed using the binary because xcode builds but throws an error about packageManager.app, btw.

[tachyo]

Having exactly the same issue here. i'm running OS X 10.9.1 and installed the binary release 2.4.

PS: an guid how to build from source would be awesome for less experienced users like me (no priority)

[SlEePlEs5]

I see, there's a permissions issue. I will fix the installer, but here's a temporary fix in the meantime.

Open Terminal, and type in these two commands:

sudo chown root:wheel /Library/LaunchDaemons/logKext.plist
sudo launchctl load /Library/LaunchDaemons/logKext.plist

You will need to enter your password. Everything should then work as normal. Thanks for reporting this!

[gallowstree]

I tried running those commands but if I call logkextClient again, the same error appears. I tried re-installing, but still no luck. Any other step I should take?

Thanks a lot for your help, I really appreciate it.

[SlEePlEs5]

Run the commands again just to make sure, then post the output of these 3 commands to pastebin:

kextstat
ps -A
sudo launchctl list

Post the link back here, and I'll try to figure out what the problem is.

[patricktr]

Same issue here. Note, when I typed the permissions command, all went well. When I tried to load the plist file again, terminal outputs: "com.fsb.logKext: Already loaded"

Here is the pastebin you asked for. http://pastebin.com/UzwtSGRB

[SlEePlEs5]

the logKextDaemon job is indeed loaded, so it seems we have another problem. The kext itself isn't loaded, and I believe the daemon exits with an error if it can't find the kext.

Run sudo kextutil /System/Library/Extensions/logKext.kext in Terminal and send me the output, it should help me figure things out.

[gallowstree]

This is what it says when I run the command.

(kernel) kxld[com.fsb.kext.logKext]: The super class vtable 'ZTV12IOUserClient' for vtable 'ZTV17logKextUserClient' is out of date. Make sure your kext has been built against the correct headers. (kernel) kxld[com.fsb.kext.logKext]: The super class vtable 'ZTV9IOService' for vtable 'ZTV21com_fsb_iokit_logKext' is out of date. Make sure your kext has been built against the correct headers. (kernel) Can't load kext com.fsb.kext.logKext - link failed. (kernel) Failed to load executable for kext com.fsb.kext.logKext. (kernel) Kext com.fsb.kext.logKext failed to load (0xdc008016). (kernel) Failed to load kext com.fsb.kext.logKext (error 0xdc008016). Failed to load /System/Library/Extensions/logKext.kext - (libkern/kext) link error. Check library declarations for your kext with kextlibs(8).

[HibGut]

I have the same problem. At first I got installation errors. The installer progress bar seemed to finish, it went through "Optimizing system", then "Registering components", but at the end, instead of a success message, I got this:

Then same as Langfordjoey above: "Error: logKext Preferences cannot be found. Is logKextDaemon running?"

Fixing permissions (chown) didn't help. Finder now reports logKext.plist as system: read&write, wheel: read only. everyone: read only.

Ran uninstall script (got some errors there too, but didn't save them), then ran installer again. This time it succeeded, but still same error as OP. Fixed permissions again, rebooted - no help.

Here is the output of the diagnosis commands you asked to run: http://pastebin.com/cJik1yWe

I noticed that /Library/Application\ Support/logKext is inaccessible in Finder. "The folder 'logKext' can’t be opened because you don’t have permission to see its contents." The folder icon has the little "no entry" symbol in the corner. Is that normal? I'm running as an admin user in OS X 10.8.5.

[snrkl]

same issue - here is my output:

Software Mac OS X Lion 10.7.5 (11G63b)

sudo logKextClient Error: logKext Preferences cannot be found. Is logKextDaemon running? The-Mac-Mini:~ snrkl$ sudo kextutil /System/Library/Extensions/logKext.kext (kernel) kxld[com.fsb.kext.logKext]: The super class vtable 'ZTV12IOUserClient' for vtable 'ZTV17logKextUserClient' is out of date. Make sure your kext has been built against the correct headers. (kernel) kxld[com.fsb.kext.logKext]: The super class vtable 'ZTV9IOService' for vtable 'ZTV21com_fsb_iokit_logKext' is out of date. Make sure your kext has been built against the correct headers. (kernel) Can't load kext com.fsb.kext.logKext - link failed. (kernel) Failed to load executable for kext com.fsb.kext.logKext. (kernel) Kext com.fsb.kext.logKext failed to load (0xdc008016). (kernel) Failed to load kext com.fsb.kext.logKext (error 0xdc008016). Failed to load /System/Library/Extensions/logKext.kext - (libkern/kext) link error. Check library declarations for your kext with kextlibs(8).

[ghost]

Sorry for this but how would one install this from the files in logkext-master?

[DoctorJazz]

Same problem here:

HomeMacPro:LaunchDaemons jazz$ sudo kextutil /System/Library/Extensions/logKext.kext
No kernel file specified, using '/mach_kernel' 
(kernel) kxld[com.fsb.kext.logKext]: The super class vtable '__ZTV12IOUserClient' for vtable '__ZTV17logKextUserClient' is out of date. Make sure your kext has been built against the correct headers.
(kernel) kxld[com.fsb.kext.logKext]: The super class vtable '__ZTV9IOService' for vtable '__ZTV21com_fsb_iokit_logKext' is out of date. Make sure your kext has been built against the correct headers.
(kernel) Can't load kext com.fsb.kext.logKext - link failed.
(kernel) Failed to load executable for kext com.fsb.kext.logKext.
(kernel) Kext com.fsb.kext.logKext failed to load (0xdc008016).
(kernel) Failed to load kext com.fsb.kext.logKext (error 0xdc008016).
Failed to load /System/Library/Extensions/logKext.kext - (libkern/kext) link error.
Check library declarations for your kext with kextlibs(8).

[maxiedaniels]

Having this same issue, I've tried playing with the permissions over and over, no dice.

[dharmabm]

any solution to this yet?

[SlEePlEs5]

Hello to all of you, sorry to have gone for so long. It seems like it's both a compatibility issue on older systems, and a codesigning issue on newer ones. All I know is it worked for me, but I heartily encourage all of you to clone the source and try building it yourself. You may have to change some version settings, etc, but the code itself is definitely not the problem.

If anyone finds a solution, please let me know and / or fork the project and make a pull request!

[theforcedk]

This worked for me, after getting "Error: logKext Preferences cannot be found. Is logKextDaemon running?"

sudo chown root /Library/LaunchDaemons/logKext.plist sudo chmod 644 /Library/LaunchDaemons/logKext.plist

sudo launchctl load /Library/LaunchDaemons/logKext.plist

[Fiveohfour]

The above comment from "theforcedk" worked for me to fix that same error. Only issue is that i notice some passwords are not logged, like if i go into system preferences and lock a area then unlock it by entering my admin password, it is not logged. If i go into the app store and update software & it prompts for my password there, it logs that fine...so it seems capable of recognizing some "native" fields entries but not others, is there anything i can do to change that? is it a permissions or ownership issue or is that just a technical limitation? I thought i remembered it doing that without issue in OS X 10.6 but i realize much may have changed since then. Thanks

[Fiveohfour]

Actually, interesting observation, in the admin password field to unlock certain settings in system preferences, it logs an entry if you enter an incorrect password and hit submit & then it tells you its incorrect, but does NOT proceed to, or ever, log the correct password when entered.

[jonathanbright]

I was able to eliminate the error "Error: logKext Preferences cannot be found. Is logKextDaemon running?" by typing the following commands in terminal:

sudo chown root:wheel /Library/LaunchDaemons/logKext.plist
sudo chown root /Library/LaunchDaemons/logKext.plist
sudo chmod 644 /Library/LaunchDaemons/logKext.plist
sudo launchctl load /Library/LaunchDaemons/logKext.plist

[buttsteak]

hi, I'm really stupid with this stuff, but i did get it to work. i noticed that syamtec antivirus was doing things in monitor, so i disabled it and started the process over. i used the advice provide by theforcekd to get past the is logkext daemon running? i will attempt to cut and paste. if this is stupid sorry.
https://github.com/theforcedk

[buttsteak]

to clarify, i disabled antivirus. then uninstalled deleted even the pkg file and then redownloaded and reinstalled

[soragon]

Having a similar issue here too. First began with installation issues like @HibGut posted.

Then it was Is logKextDaemon running?, and that was solved by using @jonathanbright's suggestion:

sudo chown root:wheel /Library/LaunchDaemons/logKext.plist
sudo chown root /Library/LaunchDaemons/logKext.plist
sudo chmod 644 /Library/LaunchDaemons/logKext.plist
sudo launchctl load /Library/LaunchDaemons/logKext.plist

Now I get the error:

Error finding passKey in keychain (-25300). Failing

Which I guess has to do with the codesigning in Yosemite?

I tried compiling my own and using 10.7 (default) and 10.10 as deployment targets, but both had the same issues. Xcode does spit out a lot of 'deprecated' warnings but I don't think that's directly related to this problem.

Any suggestions?

[danhart]

It works fine for me on Yosemite with only:

sudo chown root:wheel /Library/LaunchDaemons/logKext.plist
sudo chown root /Library/LaunchDaemons/logKext.plist
sudo chmod 644 /Library/LaunchDaemons/logKext.plist
sudo launchctl load /Library/LaunchDaemons/logKext.plist

[omsaj]

has anyone managed to figure this out? i keep getting the same message "Is logKextDaemon running?" I'm using OS X mavericks I know nothing about programing "I only signed up for this site for logkext"

[louisabraham]

@SlEePlEs5 Your solution worked for me, but the installer is not fixed :(