mash: Crash uploads don't work because LibCrosService not available to resolve proxies |
||||
Issue description* Add --mash to /etc/chrome_dev.conf * Start chrome * Go to chrome//:crash to crash renderer * Go to chrome//:crashes and click "Start uploading crashes" * Watch /var/log/messages (These logs are for a different process crashing, but chrome does the same.) 2017-01-09T11:08:14.736987-08:00 NOTICE crash_sender[1604]: Considering metadata /var/spool/crash/esif_ufd.20170109.110429.28871.meta. 2017-01-09T11:08:14.756997-08:00 NOTICE crash_sender[1622]: Current send rate: 27sends/24hrs 2017-01-09T11:08:14.762358-08:00 NOTICE crash_sender[1629]: Scheduled to send in 0s. 2017-01-09T11:08:14.783466-08:00 NOTICE crash_sender[1666]: Sending crash: 2017-01-09T11:08:14.784290-08:00 NOTICE crash_sender[1667]: Metadata: /var/spool/crash/esif_ufd.20170109.110429.28871.meta (minidump) 2017-01-09T11:08:14.785316-08:00 NOTICE crash_sender[1668]: Payload: /var/spool/crash/esif_ufd.20170109.110429.28871.dmp 2017-01-09T11:08:14.786546-08:00 NOTICE crash_sender[1669]: Version: 9152.0.0 2017-01-09T11:08:14.787379-08:00 NOTICE crash_sender[1670]: Exec name: esif_ufd 2017-01-09T11:08:14.791304-08:00 INFO list_proxies[1671]: Resolving proxies for URL: https://clients2.google.com/cr/report 2017-01-09T11:08:39.818066-08:00 ERR list_proxies[1671]: Failed to call method: org.chromium.LibCrosServiceInterface.ResolveNetworkProxy: object_path= /org/chromium/LibCrosService: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. 2017-01-09T11:08:39.818159-08:00 ERR list_proxies[1671]: CallMethodAndBlockWithTimeout(...): Domain=dbus, Code=org.freedesktop.DBus.Error.NoReply, Message=Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. 2017-01-09T11:08:39.818196-08:00 ERR list_proxies[1671]: Call to ResolveNetworkProxy failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Probably we're not hooking up the dbus LibCrosService correctly.
,
Feb 1 2017
I'm going to start by enabling as much of LibCrosService as I can in the browser process. Longer term LibCrosService should be split into multiple smaller services. Perhaps the proxy lookup could live in a network service. Or chrome could push the proxy information into crash_reporter / crash_sender. For reference, see crash reporter's list_proxies application: https://chromium.googlesource.com/chromiumos/platform2/+/master/crash-reporter/list_proxies.cc (Dan, do you know if we have other bugs about LibCrosService? I remember chatting about it, but I don't find other bugs.)
,
Feb 1 2017
Actually, I think LibCrosService is working. Failure to upload chrome crash reports is some other problem - I'll file a separate bug. * We are initializing LibCrosService in the browser process: https://cs.chromium.org/chromium/src/chrome/browser/chromeos/chrome_browser_main_chromeos.cc?sq=package:chromium&dr=C&l=247 * From the command line I can poke it via dbus (it's weird because it raises a signal in response to the method call): dbus-monitor --system interface=org.chromium.TestInterface & dbus-send --system --type=method_call --dest=org.chromium.LibCrosService /org/chromium/LibCrosService org.chromium.LibCrosServiceInterface.ResolveNetworkProxy string:http://www.example.com/ string:org.chromium.TestInterface string:TestSignal * I can run the system list_proxies command: list_proxies www.example.com * I can crash the sleep command and crash reporter sees it: sleep 100 & kill -SEGV 10406 grep crash_ /var/log/messages 2017-02-01T14:52:04.607317-08:00 WARNING crash_reporter[10438]: [user] Received crash notification for coreutils[10406] sig 11, user 0 (handling) 2017-02-01T14:52:04.609623-08:00 INFO crash_reporter[10438]: State of crashed process [10406]: S (sleeping) 2017-02-01T14:52:04.618553-08:00 INFO crash_reporter[10438]: Stored minidump to /var/spool/crash/coreutils.20170201.145204.10406.dmp * Running crash sender does the upload: FORCE_OFFICIAL=1 SECONDS_SEND_SPREAD=1 crash_sender grep crash_ /var/log/messages 2017-02-01T14:53:18.680464-08:00 NOTICE crash_sender[10794]: Considering metadata /var/spool/crash/coreutils.20170201.145204.10406.meta. 2017-02-01T14:53:18.711147-08:00 NOTICE crash_sender[10807]: Current send rate: 4sends/24hrs 2017-02-01T14:53:18.718475-08:00 NOTICE crash_sender[10813]: Scheduled to send in 0s. 2017-02-01T14:53:18.758967-08:00 NOTICE crash_sender[10852]: Sending crash: 2017-02-01T14:53:18.760602-08:00 NOTICE crash_sender[10853]: Metadata: /var/spool/crash/coreutils.20170201.145204.10406.meta (minidump) 2017-02-01T14:53:18.762269-08:00 NOTICE crash_sender[10855]: Payload: /var/spool/crash/coreutils.20170201.145204.10406.dmp 2017-02-01T14:53:18.763879-08:00 NOTICE crash_sender[10856]: Version: 9224.0.0 2017-02-01T14:53:18.765514-08:00 NOTICE crash_sender[10857]: Image type: force-official 2017-02-01T14:53:18.767171-08:00 NOTICE crash_sender[10858]: Exec name: coreutils 2017-02-01T14:53:19.992820-08:00 NOTICE crash_sender[10868]: Crash report receipt ID c097a59580000000 2017-02-01T14:53:19.996448-08:00 NOTICE crash_sender[10870]: Successfully sent crash /var/spool/crash/coreutils.20170201.145204.10406.meta and removing.
,
Feb 26 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by jamescook@chromium.org
, Jan 13 2017