[Vserver] Apache Problem at Sunday morning
[Sun Mar 18 06:26:43 2007] [warn] child process 30762 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:43 2007] [warn] child process 30763 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:43 2007] [warn] child process 30764 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:43 2007] [warn] child process 30765 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:43 2007] [warn] child process 30767 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:43 2007] [warn] child process 367 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:43 2007] [warn] child process 21930 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 30762 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 30763 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 30764 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 30765 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 30767 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 367 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 21930 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:47 2007] [notice] caught SIGTERM, shutting down ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Apache Problem at Sunday morning
HI all, sry for double posting. In have a strange problem with apache2 : Each sunday morning between 5 a.m. and 7 a.m. some apache's in different vservers shutdown and do not come back. I'm running debian etch on the vservers and debian sid on the hosts. The silliest thing is that each Sunday these were different vservers. I only get the following message in apache's error log: [Sun Mar 18 06:26:43 2007] [warn] child process 30762 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:43 2007] [warn] child process 30763 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:43 2007] [warn] child process 30764 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:43 2007] [warn] child process 30765 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:43 2007] [warn] child process 30767 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:43 2007] [warn] child process 367 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:43 2007] [warn] child process 21930 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 30762 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 30763 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 30764 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 30765 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 30767 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 367 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 21930 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:47 2007] [notice] caught SIGTERM, shutting down Limit's weren't hit. I would be thankful for each hint. Best regards Oliver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Apache Problem at Sunday morning
On Sunday 18 March 2007 08:43, Cryptronic wrote: the first thing i would look at is what cron jobs are running in guests and also host on sunday mornings? it sounds like a cron.weekly script may be raising havoc? HI all, sry for double posting. In have a strange problem with apache2 : Each sunday morning between 5 a.m. and 7 a.m. some apache's in different vservers shutdown and do not come back. I'm running debian etch on the vservers and debian sid on the hosts. The silliest thing is that each Sunday these were different vservers. I only get the following message in apache's error log: [Sun Mar 18 06:26:43 2007] [warn] child process 30762 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:43 2007] [warn] child process 30763 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:43 2007] [warn] child process 30764 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:43 2007] [warn] child process 30765 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:43 2007] [warn] child process 30767 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:43 2007] [warn] child process 367 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:43 2007] [warn] child process 21930 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 30762 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 30763 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 30764 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 30765 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 30767 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 367 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:45 2007] [warn] child process 21930 still did not exit, sending a SIGTERM [Sun Mar 18 06:26:47 2007] [notice] caught SIGTERM, shutting down Limit's weren't hit. I would be thankful for each hint. Best regards Oliver ___ 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] Apache Problem at Sunday morning
On Sun, Mar 18, 2007 at 12:43:40PM +, Cryptronic wrote: HI all, sry for double posting. In have a strange problem with apache2 : Each sunday morning between 5 a.m. and 7 a.m. some apache's in different vservers shutdown and do not come back. [Sun Mar 18 06:26:43 2007] [warn] child process 30762 still did not exit, sending a SIGTERM I have the same on multiple Debian Sarge machines, running apache1.3 and apache2.0, not running any vserver patches. I'd say vserver unrelated. I bet each sunday morning between 5 and 7 your logrotation kicks in, and apache doesn't reload cleanly -- Debian unsolved bug for years; quickfix is a killall -9 apache2 then apache2ctl start in the logrotation script. A bug was filed on apache on the BTS (not by me) but I can't find it back. Tom ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Vserver CPU limit question
On Sat, Mar 17, 2007 at 10:17:47PM -0700, Albert Mak (almak) wrote: Hi Herbert Here is the output of /proc/virtual/2/status as requested Both context 2 and 3 have the same setting. -bash-2.05b# cat /proc/virtual/2/status UseCnt: 7 Tasks: 2 Flags: 000202020210 ~~ http://linux-vserver.org/Capabilities_and_Flags 0100 sched_hard 0200 sched_prio so you haven't enabled sched_hard here, which explains why you do not see hard scheduling behaviour :) HTC, Herbert BCaps: 354c24ff CCaps: 0101 Ticks: 0 Thanks. -Albert -Original Message- From: Herbert Poetzl [mailto:[EMAIL PROTECTED] Sent: Saturday, March 17, 2007 11:36 AM To: Albert Mak (almak) Cc: vserver@list.linux-vserver.org Subject: Re: [Vserver] Vserver CPU limit question On Fri, Mar 16, 2007 at 06:54:26PM -0700, Albert Mak (almak) wrote: Hi, I have Linux (2.6.14.3 Kernel) with Vserver 2.0.1 and testing the CPU limit capabilities. I have 2 vserver contexts both running CPU intensive app capable of using up 100% CPU, I am setting up on vserver to limit 1 context to 10% CPU and the 2nd to 80% CPU, both using flags sched_prio. I am seeing CPU usage split 50/50 between the 2 contexts. I repeated the same test using sched_hard with the same result (kernel VSERVER_HARDCPU config set to y). I am expecting to see at least the CPU usage close to the Vserver limits. Have I got the wrong settings or some other issues. Your help is really appreciated. -Albert top - 18:37:04 up 26 min, 1 user, load average: 2.04, 1.40, 0.62 Tasks: 127 total, 3 running, 124 sleeping, 0 stopped, 0 zombie Cpu(s): 98.7% us, 1.3% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi, 0.0% si Mem:513084k total, 115660k used, 397424k free,10200k buffers Swap:0k total,0k used,0k free,39332k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 6616 root 20 0 1332 228 184 R 49.8 0.0 2:23.12 exceed_cpu_limi 6513 root 20 0 1336 232 184 R 48.1 0.0 2:43.79 exceed_cpu_limi -bash-2.05b# vps PID CONTEXT TTY TIME CMD 3672 0 MAIN pts/000:00:00 bash 6513 2 APP1 pts/000:03:01 exceed_cpu_limi 6616 3 APP2 pts/000:02:40 exceed_cpu_limi 7655 1 ALL_PROC pts/000:00:00 vps 7656 1 ALL_PROC pts/000:00:00 ps -bash-2.05b# pwd /etc/vservers/APP1 -bash-2.05b# cat flags sched_prio you want to add sched_hard here if you want hard scheduling, the prio scheduler will only adjust priorities according to the token buckets ... I'd also suggest to use a more recent kernel (and probably Linux-VServer patch) than this one as the scheduler was enhanced quite a lot in 2.2.x -bash-2.05b# cat schedule 80 100 200 50 140 dummy -bash-2.05b# pwd /etc/vservers/APP2 -bash-2.05b# cat flags sched_prio -bash-2.05b# cat schedule 10 100 200 50 140 dummy -bash-2.05b# cat /proc/virtual/2/sched Token: 140 FillRate: 1 Interval:100 TokensMin:50 TokensMax: 140 PrioBias: 0 VaVaVoom: -5 cpu 0: 229674 71 0 -bash-2.05b# cat /proc/virtual/3/sched Token: 140 FillRate: 10 Interval:100 TokensMin:50 TokensMax: 140 PrioBias: 0 VaVaVoom: -5 cpu 0: 217275 54 0 looks like none of the token buckets is active here, what does the /proc/virtual/2/status show? TIA, Herbert ___ 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] Apache Problem at Sunday morning
Hi all, thanks you two, I think this is a very possible thing ;) I patched all the logrotate files. Thanks for the hints. best regards Oliver Tom Laermans schrieb: On Sun, Mar 18, 2007 at 12:43:40PM +, Cryptronic wrote: HI all, sry for double posting. In have a strange problem with apache2 : Each sunday morning between 5 a.m. and 7 a.m. some apache's in different vservers shutdown and do not come back. [Sun Mar 18 06:26:43 2007] [warn] child process 30762 still did not exit, sending a SIGTERM I have the same on multiple Debian Sarge machines, running apache1.3 and apache2.0, not running any vserver patches. I'd say vserver unrelated. I bet each sunday morning between 5 and 7 your logrotation kicks in, and apache doesn't reload cleanly -- Debian unsolved bug for years; quickfix is a killall -9 apache2 then apache2ctl start in the logrotation script. A bug was filed on apache on the BTS (not by me) but I can't find it back. Tom ___ 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] Re: about Vserver for ARM
Hi Herbert, Thanks! I can build vserver for ARM successfully with your approach, but how to use make install to install those verser related files to corrosponding directory in rootfs? For example, my rootfs is under /work/rootfs/opie, how can I install vserver to this directory? Actually I want to use a binary make for ARM to run make install on the phone, but I failed to get the ARM version make. Any ideas? Thanks, Wenbin On 3/13/07, Herbert Poetzl [EMAIL PROTECTED] wrote: On Tue, Mar 13, 2007 at 01:45:56AM -0400, Wenbin Zhang wrote: Hi Herbert, Now I merged Vserver code and OpenEZX code, and compile the kernel with vserver code successfully. However, according to http://linux-vserver.org/Installation_on_Linux_2.6 , we still need compile util-vserver, which is user land tool for vserver. I download the util-vserver code, want to cross-compile it with arm-linux-gcc. But I tried below command: # ./configure --target=arm-linux --prefix=/ I expect to generate a ARM version Makefile. However, the generated Makefile is still for x86 gcc version. What's wrong with my process? Any ideas? if you have a proper cross compile toolchain (if not, you can get one from me), try the following: export ARCH=arm export CC=arm-linux-gcc export CPP=arm-linux-cpp export CXX=arm-linux-c++ export DIET=arm-linux-diet then do: ./configure --prefix= and make if your toolchain is working correctly, that should build you a proper util-vserver toolset for arm note that you might have to comment out the warning line in the alternative syscall implementation like this: // #warning syscall arch arm not tested yet best, Herbert Thank you, Wenbin ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] how to make default system running on the top of one vserver?
Hello Guys, I have one question here, how to make default system running on the top of one vserver? That is: - vserver --- host linux hardware --- 1) I setup one server on the default host system.( Both the host system and the verser are linux). 2) After the machine power on and boot, the whole thing will be taken over by the vserver, say, the GUI display, the input are controlled by vserver automatically. After boot, the user were not expected to use the host linux again. 3) But the display/input control still can be switched to the host linux in case of need. After using, the control will be able to switch back to vserver. Any good idea to achieve this? Thanks, Wenbin ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
