Sun, 24 Nov 2013 17:29:25 -0500 OK, thanks - will try the time out link first….removing run time scripts etc., it seems it would be easier to rebuild the guest and move over ~/home…FYI I think I need alsa as we use the sound, so finding out which services are needed would probably take some doing. A bit worrying that this happens, though not a show stopper as we can get to all the data in the guest…Thanks for the help! On Nov 24, 2013, at 5:22 PM, Herbert Poetzl <herbert@13thfloor.at> wrote: > On Sun, Nov 24, 2013 at 05:14:27PM -0500, Madog wrote: >> Thanks Herbert - > >> As best I know, I'm using the standard Debian Squeeze kernel >> (notably, this isn't happening on all guests, but is on one >> that I use a lot for testing, restart it frequently). > >> Is there a way to fix this? > >> Change the default time out time (and how?) > > http://www.nongnu.org/util-vserver/doc/conf/configuration.html > search for timeout > >> or somehow force clean up on the guest? > > the guest is usually cleaned up when it is created, > but you can also clean it up manually by removing > services and runlevel scripts you do not need in > a guest (like for example alsa) > > best, > Herbert > >> On Nov 24, 2013, at 5:08 PM, Herbert Poetzl <herbert@13thfloor.at> wrote: > >>> On Sun, Nov 24, 2013 at 12:00:17PM -0500, Madog wrote: >>>> Hi All: > >>> Hi Madog! > >>>> Periodically I get a weird restart issue with one of my guests >>>> (I'm running Gnome in the guest, and have a encrypted mount >>>> there too using EncFS) and I can no longer remote via X to the >>>> guest (am using x2go). I can still access data on the guest >>>> from the host and if I build a new guest and copy over ~/home >>>> things function again. I'm using Debian Squeeze. > >>>> Output is shown below that shows I believe several errors >>>> including "Perhaps there is a stale lock file?" at the end of >>>> the restart….any suggestions? Thanks! > >>>> vserver VserverGuestXYZ stop >>>> Using makefile-style concurrent boot in runlevel 6. >>>> Shutting down ALSA...done (none loaded). >>>> Stopping GNOME Display Manager: gdm. >>>> Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon. >>>> Checking for running unattended-upgrades: Asking all remaining processes to terminate...done. >>>> Currently running processes (pstree): >>>> init-+-cupsd-+-5016*[cpdftocps] >>>> | |-1067*[cups-x2go] >>>> | |-7349*[cupsd] >>>> | `-6588*[pdftopdf] >>>> `-rsyslogd---3*[{rsyslogd}] >>>> Killing all remaining processes...failed. >>>> Stopping enhanced syslogd: rsyslogd/usr/lib/util-vserver/vserver.stop: line 98: 12309 Killed "${IONICE CMD[@]}" "${NICE CMD[@]}" "${CHBIND CMD[@]}" "$ VSPACE" --enter "$S CONTEXT" "${OPTS VSPACE[@]}" -- "$ VTAG" --migrate "${OPTS VTAG ENTER[@]}" --silent -- $ VCONTEXT $SILENT OPT --migrate $OPT VCONTEXT CHROOT --xid "$S CONTEXT" -- "${INITCMD STOP[@]}" >>>> A timeout occured while waiting for the vserver to finish and it will >>>> be killed by sending a SIGKILL signal. The following process list >>>> might be useful for finding out the reason of this behavior: > >>> This means that the shutdown takes longer than the configured >>> (maybe default) timeout, and util-vserver thus kills off >>> the remaining guest processes. > >>>> ---------------------------------------------------------------------- >>>> 12309 40031 VserverXYZ.domainname.com ? S+ 0:00 \ /bin/sh /etc/init.d/rc 6 >>>> 12321 40031 VserverXYZ.domainname.com? S+ 0:00 \ startpar -p 4 -t 20 - >>>> 16483 40031 VserverXYZ.domainname.com ? S 0:00 \ /bin/sh /etc/init >>>> 16600 40031 VserverXYZ.domainname.com ? S 0:00 \ start-stop-da >>>> 6111 40031 VserverXYZ.domainname.com? Sl 0:00 /usr/sbin/rsyslogd -c4 >>>> ---------------------------------------------------------------------- > >>>> vserver VserverXYZ status >>>> Vserver 'VserverXYZ' is stopped > > >>>> vserver vserverXYZ start >>>> Using makefile-style concurrent boot in runlevel 3. >>>> Starting enhanced syslogd: rsyslogd. >>>> Loading cpufreq kernel modules...done (none). >>>> CPUFreq Utilities: Setting ondemand CPUFreq governor...disabled, governor not available...done. >>>> Starting periodic command scheduler: cron. >>>> Starting NTP server: ntpd. >>>> Starting system message bus: dbus. >>>> Can't start Hardware abstraction layer - sysfs not mounted on /sys ... failed! >>>> Starting OpenBSD Secure Shell server: sshd. >>>> Cleaning up stale X2Go sessions. >>>> Starting GNOME Display Manager: gdm. >>>> Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon. >>>> Starting Common Unix Printing System: cupsdFATAL: Could not load /lib/modules/2.6.32-5-vserver-686/modules.dep: No such file or directory >>>> FATAL: Could not load /lib/modules/2.6.32-5-vserver-686/modules.dep: No such file or directory >>>> FATAL: Could not load /lib/modules/2.6.32-5-vserver-686/modules.dep: No such file or directory > >>> This suggests two things: first, you are running a rather old >>> kernel, and second, the guest is not properly cleaned up, >>> otherwise it would not mess around trying to find kernel >>> modules. > >>>> . >>>> Enabling additional executable binary formats: binfmt-supportFATAL: Could not load /lib/modules/2.6.32-5-vserver-686/modules.dep: No such file or directory >>>> Cannot create link /etc/mtab~ > >>>> Perhaps there is a stale lock file? > >>> HTH, >>> Herbert > >