Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 13 replies
  • Subscribers 6 subscribers
  • Views 3983 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 A/V Home Edition update on July 17th cause OS X Lion to hang

trudheim

Hi there,

Sophos did a self-update today, and it took my primary system (MacBook Pro, OS X Lion fully updated) out completely. It grinds the system to a total halt, spinning multicolour disk, nothing works. Hard power off, have been in through the recovery partition, done a repair disk and repair permissions, upon next boot - as soon as Sophos starts, it takes at most ten seconds and then the system is totally hung again. No app works, can not log in remotely, nada.

How on earth do I recover from this without a clean install?

/Anders

:1008211


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

    Hi there Bob,

    Well, I do use Little Snitch, but no pop-up came up about Sophos requesting access to any port it wasn't already allowed to talk to. DNS, well I run my own on the LAN (dnsmasq on RHEL), and it was working for all other queries (like for the old Mac Mini I'm typing this on), so I don't think that was it. dnsmasq is set up to forward DNS requests and then cache them, so it is a very simple setup.

    I have a squid proxy in use, that then forwards through Privoxy (cutting out all the advertising), so I can probably enable debug in both of those to see what Sophos is requesting and if it is getting blocked. I would not expect Sophos to block access to the whole system though if the Live Protection can't reach the home server for whatever reason. I'd expect it to tell me that there is a network issue and maybe something about what network issue that is. :)

    There are no other firewalls blocking anything, but the system is masqueraded out on to the ADSL line by the DSL router. There was no DSL service interruptions at the time, so we can rule that out.

    I'll try and enable Live Protection again, just to see what it actually is doing and if today works better than yesterday. I'll let you know how it goes, but the MacBook have been working fine since I managed to turn Live Protection off yesterday. It's an odd one this..

    /Anders

    :1008243
Reply
  • 0

    Hi there Bob,

    Well, I do use Little Snitch, but no pop-up came up about Sophos requesting access to any port it wasn't already allowed to talk to. DNS, well I run my own on the LAN (dnsmasq on RHEL), and it was working for all other queries (like for the old Mac Mini I'm typing this on), so I don't think that was it. dnsmasq is set up to forward DNS requests and then cache them, so it is a very simple setup.

    I have a squid proxy in use, that then forwards through Privoxy (cutting out all the advertising), so I can probably enable debug in both of those to see what Sophos is requesting and if it is getting blocked. I would not expect Sophos to block access to the whole system though if the Live Protection can't reach the home server for whatever reason. I'd expect it to tell me that there is a network issue and maybe something about what network issue that is. :)

    There are no other firewalls blocking anything, but the system is masqueraded out on to the ADSL line by the DSL router. There was no DSL service interruptions at the time, so we can rule that out.

    I'll try and enable Live Protection again, just to see what it actually is doing and if today works better than yesterday. I'll let you know how it goes, but the MacBook have been working fine since I managed to turn Live Protection off yesterday. It's an odd one this..

    /Anders

    :1008243
Children
No Data