Company Christmas Holidays
North American Headquarters in Miami, USA: Dec 25, 2015, Jan 1st 2016
European Headquarters in Muenster, Germany: Dec 21, 2015 until Jan 03rd 2016
Limited support is available during this period.
We at PROVISIO wish you Merry Christmas and a Happy New Year!

 

Rapport bogue: Abnormal SiteKiosk Program termination

Reproduction

.

Description

Hi,
is there a way to check (in some logs maybe?) why the Sitekiosk application stopped responding/crashed?

We have set up in the config that the Sitekiosk should log everything, but once the crash happens (twice-three times a hour just by browsing random webpages), while using the IE engine, we get:
....
20 03ed 2019-08-05 08:16:54 +0200 [SiteKiosk] Frame-Navigation: about:blank
40 03eb 2019-08-05 08:16:55 +0200 [SiteKiosk] abnormal sitekiosk program termination
20 03e9 2019-08-05 08:16:56 +0200 [SiteKiosk] started

While using Chrome engine we at least get the exit code, but that's about it:
20 03ec 2019-08-01 08:28:12 +0200 [SiteKiosk] Navigation: https://accounts.google.com/CheckCookie?hl=sv&checkedDomains=youtube&checkConnection=youtube:190:1&pstMsg=1&chtml=LoginDoneHtml&service=mail&continue=https://mail.google.com/mail/&gidl=EgIIAA
20 0000 2019-08-01 08:28:13 +0200 [SiteKioskNG] Clearing cache for 'contentPlayer/App01'
20 0000 2019-08-01 08:28:13 +0200 [SiteKioskNG] Cookies successfully deleted.
20 0000 2019-08-01 08:28:13 +0200 [SiteKioskNG] 0 authentication entries successfully deleted.
20 0000 2019-08-01 08:28:13 +0200 [SiteKioskNG] 1 LocalStorage entries successfully deleted.
20 0000 2019-08-01 08:28:13 +0200 [SiteKioskNG] 1 IndexDB entries successfully deleted.
20 0000 2019-08-01 08:28:13 +0200 [SiteKioskNG] 0 WebDB entries successfully deleted.
10 0000 2019-08-01 08:28:13 +0200 [SKNG RootApp] (PID: 9268) App 'App01:contentPlayer:PID 9268' has exited (3221225477).
20 0000 2019-08-01 08:28:13 +0200 [SKNG RootApp] Shutdown root app with exitCode: -1
20 0000 2019-08-01 08:28:13 +0200 [SiteKioskNG] Clearing cache for 'WebApp/Standalone'
20 0000 2019-08-01 08:28:13 +0200 [SiteKioskNG] Cookies successfully deleted.

The RAM/resources are sufficient, the setup takes around 20% of RAM. No additional logs entries found in Window's event viewer.
After 30 seconds when the SItekiosk stops responding, it gets restarted automatically by the Watchdog function.

Réponse: (5)

Re: Abnormal SiteKiosk Program termination 07/08/2019 12:24
Hello,

With the IE based skins there are no further logs except the Windows Event log (Warnings and Errors from the Windows Event log are also displayed in the SiteKiosk Log and at the protocol of the machine on SiteRemote - [Windows/System], [Windows/Application]).
When using the Chrome Browser Skin you also can check the “SiteKioskNG.log” stored at “C:\Users\[user name]\AppData\Local\Temp” ([user name] = Windows user you started SiteKiosk within).

Or you first check if it is about (CPU?) performance and increase the time interval for the Software Watchdog – default 30 Seconds (SiteKiosk configuration-->Maintenance-->Monitoring-->Settings).

Further information about the log entry “abnormal sitekiosk program termination” you can find at this FAQ: https://www.provisio.com/en-GB/CustomerSupportCenter/ArticleDetails.aspx?ArticleID=6034

Some background information about the Software Watchdog here:
https://www.provisio.com/helpconsole/SiteKiosk%20Help/en-US/default.htm?maintenance.htm#three


If it is a reproducible browser crash on a certain web page you may check if it is an issue of the web page:
The IE based skins are using the IE Webbrowser Control of the installed Internet Explorer.
The Chrome Browser Skin uses a Chromium CEF engine installed with SiteKiosk (open source and also source for Google Chrome).
More information here: https://bitbucket.org/chromiumembedded/cef/src/master/README.md
https://en.wikipedia.org/wiki/Chromium_Embedded_Framework

To compare you need to check in Internet Explorer (or IE Webbrowser Control) on that system or even with the corresponding Chromium CEF Test application.

