Re: [Vserver] behavior i have never seen before

2007-04-30 Thread Chuck
On Monday 30 April 2007 13:30, Herbert Poetzl wrote:

i just found what it was about 30 min ago. turns out the object module loaded 
in nagios that shares data with the npc plugin in cacti is a bit fussy and if 
something goes slightly odd with it, it would lose its mysql connection, go 
dormant and remove nagios from the process list yet nagios would run but not 
interface with the module any more, nor would it have the pid assigned to it.

the real culprit was not enough memory allocated to the various mysql options, 
especially innodb. :)

sorry for the 'noise' on here, its just i had never ever seen this happen 
before. it is all fixed and working properly now and visible in ps. :)

thanks!

> On Sun, Apr 29, 2007 at 07:46:46PM -0400, Chuck wrote:
> > 
> > it just started today. has been behaving before this. i have a vserver 
> > configured to run cacti and nagios. oddly nagios runs, but does not show 
in 
> > the process listing using ps ax. it once did. when i go to stop it with 
the 
> > init scrip it says it cannot find the pid but if i run the init with stop 
> > once more it stops it and it truly does.
> > 
> > it appears to be hiding somehow and it appears to function normally.
> > 
> > any clues? i don't know if this is an o/s problem that just developed or a 
> > vserver situation or  a nagios configuration that i may have messed up 
> > accidently or what.. stopping and starting the vserver does not make it 
> > appear in the process listing although it is running.
> > 
> > im running gentoo on the host amd64
> > 
> > 2.6.19-vs2.2.0-rc2
> 
> let's try the final version (vs2.2.0) with a recent
> 2.6.19.7 kernel first, and see if the issue remains
> 
> > util-vserver-0.30.212-r2
> 
> won't hurt to try one of the 0.30.213 release candidates
> too, just to make sure ...
> 
> TIA,
> Herbert
> 
> > and a gentoo amd64 guest.
> > 
> > -- 
> > 
> > Chuck
> > ___
> > Vserver mailing list
> > Vserver@list.linux-vserver.org
> > http://list.linux-vserver.org/mailman/listinfo/vserver
> 

-- 

Chuck

"...and the hordes of M$*ft users descended upon me in their anger,
and asked 'Why do you not get the viruses or the BlueScreensOfDeath
or insecure system troubles and slowness or pay through the nose 
for an OS as *we* do?!!', and I answered...'I use Linux'. "
The Book of John, chapter 1, page 1, and end of book


___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] anybody has experience for Vserver on ARM

2007-04-30 Thread Wenbin Zhang

yes, i got the warning message while compile vcmd:

[EMAIL PROTECTED] vcmd-0.08]# make
arm-angstrom-linux-gnueabi-gcc -g -Wall -O2 -Ivserver -o vcmd vcmd.c
In file included from vserver.h:4,
from vcmd.c:34:
syscall.h:110:2: warning: #warning syscall arch arm not tested yet
.

Seems the syscall does not tested on ARM. Anybody make vserver successfully
on ARM? Thank you so much!

Thanks,
Wenbin


On 4/30/07, Herbert Poetzl <[EMAIL PROTECTED]> wrote:


On Sun, Apr 29, 2007 at 05:30:45PM -0400, Wenbin Zhang wrote:
> Actually I think the syscall error is because of strace on ARM, not
because
> of vcmd.
> [EMAIL PROTECTED]:/work/test# ./vcmd
> wenbin print: num_cmd = 0, num_id = 0
> Illegal instruction
>
> [EMAIL PROTECTED]:/work/test# strace -fF -o vcmd.trace ./vcmd
> syscall: unknown syscall trap 0xef000139
>
> "unknow syscall" should be a strace bug, I think. The basic failure is
> becuase of "illegal instruction" during vserver(num_cmd, num_id, data)
> syscall.

well, the syscall trap looks fine, 313 is the syscall
on arm and it seems that util-vserver uses the same
implementation, so that should be fine too ...

you might get a warning at compile time, if that would
be interesting to have, otherwise something with your
toolchain could be wrong ...

best,
Herbert

