New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frame receives random SIGTERM from init process (pid=1) on custom UC22 appliance #120
Comments
Hi Tobias, PID 1 is systemd… so something must be causing systemd to try and restart Frame. The obvious candidate would be the snap refreshing, can you see if things in
That one's more worrying. Is the error the same when this happens? What's |
No, terminating on receiving SIGTERM is correct behaviour. Any problem lies in not understanding why systemd is sends SIGTERM, nor why snapd doesn't restart Frame after it exits. |
Thanks @Saviq @AlanGriffiths for the quick feedback.
Service-related things in
I have not been able to reproduce this one yet, so I can't provide further details right now. Will update here if I observe this again. |
One thing I noticed in the logs:
This only occurred once, but I can't tell if this was during an initial boot (i.e. frame was setting up the first time). |
That looks somewhat like canonical/mir#2799. (But without a stack trace it is hard to be sure if it is the same thing - there might be clues earlier in the log) |
I checked my test installations for these log lines, below is the full log from a Three things I noticed, but don't know if they are relevant. This is on a Raspberry Pi 3B with the config provided in my first post.
Longer log snip
I did not observe another instance of unexpected restarts or fatal errors since yesterday, so unless you spot something worth investigating, this can be closed for now. |
Will close, please report back if you see anything new. Thanks! |
On my Ubuntu Core appliance, Frame sometimes receives SIGTERM from the init process:
I cannot reproduce this reliably yet. I observed both a single automatic restart of the frame daemon service and a completely black screen where I would need to force-restart Frame.
Expected behavior
Ubuntu Frame should stay up and running.
Actual behavior
Ubuntu Frame daemon service restarts, or sometimes halts completely. Error message in
ubuntu-frame.daemon
log:I'm providing as much debug information as possible below in
<details>
tags to keep this readable 🙂 Based on the debug message, this may also be a better fit for the mir repo, please move it if necessary.Device / OS setup
Ubuntu Core 22 custom model image on a Raspberry Pi 3B rev 1.2,
armhf
architecture.The gadget snap is based on the reference
pi-gadget
snap (22-armhf
branch) and only adds minor modifications to config.txt, two kernel command line parameters and default config / connection for seeded snaps.The appliance is set up via a WiFi captive portal without an initial internet connection, so the system time is usually way behind until users have configured their WiFi credentials and NTP could sync the correct time.
Installed snaps:
Ubuntu Frame configuration
Kernel command line in /proc/cmdline
My config.txt is pretty much the default pi-gadget version from
22-armhf
, note the### BEGIN/END customizations
comment:contents of config.txt
The text was updated successfully, but these errors were encountered: