New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 621370 link

Starred by 1 user
Status: Fixed
Owner:
borisv@chromium.org
Closed: Aug 2016
Cc:
█ rnimmagadda@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

UPdate is failing with error 11

Reported by kalyanch...@gmail.com, Jun 19 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Steps to reproduce the problem:
Install Google chrome in MAC Elcapitino
open about google chrome and see the update 

What is the expected behavior?
Chrome should show up to date

What went wrong?
Chrome is showing Update failed (error: 11)

Error details:
KSLockFile unable to open() lock file. [com.google.UpdateEngine.CommonErrorDomain:602 - '/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore.lock' - 'KSLockFile.m:431'] (The operation couldn’t be completed. Permission denied [NSPOSIXErrorDomain:13])
KSKeyedPersistentStore lock file error. [com.google.UpdateEngine.CommonErrorDomain:502 - '/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore.lock' - 'KSKeyedPersistentStore.m:329'] (KSLockFile unable to open() lock file. - '/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore.lock' [com.google.UpdateEngine.CommonErrorDomain:602])
KSPersistentTicketStore could not store ticket. (productID: com.google.Chrome) [com.google.UpdateEngine.CoreErrorDomain:1051 - '/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore'] (KSKeyedPersistentStore lock file error. - '/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore.lock' [com.google.UpdateEngine.CommonErrorDomain:502])
KSOmahaServer cannot save the updated ticket: '<KSTicket:0x21fc30
	productID=com.google.Chrome
	version=50.0.2661.102
	xc=<KSPathExistenceChecker:0x5047a0 path=/Applications/Google Chrome.app>
	serverType=Omaha
	url=https://tools.google.com/service/update2
	creationDate=2016-06-10 17:05:30
	tagPath=/Applications/Google Chrome.app/Contents/Info.plist
	tagKey=KSChannelID
	brandPath=/Library/Google/Google Chrome Brand.plist
	brandKey=KSBrandID
	versionPath=/Applications/Google Chrome.app/Contents/Info.plist
	versionKey=KSVersion
	cohort=1:1y5/eyo:
	cohortName=51_mac_103
>' (productID: com.google.Chrome) [com.google.UpdateEngine.CoreErrorDomain:602 - 'https://tools.google.com/service/update2'] (KSPersistentTicketStore could not store ticket. - '/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore' [com.google.UpdateEngine.CoreErrorDomain:1051])

Did this work before? No 

Chrome version: 51.0.2704.103  Channel: stable
OS Version: OS X 10.11.5
Flash Version: Shockwave Flash 22.0 r0

Comment 1 by rnimmagadda@chromium.org, Jun 20 2016

Cc: rnimmagadda@chromium.org
Labels: Needs-Feedback
Unable to repro this issue on MAC (10.11.5) for Google Chrome Stable Version - 51.0.2704.103

Screen-recording is attached.

@kalyancherukuri42: Could you please re-test the same on the next update/install the old build and upgrade to new version and let us know your observations.

Thank you.
621370.mov
3.9 MB Download

Comment 2 by borisv@chromium.org, Jun 22 2016

Owner: borisv@chromium.org
Hello kalyancherukuri42,

The messages are noise - I just implemented code to remove them. But the error 11 is not expected. Have you enabled updates for all users?

If you have done that, could you run the following command on your machine and send the logs to borisv@chromium.org?

/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/ksdiagnostics

Thank you,
Boris

Comment 3 by ccameron@chromium.org, Jul 1 2016

Status: Assigned (was: Unconfirmed)

Comment 4 by borisv@chromium.org, Jul 1 2016 

The actual reason for error 11 reported by the user is unknown. The error messages are due to Keystone (Google Software Update) bug b/29464824 that is fixed on versions 1.2.5.1173+. A Keystone version with the fix for the unnecessary error messages is actively being tested now and should ship it in the coming weeks. Unless more data is provided on the actual error, I will resolve this bug when that version of Keystone ships.

Comment 5 by borisv@chromium.org, Aug 11 2016

Status: Fixed (was: Assigned)
Keystone 1.2.5.1190 has shipped and this error message should not be displayed anymore.
►

Sign in to add a comment