mirror of
https://github.com/debloper/xiosk.git
synced 2026-04-26 21:35:51 +03:00
[GH-ISSUE #41] Watchdog? "If Chromium isn't running, reboot?" #39
Labels
No labels
bug
bug
documentation
enhancement
enhancement
feature request
good first issue
good first issue
help wanted
invalid
priority: high
priority: low
priority: medium
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/xiosk#39
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @andiohn on GitHub (Oct 4, 2024).
Original GitHub issue: https://github.com/debloper/xiosk/issues/41
I've had the system boot up before I arrive at work and when I do, it's on the desktop. So, I assume that the TV was off and chrome didn't start? I'm not sure where to look for that.
A simple 'if this isn't running start it' or 'if this isn't running, reboot'
@andiohn commented on GitHub (Oct 4, 2024):
Ya, that would be big to help it be more resiliant. An even better thing would be to use docker containers for each part, but that sounds like massive rewrite.
It could be possible that this could be a really good barebones digital signage platform that uses normal, existing tech so that it possibly doesn't even need to be maintained, just enhanced over time.
@andiohn commented on GitHub (Oct 4, 2024):
This option is interesting, it basically just checks to see if a program is running, and if it isn't, it launches it. We could have this wait like every 15 minutes and then check.
https://stackoverflow.com/questions/19284919/how-to-test-if-a-process-exists-in-bash
@debloper commented on GitHub (Oct 7, 2024):
If it's related to #32 (please confirm), then I think it's more important to discover why is that happening.
As a coverup/hotfix a lot can be done, including a scheduled reboot each 6hrs or something (and feel free to do so, if you so prefer). But I'd rather discover and kill the issue at its root.
@andiohn commented on GitHub (Oct 29, 2024):
Ya, this is needed because we can't really anticipate all possible memory leaks or issues that it'll run into. Also, if there was a way to send a notification, we could keep a log but that might not be possible.
I have to get the remote people to reboot it and we know that we'll get corruption that way.