Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 6 subscribers
  • Views 18664 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

    Hi,

    I just suddeny, this morning, got an alert saying that the Sophos On-Access scanner wasn't running. Went to Sophos Preferences and confirmed that was the case, but also found that trying to start it doesn't work for me either. AFAIK, it has been working - I certainly haven't seen that alert before. I have v9.0.11 and this Mac is still running Mac OS X 10.6.8 (only wishing I could find the three uninterrupted days that I know from experience I would need to do the full, clean install of 10.9 and all my apps!)

    Anyway, in the course of investigating, I also noticed that I have about 80 (eighty!) iterations of launchctl in the process table (running hierarchically under launchd/uc). I'm not sure if that's related to the problems with SAV?

    I'm guessing that a reboot well might fix the problem, so I'll try that after I've posted this. But I'm somewhat mystified as to why this has suddenly happened now. I'm quite sure that SAV has been at version 9.0.11 since sometime back in 2013 - and the dates on the app don't contradict that belief, although Finder does report the app as version 9.0.1 for some reason, whilst the app's About pane confirms 9.0.11 - why???

    :1018607
Reply
  • 0

    Hi,

    I just suddeny, this morning, got an alert saying that the Sophos On-Access scanner wasn't running. Went to Sophos Preferences and confirmed that was the case, but also found that trying to start it doesn't work for me either. AFAIK, it has been working - I certainly haven't seen that alert before. I have v9.0.11 and this Mac is still running Mac OS X 10.6.8 (only wishing I could find the three uninterrupted days that I know from experience I would need to do the full, clean install of 10.9 and all my apps!)

    Anyway, in the course of investigating, I also noticed that I have about 80 (eighty!) iterations of launchctl in the process table (running hierarchically under launchd/uc). I'm not sure if that's related to the problems with SAV?

    I'm guessing that a reboot well might fix the problem, so I'll try that after I've posted this. But I'm somewhat mystified as to why this has suddenly happened now. I'm quite sure that SAV has been at version 9.0.11 since sometime back in 2013 - and the dates on the app don't contradict that belief, although Finder does report the app as version 9.0.1 for some reason, whilst the app's About pane confirms 9.0.11 - why???

    :1018607
Children
No Data
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?