Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 6 subscribers
  • Views 18661 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

On Access Scanning suddenly disabled

brvx

Happened suddenly on the 10.6. This was in the log

com.sophos.intercheck: Info:    ic_worker_start: unable to load on access kext at 14:40 on 20 May 2014

 

Restarting didn't get it back. Ran launchctl -w load  both for the entire kext and then the executable alone, but that didn't work. Next tried running the executable from sudo and got

 

sudo: unable to execute /System/Library/Extensions/SophosOnAccessInterceptor.kext/Contents/MacOS/Sophos Anti-Virus: Bad executable (or shared library)

Finally, an uninstall and reinstall fixed it (fortunately, the uninstall didn't remove the preference .plist and/or cache, so I didn't have to redo all my prefs.) But would like to know what else I could have done without reinstalling, and what happened here? Seems the executable got corrupt? Out of the blue.

:1017341


This thread was automatically locked due to age.
Parents
  • 0

    Postscript:

    I rebooted and that did indeed fix the problem, but I'd still prefer to know what caused it!

    Before I rebooted, I did notice one other thing that seemed very odd to me. Activity Monitor was showing total system activity at 55-60%, yet the process list only showed processes totalling around 25% CPU and they were mostly user processes. I have no idea how there could be system process CPU activity without it being shown which specific processes were active!

    By the time I rebooted, there were more than 200 launchctl processes listed (never using any cumulative CPU resource). Now, more than 24 hours after rebooting, there are no launchctl processes listed at all, nor have I seen any.

    :1018611
Reply
  • 0

    Postscript:

    I rebooted and that did indeed fix the problem, but I'd still prefer to know what caused it!

    Before I rebooted, I did notice one other thing that seemed very odd to me. Activity Monitor was showing total system activity at 55-60%, yet the process list only showed processes totalling around 25% CPU and they were mostly user processes. I have no idea how there could be system process CPU activity without it being shown which specific processes were active!

    By the time I rebooted, there were more than 200 launchctl processes listed (never using any cumulative CPU resource). Now, more than 24 hours after rebooting, there are no launchctl processes listed at all, nor have I seen any.

    :1018611
Children
No Data
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?