> Thanks,
> Wenbin
>
>
> On 4/29/07, Wenbin Zhang <[EMAIL PROTECTED]> wrote:
> >
> >I traced the vcmd command. When the vcmd command is run and without
> >arguments, the error is:
> >syscall: unknown syscall trap 0xef000139
> >
> >This syscall error is occured while "num_ret = vserver(num_cmd, num_id,
> >data);" is executed. I guss ARM is using a different method to register
new
> >syscall?
> >
> >Thanks,
> >Wenbin
> >
> >
> >On 4/29/07, Herbert Poetzl <[EMAIL PROTECTED]> wrote:
> >>
> >> On Fri, Apr 27, 2007 at 01:02:34PM -0400, Wenbin Zhang wrote:
> >> > Hello, guys,
> >> >
> >> > This time I build a new Vserver enabled kernel and GPE package, now
> >> solved
> >> > the "Illegal instruction" on ARM.
> >> > But I tried "vcmd -i 42 -C ctx_create -- ps auxwww", it just simply
> >> > hung (but I can interrupt the command).
> >> > Any approach to solve this?
> >>
> >> strace -fF -o vcmd.trace vcmd
> >>
> >> > Btw, I tried below command for the vserver kernel, seems OK.
> >> > 1)[EMAIL PROTECTED]:/work/vcmd-0.08# cat /proc/virtual/info
> >> > VCIVersion: 0002:0002
> >> > VCISyscall: 313
> >> > VCIKernel:  0336
> >> >
> >> > 2) [EMAIL PROTECTED]:/work/vcmd-0.08# setattr --~hide /proc/uptime
> >> >
> >> > 3) [EMAIL PROTECTED]:/work/vcmd-0.08# vserver-stat
> >> > CTX   PROCVSZRSS  userTIME   sysTIMEUPTIME NAME
> >> > 0   49 165.9M  63.9M   0m55s76   0m24s19  10m14s64 root server
> >> >
> >> > 4) [EMAIL PROTECTED]:/work/vcmd-0.08# vserver-info
> >> > Versions:
> >> >   Kernel: 2.6.16.13-vs2.0.3-rc1
> >> >   VS-API: 0x00020002
> >> > util-vserver: 0.30.212; Apr 17 2007, 18:47:18
> >> >
> >> > Features:
> >> >   CC: arm-angstrom-linux-gnueabi-gcc,
> >> > arm-angstrom-linux-gnueabi-gcc (GCC) 4.1.1
> >> >  CXX: arm-angstrom-linux-gnueabi-c++,
> >> > arm-angstrom-linux-gnueabi-c++ (GCC) 4.1.1
> >> > CPPFLAGS: ''
> >> >   CFLAGS: '-g -O2 -std=c99 -Wall -pedantic -W
> >> > -funit-at-a-time'
> >> > CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W
> >> > -fmessage-length=0 -funit-at-a-time'
> >> >   build/host: i686-pc-linux-gnu/arm-unknown-none
> >> > Use dietlibc: no (you have been warned)
> >> ~
> >>
> >> >   Build C++ programs: yes
> >> >   Build C99 programs: yes
> >> >   Available APIs: v13,net,v21
> >> >ext2fs Source: kernel
> >> >syscall(2) invocation: traditional
> >> >  vserver(2) syscall#: 313/fallback
> >> >
> >> > Paths:
> >> >   prefix:
> >> >sysconf-Directory: ${prefix}/etc
> >> >cfg-Directory: ${prefix}/etc/vservers
> >> > initrd-Directory: $(sysconfdir)/init.d
> >> >   pkgstate-Directory: ${prefix}/var/run/vservers
> >> >  vserver-Rootdir: /vservers
> >> >
> >> > Assumed 'SYSINFO' as no other option given; try '--help' for more
> >> > information.
> >> >
> >> > Seems everything is fine, but why vcmd cannot be run correctly?
> >>
> >> no idea, maybe a broken toolchain?
> >>
> >> best,
> >> Herbert
> >>
> >> > (I can run vcmd correctly on my PC machine)
> >> >
> >> > Thanks,
> >> > Wenbin
> >> >
> >> > On 4/27/07, Wenbin Zhang <[EMAIL PROTECTED]> wrote:
> >> > >
> >> > >
> >> > >
> >> > >On 4/26/07, Herbert Poetzl < [EMAIL PROTECTED]> wrote:
> >> > >>
> >> > >> On Wed, Apr 25, 2007 at 12:40:12AM -0400, Wenbin Zhang wrote:
> >> > >> > >
> >> > >> > >
> >> > >> > >> vcmd -i 42 -C ctx_create -- ps auxwww
> >> > >> > >> vserver: ret = 0x002A (42)
> >> > >> > >> USER   PID %CPU %MEMVSZ   RSS TTY  ST

