Porteus Kiosk hangs up after a few days

Post bug reports related to either the kiosk ISO or the kiosk wizard here.
smock
White ninja
White ninja
Posts: 7
Joined: 22 Aug 2022, 08:50
Distribution: Porteus Kiosk 5.4.0

Porteus Kiosk hangs up after a few days

Post#1 by smock » 13 Mar 2023, 10:26

Hello

I'm using Porteus Kiosk 5.4.0 on a so-called "commercial grade" Intel Atom touch screen PC with screensaver slideshow and dpms_idle enabled. Other power saving options (freeze_idle, ...) are not configured.

I'm facing a few issues when the panel is running for a longer time without interaction. The biggest problem is that after something like 5 days no interaction with the touch PC is possible anymore:
  • screen is off
  • power LED is green and the PC is warmed
  • PC isn't reachable over the network
  • nothing happens when...
    ...the touch screen gets touched
    ...the power button gets pressed
    ...a keyboard gets connected and a key is pressed, also e.g. NUM lock cannot be activated
Please find here the output of debug.sh: https://pastebin.com/frKZgfPH (pw: 1sikXCWq6L)

Any hint how to isolate this issue is much appreciated.

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5660
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Porteus Kiosk hangs up after a few days

Post#2 by fanthom » 13 Mar 2023, 10:51

Hello smock,

Please setup full persistence for logs:

Code: Select all

persistence=/var/log
recreate the freeze -> reboot kiosk -> provide /var/log/messages file.
Hopefully the error will be logged there.

Thanks
Please add [Solved] to your thread title if the solution was found.

smock
White ninja
White ninja
Posts: 7
Joined: 22 Aug 2022, 08:50
Distribution: Porteus Kiosk 5.4.0

Porteus Kiosk hangs up after a few days

Post#3 by smock » 13 Mar 2023, 11:28

Hello fanthom,

many thanks for your quick feedback.

Didn't know that persistence parameter takes paths too. We're using persistence=full since our application depends on some persistent data within the browser.

Is it somehow possible to combine persistence=full with persistence=/var/log? Docs do not specify multiple arguments for persistence.

Thank you!

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5660
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Porteus Kiosk hangs up after a few days

Post#4 by fanthom » 13 Mar 2023, 11:51

"Docs do not specify multiple arguments for persistence."
This is intended. If users set persistence for a wrong folder (e.g. /etc) then they may break the system.
I'm not going to support such scenarios.

"Is it somehow possible to combine persistence=full with persistence=/var/log?"
Use this:

Code: Select all

persistence=full /var/log
Thanks
Please add [Solved] to your thread title if the solution was found.

smock
White ninja
White ninja
Posts: 7
Joined: 22 Aug 2022, 08:50
Distribution: Porteus Kiosk 5.4.0

Porteus Kiosk hangs up after a few days

Post#5 by smock » 13 Mar 2023, 12:33

I see :). Will setup this and observe the logs, thanks a lot!

smock
White ninja
White ninja
Posts: 7
Joined: 22 Aug 2022, 08:50
Distribution: Porteus Kiosk 5.4.0

Porteus Kiosk hangs up after a few days

Post#6 by smock » 23 Mar 2023, 06:22

I could reproduce the issue with persistent /var/log. Unfortunately /var/log/messages does not show anything else than a daily “…rsyslogd was HUPed” message which stops to appear as soon as the panel freezes.

Then I set up a test case with no dpms_idle setting. With this configuration the panel didn't freeze for ~7 days.

Is there probably some other energy saving settings which dpms_idle triggers in the background?

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5660
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Porteus Kiosk hangs up after a few days

Post#7 by fanthom » 23 Mar 2023, 07:16

I have seen the case when external touchscreen monitor was cutting off the touch input when going into the sleep mode.
Touch input was not restored when the monitor was powered on, PC reboot was the only solution.

Maybe this is your case?
Please try connecting to the kiosk over SSH/VNC and check if it really freezes or if its just the touch input not working.

Thanks
Please add [Solved] to your thread title if the solution was found.

Post Reply