Google Admin show gray status for the Chrombox even though the player actively responding to admin console
Reported by
tuan...@scala.com,
Sep 27 2016
|
|||||||
Issue descriptionChrome Version : <Chrome Version: 53.0.2785.103> This issue is related to the Google Admin Console not updating the correct status of the Chromebox device The device is currently in domain: gstv-chrome.com device serial number is 91DED00GA1054400004LMA0 This issue has been reported and discussed with Alex Huie and Raj Duraisamy at Google
,
Oct 10 2016
Today all my chromeboxes show red status and yet the device performed system log upload and responding to screen capture and reboot.This problem happens to all my devices on stable, beta and canary channel. Strange! How do I find out what is the current version of the Google Admin Server software to include here to indicate the version that is having problem?
,
Nov 15 2016
,
Nov 15 2016
@mlight, is this reproducible. I think there's another/similar bug related to the same issue. YOu could dupe this into that or merge that into this.
,
Nov 15 2016
There had been a previous issue 649344 where a gray heartbeat was always displayed (due to a de-provisioned device's unknown-state heartbeat never being refreshed, even if it was later re-enrolled). This problem does not seem to be related since Cpanel is apparently looking for a heartbeat but isn't finding one.
,
Nov 15 2016
This issue happened once with my device and the other is with my customer's device and i believe it was fixed with the Admin Console released around 10/17. Raj Duraisamy@goodle has better insight to this issue.
,
Nov 15 2016
[Triage] Vidster, can you help triage this?
,
Nov 15 2016
Started trying to reproduce this about 2 hours ago. Cpanel is being Extremely Sluggish today (crosprqa4.com domain). It took most of those 2 hours just to transfer my sumo into an OU where kiosk health monitoring is enabled. Once transferred and had launched a chrome sign kiosk video, the health light went from gray to green in about 3 minutes (reasonable). My device is running M55- beta, build 8872.34.0, test image.
,
Nov 16 2016
tuan.vu@ - can you attach the devices logs to this bug. Follow the steps below to get the logs. 1. Reboot the device and stop the kiosk app from auto launching (ctl + alt + s) 2. Log in to the device 3. In chrome go to chrome://net-internals/#chromeos 4. Click "Store Debug Logs" --> this will create a .tgz file and place it in your downloads folder. 5. Attach the .tgz file to this bug
,
Nov 16 2016
,
Nov 16 2016
@Harpeet, Unfortunately, this device has been sent back to the customer. I no longer have this device at hand. I can request the customer to capture the requested log but it will be of today ( not at the time of the failure ). Please let me know if you want that.
,
Nov 16 2016
Yes go ahead and have them capture these logs but it'll be best to get the logs again when the issue is happening.
,
Nov 17 2016
I believe we have already addressed this issue and have not seen any new complaints so far. I am closing this bug. Tuan, if you happen to observe the same issue, please create a new bug. Thanks.
,
Dec 9 2016
Verified in M55-Beta and M56-Dev. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by tkonch...@chromium.org
, Sep 30 2016