Hello Xi Yuan,

Scott referred me to you as a good person to start with for triaging this problem.  It isn't clear if this is due to chromeos not reporting its active kiosk status, or cpanel not reporting it properly, or maybe something with my panther device itself.  I will be trying the same test on a rikku later this afternoon and will update this issue then.

Thanks!
-- Mike

+jinzhang

Have you configured device_status_frequency in device policy? If not, default status report frequency is 3 hours [1]. I suspect this is why CSB is still showing up in the report.

Jin, is there a way to see the timestamp of a device status report, i.e. when the report is received?

[1]: https://cs.chromium.org/chromium/src/chrome/browser/chromeos/policy/proto/chrome_device_policy.proto?rcl=0&l=106

I have not changed the device status report frequency.  Is that a cpanel attribute?  Under Device Management -> Chrome Management -> Device Settings I do have these enabled: User & Device Reporting: "Enable device state reporting", and under Kiosk Settings: "Enable device health monitoring" and "Enable device system log upload".

Ah, I found a chrome browser policy called "Report Upload Frequency" which is currently "900000". I assume that's milliseconds?  which would be 15 minutes. I'll try to tweak that.

Xiyuan, for kiosk devices (has auto launched app configured in policy), devices upload status every 15 minutes instead of 3 hours. Note that this frequency policy is not exposed in CPanel. However, the frequency is not the issue here.

I think the issue is when no more kiosk session status is being reported, DMServer didn't actually clear the old session status information, causing stale information being displayed.

Let me get the last status report time to confirm.

Last status report time was 2016-08-30 16:15:06 PST, with the active app as "Mike Kiosk Printtest". Mike, did you update the auto-launched Kiosk app via CPanel?

Yes, I was in the midst of M54-dev testing and needed to move on to the next of 28 tests. 

Filed a server-side bug to track this issue.

The same test on a rikku device has slightly different results.  Enrolled the device, moved it to Operations -> Facilities, rebooted, interrupted the auto-launch of Chrome Sign Builder, and after a half hour Cpanel is still showing the gray circle (Device online/offline status is unknown).  It is definitely alive and sitting at the home screen waiting for something to be clicked. (serial number D9Z0BPW0015180EE8F7600, IP 100.107.2.226).

I'll let it sit overnight and see what Cpanel shows in the morning.

As of 9:45am today (8/31), the Cpanel status for my rikku is:

   Red circle:  "Device is offline."  [It is alive and well, albeit idle]
   Kiosk App info:  "Chrome Sign Builder 1.0.4"  [No kiosk app is running]
 

Can you please verify on the rikku device the policy |heartbeat_enabled| policy is true?

Wait, I saw the device was back online again. Did you do anything?

I moved the mouse, but didn't execute anything.  My Cpanel still shows the red-circle "device is offline" status.

Chrome Policy "HeartbeatEnabled" is "true".

I entered a Public Session to check the chrome browser policies, and now Cpanel is showing the green "Device is online" status.

I suspect when device escapes auto-launch and sits on the home screen, the heartbeat scheduler may not be initialized, hence no heartbeat sent via GCM. However, I'm not the client expert here.

Drew, do you know if this is the case?

I have taken the rikku off-line for now.  I will resume M54-dev testing later this afternoon (8/31).

The rikku is online again.  At approximately 3:30pm (8/31) I assigned the device to Operations -> Facilities, rebooted, let it play Chrome Sign Builder for a couple of minutes, then rebooted again and aborted the auto-launch of CSB.

It has been sitting on the home screen doing nothing for a little over a half hour.  Cpanel shows the "Device is online" fine, but is still showing CSB as the Kiosk App info.  I'll refresh the device status page every half hour or so until 6pm tonight, and let it sit idle overnight.

Just checked the rikku status, and it showed the red circle (Device is offline).
Looking at the box, I saw its blue power button flashing, which I'm betting means it has automatically decided to go to sleep when it has been idle for awhile.

Clicking the mouse wakes the rikku up.  

Back on Cpanel, the heartbeat is green (online) again.
The Kiosk App info is still showing CSB, though.

I'll see if there is a way to prevent the rikku from auto-sleeping.

I located an extension called "keep-awake" (webstore id: bijihlabcfdnabacffofojgmehjdielb).  Hopefully that will keep the rikku alert through the night.

The keep-awake extension did its job; the guado did not go into sleep mode overnight.

The cpanel system activity info shows:  
   heartbeat:  gray circle (device online/offline status unknown)
   Kiosk app info:  Chrome Sign Builder 1.04  [definitely no kiosk app running]

This is fixed server-side and the fix will be in production in about a week from now.

kiosk app info not being reported if application is not currently running