Guest User!

You are not Sophos Staff.

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

Sophos stops working when my mac starts up

mikeroy22

Hope someone can point me in the right direction.

I'm using a mac (10.6.8) and have the latest sophos 8.04C - every time I close down my mac and restart it the next morning Sophos stops working and wont allow me to change anything at all via preferences. If I just put my mac to sleep there's no problem at all when it wakes up and sophos continues to work.

If I download the sophos software again everything works smoothly until the next time I shut down my mac ..........!

Maybe I'm missing something - perhaps I've got one of the settings wrong, perhaps my OS wont work with the latest sophos - I just don't know!

Anyone got any ideas?

Thanks in advance

:1007673


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

    I had this happen for the first time today (on-access scanner turns off and greys out in the menu).   Since rebooting doesn't seem to help anyone, I did not bother.  Instead, I went to the Console, where I found this message:

    8/30/13 1:47:12.774 PM com.apple.launchd.peruser.501[143]: (com.sophos.uiserver[53228]) Exited: Killed: 9
    8/30/13 1:47:17.540 PM com.apple.launchd[1]: (com.sophos.intercheck[44628]) Exit timeout elapsed (20 seconds). Killing

    A quick search in Terminal (using the locate command) for com.sophos.intercheck shows

    /Library/LaunchDaemons/com.sophos.intercheck.plist

    which contains /Library/Sophos Anti-Virus/InterCheck.app/Contents/MacOS/InterCheck so I logged in as root and launched InterCheck manually from the command line.  I probably should have used launchctl, but I just entered "/Library/Sophos Anti-Virus/InterCheck.app/Contents/MacOS/InterCheck" at the prompt.  InterCheck launched and did a few things for 7-10 seconds, but the shield when back to black and Sophos preferences now says On-access scan is enabled.  Might not be necessary to launch as root, but probably is.

    Sounds like InterCheck met an error it couldn't handle and couldn't recover to relaunch.  Could be a memory issue - OS X from 10.6 on leaks memory badly.  I hope the above information helps diagnose this and for users to get back working in the meantime.  

    The only oddity I am now experiencing is that the Sophos preferences pane shows a locked icon, and will not let me unlock it.  Manually scanning also only lets me scan as the current user, and does not ask me to authenticate to a user with higher privileges.

    10.8.4, 5G Ram, Unibody Macbook

    :1013110
Reply
  • 0

    I had this happen for the first time today (on-access scanner turns off and greys out in the menu).   Since rebooting doesn't seem to help anyone, I did not bother.  Instead, I went to the Console, where I found this message:

    8/30/13 1:47:12.774 PM com.apple.launchd.peruser.501[143]: (com.sophos.uiserver[53228]) Exited: Killed: 9
    8/30/13 1:47:17.540 PM com.apple.launchd[1]: (com.sophos.intercheck[44628]) Exit timeout elapsed (20 seconds). Killing

    A quick search in Terminal (using the locate command) for com.sophos.intercheck shows

    /Library/LaunchDaemons/com.sophos.intercheck.plist

    which contains /Library/Sophos Anti-Virus/InterCheck.app/Contents/MacOS/InterCheck so I logged in as root and launched InterCheck manually from the command line.  I probably should have used launchctl, but I just entered "/Library/Sophos Anti-Virus/InterCheck.app/Contents/MacOS/InterCheck" at the prompt.  InterCheck launched and did a few things for 7-10 seconds, but the shield when back to black and Sophos preferences now says On-access scan is enabled.  Might not be necessary to launch as root, but probably is.

    Sounds like InterCheck met an error it couldn't handle and couldn't recover to relaunch.  Could be a memory issue - OS X from 10.6 on leaks memory badly.  I hope the above information helps diagnose this and for users to get back working in the meantime.  

    The only oddity I am now experiencing is that the Sophos preferences pane shows a locked icon, and will not let me unlock it.  Manually scanning also only lets me scan as the current user, and does not ask me to authenticate to a user with higher privileges.

    10.8.4, 5G Ram, Unibody Macbook

    :1013110
Children
No Data