SiteKiosk 9.7 uses Chromium 73.0.3683.75 Windows 32 Bit. Here you can find the corresponding Chromium test application for download (unzip 2x and run the cefclient.exe in the "Release" folder) which is currently used in SiteKiosk 9.7.5026 (Chromium 73.0.3683.75 Windows 32 Bit):
http://opensource.spotify.com/cefbuilds/cef_binary_3.3683.1920.g9f41a27_windows32_client.tar.bz2

For testing it in the Internet Explorer Webbrowser Control (outside / without SiteKiosk) you can download a ZIP from our web page and then execute the exe after extracting the files (you do not need to install anything):
Here a PDF with further descriptions and a link to a Webbrowser Control test application:
http://www.provisio.com/Download/Webbrowser%20Control%20Test%20Applikation%20EN.pdf

Regards,
Michael Olbrich
Re: Abnormal SiteKiosk Program termination 13/08/2019 09:50
Hi,
thanks for the info.

I have extracted the sitekioskng.log from using the Chrome engine:
https://pastebin.com/H7z9ERQK

Here, the crash occured on 9:35:28:
08-13 09:35:12|DEBUG|6640: Pinging (BID: 1) frame 3 'file:///C:/SiteKiosk/SiteKioskNG/assets/apps/contentPlayer/siteKioskContent/assets/player/index.html?section=0&mode=main&shouldStopWhenIdle=false'

08-13 09:35:12|DEBUG|6640: Pinged (BID: 1) frame 3

08-13 09:35:12|DEBUG|6640: Pong (BID: 1)

08-13 09:35:28|DEBUG|1428: SKNG: DEBUG (SKNG RootApp): Pinger for app App01:contentPlayer:PID 5596 has not responded, shutting down.

08-13 09:35:28|DEBUG|1428: C4A8EF1F0:{"id":22,"method":"log.debug","params":["SKNG RootApp",0,"Pinger for app App01:contentPlayer:PID 5596 has not responded, shutting down."]}

08-13 09:35:28|DEBUG|5116: SKNG:NodeJS: did not receive pong in time, exiting ...
08-13 09:35:28|DEBUG|1428: SKNG: INFO (SKNG RootApp): Shutdown root app with exitCode: -1

08-13 09:35:28|DEBUG|1428: C4A8EF1F0:{"id":23,"method":"log.info","params":["SKNG RootApp",0,"Shutdown root app with exitCode: -1"]}

08-13 09:35:28|DEBUG|1428: SKNG: SiteKiosk.CefApp.exe Exited: -1


Then, at 9:36 the whole Sitekiosk app restarted (watchdog is set up for 30 seconds).
I will also test with the Chrome/IE tools you suggested, but I think the issue is not limited to some specific website, as it happens quite randomly.
There are not warning/errors in Windows/System or Application log during the crash. The CPU load is also fine - no overhead.

Do you have any suggestions why this might be happening from the log? Some permission/access issues maybe?

Thanks
Re: Abnormal SiteKiosk Program termination 13/08/2019 10:24
Hello,

the logs just show that the browser was unresponsive when the watchdog checked it, therefore the watchdog triggered the restart. This is intended behaviour and unless this happens in a reproducible scenario it can have a multitude or reasons. If you find the the watchdog to trigger restarts too frequently you can change the intervall as described in the previous answer.
Re: Abnormal SiteKiosk Program termination 13/08/2019 10:34
If we prolong the watchdog interval or even disable it completely, then the SItekiosk app restarts after the set interval (or never - and the machine needs to be shutdown/restarted manually).
We have eliminated GPO, Symantec AV, HW drivers as a culprit.
This does not happen only on one machine.

Do you have some other recommendations we can try or are there any more detailed logs that could be checked?
Re: Abnormal SiteKiosk Program termination 13/08/2019 10:56
Hello,

I am sorry, but unless there is a reproducible scenario the above is about what you can do (though you should never disable the watchdog for obvious reasons). With a reproducible scenario we can debug the problem in our development lab to find the reason and fix it or provide you with required changes to the configuration.

Please note that when you experience this unreproducible/random screnario with the IE engine as well with the Chrome engine, it is quite likely that the cause of the problem is not SiteKiosk but some outside source, because both engines and how they are implemented are/is significantly different.

There is one additional thing though, that you can check and that both engines would have in common if activated. Are you using the content filter of SiteKiosk? If so and if you are able to do it, then please deactivate it for testing purposes, to see if the problem stops occurring.