On Mon, Jun 07, 2004 at 06:20:24AM +0200, Dimitri Roschkowski wrote: > Hi, > > my last Mail was about the crash of the master server by a high load, > that cause by some vserver. Yesterday I found a realy strange thing, > which happend one minute befor the master server crashed: > > 11:17:01 up 1 day, 22 min, 0 users, load average: 3.17, 2.57, 2.37 > USER TTY LOGIN@ IDLE JCPU PCPU WHAT > CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME DESCRIPTION > 0 34 117MB 3kB 2h04m27 28m36.45 1d12h22 root server > 49163 36 1GB 13kB m08.32 m02.97 1d12h19 v12 > 49166 54 2GB 52kB 4m56.48 4m33.37 1d12h19 v15 > 49169 15 39MB 3kB 2m29.66 1m22.73 1d12h18 v18 > 49170 12 158MB 2kB m49.51 m11.68 1d12h18 v19 > 49174 41 647MB 21kB 5m19.56 1m02.99 11h16m34 v10 > 49175 33 489MB 20kB 3m29.60 m40.07 6h59m42 v01 > 49176 40 555MB 24kB 3m26.92 m41.36 6h59m22 v02 > 49177 33 484MB 19kB 3m21.93 m37.78 6h58m54 v03 > 49178 33 484MB 18kB 3m19.57 m38.10 6h58m33 v04 > 49179 46 795MB 50kB 5m29.05 1m48.18 6h58m20 v05 > 49180 39 504MB 20kB 3m10.16 m56.96 6h58m08 v06 > 49181 38 506MB 20kB 3m16.94 m38.14 6h57m48 v07 > 49182 33 483MB 18kB 3m18.24 m38.33 6h57m36 v08 > 49183 31 474MB 17kB 3m18.96 m37.63 6h57m24 v09 > 49184 19 111MB 3kB m02.93 m00.50 6h57m24 > 49185 23 179MB 6kB m03.54 m00.79 6h57m07 > 49186 29 429MB 13kB 2m15.02 m28.12 6h57m07 v11 > 49187 29 427MB 12kB m01.51 m00.80 6h56m55 > 49188 23 140MB 4kB 1m24.48 m25.44 6h56m54 v13 > 49189 27 455MB 16kB 2m13.71 m29.22 6h56m35 v14 > 49191 32 475MB 17kB 2m14.63 m27.78 6h56m16 v16 > 49192 26 154MB 6kB 2m11.79 m28.77 6h56m10 > 49194 26 454MB 14kB m03.47 m01.16 6h55m55 v20 > > As you can see, there are 24 vservers running (of 20 vservers). Whats > the Problem? This happend one minute before the master server (suse 9.0 > with 2.4.25 and vs1.26) crashed. > > Another thing I noticed about SuSE vservers running on a SuSE master > server, that the vserver can take over the local terminal, if this lines > are enabled in the /etc/inittab of a vserver: > 1:2345:respawn:/sbin/mingetty --noclear tty1 > 2:2345:respawn:/sbin/mingetty tty2 > 3:2345:respawn:/sbin/mingetty tty3 > 4:2345:respawn:/sbin/mingetty tty4 > 5:2345:respawn:/sbin/mingetty tty5 > 6:2345:respawn:/sbin/mingetty tty6 > > Thats my config file: > IPROOT="eth0:xxxxxxxxxxxx" > IPROOTDEV="eth0" > ONBOOT=yes > S_HOSTNAME=xxxxxxxxxxxxx > S_DOMAINNAME="xxxxxxxxxxxxx" > S_NICE= > ULIMIT="-HS -u 80" > S_CAPS="CAP_NET_RAW" > S_FLAGS="lock nproc fakeinit" > > How can I prevent it?
hmm, I'd try to update to 2.4.26 + vs1.27 just because I 'think' that some kernels issues (between 2.4.25 and 2.4.26) might be the reason, otherwise I'd check the hardware, as linux-vserver is _very_ stable in the stable branch ... best, Herbert > Cheers > Dimitri > > _______________________________________________ > Vserver mailing list > [EMAIL PROTECTED] > http://list.linux-vserver.org/mailman/listinfo/vserver _______________________________________________ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
