HI Tony,

1. Wondering if you have considered the method described at Freedesktop.org(one of my primary sources of info on systemd) http://freedesktop.org/wiki/Software/systemd/Debugging/

2. Is this for a special purpose? If not and if you're just setting up a regular maintenance system, have you considered extracting and aggregating logs remotely using IP instead of serial using something like Logstash?

This is not about a 'regular maintenance system', but rather a low-level, Xen/Kernel boot debugging process, where _specifically_ serial console logs are requested by the devs, etc. I hadn't considered the systemd debugging process; tbh, I wasn't yet aware of the _early_ debug.shell. This "Shutdown Never Finishes If normal reboot or poweroff never finish even after waiting a few minutes, the above method to create the shutdown log will not help and the log must be obtained using other methods. Two options that are useful for debugging boot problems can be used also for shutdown problems: use a serial console use a debug shell - not only is it available from early boot, it also stays active until late shutdown. " seems like it'd grab the early processes/info. Not at all sure if/how using "a debug shell" works with Xen in the mix. At 'another post', I was instructed by one of the devs that serial console is "expected" to be working first, before debugging kernel-xen, and, in the post above, there's reference to the "Xen console driver", which, I gather is what requires console output? In any case, the Suse kernel-/xen- folks have NOT requested/suggested the output from the systemd-debugging process you've provided reference to (I presume they'd be aware_, but, rather, ONLY have requested serial console log output. If the systemd info *IS* a possibilty that provides a sufficient alternative, AND gets around the fact that I'm currently unable to get a peep out of serial console, I'd be VERY interested to know that. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org