Seeing lots of Chrome errors in /var/log/system.log
Reported by
cmcmac...@gravie.com,
Nov 2 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36 Steps to reproduce the problem: 1. Install Chrome 2. Use it 3. Look at the logs in /var/log/system.log What is the expected behavior? That it would not log a ton of errors into the system log file What went wrong? Mac OSX 10.12.6 Chrome Version 62.0.3202.62 (Official Build) (64-bit) Also the version list on the right lists 62 as beta but based on what I see this is no longer a beta. Oct 24 14:54:41 hostname GoogleSoftwareUpdateDaemon[91738]: 2017-10-24 14:54:41.719 GoogleSoftwareUpdateDaemon[91738/0x700001c1b000] [lvl=2] -[KSOutOfProcessFetcher(PrivateMethods) helperErrorAvailable:] KSOutOfProcessFetcher helper tool STDERR: 2017-10-24 14:54:41.718 ksfetch[91744:13011195] NetworkStorageDB:_openDBReadConnections: failed to open read connection to DB @ /var/empty/Library/Caches/com.google.Keystone/Cache.db. Error=14. Cause=unable to open database file 2017-10-24 14:54:41.718 ksfetch[91744:13011195] CacheRead: unable to open cache files in /var/empty/Library/Caches/com.google.Keystone Have tried uninstalling and reinstalling chrome and the errors persist. Did this work before? N/A Chrome version: 62.0.3202.62 Channel: n/a OS Version: OS X 10.12.6 Flash Version:
,
Nov 3 2017
,
Nov 3 2017
The updater uses extensively ASL logs as the originally recommended way to log events by Apple. Most of these are benign warnings, logged at level ASL_LEVEL_NOTICE. The one mentioned in the bug is due to sandboxing of the process that downloads the updates. As updater in this case runs as root, we spin a separate process with lowered permissions to perform the downloads and this causes some stderr messages to be generated. That said, with 10.12 macOS moved into new logging mechanism that can be queried easily and can take even more data, making the /var/log/system.log obsolete. When it was originally introduced, we saw some reliability issues with the new logging system - large number of data loss was observed, so we temporarily continued to use the ASL logs. |
|||
►
Sign in to add a comment |
|||
Comment 1 by meh...@chromium.org
, Nov 3 2017