Re: [Vserver] behavior i have never seen before

2007-04-30 Thread Herbert Poetzl
On Sun, Apr 29, 2007 at 07:46:46PM -0400, Chuck wrote:
> 
> it just started today. has been behaving before this. i have a vserver 
> configured to run cacti and nagios. oddly nagios runs, but does not show in 
> the process listing using ps ax. it once did. when i go to stop it with the 
> init scrip it says it cannot find the pid but if i run the init with stop 
> once more it stops it and it truly does.
> 
> it appears to be hiding somehow and it appears to function normally.
> 
> any clues? i don't know if this is an o/s problem that just developed or a 
> vserver situation or  a nagios configuration that i may have messed up 
> accidently or what.. stopping and starting the vserver does not make it 
> appear in the process listing although it is running.
> 
> im running gentoo on the host amd64
> 
> 2.6.19-vs2.2.0-rc2

let's try the final version (vs2.2.0) with a recent
2.6.19.7 kernel first, and see if the issue remains

> util-vserver-0.30.212-r2

won't hurt to try one of the 0.30.213 release candidates
too, just to make sure ...

TIA,
Herbert

> and a gentoo amd64 guest.
> 
> -- 
> 
> Chuck
> ___
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] anybody has experience for Vserver on ARM

2007-04-30 Thread Herbert Poetzl
On Sun, Apr 29, 2007 at 05:30:45PM -0400, Wenbin Zhang wrote:
> Actually I think the syscall error is because of strace on ARM, not because
> of vcmd.
> [EMAIL PROTECTED]:/work/test# ./vcmd
> wenbin print: num_cmd = 0, num_id = 0
> Illegal instruction
> 
> [EMAIL PROTECTED]:/work/test# strace -fF -o vcmd.trace ./vcmd
> syscall: unknown syscall trap 0xef000139
> 
> "unknow syscall" should be a strace bug, I think. The basic failure is
> becuase of "illegal instruction" during vserver(num_cmd, num_id, data)
> syscall.

well, the syscall trap looks fine, 313 is the syscall
on arm and it seems that util-vserver uses the same
implementation, so that should be fine too ...

you might get a warning at compile time, if that would
be interesting to have, otherwise something with your
toolchain could be wrong ...

best,
Herbert

