Guest User!

You are not Sophos Staff.

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

Message says "Sophos Anti-Virus is not running"

alansky

I've suddenly started getting a "Sophos Anti-Virus is not running" message after restarting my Mac. Running OS X 10.7.4. When I check Activity Monitor, SophosUIServer and SophosAutoUpdate appear to be running normally. The application itself does not run in the background and never has. Why am I getting this message?

Thanks!

:1007481


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

    bobcook: reboots did not do any good previously. That's always the first troubleshooting step, per Dogbert.

    I looked for the corrupt file listed in the log and it did not exist in the cache folder. Since deleting cache and or plist files is another standard troubleshooting step, I just went ahead and trashed all the Sophos cache files.

    Interestingly, in Console when I filtered for the word "corrupt", first I got about half a dozen listings (all of them indicating they were in the same cache folder). When I went back later without closing Console in the meantime, I only got one entry. The log file had not rolled over. 

    OK, today they're back in Console. I *know* they were not there yesterday. I guess I'll have to chalk up that particular observation to Operator Insanity. In any case, here are those lines from the log, spanning about three days:

    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1024
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1168
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1181
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1201
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1260
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1292
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1059
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1068
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1212
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1245
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1304

    My cache folders, of course, have reconstituted themselves by now, but none of these files exist in there. And my Sophos and its auto-updating have been working fine for about 20 hours so far, knock on wood.

    To recap my problem as best I can remember it: first the Update Now in the shield menu was grayed out; when I then opened Preferences to try to change the update schedule (my way of poking it with a sharp stick) I got a message that the change couldn't be made, making me think it might be a permissions problem; after this the shield icon in the menu bar got an X in it. I tried uninstalling and reinstalling Sophos which did not help, indicating a cache or plist problem in my mind. That's when I looked in the log.

    Hope this helps.

    :1011992
Reply
  • 0

    bobcook: reboots did not do any good previously. That's always the first troubleshooting step, per Dogbert.

    I looked for the corrupt file listed in the log and it did not exist in the cache folder. Since deleting cache and or plist files is another standard troubleshooting step, I just went ahead and trashed all the Sophos cache files.

    Interestingly, in Console when I filtered for the word "corrupt", first I got about half a dozen listings (all of them indicating they were in the same cache folder). When I went back later without closing Console in the meantime, I only got one entry. The log file had not rolled over. 

    OK, today they're back in Console. I *know* they were not there yesterday. I guess I'll have to chalk up that particular observation to Operator Insanity. In any case, here are those lines from the log, spanning about three days:

    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1024
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1168
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1181
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1201
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1260
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1292
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1059
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1068
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1212
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1245
    com.sophos.intercheck: Corrupt file: /Library/Caches/com.sophos.sau/warehouse/1304

    My cache folders, of course, have reconstituted themselves by now, but none of these files exist in there. And my Sophos and its auto-updating have been working fine for about 20 hours so far, knock on wood.

    To recap my problem as best I can remember it: first the Update Now in the shield menu was grayed out; when I then opened Preferences to try to change the update schedule (my way of poking it with a sharp stick) I got a message that the change couldn't be made, making me think it might be a permissions problem; after this the shield icon in the menu bar got an X in it. I tried uninstalling and reinstalling Sophos which did not help, indicating a cache or plist problem in my mind. That's when I looked in the log.

    Hope this helps.

    :1011992
Children
No Data