parts of my nautilus feedback report think I am on the East Coast |
||
Issue descriptionhttps://listnr.corp.google.com/product/208/report/85854801016 There seems to be a 3-hour discrepancy depending on the log. More specifically: There is this on the report page. I assume that's when the report arrived at the server. Submitted on: December 18, 2018 15:26:51 (PST) Then in the system logs, near the top, there is this entry: LOGDATE=Tue Dec 18 10:24:36 PST 2018 Is that the beginning of log collection? That seems possible. The chrome_user_log ends here, which is consistent at about 10:25am: [1624:1624:1218/102557.736722:WARNING: However, the kernel log and vmlog end three hours later: [1218/132503] 5554 0 0 5350 20023 1.00 1499941 1499941 2018-12-18T13:24:57.414594-05:00 WARNING mosys[30577]: libminijail[30577]: SECURE_NOROOT not set, not dropping bounding set Other end times: tlsdate: 2018-12-18T10:46:51.009023-05:00 INFO tlsdated[2506]: [event:handle_time_setter] time set from the network (1545148011) (this could be sparsely populated in time) top: top - 10:25:01 up 13 days, 13:56, 0 users, load average: 16.29, 5.67, 3.74 update_manager: [1218/132422:ERROR:real_shill_provider.cc(128)] Could not find connection type (service: /service/1714) chrome_system_log: [1826:1848:1218/132421.046591:VERBOSE1:drm_display.cc(104)] DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=35 connector=57 origin=0,0 size=1920x1200
,
Dec 19
LOGDATE is the time at which debugd started collecting the logs: https://cs.corp.google.com/chromeos_public/src/platform2/debugd/src/log_tool.cc?type=cs&q=%22LOGDATE%22+p:chromeos_public&g=0&l=68 The "Submitted on" date is probably the time at which is was received and handled by the feedback server? +sling@
,
Dec 19
If Chrome filled in the submission time then we'd use that. If not, then our servers would fill it in with the time it handled the request. |
||
►
Sign in to add a comment |
||
Comment 1 by semenzato@chromium.org
, Dec 19Components: OS>Systems
Labels: OS-Chrome