ShortRound3
Level 1 (0 points)

Q: Why are time capsule back-ups so slow?

My Time Machine  backups on a Mac Book Pro with a new Time Capsule seem to be very slow even when there have been very few changes to documents.

Posted on Mar 24, 2014 6:25 PM

by Linc Davis,Solvedanswer
Linc Davis Linc Davis
Level 10 (208,037 points)
Applications
A:

Remove the worthless Norton/Symantec product by following the instructions on either of these pages:

Uninstalling your Norton product for Mac

Removing Symantec programs for Macintosh

If you have a different version of the product, the procedure may be different. Back up all data before making any changes.

Posted on Mar 25, 2014 8:57 AM

Close
ShortRound3

Q: Why are time capsule back-ups so slow?

  • All replies
  • Helpful answers

  • by Linc Davis,

    Linc Davis Linc Davis Mar 24, 2014 7:01 PM in response to ShortRound3
    Level 10 (208,037 points)
    Applications
    Mar 24, 2014 7:01 PM in response to ShortRound3

    If you have more than one user account, these instructions must be carried out as an administrator.

    Launch the Console application in any of the following ways:

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.

    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select

    View â–¹ Show Log List

    from the menu bar.

     

    Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message that corresponds to an abnormal backup. Now

    CLEAR THE WORD "Starting" FROM THE TEXT FIELD

    so that all messages are showing, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them to the Clipboard by pressing the key combination command-C. Paste (command-V) into a reply to this message.

    If all you see are messages that contain the word "Starting," you didn't clear the text field.

    If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.

    When posting a log extract, be selective. Don't post more than is requested.

    Please do not indiscriminately dump thousands of lines from the log into this discussion.

     

    Some personal information, such as the names of your files, may be included — anonymize before posting.

  • by ShortRound3,

    ShortRound3 ShortRound3 Mar 25, 2014 7:16 AM in response to Linc Davis
    Level 1 (0 points)
    Mar 25, 2014 7:16 AM in response to Linc Davis

    Thanks for your response to my inquiry.  I have followed your instructions.  I have deleted at least three pages of Console lines from this response.  I have attempted to delete all those that were identical but left many similar but not identical.  As it remains lengthy I hope I have not breached protocol too badly.  There are some ominous messages related to Safari in the Console message. 

     

    3/25/14 9:02:02.520 AM com.apple.backupd[17484]: Starting automatic backup

    3/25/14 9:02:47.000 AM kernel[0]: nspace-handler-set-snapshot-time: 1395752569

    3/25/14 9:02:47.928 AM com.apple.mtmd[40]: Set snapshot time: 2014-03-25 09:02:49 -0400 (current time: 2014-03-25 09:02:47 -0400)

    3/25/14 9:03:03.104 AM com.apple.backupd[17484]: Attempting to mount network destination URL: afp://J%20V*****;AUTH=SRP@J**s-AirPort-Time-Capsule.local/Data

    3/25/14 9:03:08.679 AM NetAuthSysAgent[17499]: TUAMHandler::SetUAMType setting UAMType to 13

    3/25/14 9:03:08.000 AM kernel[0]: inet6_cksum: out of data by -60

    3/25/14 9:03:23.315 AM mds[41]: (Normal) Volume: volume:0x7fde392a9000 ********** Bootstrapped Creating a default store:0 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/Data

    3/25/14 9:03:23.566 AM com.apple.backupd[17484]: Mounted network destination at mount point: /Volumes/Data using URL: afp://J%20Vaughn;AUTH=SRP@Jays-AirPort-Time-Capsule.local/Data

    3/25/14 9:04:05.983 AM com.apple.kextd[12]: kext com.seagate.driver.PowSecDriverCore  501019000 is in exception list, allowing to load

    3/25/14 9:04:21.000 AM kernel[0]: hfs: mounted Time Machine Backups on device disk4s2

    3/25/14 9:04:22.441 AM com.apple.backupd[17484]: Disk image /Volumes/Data/J V*****’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups

    3/25/14 9:04:23.261 AM mds[41]: (Error) Volume: Root store set to FSOnly with matching create! (loaded:1)

    3/25/14 9:04:23.871 AM com.apple.backupd[17484]: Backing up to /dev/disk4s2: /Volumes/Time Machine Backups/Backups.backupdb

    3/25/14 9:05:39.627 AM WindowServer[88]: CoreAnimation: context hosting changed while locked!

    3/25/14 9:05:55.332 AM com.apple.backupd[17484]: Will copy (177.5 MB) from Macintosh HD

    3/25/14 9:05:55.335 AM com.apple.backupd[17484]: Found 765 files (177.5 MB) needing backup

    3/25/14 9:05:56.152 AM com.apple.backupd[17484]: 2.46 GB required (including padding), 1.83 TB available

    3/25/14 9:06:16.000 AM kernel[0]: hfs: mounted Recovery HD on device disk0s3

    3/25/14 9:06:17.017 AM mds[41]: (Normal) Volume: volume:0x7fde395ba000 ********** Bootstrapped Creating a default store:0 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/Recovery HD

    3/25/14 9:06:17.083 AM fseventsd[51]: Logging disabled completely for device:1: /Volumes/Recovery HD

    3/25/14 9:06:17.000 AM kernel[0]: hfs: unmount initiated on Recovery HD on device disk0s3

    3/25/14 9:06:24.632 AM storeagent[284]: CKSoftwareMap: Registering with Daemon

    3/25/14 9:06:44.081 AM parentalcontrolsd[17799]: StartObservingFSEvents [849:] -- *** StartObservingFSEvents started event stream

    3/25/14 9:07:01.000 AM kernel[0]: Sandbox: mdworker(17794) deny file-read-data /Applications/SplashID Safe.localized/.localized

    3/25/14 9:07:11.507 AM Safari[14331]: CGWindowContextCreate: failed to create window context delegate.

    3/25/14 9:07:11.569 AM Safari[14331]: CGContextSaveGState: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.

    3/25/14 9:07:12.228 AM Safari[14331]: CGContextResetCTM: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.

    3/25/14 9:07:12.233 AM Safari[14331]: CGContextResetClip: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.

    3/25/14 9:07:12.238 AM Safari[14331]: CGContextTranslateCTM: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.

    3/25/14 9:07:12.250 AM Safari[14331]: CGContextScaleCTM: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.

    3/25/14 9:07:12.254 AM Safari[14331]: CGContextSaveGState: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.

    3/25/14 9:07:12.257 AM Safari[14331]: clip: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.

    3/25/14 9:07:12.261 AM Safari[14331]: CGContextRestoreGState: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.

    3/25/14 9:07:12.265 AM Safari[14331]: CGContextTranslateCTM: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.

    3/25/14 9:07:12.269 AM Safari[14331]: CGContextTranslateCTM: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.

    3/25/14 9:07:12.272 AM Safari[14331]: CGContextRestoreGState: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.

    3/25/14 9:07:12.276 AM Safari[14331]: CGContextSynchronize: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.

    3/25/14 9:07:17.000 AM kernel[0]: com.apple.WebKit (map: 0xffffff8029b113c0) triggered DYLD shared region unnest for map: 0xffffff8029b113c0, region 0x7fff86a00000->0x7fff86c00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

    3/25/14 9:07:25.000 AM kernel[0]: Sandbox: com.apple.WebKit(17800) deny mach-lookup rapportd_s:501_415ba-b2cb-43c7-94d5_

    3/25/14 9:07:25.000 AM kernel[0]: Sandbox: com.apple.WebKit(17800) deny mach-lookup rapportd_s:501_415ba-b2cb-43c7-94d5__caf28f87-ff19ba51-d0423ec0-58469dc0_

    3/25/14 9:07:25.000 AM kernel[0]: Sandbox: com.apple.WebKit(17800) deny mach-per-user-lookup

    3/25/14 9:10:52.147 AM hp_psc_1300_series[17815]: The function `CGContextErase' is obsolete and will be removed in an upcoming update. Unfortunately, this application, or a library it uses, is using this obsolete function, and is thereby contributing to an overall degradation of system performance.

    3/25/14 9:11:27.634 AM Symantec Daemon[17435]: An error has been encountered processing an event (getParameterValueAsInteger< u_int32_t >( kSymEventClassParameterID, theClass ))

    3/25/14 9:12:55.469 AM WindowServer[88]: disable_update_timeout: UI updates were forcibly disabled by application "System Preferences" for over 1.00 seconds. Server has re-enabled them.

    3/25/14 9:12:57.502 AM com.apple.prefs.backup.remoteservice[17827]: assertion failed: 13C64: liblaunch.dylib + 25164 [38D1AB2C-A476-385F-8EA8-7AB604CA1F89]: 0x25

    3/25/14 9:12:59.071 AM com.apple.prefs.backup.remoteservice[17827]: Bogus event received by listener connection:

    <error: 0x7fff7301fb50> { count = 1, contents =

                      "XPCErrorDescription" => <string: 0x7fff7301fe60> { length = 18, contents = "Connection invalid" }

    3/25/14 9:13:00.570 AM WindowServer[88]: common_reenable_update: UI updates were finally reenabled by application "System Preferences" after 6.10 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/25/14 9:13:18.558 AM com.apple.prefs.backup.remoteservice[17827]: Could not connect the action warnCullingPressed: to target of class TMOptionsSheetController

    3/25/14 9:13:18.559 AM com.apple.prefs.backup.remoteservice[17827]: Could not connect the action backUpOnBatteryPowerPressed: to target of class TMOptionsSheetController

    3/25/14 9:13:19.480 AM WindowServer[88]: window 1580 is already attached to window 157e

    3/25/14 9:13:35.299 AM WindowServer[88]: _CGXGetWindowOrderingGroup: Operation on a window 0x1580 requiring rights 0x5 by caller System Preferences

    3/25/14 9:13:57.886 AM System Preferences[17819]: view service marshal for <NSRemoteView: 0x7f9e28d6a570> failed to forget accessibility connection due to Error Domain=NSCocoaErrorDomain Code=4099 "Couldn’t communicate with a helper application." (The connection was invalidated from this process.) UserInfo=0x60000046b8c0 {NSDebugDescription=The connection was invalidated from this process.}

    timestamp: 09:13:57.885 Tuesday 25 March 2014

    process/thread/queue: System Preferences (17819) / 0x113d08000 / com.apple.NSXPCConnection.user.endpoint

    code: line 2972 of /SourceCache/ViewBridge/ViewBridge-46.2/NSRemoteView.m in __57-[NSRemoteView viewServiceMarshalProxy:withErrorHandler:]_block_invoke

    domain: communications-failure

    3/25/14 9:14:09.577 AM WindowServer[88]: window 1583 is already attached to window 157e

    3/25/14 9:14:47.122 AM WindowServer[88]: _CGXGetWindowOrderingGroup: Operation on a window 0x1583 requiring rights 0x5 by caller System Preferences

    3/25/14 9:15:26.354 AM Console[17835]: setPresentationOptions called with NSApplicationPresentationFullScreen when there is no visible fullscreen window; this call will be ignored.

    3/25/14 9:15:29.070 AM WindowServer[88]: disable_update_timeout: UI updates were forcibly disabled by application "Console" for over 1.00 seconds. Server has re-enabled them.

    3/25/14 9:15:30.143 AM WindowServer[88]: common_reenable_update: UI updates were finally reenabled by application "Console" after 2.07 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/25/14 9:20:46.957 AM WindowServer[88]: disable_update_timeout: UI updates were forcibly disabled by application "System Preferences" for over 1.00 seconds. Server has re-enabled them.

    3/25/14 9:20:47.784 AM com.apple.prefs.backup.remoteservice[17851]: assertion failed: 13C64: liblaunch.dylib + 25164 [38D1AB2C-A476-385F-8EA8-7AB604CA1F89]: 0x25

    3/25/14 9:20:48.673 AM com.apple.prefs.backup.remoteservice[17851]: Bogus event received by listener connection:

    <error: 0x7fff7301fb50> { count = 1, contents =

                      "XPCErrorDescription" => <string: 0x7fff7301fe60> { length = 18, contents = "Connection invalid" }

    3/25/14 9:20:49.543 AM WindowServer[88]: common_reenable_update: UI updates were finally reenabled by application "System Preferences" after 3.59 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/25/14 9:24:13.037 AM xpcproxy[17863]: assertion failed: 13C64: xpcproxy + 3438 [D559FC96-E6B1-363A-B850-C7AC9734F210]: 0x2

    3/25/14 9:25:34.101 AM com.apple.backupd[17484]: Copied 826 items (177.1 MB) from volume Macintosh HD. Linked 4915.

    3/25/14 9:26:52.125 AM secd[189]: SecErrorGetOSStatus unknown error domain: com.apple.security.sos.error for error: The operation couldn’t be completed. (com.apple.security.sos.error error 2 - Public Key not available - failed to register before call)

    3/25/14 9:26:52.125 AM secd[189]: securityd_xpc_dictionary_handler EscrowSecurityAl[1805] DeviceInCircle The operation couldn’t be completed. (com.apple.security.sos.error error 2 - Public Key not available - failed to register before call)

    3/25/14 9:29:30.774 AM com.apple.backupd[17484]: Will copy (12.8 MB) from Macintosh HD

    3/25/14 9:29:30.776 AM com.apple.backupd[17484]: Found 182 files (12.8 MB) needing backup

    3/25/14 9:29:30.777 AM com.apple.backupd[17484]: 2.26 GB required (including padding), 1.83 TB available

    3/25/14 9:30:19.000 AM kernel[0]: Sandbox: mdworker(17873) deny file-read-data /Applications/SplashID Safe.localized/.localized

    3/25/14 9:31:30.980 AM com.apple.prefs.backup.remoteservice[17887]: assertion failed: 13C64: liblaunch.dylib + 25164 [38D1AB2C-A476-385F-8EA8-7AB604CA1F89]: 0x25

    3/25/14 9:31:31.057 AM com.apple.prefs.backup.remoteservice[17887]: assertion failed: 13C64: liblaunch.dylib + 25164 [38D1AB2C-A476-385F-8EA8-7AB604CA1F89]: 0x25

    3/25/14 9:31:31.474 AM WindowServer[88]: disable_update_timeout: UI updates were forcibly disabled by application "System Preferences" for over 1.00 seconds. Server has re-enabled them.

    3/25/14 9:31:31.822 AM com.apple.prefs.backup.remoteservice[17887]: Bogus event received by listener connection:

    <error: 0x7fff7301fb50> { count = 1, contents =

                      "XPCErrorDescription" => <string: 0x7fff7301fe60> { length = 18, contents = "Connection invalid" }

    3/25/14 9:31:32.258 AM WindowServer[88]: common_reenable_update: UI updates were finally reenabled by application "System Preferences" after 1.78 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/25/14 9:31:50.091 AM system_profiler[17897]: FIXME: IOUnserialize has detected a string that is not valid UTF-8, "P                   �".

    3/25/14 9:32:21.901 AM WindowServer[88]: disable_update_timeout: UI updates were forcibly disabled by application "Finder" for over 1.00 seconds. Server has re-enabled them.

    3/25/14 9:32:24.289 AM Finder[219]: FIXME: IOUnserialize has detected a string that is not valid UTF-8, "P                   �".

    3/25/14 9:32:24.579 AM WindowServer[88]: Display 0x2b105dcd captured by conn 0xd003

    3/25/14 9:32:32.559 AM Finder[219]: FIXME: IOUnserialize has detected a string that is not valid UTF-8, "P                   �".

    3/25/14 9:32:35.354 AM WindowServer[88]: common_reenable_update: UI updates were finally reenabled by application "Finder" after 14.45 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/25/14 9:32:36.584 AM WindowServer[88]: Display 0x2b105dcd released by conn 0xd003

    3/25/14 9:32:44.654 AM WindowServer[88]: disable_update_timeout: UI updates were forcibly disabled by application "System Preferences" for over 1.00 seconds. Server has re-enabled them.

    3/25/14 9:32:45.008 AM com.apple.prefs.backup.remoteservice[17917]: assertion failed: 13C64: liblaunch.dylib + 25164 [38D1AB2C-A476-385F-8EA8-7AB604CA1F89]: 0x25

    3/25/14 9:32:45.376 AM com.apple.prefs.backup.remoteservice[17917]: Bogus event received by listener connection:

    <error: 0x7fff7301fb50> { count = 1, contents =

                      "XPCErrorDescription" => <string: 0x7fff7301fe60> { length = 18, contents = "Connection invalid" }

    3/25/14 9:32:45.754 AM WindowServer[88]: common_reenable_update: UI updates were finally reenabled by application "System Preferences" after 2.10 seconds (server forcibly re-enabled them after 1.00 seconds)

    3/25/14 9:33:21.000 AM kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=17920[GoogleSoftwareUp] final status 0x0, allowing (remove VALID) page

    3/25/14 9:33:22.462 AM GoogleSoftwareUpdateDaemon[17921]: -[KeystoneDaemon logServiceState] GoogleSoftwareUpdate daemon (1.1.0.3659) vending:

                      com.google.Keystone.Daemon.UpdateEngine: 1 connection(s)

                      com.google.Keystone.Daemon.Administration: 0 connection(s)

    3/25/14 9:33:22.589 AM GoogleSoftwareUpdateDaemon[17921]: -[KSUpdateCheckAction performAction] KSUpdateCheckAction starting update check for ticket(s): {(

                      <KSTicket:0x373ee0

                                        productID=com.google.Keystone

                                        version=1.1.0.3659

                                        xc=<KSPathExistenceChecker:0x374710 path=/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/>

                                        serverType=Omaha

                                        url=https://tools.google.com/service/update2

                                        creationDate=2011-06-06 12:13:16

                      Using server: <KSOmahaServer:0x378010

                      engine=<KSDaemonUpdateEngine:0x36ada0>

                      params={

                                        EngineVersion = "1.1.0.3659";

                                        ActivesInfo = {

                                                          "com.google.Keystone" = {

                                                                            LastActiveDate = 2014-03-25 13:33:22 +0000;

                                                                            LastActivePingDate = 2014-03-24 07:00:01 +0000;

                                                                            LastRollCallPingDate = 2014-03-24 07:00:01 +0000;

                                                          };

                                                          "com.google.talkplugin" = {

                                                                            LastActivePingDate = 2011-09-05 07:00:00 +0000;

                                                                            LastActiveDate = 2011-09-04 18:14:06 +0000;

                                                                            LastRollCallPingDate = 2014-03-24 07:00:00 +0000;

                                                          };

                                        };

                                        UserInitiated = 0;

                                        IsSystem = 1;

                                        OmahaOSVersion = "10.9.2_i486";

                                        Identity = KeystoneDaemon;

                                        AllowedSubdomains = (

                                                          ".omaha.sandbox.google.com",

                                                          ".tools.google.com",

                                                          ".www.google.com",

                                                          ".corp.google.com"}

    3/25/14 9:33:25.897 AM GoogleSoftwareUpdateDaemon[17921]: -[KSCheckAction performAction] KSCheckAction checking 2 ticket(s).

    3/25/14 9:33:25.904 AM GoogleSoftwareUpdateDaemon[17921]: -[KSUpdateCheckAction performAction] KSUpdateCheckAction starting update check for ticket(s): {(

                      <KSTicket:0x2648a0

                                        productID=com.google.Keystone

                                        version=1.1.0.3659

                                        xc=<KSPathExistenceChecker:0x271360 path=/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/>

                                        serverType=Omaha

                                        url=https://tools.google.com/service/update2

                                        creationDate=2011-06-06 12:13:16

                      <KSTicket:0x26ecf0

                                        productID=com.google.talkplugin

                                        version=5.2.4.18058

                                        xc=<KSPathExistenceChecker:0x265d00 path=/Library/Application Support/Google/GoogleTalkPlugin.app>

                                        serverType=Omaha

                                        url=https://tools.google.com/service/update2

                                        creationDate=2011-06-06 12:13:16

    Using server: <KSOmahaServer:0x26e020

                      engine=<KSDaemonUpdateEngine:0x36ada0>

                      params={

                                        EngineVersion = "1.1.0.3659";

                                        ActivesInfo = {

                                                          "com.google.Keystone" = {

                                                                            LastActiveDate = 2014-03-25 13:33:22 +0000;

                                                                            LastActivePingDate = 2014-03-25 07:00:01 +0000;

                                                                            LastRollCallPingDate = 2014-03-25 07:00:01 +0000;

                                                          };

                                                          "com.google.talkplugin" = {

                                                                            LastActivePingDate = 2011-09-05 07:00:00 +0000;

                                                                            LastActiveDate = 2011-09-04 18:14:06 +0000;

                                                                            LastRollCallPingDate = 2014-03-24 07:00:00 +0000;

                                        UserInitiated = 0;

                                        IsSystem = 1;

                                        OmahaOSVersion = "10.9.2_i486";

                                        Identity = KeystoneDaemon;

                                        AllowedSubdomains = (

                                                          ".omaha.sandbox.google.com",

                                                          ".tools.google.com",

                                                          ".www.google.com",

                                                          ".corp.google.com"

    3/25/14 9:33:52.488 AM GoogleSoftwareUpdateDaemon[17921]: -[KeystoneDaemon main] GoogleSoftwareUpdateDaemon inactive, shutdown.

    3/25/14 9:35:19.082 AM com.apple.prefs.backup.remoteservice[17940]: assertion failed: 13C64: liblaunch.dylib + 25164 [38D1AB2C-A476-385F-8EA8-7AB604CA1F89]: 0x25

    3/25/14 9:35:19.411 AM com.apple.prefs.backup.remoteservice[17940]: Bogus event received by listener connection:

    <error: 0x7fff7301fb50> { count = 1, contents =

                      "XPCErrorDescription" => <string: 0x7fff7301fe60> { length = 18, contents = "Connection invalid" }

    3/25/14 9:36:04.844 AM com.apple.backupd[17484]: Copied 247 items (12.8 MB) from volume Macintosh HD. Linked 2751.

    3/25/14 9:36:27.374 AM com.apple.backupd[17484]: Created new backup: 2014-03-25-093609

    3/25/14 9:38:32.839 AM com.apple.prefs.backup.remoteservice[17949]: assertion failed: 13C64: liblaunch.dylib + 25164 [38D1AB2C-A476-385F-8EA8-7AB604CA1F89]: 0x25

    3/25/14 9:38:33.142 AM com.apple.prefs.backup.remoteservice[17949]: Bogus event received by listener connection:

    <error: 0x7fff7301fb50> { count = 1, contents =

                      "XPCErrorDescription" => <string: 0x7fff7301fe60> { length = 18, contents = "Connection invalid" }

    3/25/14 9:38:38.105 AM System Preferences[17944]: view service marshal for <NSRemoteView: 0x7f869bc60f40> failed to forget accessibility connection due to Error Domain=NSCocoaErrorDomain Code=4099 "Couldn’t communicate with a helper application." (The connection was invalidated from this process.) UserInfo=0x60000047b340 {NSDebugDescription=The connection was invalidated from this process.}

    timestamp: 09:38:38.104 Tuesday 25 March 2014

    process/thread/queue: System Preferences (17944) / 0x108a0f000 / com.apple.NSXPCConnection.user.endpoint

    code: line 2972 of /SourceCache/ViewBridge/ViewBridge-46.2/NSRemoteView.m in __57-[NSRemoteView viewServiceMarshalProxy:withErrorHandler:]_block_invoke

    domain: communications-failure

    3/25/14 9:38:38.187 AM com.apple.prefs.backup.remoteservice[17949]: <NSViewServiceMarshal: 0x7fc0b852b880> failed to complete rights grant DCA2E63C-35C8-4270-B5D1-A073D43B9FD4 due to 3

    timestamp: 09:38:38.186 Tuesday 25 March 2014

    process/thread/queue: com.apple.prefs.backup.remoteservice (17949) / 0x7fff739f1310 / com.apple.main-thread

    code: line 697 of /SourceCache/ViewBridge/ViewBridge-46.2/NSViewServiceMarshal.m in -[NSViewServiceMarshal invalidateWindowRights]

    domain: exceptions

    3/25/14 9:38:55.742 AM com.apple.backupd[17484]: Starting post-backup thinning

    3/25/14 9:38:55.742 AM com.apple.backupd[17484]: No post-backup thinning needed: no expired backups exist

    3/25/14 9:38:56.835 AM com.apple.backupd[17484]: Backup completed successfully.

  • by Linc Davis,Solvedanswer

    Linc Davis Linc Davis Mar 25, 2014 8:57 AM in response to ShortRound3
    Level 10 (208,037 points)
    Applications
    Mar 25, 2014 8:57 AM in response to ShortRound3

    Remove the worthless Norton/Symantec product by following the instructions on either of these pages:

    Uninstalling your Norton product for Mac

    Removing Symantec programs for Macintosh

    If you have a different version of the product, the procedure may be different. Back up all data before making any changes.

  • by ShortRound3,

    ShortRound3 ShortRound3 Mar 26, 2014 7:29 PM in response to ShortRound3
    Level 1 (0 points)
    Mar 26, 2014 7:29 PM in response to ShortRound3

    This worked. Thanks for your help.  Of course I now wonder if I am now practicing a computer version of "unsafe sex."

  • by Linc Davis,Helpful

    Linc Davis Linc Davis Mar 26, 2014 8:08 PM in response to ShortRound3
    Level 10 (208,037 points)
    Applications
    Mar 26, 2014 8:08 PM in response to ShortRound3
    1. This is a comment on what you should and should not do to protect yourself from malicious software ("malware") that circulates on the Internet. It does not apply to software, such as keystroke loggers, that may be installed deliberately by an intruder who has hands-on access to your computer, or who has been able to log in to it remotely. That threat is in a different category, and there's no easy way to defend against it. If you have reason to suspect that you're the target of such an attack, you need expert help.
      
    If you find this comment too long or too technical, read only sections 5, 6, and 10.
      
    OS X now implements three layers of built-in protection specifically against malware, not counting runtime protections such as execute disable, sandboxing, system library randomization, and address space layout randomization that may also guard against other kinds of exploits.

    2. All versions of OS X since 10.6.7 have been able to detect known Mac malware in downloaded files, and to block insecure web plugins. This feature is transparent to the user. Internally Apple calls it "XProtect."
    The malware recognition database used by XProtect is automatically updated; however, you shouldn't rely on it, because the attackers are always at least a day ahead of the defenders.
       
    The following caveats apply to XProtect:
    • It can be bypassed by some third-party networking software, such as BitTorrent clients and Java applets.
    • It only applies to software downloaded from the network. Software installed from a CD or other media is not checked.
    As new versions of OS X are released, it's not clear whether Apple will indefinitely continue to maintain the XProtect database of older versions such as 10.6. The security of obsolete system versions may eventually be degraded. Security updates to the code of obsolete systems will stop being released at some point, and that may leave them open to other kinds of attack besides malware.
      
    3. Starting with OS X 10.7.5, there has been a second layer of built-in malware protection, designated "Gatekeeper" by Apple. By default, applications and Installer packages downloaded from the network will only run if they're digitally signed by a developer with a certificate issued by Apple. Software certified in this way hasn't necessarily been tested by Apple, but you can be reasonably sure that it hasn't been modified by anyone other than the developer. His identity is known to Apple, so he could be held legally responsible if he distributed malware. That may not mean much if the developer lives in a country with a weak legal system (see below.)
       
    Gatekeeper doesn't depend on a database of known malware. It has, however, the same limitations as XProtect, and in addition the following:
    • It can easily be disabled or overridden by the user.
    • A malware attacker could get control of a code-signing certificate under false pretenses, or could simply ignore the consequences of distributing codesigned malware.
    • An App Store developer could find a way to bypass Apple's oversight, or the oversight could fail due to human error.
    Apple has so far failed to revoke the codesigning certificates of some known abusers, thereby diluting the value of Gatekeeper and the Developer ID program. These failures don't involve App Store products, however.
      
    For the reasons given, App Store products, and — to a lesser extent — other applications recognized by Gatekeeper as signed, are safer than others, but they can't be considered absolutely safe. "Sandboxed" applications may prompt for access to private data, such as your contacts, or for access to the network. Think before granting that access. Sandbox security is based on user input. Never click through any request for authorization without thinking.
           
    4. Starting with OS X 10.8.3, a third layer of protection has been added: a "Malware Removal Tool" (MRT). MRT runs automatically in the background when you update the OS. It checks for, and removes, malware that may have evaded the other protections via a Java exploit (see below.) MRT also runs when you install or update the Apple-supplied Java runtime (but not the Oracle runtime.) Like XProtect, MRT is effective against known threats, but not against unknown ones. It notifies you if it finds malware, but otherwise there's no user interface to MRT.
     
    5. The built-in security features of OS X reduce the risk of malware attack, but they are not, and never will be, complete protection. The best defense is always going to be your own intelligence. With the possible exception of Java exploits, all known malware circulating on the Internet that affects a fully-updated installation of OS X 10.6 or later takes the form of so-called "Trojan horses," which can only have an effect if the victim is duped into running them. The threat therefore amounts to a battle of wits between you and the scam artists. If you're smarter than they think you are, you'll win. That means, in practice, that you always stay within a safe harbor of computing practices. How do you know when you're leaving the safe harbor? Below are some warning signs of danger.
      
    Software from an untrustworthy source
    • Software of any kind is distributed via BitTorrent. or Usenet, or on a website that also distributes pirated music or movies.
    • Software with a corporate brand, such as Adobe Flash Player, doesn't come directly from the developer’s website.
    • Rogue websites such as Softonic and CNET Download distribute free applications that have been packaged in a superfluous "installer."
    • The software is advertised by means of spam or intrusive web ads.
    Software that is plainly illegal or does something illegal
    • High-priced commercial software such as Photoshop is "cracked" or "free."
    • An application helps you to infringe copyright, for instance by circumventing the copy protection on commercial software, or saving streamed media for reuse without permission.
    Conditional or unsolicited offers from strangers
    • A telephone caller or a web page tells you that you have a “virus” and offers to help you remove it. (Some reputable websites did legitimately warn visitors who were infected with the "DNSChanger" malware. That exception to this rule no longer applies.)
    • A web site offers free content such as video or music, but to use it you must install a “codec,” “plug-in,” "player," "downloader," "extractor," or “certificate” that comes from that same site, or an unknown one.
    • You win a prize in a contest you never entered.
    • Someone on a message board such as this one is eager to help you, but only if you download an application of his choosing.
    • A "FREE WI-FI !!!" network advertises itself in a public place such as an airport, but is not provided by the management.
    • Anything online that you would expect to pay for is "free."
    Unexpected events
    • You open what you think is a document and get an alert that it's "an application downloaded from the Internet." Click Cancel and delete the file. Even if you don't get the alert, you should still delete any file that isn't what you expected it to be.
    • An application does something you don't expect, such as asking for permission to access your contacts, your location, or the Internet for no obvious reason.
    • Software is attached to email that you didn't request, even if it comes (or seems to come) from someone you trust.
    I don't say that leaving the safe harbor just once will necessarily result in disaster, but making a habit of it will weaken your defenses against malware attack. Any of the above scenarios should, at the very least, make you uncomfortable.
      
    6. Java on the Web (not to be confused with JavaScript, to which it's not related, despite the similarity of the names) is a weak point in the security of any system. Java is, among other things, a platform for running complex applications in a web page, on the client. That was always a bad idea, and Java's developers have proven themselves incapable of implementing it without also creating a portal for malware to enter. Past Java exploits are the closest thing there has ever been to a Windows-style virus affecting OS X. Merely loading a page with malicious Java content could be harmful.
      
    Fortunately, client-side Java on the Web is obsolete and mostly extinct. Only a few outmoded sites still use it. Try to hasten the process of extinction by avoiding those sites, if you have a choice. Forget about playing games or other non-essential uses of Java.
       
    Java is not included in OS X 10.7 and later. Discrete Java installers are distributed by Apple and by Oracle (the developer of Java.) Don't use either one unless you need it. Most people don't. If Java is installed, disable it — not JavaScript — in your browsers.
       
    Regardless of version, experience has shown that Java on the Web can't be trusted. If you must use a Java applet for a task on a specific site, enable Java only for that site in Safari. Never enable Java for a public website that carries third-party advertising. Use it only on well-known, login-protected, secure websites without ads. In Safari 6 or later, you'll see a lock icon in the address bar with the abbreviation "https" when visiting a secure site.

    Stay within the safe harbor, and you’ll be as safe from malware as you can practically be. The rest of this comment concerns what you should not do to protect yourself.

    7. Never install any commercial "anti-virus" or "Internet security" products for the Mac, as they all do more harm than good, if they do any good at all. If you need to be able to detect Windows malware in your files, use one of the free security apps in the Mac App Store — nothing else.
      
    Why shouldn't you use commercial "anti-virus" products?
    • To recognize malware, the software depends on a database of known threats, which is always at least a day out of date. New threats are emerging on a daily basis. Research has shown that most successful attacks are "zero-day" — that is, previously unknown. Recognition-based malware scanners do not defend against such attacks.
    • Their design is predicated on the nonexistent threat that malware may be injected at any time, anywhere in the file system. Malware is downloaded from the network; it doesn't materialize from nowhere.
    • In order to meet that nonexistent threat, the software modifies or duplicates low-level functions of the operating system, which is a waste of resources and a common cause of instability, bugs, and poor performance.
    • By modifying the operating system, the software itself may create weaknesses that could be exploited by malware attackers.
    8. An anti-malware product from the App Store, such as "ClamXav," has the same drawback as the commercial suites of being always out of date, but it does not inject code into the operating system. That doesn't mean it's entirely harmless. It may report email messages that have "phishing" links in the body, or Windows malware in attachments, as infected files, and offer to delete or move them. Doing so will corrupt the Mail database. The messages should be deleted from within the Mail application.
        
    An anti-virus app is not needed, and cannot be relied upon, for protection against OS X malware. It's useful only for detecting Windows malware, and even for that use it's not really effective, because new Windows malware is emerging much faster than OS X malware. Windows malware can't harm you directly (unless, of course, you use Windows.) Just don't pass it on to anyone else.
        
    A Windows malware attachment in email is usually easy to recognize without the need for any software; for example:
      
    ♥♥♥♥♥♥♥♥♥♥♥♥♥♥!!!!!!!H0TBABEZ4U!!!!!!!.AVI♥♥♥♥♥♥♥♥♥♥♥♥♥♥.exe
       
    Software may be able to tell you which particular trojan it is, but do you really care? In practice, there's seldom a reason to use recognition software unless an institutional policy requires it. Windows malware is so widespread that you should assume it's in every unknown email attachment until proven otherwise. Nevertheless, ClamXav or a similar App Store product may be useful if an uninformed network administrator says you must have some kind of "anti-virus" application.
      
    The ClamXav developer won't try to "upsell" you to a paid version of the product. Other developers may do that. Don't be upsold. For one thing, you should not pay to protect Windows users from the consequences of their choice of computing platform. For another, a paid upgrade from a free app will probably have all the disadvantages mentioned in section 7.
      
    9. It seems to be a common belief that the built-in Application Firewall acts as a barrier to infection, or prevents malware from functioning. It does neither. It blocks inbound connections to certain network services you're running, such as file sharing. It's disabled by default and you should leave it that way if you're behind a router on a private home or office network. Activate it only when you're on an untrusted network, for instance a public Wi-Fi hotspot, where you don't want to provide services. Disable any services you don't use in the Sharing preference pane. All are disabled by default.
        
    10. As a Mac user you don't have to live in fear that your computer may be infected every time you install software, read email, or visit a web page. But neither should you assume that you will always be safe from exploitation, no matter what you do. The greatest harm done by security software is precisely its selling point: it makes people feel safe. They may then feel safe enough to take risks from which the software doesn't protect them. "Hmmmm, this torrent is a crack of that new game I want. I think I'll download it. It could be a trojan, but the antivirus will warn me if it is." Then they wonder why their Mac is so slow all of a sudden. It's slow because it's running flat out mining bitcoins for a hacker who has already sold their credit card number and banking passwords to a criminal gang. Maybe a week later the antivirus does warn them, but what good does that do?
        
    Nothing can lessen the need for safe computing practices.