> Thanks,
> Wenbin
> 
> 
> On 4/29/07, Wenbin Zhang <[EMAIL PROTECTED]> wrote:
> >
> >I traced the vcmd command. When the vcmd command is run and without
> >arguments, the error is:
> >syscall: unknown syscall trap 0xef000139
> >
> >This syscall error is occured while "num_ret = vserver(num_cmd, num_id,
> >data);" is executed. I guss ARM is using a different method to register new
> >syscall?
> >
> >Thanks,
> >Wenbin
> >
> >
> >On 4/29/07, Herbert Poetzl <[EMAIL PROTECTED]> wrote:
> >>
> >> On Fri, Apr 27, 2007 at 01:02:34PM -0400, Wenbin Zhang wrote:
> >> > Hello, guys,
> >> >
> >> > This time I build a new Vserver enabled kernel and GPE package, now
> >> solved
> >> > the "Illegal instruction" on ARM.
> >> > But I tried "vcmd -i 42 -C ctx_create -- ps auxwww", it just simply
> >> > hung (but I can interrupt the command).
> >> > Any approach to solve this?
> >>
> >> strace -fF -o vcmd.trace vcmd
> >>
> >> > Btw, I tried below command for the vserver kernel, seems OK.
> >> > 1)[EMAIL PROTECTED]:/work/vcmd-0.08# cat /proc/virtual/info
> >> > VCIVersion: 0002:0002
> >> > VCISyscall: 313
> >> > VCIKernel:  0336
> >> >
> >> > 2) [EMAIL PROTECTED]:/work/vcmd-0.08# setattr --~hide /proc/uptime
> >> >
> >> > 3) [EMAIL PROTECTED]:/work/vcmd-0.08# vserver-stat
> >> > CTX   PROCVSZRSS  userTIME   sysTIMEUPTIME NAME
> >> > 0   49 165.9M  63.9M   0m55s76   0m24s19  10m14s64 root server
> >> >
> >> > 4) [EMAIL PROTECTED]:/work/vcmd-0.08# vserver-info
> >> > Versions:
> >> >   Kernel: 2.6.16.13-vs2.0.3-rc1
> >> >   VS-API: 0x00020002
> >> > util-vserver: 0.30.212; Apr 17 2007, 18:47:18
> >> >
> >> > Features:
> >> >   CC: arm-angstrom-linux-gnueabi-gcc,
> >> > arm-angstrom-linux-gnueabi-gcc (GCC) 4.1.1
> >> >  CXX: arm-angstrom-linux-gnueabi-c++,
> >> > arm-angstrom-linux-gnueabi-c++ (GCC) 4.1.1
> >> > CPPFLAGS: ''
> >> >   CFLAGS: '-g -O2 -std=c99 -Wall -pedantic -W
> >> > -funit-at-a-time'
> >> > CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W
> >> > -fmessage-length=0 -funit-at-a-time'
> >> >   build/host: i686-pc-linux-gnu/arm-unknown-none
> >> > Use dietlibc: no (you have been warned)
> >> ~
> >>
> >> >   Build C++ programs: yes
> >> >   Build C99 programs: yes
> >> >   Available APIs: v13,net,v21
> >> >ext2fs Source: kernel
> >> >syscall(2) invocation: traditional
> >> >  vserver(2) syscall#: 313/fallback
> >> >
> >> > Paths:
> >> >   prefix:
> >> >sysconf-Directory: ${prefix}/etc
> >> >cfg-Directory: ${prefix}/etc/vservers
> >> > initrd-Directory: $(sysconfdir)/init.d
> >> >   pkgstate-Directory: ${prefix}/var/run/vservers
> >> >  vserver-Rootdir: /vservers
> >> >
> >> > Assumed 'SYSINFO' as no other option given; try '--help' for more
> >> > information.
> >> >
> >> > Seems everything is fine, but why vcmd cannot be run correctly?
> >>
> >> no idea, maybe a broken toolchain?
> >>
> >> best,
> >> Herbert
> >>
> >> > (I can run vcmd correctly on my PC machine)
> >> >
> >> > Thanks,
> >> > Wenbin
> >> >
> >> > On 4/27/07, Wenbin Zhang <[EMAIL PROTECTED]> wrote:
> >> > >
> >> > >
> >> > >
> >> > >On 4/26/07, Herbert Poetzl < [EMAIL PROTECTED]> wrote:
> >> > >>
> >> > >> On Wed, Apr 25, 2007 at 12:40:12AM -0400, Wenbin Zhang wrote:
> >> > >> > >
> >> > >> > >
> >> > >> > >> vcmd -i 42 -C ctx_create -- ps auxwww
> >> > >> > >> vserver: ret = 0x002A (42)
> >> > >> > >> USER   PID %CPU %MEMVSZ   RSS TTY  STAT START
> >> TIME
> >> > >> COMMAND
> >> > >> > >> root 11780   0.0  0.0   1944   672 pts/2R+   13:35
> >> 0:00 ps
> >> > >> > >> auxwww
> >> > >> > >>
> >> > >> > >I downloaded the vcmd source, and crosscompiled it, then copy to
> >> the
> >> > >> ARM
> >> > >> > phone, however, when I tried to run the command, it cannot create
> >> the
> >> > >> > process successfully, very strange...
> >> > >> > when I run "vcmd -h", it can show the help, but  when I run