SophosAutoupdate continuously crashes in Sophos Anti-Virus for Mac version 9.0.7

  • Article ID: 120471
  • Rating:
  • 9 customers rated this article 3.6 out of 6
  • Updated: 25 Apr 2014

Issue

Customers find that their endpoints are out of date, and that SophosAutoupdate is continuously crashing.
The following crash can be found in the system.log:

Jan 15 18:03:27 MyMachine SophosAutoUpdate[344]: -[SAVCFReadStream streamStatus]: unrecognized selector sent to instance 0x79661e60
Jan 15 18:03:27 MyMachine SophosAutoUpdate[344]: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[SAVCFReadStream streamStatus]: unrecognized selector sent to instance 0x79661e60'
*** Call stack at first throw:
(
0 CoreFoundation 0x96904a67 __raiseError + 231
1 libobjc.A.dylib 0x9a9af189 objc_exception_throw + 155
2 CoreFoundation 0x96908070 -[NSObject doesNotRecognizeSelector:] + 256
3 CoreFoundation 0x96856cd9 ___forwarding___ + 457
4 CoreFoundation 0x96856aa2 _CF_forwarding_prep_0 + 50
5 CoreFoundation 0x9682069a CFReadStreamGetStatus + 106
6 SophosAutoUpdate 0x000884ea al_url_get + 2692
7 SophosAutoUpdate 0x00092caf al_update_sync + 2282
8 SophosAutoUpdate 0x0009204d al_update_perform + 909
9 SophosAutoUpdate 0x00094c26 al_worker_handler + 183
10 CoreFoundation 0x967c1d0a __CFMachPortPerform + 346
11 CoreFoundation 0x967c1b91
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 49
12 CoreFoundation 0x967c17bb __CFRunLoopDoSource1 + 155
13 CoreFoundation 0x967fae01 __CFRunLoopRun + 2193
14 CoreFoundation 0x967fa1dc CFRunLoopRunSpecific + 332
15 CoreFoundation 0x9680af01 CFRunLoopRun + 129
16 SophosAutoUpdate 0x00094ce0 al_worker_run + 165
17 libsystem_c.dylib 0x9cee4ed9 _pthread_start + 335
18 libsystem_c.dylib 0x9cee86de thread_start + 34
)

First seen in

Sophos Anti-Virus for Mac OS X version 9.0.7

Cause

This issue will occur when endpoints are updating from a customer hosted webCID, and the web server is authenticated, or the endpoint goes through an authenticated proxy to get to the web server.

What To Do

The issue has been fixed in the 9.0.8 release.

To workaround this issue and allow the upgrade to version 9.0.8 customers can:

  • change their Updating Policy to use a network location for updates
  • disable authentication on the web server
  • remove the need to go through an authenticated proxy

 
If you need more information or guidance, then please contact technical support.

Rate this article

Very poor Excellent

Comments