Subject: Re: [vserver] Segfault on shuting down new gentoo guest
From: "Michael S. Zick" <mszick@morethan.org>
Date: Fri, 11 Jan 2008 09:39:48 -0600

 Fri, 11 Jan 2008 09:39:48 -0600
On Fri January 11 2008 09:23, Oliver Welter wrote:
> Hello Herbert, All,
> 
> Herbert Poetzl schrieb:
> > On Tue, Jan 08, 2008 at 03:18:02PM +0100, Oliver Welter wrote:
> >>
> >> Herbert Poetzl wrote:
> >>> On Mon, Jan 07, 2008 at 08:05:54AM +0100, Oliver Welter wrote:
> >>> Hi List, Hollow,
> >>>
> >>> I installed a new guest from scratch using the stage4 tarbal from
> >>> Hollows Website. The clean tarball works fine.
> >>> I now ran "emerge -u system", as baselayout was updated, too, I reran
> >>> the initpost script also. Server starts and works fine, but I get this
> >>> on shutdown:
> >>>
> >>> # vserver test stop
> >>> /usr/lib/util-vserver/vserver.stop: line 85:  8580
> >>> Speicherzugriffsfehler  "${NICE CMD[@]}" "${CHBIND CMD[@]}" "$ VTAG"
> >>> --migrate "${OPTS VTAG ENTER[@]}" --silent -- $ VCONTEXT $SILENT OPT
> >>> --migrate --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:
> >>>
> >>> Any ideas?
> >>>
> >>>> as usual, please add the output of testme.sh
> >>>> and/or provide the kernel/patch/userspace versions
> >> Sorry, guest is, as stated, a stage4 from hollow with all packages
> >> updated by "emerge -u world". As it ran before and there are other
> >> guests running find on the same host I assume that something inside the
> >> guest segfaults. I have only syslog-ng running inside the guest.
> >
> > try chroot-ing into the guest filesystem and
> > carefully see if typical commands can be executed
> >
> The server is working, so I cant find anything that is obviously broken
> but I found something else. The commandline that crashes is a bash:
> /bin/bash /usr/sbin/chbind --silent --secure --nid 10099 --ip
> 192.168.0.123/24 --ip 212.x.x.x/25 /usr/sbin/vtag --migrate --tag 10099
> --silent -- /usr/sbin/vcontext --silent --migrate --chroot --xid 10099
> -- env -i TERM=xterm RUNLEVEL=0 /sbin/rc shutdown
> 
> And, I see this in my dmesg of the host:
> 
> 
> vxW: xid=10099 did lookup hidden f5de3ce0[#0,4026531875] �/proc/bus�.
> vxW: xid=10099 did lookup hidden f5de3ce0[#0,4026531875] �/proc/bus�.
> vxW: xid=10099 did lookup hidden f5de3ce0[#0,4026531875] �/proc/bus�.
> vxW: xid=10099 did lookup hidden f5d83aa0[#0,4026531866]
> /proc/sys/fs/binfmt misc
> dynamic contexts disabled.
> 
> Any hints ?
>

Are any of the executables in that command line interpetted without a #!
first line naming the interpeter path?
I.E: Scripts that expect the interpeter to be set in binfmt misc?
(Common would be pearl, python, lua, ...)

Mike
> 
> Oliver
> 
> 
> > HTH,
> > Herbert
> >
> >> Oliver
> >>
> >>  Kernel: 2.6.20-vs2.2.0-gentoo
> >>                    VS-API: 0x00020200
> >>              util-vserver: 0.30.214; Sep 30 2007, 00:17:12
> >>
> >> Features:
> >>                        CC: i686-pc-linux-gnu-gcc, i686-pc-linux-gnu-gcc
> >> (GCC) 4.1.2 (Gentoo 4.1.2 p1.0.1)
> >>                       CXX: i686-pc-linux-gnu-g++, i686-pc-linux-gnu-g++
> >> (GCC) 4.1.2 (Gentoo 4.1.2 p1.0.1)
> >>                  CPPFLAGS: ''
> >>                    CFLAGS: '-O3 -march=pentium4 -fomit-frame-pointer
> >> -std=c99 -Wall -pedantic -W -funit-at-a-time'
> >>                  CXXFLAGS: '-O3 -march=pentium4 -fomit-frame-pointer
> >> -ansi -Wall -pedantic -W -fmessage-length=0 -funit-at-a-time'
> >>                build/host: i686-pc-linux-gnu/i686-pc-linux-gnu
> >>              Use dietlibc: yes
> >>        Build C++ programs: no (affected: vbuild, vcheck)
> >>        Build C99 programs: yes
> >>            Available APIs: v13,net,v21,v22,v23,netv2
> >>             ext2fs Source: e2fsprogs
> >>     syscall(2) invocation: alternative
> >>       vserver(2) syscall#: 273/glibc
> >>
> >>
> >> --
> >> Protect your environment -  close windows and adopt a penguin!
> >> PGP-Key: 3B2C 8095 A7DF 8BB5 2CFF  8168 CAB7 B0DD 3985 1721
> >>
> >>
> >
> >
>