Re: [systemd-devel] Troubleshooting Failed Nspawn Starts

2015-08-20 Thread Rich Freeman
On Sun, Aug 16, 2015 at 9:29 AM, Lennart Poettering lenn...@poettering.net wrote: Could you file a github RFE issue, asking for support for watchdog keep-alive message send stuff in PID 1 and nspawn, and watchdog keep-alive message receive stuff in nspawn? I think it would make a lot of sense

Re: [systemd-devel] Troubleshooting Failed Nspawn Starts

2015-08-16 Thread Lennart Poettering
On Fri, 14.08.15 14:23, Rich Freeman (r-syst...@thefreemanclan.net) wrote: On Fri, Aug 14, 2015 at 1:30 PM, Lennart Poettering mzerq...@0pointer.de wrote: On Mon, 10.08.15 08:03, Rich Freeman (r-syst...@thefreemanclan.net) wrote: We have watchdog (see WatchdogSec= documentation in

Re: [systemd-devel] Troubleshooting Failed Nspawn Starts

2015-08-14 Thread Lennart Poettering
On Mon, 10.08.15 08:03, Rich Freeman (r-syst...@thefreemanclan.net) wrote: Occassionally I'll have nspawn containers that freeze up when they're loading. What is the best way to troubleshoot these and get useful info to devs? Well, not sure what freeze means here... I'd always start by

[systemd-devel] Troubleshooting Failed Nspawn Starts

2015-08-10 Thread Rich Freeman
Occassionally I'll have nspawn containers that freeze up when they're loading. What is the best way to troubleshoot these and get useful info to devs? This is on systemd-218, on Gentoo. Also, is there any way to detect these freezes, perhaps getting the service launching it to at least fail?