Page 1 of 2
kernel: VM: killing process
Posted: 2005-07-08 08:18
by as-n
Hallo,
jetzt hat es mienen Server wieder erwischt:
Code: Select all
Jul 7 18:52:10 h9284 kernel: grsec: From 66.249.68.133: signal 11 sent to /usr/sbin/httpd2-prefork[httpd2-prefork:32310] uid/euid:30/30 gid/egid:8/8, parent /usr/sbin/httpd2-prefork[httpd2-prefork:6249] uid/euid:0/0 gid/egid:0/0
Jul 7 18:52:10 h9284 kernel: grsec: From 66.249.68.133: denied resource overstep by requesting 8392704 for RLIMIT_STACK against limit 8388608 for /usr/sbin/httpd2-prefork[httpd2-prefork:32310] uid/euid:30/30 gid/egid:8/8, parent /usr/sbin/httpd2-prefork[httpd2-prefork:6249] uid/euid:0/0 gid/egid:0/0
Jul 7 18:52:10 h9284 kernel: grsec: From 66.249.68.133: signal 11 sent to /usr/sbin/httpd2-prefork[httpd2-prefork:32310] uid/euid:30/30 gid/egid:8/8, parent /usr/sbin/httpd2-prefork[httpd2-prefork:6249] uid/euid:0/0 gid/egid:0/0
Jul 7 18:52:10 h9284 kernel: grsec: From 66.249.68.133: denied resource overstep by requesting 8392704 for RLIMIT_STACK against limit 8388608 for /usr/sbin/httpd2-prefork[httpd2-prefork:32310] uid/euid:30/30 gid/egid:8/8, parent /usr/sbin/httpd2-prefork[httpd2-prefork:6249] uid/euid:0/0 gid/egid:0/0
Jul 7 18:52:10 h9284 kernel: grsec: more alerts, logging disabled for 10 seconds
Jul 8 00:00:10 h9284 kernel: grsec: time set by /usr/sbin/ntpdate[ntpdate:2742] uid/euid:0/0 gid/egid:0/0, parent /bin/bash[sh:17267] uid/euid:0/0 gid/egid:0/0
Jul 8 00:40:44 h9284 kernel: VM: killing process httpd2-prefork
Jul 8 00:41:34 h9284 kernel: VM: killing process httpd2-prefork
Jul 8 00:42:17 h9284 kernel: VM: killing process mysqld
Jul 8 00:42:23 h9284 kernel: VM: killing process httpd2-prefork
Jul 8 00:57:53 h9284 kernel: VM: killing process httpd2-prefork
Jul 8 00:58:03 h9284 kernel: VM: killing process httpd2-prefork
Jul 8 00:58:10 h9284 kernel: VM: killing process mcat /proc/mysqld
Jul 8 00:58:12 h9284 kernel: VM: killing process mysqld
Jul 8 00:58:16 h9284 kernel: VM: killing process httpd2-prefork
Ich weiß bloß nicht warum:
Code: Select all
cat /proc/meminfo
total: used: free: shared: buffers: cached:
Mem: 526393344 501358592 25034752 0 22106112 226082816
Swap: 526409728 43900928 482508800
MemTotal: 514056 kB
MemFree: 24448 kB
MemShared: 0 kB
Buffers: 21588 kB
Cached: 184592 kB
SwapCached: 36192 kB
Active: 110204 kB
Inactive: 133080 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 514056 kB
LowFree: 24448 kB
SwapTotal: 514072 kB
SwapFree: 471200 kB
Un um die Uhrzeit dürfte doch auch nicht gar so viel los sein, lediglich srv-report läuft da, aber kann das daran liegen?
Kernel ist Linux h9284 2.4.31-grsec #1 SMP Di Jul 5 10:59:54 CEST 2005 i686 i686 i386 GNU/Linux.
Was könnte ich da noch schauen?
Ciao
AS-N
Re: kernel: VM: killing process
Posted: 2005-07-08 08:53
by captaincrunch
Dein Apache hat versucht, einen Bereich auf dem Stack zu allokieren, der größer als erlaubt ist. 8 MB sind schließlich auch schon eine ganze Menge Holz. Vielleicht schaust du mal, auf was zu diesem Zeitpunkt zugegriffen wird, so dass abschätzbar wäre, was der Indianer da gerade so treibt.
Re: kernel: VM: killing process
Posted: 2005-07-08 09:19
by as-n
Naja, das ist der googlebot der das immer auslöst, aber der ist schon immer fast ständig bei uns unterwegs, ist auch recht so.
Dürfte also die mysql sein, die zu der Zeit vertärkt in Gebrauch ist, da ist ein osCommerce shop drauf und mit dem googlebot kommen da schon einige Zugriffe zustande.
Was mich aber eigentlich wundert ist, dass VM dann urplötzlich um kurz vor 1:00 anfängt den apachen und die mysql zu killen, obwohl da sonst keinerlei Meldung mehr dazu steht, heute früh war da sogar eine Tabelle in der db kaputt deshalb.
Ciao
AS-N
Re: kernel: VM: killing process
Posted: 2005-07-08 11:25
by Joe User
AS-N wrote:Naja, das ist der googlebot der das immer auslöst, aber der ist schon immer fast ständig bei uns unterwegs, ist auch recht so.
Als kleinen Workaround kannst Du folgende Zeile ans Ende der robots.txt setzen, dadurch wird (nicht nur) der Googlebot etwas ausgebremst, indem er zwischen jedem Zugriff eine Zwangspause von 1 Sekunde einlegt:
Re: kernel: VM: killing process
Posted: 2005-07-12 11:39
by as-n
Es hat wieder zugeschlagen, jetzt ging gar nichts mehr:
Code: Select all
Jul 12 10:09:11 h9284 postfix/master[14529]: warning: process /usr/lib/postfix/trivial-rewrite pid 6812 killed by signal 9
Jul 12 10:09:11 h9284 postfix/master[14529]: warning: /usr/lib/postfix/trivial-rewrite: bad command startup -- throttling
Jul 12 10:09:11 h9284 postfix/master[14529]: warning: process /usr/lib/postfix/smtpd pid 6808 killed by signal 9
Jul 12 10:09:11 h9284 postfix/master[14529]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Jul 12 10:09:21 h9284 postfix/master[14529]: warning: process /usr/lib/postfix/tlsmgr pid 8705 killed by signal 9
Jul 12 10:14:30 h9284 kernel: VM: killing process php
Jul 12 10:14:30 h9284 kernel: VM: killing process trivial-rewrite
Jul 12 10:14:30 h9284 kernel: VM: killing process smtpd
Jul 12 10:14:30 h9284 kernel: VM: killing process confixx_counter
Jul 12 10:14:30 h9284 kernel: VM: killing process tlsmgr
Jul 12 10:14:40 h9284 kernel: VM: killing process php
Jul 12 10:14:40 h9284 kernel: VM: killing process popper
Jul 12 10:14:43 h9284 kernel: VM: killing process xinetd
Jul 12 10:14:43 h9284 kernel: VM: killing process sh
Jul 12 10:14:43 h9284 kernel: VM: killing process popper
Jul 12 10:14:43 h9284 kernel: VM: killing process mysqld
Jul 12 10:14:43 h9284 kernel: VM: killing process httpd2-prefork
Jul 12 10:14:43 h9284 kernel: VM: killing process confixx_counter
Jul 12 10:14:43 h9284 kernel: VM: killing process httpd2-prefork
Jul 12 10:14:43 h9284 kernel: VM: killing process httpd2-prefork
Jul 12 10:14:43 h9284 kernel: VM: killing process rotate.pl
Jul 12 10:15:03 h9284 postfix/master[14529]: warning: unix_trigger_event: read timeout for service private/tlsmgr
Jul 12 10:19:48 h9284 postfix/pickup[13622]: fatal: watchdog timeout
Jul 12 10:20:55 h9284 postfix/master[14529]: warning: process /usr/lib/postfix/pickup pid 13622 exit status 1
Jul 12 10:28:03 h9284 sshd[6938]: fatal: ssh-rand-helper child produced insufficient data
Jul 12 10:42:22 h9284 postfix/master[14529]: warning: unix_trigger_event: read timeout for service public/flush
Jul 12 10:43:39 h9284 kernel: VM: killing process cron
Jul 12 10:43:39 h9284 kernel: VM: killing process confixx_counter
Jul 12 10:43:50 h9284 kernel: VM: killing process perl
Jul 12 10:49:07 h9284 kernel: VM: killing process sh
Jul 12 10:49:07 h9284 kernel: VM: killing process perl
Jul 12 10:49:58 h9284 kernel: VM: killing process php
Jul 12 10:49:58 h9284 kernel: VM: killing process httpd2-prefork
Jul 12 10:49:51 h9284 postfix/master[14529]: warning: unix_trigger_event: read timeout for service private/tlsmgr
Jul 12 10:52:04 h9284 kernel: VM: killing process smtpd
Jul 12 10:52:10 h9284 kernel: VM: killing process httpd2-prefork
Jul 12 10:52:14 h9284 postfix/master[14529]: warning: process /usr/lib/postfix/smtpd pid 7081 killed by signal 9
Jul 12 10:52:36 h9284 kernel: VM: killing process amavisd
Jul 12 10:56:52 h9284 kernel: VM: killing process sh
Jul 12 10:56:52 h9284 kernel: VM: killing process confixx_counter
Jul 12 10:56:52 h9284 kernel: VM: killing process confixx_counter
Jul 12 10:59:18 h9284 postfix/smtpd[6841]: warning: network_biopair_interop: error reading 5 bytes from the network: Connection reset by peer
Jul 12 10:59:27 h9284 postfix/master[14529]: warning: unix_trigger_event: read timeout for service public/flush
Jul 12 11:01:27 h9284 kernel: VM: killing process bounce
Jul 12 11:01:19 h9284 postfix/master[14529]: warning: process /usr/lib/postfix/bounce pid 7331 killed by signal 9
Jul 12 11:02:08 h9284 postfix/master[14529]: warning: process /usr/lib/postfix/smtpd pid 6841 killed by signal 9
Jul 12 11:04:43 h9284 kernel: VM: killing process pipelog.pl
Jul 12 11:05:00 h9284 kernel: VM: killing process httpd2-prefork
Jul 12 11:05:22 h9284 kernel: VM: killing process smtpd
Jul 12 11:05:22 h9284 kernel: VM: killing process qmgr
Jul 12 11:05:27 h9284 kernel: VM: killing process confixx_counter
Jul 12 11:05:27 h9284 kernel: VM: killing process run-crons
Jul 12 11:07:19 h9284 kernel: VM: killing process confixx_counter
Jul 12 11:04:09 h9284 postfix/master[14529]: warning: process /usr/lib/postfix/qmgr pid 31063 killed by signal 9
Jul 12 11:12:01 h9284 syslogd: select: Cannot allocate memory
Jul 12 11:09:50 h9284 kernel: VM: killing process httpd2-prefork
Jul 12 11:10:19 h9284 kernel: VM: killing process rotate.pl
Jul 12 11:12:57 h9284 kernel: VM: killing process httpd2-prefork
Jul 12 11:14:34 h9284 postfix/master[14529]: warning: unix_trigger_event: read timeout for service private/tlsmgr
Jul 12 11:15:03 h9284 postfix/master[14529]: warning: process /usr/lib/postfix/flush pid 7367 killed by signal 9
Jul 12 11:15:08 h9284 postfix/master[14529]: warning: /usr/lib/postfix/flush: bad command startup -- throttling
Jul 12 11:17:46 h9284 kernel: VM: killing process flush
Jul 12 11:18:50 h9284 kernel: VM: killing process httpd2-prefork
Jul 12 11:24:39 h9284 kernel: Warning: null TTY for (88:04) in tty_fasync
Was könnte das denn sein?
Wo kann ich da noch nachforschen?
Ciao
AS-N
Re: kernel: VM: killing process
Posted: 2005-07-12 15:59
by Joe User
Wann und wie steigt der vanilla-Kernel aus?
Re: kernel: VM: killing process
Posted: 2005-07-12 16:30
by as-n
Hallo,
Vanilla-Kernel? Zur Zeit habe ich den Standart 2.4.29 Kernel von Strato drauf, da ich zuerst meinen gresc-gepatchten 2.4.31 in Verdacht hatte, aber es scheint nicht daran zu liegen.
Es handelt sich im Ã?brigen um eine SuSE9.0.
Der Apache hat da gerade folgendes gemacht:
Code: Select all
66.249.68.142 - - [12/Jul/2005:11:11:10 +0200] "GET /catalog/product_info.php/name/Aranjuez%20Classic%20Gold%20A%20600/products_id/allprods.php/language/es HTTP/1.0" 200 262 "-" "Googlebot/2.1 (+http://www.googlebot.com/bot.html)"
69.14.233.10 - - [12/Jul/2005:11:25:10 +0200] "GET /catalog/images/flatwound.jpg HTTP/1.1" 200 11390 "http://www.wholenote.com/fretbuzz/fbmsg.asp?i=344748&n=Equipment&t=2&th=344378" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; eBook; .NET CLR 1.1.4322)"
Es scheint also, dass er beim Versuch gestorben ist die Datei allprods.php anzuzeigen.
Das kann ich mir sogar vorstellen, denn die ist rießig und ich hatte testweise gzip aktiviert.
Vielleicht war das einfach zu viel für den Kasten?
Ciao
AS-N
Re: kernel: VM: killing process
Posted: 2005-07-12 18:23
by lufthansen
hi ich habe das gleiche problem mit dem std. 2.4.29 von strato.
das letzte wa sich beim letzten mal sehen konnte war ein load von 24-30 und das mein sftp und mc prozess beide so um die 256 mb (!) in anspruch genommen haben, das kann die anderen male aber nicht so gewesen sein weil da keiner eingelogt war, ich werde nacher mal auf nen aktuellen kernel updaten und dann noch mal gucken.
Re: kernel: VM: killing process
Posted: 2005-07-12 23:49
by lufthansen
also um noch ein bißchen verwirrung zu stiften =)
ich habe vorhin im _resuce_ sys ein kernel packet entpackt und dann bekam ich folgenden fehler ....
__alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
VM: killing process tar
Killed
das heißt für mich hardwar putt oder aber eine generel unverträglichkeit mit der hardware wobei ich imo nicht sagen kann welcher kernel in dem resuce system lief.
Re: kernel: VM: killing process
Posted: 2005-07-13 01:03
by thomas80
Hallo,
hier mal ein unschöner Auszug aus meiner /var/log/messages:
Code: Select all
Jul 12 03:03:35 XXX kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Jul 12 03:03:35 XXX kernel: VM: killing process spamd
Jul 12 03:11:23 XXX kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Jul 12 03:11:26 XXX kernel: VM: killing process apache2
Jul 12 03:18:13 XXX kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Jul 12 03:18:14 XXX kernel: VM: killing process sh
Jul 12 03:18:51 XXX kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Jul 12 03:18:52 XXX kernel: VM: killing process tor
Jul 12 03:22:45 XXX kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Jul 12 03:22:45 XXX kernel: VM: killing process spamd
Jul 12 03:22:55 XXX kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Jul 12 03:22:55 XXX kernel: VM: killing process spamd
Das ganze hat am 10. Juli angefangen und dann sporadisch Prozesse gekillt. Wie man sieht, ist nicht nur ein Programm betroffen.
Kernel ist 2.4.31-grsec (von CC), RBAC habe ich jetzt mal deaktiviert. Server steht bei netdirekt.
Weiss einer was? Werde morgen mal einen aktuellen 2.6er (Vanilla) kompilieren, und dann mal schauen.
Was mir noch auffält: Trotz gerade gekilltem Load ist der Server über SSH sehr "träge" (ping z.B. braucht 5 Sekunden, um den ersten Ping anzuzeigen, bei einer Latenz von unter 10 ms zum Rootforum).
----Edit
Server läuft jetzt merkwürdigerweise wieder sehr schnell und bis jetzt ohne Probleme. Werde aber morgen trotzdem mal den neuen Kernel installieren und das weiter beobachten.
Gruß, Thomas
Re: kernel: VM: killing process
Posted: 2005-07-13 09:19
by lufthansen
hmm komisch ....
ich habe kernel 2.6.11 laufen und das gleiche spielchen .....
aber das scheinen ja schon einige zu haben.
Re: kernel: VM: killing process
Posted: 2005-07-13 14:08
by lufthansen
setzt ihr auhc postfix ein ?
habe vorhin gesehn das proxymap sich ne menge ram gefresse hat
Re: kernel: VM: killing process
Posted: 2005-07-13 15:41
by thomas80
Jo, auch Postfix.
Re: kernel: VM: killing process
Posted: 2005-07-13 20:59
by as-n
Jetzt hängt der Kasten schon wieder, das letzte was top zeigte war:
Code: Select all
top - 20:38:40 up 1 day, 6:33, 1 user, load average: 145.99, 158.96, 134.41
Tasks: 274 total, 142 running, 131 sleeping, 0 stopped, 1 zombie
Cpu(s): 0.2% user, 99.1% system, 0.0% nice, 0.6% idle
Mem: 514324k total, 511144k used, 3180k free, 404k buffers
Swap: 514072k total, 514072k used, 0k free, 3996k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
28101 wwwrun 18 0 6908 1328 556 R 0.8 0.3 0:04.74 httpd2-prefork
28124 wwwrun 20 0 7028 1400 540 R 0.8 0.3 0:05.32 httpd2-prefork
30102 wwwrun 17 0 6476 1092 504 R 0.8 0.2 0:04.54 httpd2-prefork
29175 wwwrun 20 0 6852 1228 532 R 0.8 0.2 0:04.93 httpd2-prefork
9209 root 20 0 492 196 136 R 0.8 0.0 0:22.63 master
24723 wwwrun 20 0 7008 376 368 R 0.8 0.1 0:07.90 httpd2-prefork
27666 wwwrun 20 0 46536 29m 444 R 0.8 5.8 0:13.03 httpd2-prefork
27971 wwwrun 18 0 6880 1252 428 R 0.8 0.2 0:06.05 httpd2-prefork
30109 wwwrun 14 0 5240 1372 608 R 0.8 0.3 0:04.23 httpd2-prefork
24206 wwwrun 20 0 46436 24m 312 R 0.8 4.8 0:14.62 httpd2-prefork
27032 wwwrun 20 0 40184 21m 320 R 0.8 4.3 0:12.94 httpd2-prefork
29822 wwwrun 20 0 6768 876 440 R 0.8 0.2 0:05.01 httpd2-prefork
30147 wwwrun 14 0 5192 1340 592 R 0.8 0.3 0:03.89 httpd2-prefork
30169 wwwrun 20 0 5084 900 612 R 0.8 0.2 0:04.43 httpd2-prefork
30181 wwwrun 20 0 5100 1280 676 R 0.8 0.2 0:04.38 httpd2-prefork
30192 wwwrun 20 0 5164 1236 568 R 0.8 0.2 0:04.59 httpd2-prefork
30240 root 20 0 1484 692 208 R 0.8 0.1 0:04.75 confixx_counter
Jetzt komme ich gar nicht mehr ran, es ist zum ........naja.
Ich hatte die mysql schon auf einen anderen Server ausgelagert, aber das hat es scheinbar auch nicht gebracht, irgend was muss doch da faul sein.
So Neustart, folgendes steht in den Logs:
mail
Code: Select all
Jul 13 20:13:52 h9284 popper[30180]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:14:02 h9284 popper[30180]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:14:02 h9284 popper[30180]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:15:01 h9284 popper[29654]: web1p1 at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:15:21 h9284 popper[29654]: I/O error flushing output to client web1p1 at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:15:23 h9284 popper[29654]: Stats: web1p1 0 0 354 5590389 p54B42C4D.dip0.t-ipconnect.de 84.180.44.77 [pop_updt.c:296]
Jul 13 20:16:56 h9284 postfix/anvil[29619]: statistics: max connection rate 1/60s for (smtp:4.22.155.163) at Jul 13 20:09:55
Jul 13 20:17:03 h9284 postfix/anvil[29619]: statistics: max connection count 1 for (smtp:4.22.155.163) at Jul 13 20:09:55
Jul 13 20:17:03 h9284 postfix/anvil[29619]: statistics: max cache size 1 at Jul 13 20:09:55
Jul 13 20:17:42 h9284 popper[30241]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:17:56 h9284 popper[30241]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:17:56 h9284 popper[30241]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:18:42 h9284 popper[30260]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:18:42 h9284 popper[30249]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:18:48 h9284 popper[30249]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:18:48 h9284 popper[30249]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:18:48 h9284 popper[30260]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:18:48 h9284 popper[30260]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:21:51 h9284 postfix/qmgr[32137]: EB948360047: from=<wwwrun@horst.meindedomain.net>, size=7995, nrcpt=1 (queue active)
Jul 13 20:22:57 h9284 popper[30285]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:22:57 h9284 popper[30275]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:23:05 h9284 popper[30275]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:23:05 h9284 popper[30275]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:23:05 h9284 popper[30285]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:23:05 h9284 popper[30285]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:39:13 h9284 postfix/master[9209]: warning: process /usr/lib/postfix/smtpd pid 30242 killed by signal 9
Jul 13 20:39:14 h9284 postfix/master[9209]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Jul 13 20:39:13 h9284 postfix/qmgr[32137]: fatal: watchdog timeout
Jul 13 20:39:38 h9284 postfix/master[9209]: warning: process /usr/lib/postfix/qmgr pid 32137 killed by signal 9
Jul 13 20:44:51 h9284 popper[30337]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:44:52 h9284 popper[30372]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:44:55 h9284 popper[30346]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:45:25 h9284 postfix/smtp[26355]: warning: premature end-of-input on private/defer socket while reading input attribute name
Jul 13 20:47:29 h9284 popper[30346]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:47:30 h9284 popper[30346]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:47:17 h9284 popper[30370]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:47:30 h9284 popper[30370]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:48:38 h9284 postfix/smtp[26355]: warning: BA294360016: defer service failure
Jul 13 20:48:19 h9284 popper[30337]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:48:40 h9284 popper[30337]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:48:48 h9284 popper[30370]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:48:57 h9284 postfix/smtp[26355]: BA294360016: to=<web1p1@horst.meindedomain.net>, orig_to=<Orlando.Carrillo@meindedomain.net>, relay=127.0.0.1[127.0.0.1], delay=2323, status=deferred (conversation with 127.0.0.1[127.0.0.1] timed out while sending end of data -- message may be sent more than once)
Jul 13 20:49:07 h9284 popper[30373]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:49:19 h9284 popper[30373]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:49:20 h9284 popper[30373]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:49:20 h9284 postfix/smtp[26355]: warning: BA294360016: flush service failure
Jul 13 20:49:34 h9284 popper[30372]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:49:35 h9284 popper[30372]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:56:43 h9284 popper[30400]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:56:43 h9284 popper[30430]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:56:43 h9284 popper[30429]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:56:43 h9284 popper[30427]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:56:43 h9284 popper[30431]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:56:43 h9284 popper[30428]: (null) at dsl-084-056-141-128.arcor-ip.net (84.56.141.128): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:56:43 h9284 popper[30432]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:56:43 h9284 popper[30434]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:56:43 h9284 popper[30433]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:56:43 h9284 popper[30388]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:56:46 h9284 popper[30400]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:56:46 h9284 popper[30400]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:56:46 h9284 popper[30430]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:56:46 h9284 popper[30429]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:56:46 h9284 popper[30427]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:56:46 h9284 popper[30431]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:57:12 h9284 popper[30431]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:56:46 h9284 popper[30432]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:57:12 h9284 popper[30432]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:56:46 h9284 popper[30434]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:57:12 h9284 popper[30434]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:56:46 h9284 popper[30433]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:57:12 h9284 popper[30433]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:56:46 h9284 popper[30388]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:57:12 h9284 popper[30388]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:56:52 h9284 popper[30430]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:56:57 h9284 popper[30429]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:57:03 h9284 popper[30427]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:57:11 h9284 popper[30466]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:57:12 h9284 popper[30466]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:57:12 h9284 popper[30466]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
warn
Code: Select all
Jul 13 20:31:15 h9284 kernel: VM: killing process sh
Jul 13 20:31:35 h9284 kernel: VM: killing process confixx_counter
Jul 13 20:31:55 h9284 kernel: VM: killing process httpd2-prefork
Jul 13 20:31:57 h9284 kernel: VM: killing process confixx_counter
Jul 13 20:32:27 h9284 kernel: VM: killing process httpd2-prefork
Jul 13 20:33:32 h9284 kernel: VM: killing process confixx_counter
Jul 13 20:34:43 h9284 kernel: VM: killing process sh
Jul 13 20:34:55 h9284 kernel: VM: killing process sh
Jul 13 20:36:15 h9284 kernel: VM: killing process confixx_counter
Jul 13 20:38:34 h9284 kernel: VM: killing process smtpd
Jul 13 20:39:13 h9284 postfix/master[9209]: warning: process /usr/lib/postfix/smtpd pid 30242 killed by signal 9
Jul 13 20:39:14 h9284 postfix/master[9209]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Jul 13 20:39:13 h9284 postfix/qmgr[32137]: fatal: watchdog timeout
Jul 13 20:39:25 h9284 kernel: VM: killing process confixx_counter
Jul 13 20:39:38 h9284 postfix/master[9209]: warning: process /usr/lib/postfix/qmgr pid 32137 killed by signal 9
Jul 13 20:39:41 h9284 kernel: VM: killing process qmgr
Jul 13 20:42:13 h9284 kernel: VM: killing process httpd2-prefork
Jul 13 20:45:25 h9284 postfix/smtp[26355]: warning: premature end-of-input on private/defer socket while reading input attribute name
Jul 13 20:48:38 h9284 kernel: VM: killing process popper
Jul 13 20:48:38 h9284 kernel: VM: killing process confixx_counter
Jul 13 20:48:38 h9284 kernel: VM: killing process tlsmgr
Jul 13 20:48:38 h9284 kernel: VM: killing process popper
Jul 13 20:48:39 h9284 kernel: VM: killing process perl
Jul 13 20:48:39 h9284 kernel: VM: killing process cron
Jul 13 20:48:39 h9284 kernel: VM: killing process master
Jul 13 20:48:39 h9284 kernel: VM: killing process httpd2-prefork
Jul 13 20:48:39 h9284 kernel: VM: killing process pickup
Jul 13 20:48:39 h9284 kernel: VM: killing process popper
Jul 13 20:48:39 h9284 kernel: VM: killing process miniserv.pl
Jul 13 20:48:39 h9284 kernel: VM: killing process httpd2-prefork
Jul 13 20:48:39 h9284 kernel: VM: killing process bounce
Jul 13 20:48:39 h9284 kernel: VM: killing process httpd2-prefork
Jul 13 20:48:39 h9284 last message repeated 2 times
Jul 13 20:48:39 h9284 kernel: VM: killing process trivial-rewrite
Jul 13 20:48:39 h9284 kernel: VM: killing process httpd2-prefork
Jul 13 20:48:39 h9284 kernel: VM: killing process sh
Jul 13 20:48:39 h9284 kernel: VM: killing process httpd2-prefork
Jul 13 20:48:39 h9284 kernel: VM: killing process pipelog.pl
Jul 13 20:48:39 h9284 kernel: VM: killing process popper
Jul 13 20:48:38 h9284 postfix/smtp[26355]: warning: BA294360016: defer service failure
Jul 13 20:48:41 h9284 kernel: VM: killing process httpd2-prefork
Jul 13 20:48:41 h9284 kernel: VM: killing process qmgr
Jul 13 20:48:42 h9284 kernel: VM: killing process xinetd
Jul 13 20:49:20 h9284 postfix/smtp[26355]: warning: BA294360016: flush service failure
Jul 13 20:50:02 h9284 kernel: VM: killing process sh
Jul 13 20:50:41 h9284 kernel: kmod: failed to exec /sbin/modprobe -s -k binfmt-0000, errno = 12
Jul 13 20:52:36 h9284 kernel: VM: killing process top
Jul 13 20:52:59 h9284 kernel: VM: killing process sh
Jul 13 20:52:59 h9284 kernel: VM: killing process confixx_counter
Jul 13 20:52:59 h9284 kernel: VM: killing process confixx_counter
Jul 13 20:52:59 h9284 kernel: VM: killing process sh
Jul 13 20:53:31 h9284 kernel: VM: killing process run-crons
Jul 13 20:53:31 h9284 kernel: VM: killing process httpd2-prefork
Jul 13 20:53:31 h9284 kernel: VM: killing process popper
Jul 13 20:53:31 h9284 kernel: VM: killing process modprobe
Jul 13 20:53:44 h9284 kernel: VM: killing process confixx_counter
Jul 13 20:54:20 h9284 kernel: VM: killing process httpd2-prefork
Jul 13 20:54:20 h9284 kernel: VM: killing process httpd2-prefork
Jul 13 20:54:20 h9284 kernel: VM: killing process pipelog.pl
Jul 13 20:55:39 h9284 kernel: VM: killing process modprobe.old
Jul 13 20:55:41 h9284 kernel: VM: killing process httpd2-prefork
Jul 13 20:56:06 h9284 kernel: VM: killing process httpd2-prefork
Jul 13 20:56:30 h9284 kernel: VM: killing process confixx_counter
Jul 13 20:57:57 h9284 kernel: VM: killing process httpd2-prefork
apache
Code: Select all
66.249.69.26 - - [13/Jul/2005:20:13:12 +0200] "GET /catalog/default.php/cPath/87_172/page/1/sort/4a HTTP/1.0" 200 223 "-" "Googlebot/2.1 (+http://www.googlebot.com/bot.html)"
66.249.69.26 - - [13/Jul/2005:20:13:23 +0200] "GET /catalog/default.php/language/allprods.php HTTP/1.0" 200 223 "-" "Googlebot/2.1 (+http://www.googlebot.com/bot.html)"
66.249.68.133 - - [13/Jul/2005:20:13:08 +0200] "GET /catalog/product_info.php/products_id/2930 HTTP/1.0" 200 223 "-" "Googlebot/2.1 (+http://www.googlebot.com/bot.html)"
Ciao
AS-N
Re: kernel: VM: killing process
Posted: 2005-07-13 23:03
by as-n
Noch paar Infos direkt wäredn eines Hängers:
Code: Select all
init-+-agetty
|-amavisd---2*[amavisd]
|-bdflush
|-cron-+-22*[cron---confixx_counter]
| |-2*[cron---perl]
| `-cron---sh---run-crons---run-crons
|-dhcpcd
|-httpd2-prefork-+-110*[httpd2-prefork]
| |-httpd2-prefork---sh---modprobe
| `-pipelog.pl
|-keventd
|-khubd
|-2*[kjournald]
|-klogd
|-ksoftirqd_CPU0
|-kswapd
|-kupdated
|-master-+-pickup
| |-qmgr
| |-smtpd
| `-tlsmgr
|-6*[mingetty]
|-miniserv.pl---3*[miniserv.pl]
|-mysqld_safe---mysqld---mysqld---9*[mysqld]
|-nscd---nscd---5*[nscd]
|-portmap
|-saslauthd---4*[saslauthd]
|-sshd---sshd---bash---su---bash---pstree
|-syslogd
`-xinetd-+-2*[popper]
`-xinetd
root 11 0.0 0.0 0 0 ? DW 21:56 0:00 [kjournald]
root 56 0.0 0.0 0 0 ? SW 21:56 0:00 [kjournald]
root 507 0.0 0.0 1520 20 ? S 21:56 0:00 /sbin/dhcpcd -H -D -N -t 999999 -h linux eth0
root 574 0.0 0.0 1560 220 ? D 21:56 0:00 /sbin/syslogd
root 577 0.0 0.0 2376 16 ? S 21:56 0:00 /sbin/klogd -c 1 -2
root 590 0.0 0.0 4176 0 ? SW 21:56 0:00 /usr/sbin/saslauthd -a pam
root 591 0.0 0.0 4496 0 ? SW 21:56 0:00 /usr/sbin/saslauthd -a pam
root 592 0.0 0.0 4176 0 ? SW 21:56 0:00 /usr/sbin/saslauthd -a pam
root 593 0.0 0.0 4176 0 ? SW 21:56 0:00 /usr/sbin/saslauthd -a pam
root 594 0.0 0.0 4176 0 ? SW 21:56 0:00 /usr/sbin/saslauthd -a pam
amavis 595 0.0 0.1 44604 532 ? D 21:56 0:02 amavisd (master)
bin 608 0.0 0.0 1516 32 ? S 21:56 0:00 /sbin/portmap
root 610 0.0 0.1 8504 988 ? D 21:56 0:00 /usr/bin/perl /usr/libexec/webmin/miniserv.pl /etc/webmin/miniserv.conf
root 647 0.0 0.0 2172 320 ? S 21:56 0:00 /usr/sbin/xinetd
root 649 0.0 0.0 2460 60 ? S 21:56 0:00 /bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --pid-file=/var/lib/mysql/h9284.pid
mysql 685 0.0 0.1 106008 892 ? S 21:56 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/h
root 719 0.0 0.0 3448 88 ? S 21:56 0:00 /usr/sbin/sshd -o PidFile=/var/run/sshd.init.pid
mysql 723 0.0 0.1 106008 900 ? S 21:56 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/h
mysql 724 0.0 0.1 106008 900 ? S 21:56 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/h
mysql 725 0.0 0.1 106008 900 ? S 21:56 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/h
mysql 726 0.0 0.1 106008 900 ? S 21:56 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/h
mysql 727 0.0 0.1 106008 900 ? S 21:56 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/h
mysql 733 0.0 0.1 106008 900 ? S 21:56 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/h
mysql 734 0.0 0.1 106008 900 ? S 21:56 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/h
mysql 735 0.0 0.1 106008 900 ? S 21:56 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/h
mysql 736 0.0 0.1 106008 900 ? S 21:56 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/h
root 870 0.0 0.0 12272 360 ? S 21:56 0:01 /usr/sbin/nscd
root 871 0.0 0.0 12272 360 ? S 21:56 0:00 /usr/sbin/nscd
root 872 0.0 0.0 12272 360 ? S 21:56 0:01 /usr/sbin/nscd
root 873 0.0 0.0 12272 360 ? S 21:56 0:00 /usr/sbin/nscd
root 874 0.0 0.0 12272 360 ? S 21:56 0:00 /usr/sbin/nscd
root 875 0.0 0.0 12272 360 ? S 21:56 0:00 /usr/sbin/nscd
root 876 0.0 0.0 12272 360 ? S 21:56 0:00 /usr/sbin/nscd
root 935 0.0 0.0 5596 196 ? S 21:57 0:00 /usr/lib/postfix/master
postfix 959 0.0 0.0 5708 172 ? S 21:57 0:00 pickup -l -t fifo -u
postfix 960 0.0 0.0 5740 84 ? S 21:57 0:00 qmgr -l -t fifo -u
root 964 0.0 0.0 1516 188 ? S 21:57 0:00 /usr/sbin/cron
root 970 0.0 0.0 1500 20 tty1 S 21:57 0:00 /sbin/mingetty --noclear tty1
root 971 0.0 0.0 1500 20 tty2 S 21:57 0:00 /sbin/mingetty tty2
root 972 0.0 0.0 1500 20 tty3 S 21:57 0:00 /sbin/mingetty tty3
root 973 0.0 0.0 1500 20 tty4 S 21:57 0:00 /sbin/mingetty tty4
root 974 0.0 0.0 1500 20 tty5 S 21:57 0:00 /sbin/mingetty tty5
root 975 0.0 0.0 1500 20 tty6 S 21:57 0:00 /sbin/mingetty tty6
root 976 0.0 0.0 1492 24 ttyS0 S 21:57 0:00 /sbin/agetty -L 57600 ttyS0 vt102
mysql 992 0.0 0.1 106008 900 ? S 21:57 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/h
postfix 997 0.0 0.0 5708 88 ? S 21:57 0:00 tlsmgr -l -t unix -u
root 1084 0.0 0.0 19268 364 ? S 21:58 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
root 1085 0.0 0.0 3312 412 ? D 21:58 0:01 /usr/bin/perl /root/confixx/pipelog.pl
wwwrun 11289 0.4 0.1 21884 936 ? D 22:17 0:07 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 12414 0.9 6.1 66752 31464 ? D 22:19 0:14 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 13276 1.2 8.7 82288 45000 ? D 22:20 0:17 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
amavis 13795 0.4 0.0 45924 20 ? S 22:20 0:06 amavisd (ch2-avail)
wwwrun 14312 1.1 10.0 90184 51492 ? D 22:21 0:16 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 14359 0.1 0.2 22044 1056 ? D 22:21 0:02 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
root 14463 0.0 0.0 4136 300 ? D 22:21 0:00 sshd: a@pts/8
a 14607 0.0 0.0 2900 64 pts/8 S 22:21 0:00 -bash
root 14626 0.0 0.0 2692 64 pts/8 S 22:21 0:00 su
root 14662 0.0 0.0 2912 252 pts/8 S 22:21 0:00 bash
amavis 14929 0.0 0.0 44604 64 ? S 22:22 0:00 amavisd (virgin child)
wwwrun 15340 1.1 9.2 84652 47620 ? D 22:24 0:14 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 15438 0.1 0.1 21700 692 ? D 22:24 0:02 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 15761 0.9 6.1 66192 31776 ? D 22:26 0:10 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 16090 0.1 0.1 21888 892 ? D 22:27 0:02 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 16118 1.2 8.4 80296 43420 ? D 22:27 0:12 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 16119 1.0 6.3 67620 32812 ? D 22:27 0:10 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 16124 0.9 6.1 66076 31428 ? D 22:27 0:10 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 16125 0.9 6.6 69404 34272 ? D 22:27 0:10 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 16126 1.0 6.5 68284 33576 ? D 22:27 0:10 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 16150 1.0 7.4 73608 38284 ? D 22:27 0:11 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 16151 0.9 6.1 64952 31540 ? D 22:27 0:09 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 16155 0.1 0.2 21744 1112 ? D 22:27 0:01 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 16158 0.1 0.2 21704 1116 ? D 22:27 0:01 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 16291 0.1 0.1 21716 620 ? D 22:27 0:01 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 16292 0.1 0.2 21720 1032 ? D 22:27 0:01 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 16744 0.0 0.1 21696 880 ? D 22:28 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 16747 0.1 0.1 21736 892 ? D 22:28 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17042 0.0 0.2 20052 1420 ? D 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
root 17126 0.0 0.0 1516 44 ? S 22:29 0:00 /USR/SBIN/CRON
root 17129 0.0 0.1 3720 992 ? D 22:29 0:00 /root/confixx/confixx_counterscript.pl
wwwrun 17136 0.0 0.3 19940 1544 ? D 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17139 0.0 0.2 19936 1452 ? S 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17140 0.0 0.2 19936 1464 ? S 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17141 0.0 0.3 19936 1544 ? S 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17142 0.0 0.2 19936 1384 ? S 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17143 0.0 0.2 19876 1356 ? S 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17144 0.0 0.2 19876 1332 ? S 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17145 0.0 0.2 19812 1296 ? D 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17146 0.0 0.2 19924 1388 ? D 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17147 0.0 0.2 19912 1192 ? S 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17149 0.0 0.3 19804 1920 ? D 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17150 0.0 0.2 19804 1204 ? S 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17151 0.0 0.3 19752 2032 ? D 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17152 0.0 0.3 19804 1948 ? D 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17153 0.0 0.3 19804 1944 ? D 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17155 0.0 0.2 19920 1528 ? D 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17156 0.0 0.2 19784 1176 ? S 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17157 0.0 0.4 19804 2148 ? D 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17158 0.0 0.3 19804 1940 ? D 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17159 0.0 0.4 19880 2104 ? D 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17160 0.0 0.2 19804 1200 ? S 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17161 0.0 0.4 19804 2160 ? D 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17162 0.0 0.3 19996 1720 ? D 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17163 0.0 0.3 19804 1940 ? D 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17164 0.0 0.3 19804 1672 ? D 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17165 0.0 0.3 19804 1940 ? D 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17166 0.0 0.3 19880 1796 ? D 22:29 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
root 17167 0.0 0.2 7340 1064 ? D 22:30 0:00 smtpd -n smtp -t inet -u
wwwrun 17169 0.0 0.3 19880 1936 ? D 22:30 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
root 17171 0.0 0.0 1516 76 ? S 22:30 0:00 /USR/SBIN/CRON
root 17172 0.0 0.0 1516 64 ? S 22:30 0:00 /USR/SBIN/CRON
root 17174 0.0 0.2 5328 1268 ? D 22:30 0:00 /root/confixx/confixx_counterscript.pl
root 17175 0.0 0.2 3856 1472 ? D 22:30 0:00 perl /root/srv-report/srvreport-0.70/bin/srvreport.pl
root 17177 0.0 0.0 1516 132 ? S 22:31 0:00 /USR/SBIN/CRON
root 17178 0.0 0.3 4116 1736 ? D 22:31 0:00 /root/confixx/confixx_counterscript.pl
root 17188 0.0 0.0 1516 160 ? S 22:32 0:00 /USR/SBIN/CRON
root 17189 0.0 0.2 5328 1332 ? D 22:32 0:00 /root/confixx/confixx_counterscript.pl
root 17195 0.0 0.0 1516 148 ? S 22:33 0:00 /USR/SBIN/CRON
root 17196 0.0 0.2 4796 1280 ? D 22:33 0:00 /root/confixx/confixx_counterscript.pl
wwwrun 17197 0.0 0.2 19880 1248 ? D 22:33 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17199 0.0 0.2 19884 1520 ? S 22:33 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17200 0.0 0.2 19804 1272 ? D 22:33 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17201 0.0 0.3 19804 1684 ? D 22:33 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17202 0.0 0.2 19880 1316 ? D 22:33 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17203 0.0 0.2 19880 1276 ? D 22:33 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17204 0.0 0.3 19880 1732 ? D 22:33 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17205 0.0 0.2 19804 1148 ? S 22:33 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17206 0.0 0.2 19816 1200 ? S 22:33 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17207 0.0 0.3 19776 1732 ? D 22:33 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17208 0.0 0.2 19732 1380 ? S 22:33 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17209 0.0 0.2 19732 1356 ? D 22:33 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17210 0.0 0.3 19804 1940 ? D 22:33 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17211 0.0 0.2 19804 1368 ? D 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17212 0.0 0.2 19880 1368 ? S 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17213 0.0 0.3 19732 1744 ? D 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17214 0.0 0.3 19732 1964 ? D 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17215 0.0 0.3 19732 1672 ? D 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17216 0.0 0.3 19732 1764 ? D 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17217 0.0 0.3 19804 1696 ? D 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17220 0.0 0.3 19908 1824 ? D 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17221 0.0 0.3 19804 1708 ? D 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17222 0.0 0.3 19804 1804 ? D 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17223 0.0 0.3 19792 1568 ? S 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17228 0.0 0.2 19468 1492 ? D 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17230 0.0 0.3 19988 1856 ? D 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17231 0.0 0.3 19600 2028 ? D 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17233 0.0 0.2 19468 1500 ? D 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17235 0.0 0.2 19468 1080 ? S 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17236 0.0 0.3 19468 1976 ? D 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17237 0.0 0.3 19940 1888 ? D 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17238 0.0 0.3 19804 2032 ? D 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17239 0.0 0.2 19784 1212 ? S 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17240 0.0 0.2 19784 1208 ? S 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17241 0.0 0.1 19468 812 ? S 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17242 0.0 0.3 19468 2016 ? D 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
root 17243 0.0 0.0 1516 168 ? S 22:34 0:00 /USR/SBIN/CRON
root 17244 0.0 0.2 4796 1148 ? D 22:34 0:00 /root/confixx/confixx_counterscript.pl
wwwrun 17245 0.0 0.3 19468 2036 ? D 22:34 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
root 17247 0.0 0.0 1516 188 ? S 22:35 0:00 /USR/SBIN/CRON
root 17248 0.0 0.2 4796 1276 ? D 22:35 0:00 /root/confixx/confixx_counterscript.pl
wwwrun 17251 0.0 0.2 19468 1520 ? D 22:35 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17252 0.0 0.3 20444 1924 ? D 22:35 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17253 0.0 0.3 20444 1864 ? D 22:35 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17256 0.0 0.2 19804 1440 ? D 22:35 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17257 0.0 0.3 19468 2028 ? D 22:35 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17258 0.0 0.1 19568 796 ? S 22:35 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17261 0.0 0.2 19468 1528 ? D 22:35 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17262 0.0 0.2 19468 1528 ? D 22:35 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17263 0.0 0.2 19468 1528 ? D 22:35 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17266 0.0 0.2 19468 1092 ? D 22:35 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17268 0.0 0.3 19928 1868 ? D 22:35 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17271 0.0 0.2 19468 1528 ? D 22:35 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17273 0.0 0.3 19600 1664 ? D 22:35 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17278 0.0 0.3 20436 1692 ? D 22:35 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17280 0.0 0.2 20368 1212 ? D 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17281 0.0 0.2 19808 1516 ? D 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17282 0.0 0.1 19468 764 ? S 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17283 0.0 0.1 19468 764 ? S 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17284 0.0 0.1 19600 768 ? S 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17285 0.0 0.2 19468 1388 ? D 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17286 0.0 0.2 19600 1180 ? D 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17287 0.0 0.2 19468 1380 ? D 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17288 0.0 0.1 19468 760 ? S 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17291 0.0 0.1 19468 768 ? S 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17292 0.0 0.1 19468 768 ? S 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17293 0.0 0.3 19468 1572 ? D 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17294 0.0 0.2 19468 1400 ? D 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17295 0.0 0.3 19468 1968 ? D 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17296 0.0 0.2 19468 1404 ? D 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17297 0.0 0.2 19468 1404 ? D 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17298 0.0 0.1 19468 784 ? S 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17300 0.0 0.1 19468 784 ? S 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17301 0.0 0.1 19468 788 ? S 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17302 0.0 0.1 19468 784 ? S 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17303 0.0 0.3 19480 2040 ? D 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17304 0.0 0.4 19804 2236 ? D 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17305 0.0 0.2 19884 1484 ? S 22:36 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
root 17306 0.0 0.0 1516 208 ? S 22:36 0:00 /USR/SBIN/CRON
root 17307 0.0 0.3 4928 1640 ? D 22:37 0:00 /root/confixx/confixx_counterscript.pl
root 17309 0.0 0.0 1516 208 ? S 22:37 0:00 /USR/SBIN/CRON
wwwrun 17310 0.0 0.2 19468 1096 ? D 22:37 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
root 17312 0.0 0.2 4796 1200 ? D 22:37 0:00 /root/confixx/confixx_counterscript.pl
wwwrun 17313 0.0 0.1 19468 700 ? S 22:37 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17314 0.0 0.1 19600 948 ? S 22:37 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17315 0.0 0.2 19468 1096 ? D 22:37 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17316 0.0 0.2 19468 1096 ? D 22:37 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17317 0.0 0.3 20424 1652 ? D 22:37 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17318 0.0 0.3 19792 2020 ? D 22:37 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17319 0.0 0.2 19788 1468 ? D 22:37 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17320 0.0 0.4 19612 2316 ? D 22:37 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17321 0.0 0.2 19812 1244 ? S 22:37 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17322 0.0 0.1 19600 592 ? S 22:37 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17323 0.0 0.4 19620 2252 ? D 22:37 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17324 0.0 0.1 19468 588 ? S 22:37 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17325 0.0 0.2 19468 1216 ? D 22:37 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17326 0.0 0.1 19468 588 ? S 22:37 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17327 0.0 0.1 19468 588 ? S 22:37 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17328 0.0 0.1 19468 588 ? S 22:37 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17329 0.0 0.2 19468 1480 ? D 22:37 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17330 0.0 0.1 19468 588 ? S 22:38 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17331 0.0 0.1 19468 588 ? S 22:38 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17332 0.0 0.1 19468 588 ? S 22:38 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17333 0.0 0.1 19468 592 ? S 22:38 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17334 0.0 0.1 19468 992 ? D 22:38 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
wwwrun 17335 0.0 0.1 19468 588 ? S 22:38 0:00 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -DSSL
Re: kernel: VM: killing process
Posted: 2005-07-13 23:08
by lufthansen
22 confixx_counter prozesse ??
und 110 indiander ?
war da so viel last auf dem httpd ?
Re: kernel: VM: killing process
Posted: 2005-07-13 23:13
by as-n
Naja, auf der bestbesuchten Site waren vielleicht 400 Besucher drauf, dass kann es eigentlich nicht sein.
Re: kernel: VM: killing process
Posted: 2005-07-14 11:34
by Joe User
Was machen die 22 Confixx-Prozesse?
Wie sehen folgende Werte bei Dir aus?
Code: Select all
Timeout 300
KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 15
<IfModule prefork.c>
StartServers 5
MinSpareServers 5
MaxSpareServers 10
ServerLimit 150
MaxClients 150
MaxRequestsPerChild 0
</IfModule>
<IfModule worker.c>
StartServers 2
MinSpareThreads 25
MaxSpareThreads 75
MaxClients 150
ThreadsPerChild 25
MaxRequestsPerChild 0
</IfModule>
Hast Du Apache2-worker schon versucht? Mit welchem Resultat?
Benötigst Du amavisd-new, webmin und pipelog zwingend? Falls ja, dann hat die Kiste definitiv zu wenig RAM...
Re: kernel: VM: killing process
Posted: 2005-07-14 11:47
by as-n
Joe User wrote:Was machen die 22 Confixx-Prozesse?
Wie sehen folgende Werte bei Dir aus?
Frag mich nicht, das weiß ich auch nicht.
Joe User wrote:
Code: Select all
Timeout 300
KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 15
<IfModule prefork.c>
StartServers 5
MinSpareServers 5
MaxSpareServers 10
ServerLimit 150
MaxClients 150
MaxRequestsPerChild 0
</IfModule>
<IfModule worker.c>
StartServers 2
MinSpareThreads 25
MaxSpareThreads 75
MaxClients 150
ThreadsPerChild 25
MaxRequestsPerChild 0
</IfModule>
Mit den verschiedensten Einstellung in der tuning habe ich schon tagelang probiert, hat aber definitiv nix gebracht.
Joe User wrote:
Hast Du Apache2-worker schon versucht? Mit welchem Resultat?
Benötigst Du amavisd-new, webmin und pipelog zwingend? Falls ja, dann hat die Kiste definitiv zu wenig RAM...
Worker hatte ich schon probiert, habe ich aber nicht zum Laufen bekommen.
Er hatte als worker php_admin_flag nicht gefunden und ließ sich nicht starten, weiß nicht wo da der Fehler war.
amavis ist zwingend
webmin läuft nur wenn ich es brauche
pipelog sollte eigentlich drauf bleiben
Der Server lief ja jetzt Monate lang ohne ein Problem, außer security updates wurde nichts verändert.
Vielleicht ist auch der RAM defekt, ich lasse den Server gerade mal von Strato checken.
Ein zweiter Server, der fast 100%ig gleich dem obigen ist, läuft jetzt als Ersatz, bisher ohne Probleme.
Ciao
AS-N
Re: kernel: VM: killing process
Posted: 2005-07-14 16:22
by as-n
Spidert der Google Bot eigentlich nach der IP?
Ich hatte jetzt wochenlang hunderte von Goggle Bots auf dem Server und jetzt mit dem neuen, identischen, Server kommt er fast gar nicht mehr.
Ciao
AS-N
Re: kernel: VM: killing process
Posted: 2005-07-15 08:08
by as-n
OK, Google ist wieder da.
Ich würde jetzt doch mal gerne den worker testen, aber ich bekomme den apachen damit nicht zum Luafen:
Code: Select all
linux:~/apache # rcapache2 start
Starting httpd2 (worker) Syntax error on line 209 of /etc/apache2/httpd.conf:
Invalid command 'php_admin_value', perhaps mis-spelled or defined by a module not......
Und das kommt bei allem was mit php_admin_ anfängt.
Der Prefork startet da ohne Probleme, was will den der worker anders haben?
Ciao
AS-N
Re: kernel: VM: killing process
Posted: 2005-07-15 08:53
by andreask2
http://de3.php.net/manual/en/install.unix.apache2.php :
We do not recommend using a threaded MPM in production with Apache2. Use the prefork MPM instead, or use Apache1. For information on why, read the related FAQ entry on using Apache2 with a threaded MPM
->
http://de3.php.net/manual/en/faq.instal ... on.apache2
Re: kernel: VM: killing process
Posted: 2005-07-15 12:13
by as-n
OK, dann lassen wir das mit dem worker.
Beim Ursprungsserver ist laut Strato kein Hardwaredefekt gefunden wurden, der wurde 20 h gescannt, naja.
Der neue Server verträgt die Googlebot Angriffe mit einem Load um die 2,5 wo der erste schon jenseits der 100 war.
Ich werde mir jetzt wohl einen größeren Server leisten, 2GB RAM müssten dann aber langen.
Ciao
AS-N
Re: kernel: VM: killing process
Posted: 2005-07-15 12:28
by andreask2
Ich denke Du hast da irgendwo einen Unterschied in der Konfiguration.
Es gab z.B. bei einigen neueren PHP-Versionen ein Problem mit unserialize und Objekten, da hatten einige Scripte auf einmal riesige Performance-Probleme:
http://bugs.php.net/bug.php?id=31332
Ich wäre mir da nicht so sicher dass ein schnellerer Server das ausgleicht, womöglich passiert dort dasselbe, nur etwas später. Evtl. könntest Du mal die access_log des Apachen so konfigurieren, dass er Dir für jeden Request die Zeit aufschreibt, die er benötigt den Request abzuarbeiten:
Code: Select all
%...D The time taken to serve the request, in microseconds.
siehe:
http://httpd.apache.org/docs-2.0/mod/mo ... ml#formats
Dann kannst Du evtl. das Scipt finden, welches die Probleme macht. Du kannst das ja mal selber mit ab testen, von localhost aus.
Evtl. hilft Dir dann auch ein Profiler wie xdebug die Stelle im Script zu finden, die Probleme bereitet.
System speichermäßg überlastet
Posted: 2005-07-16 12:17
by kawfy
AS-N wrote:Jetzt hängt der Kasten schon wieder, das letzte was top zeigte war:
Code: Select all
top - 20:38:40 up 1 day, 6:33, 1 user, load average: 145.99, 158.96, 134.41
Tasks: 274 total, 142 running, 131 sleeping, 0 stopped, 1 zombie
Cpu(s): 0.2% user, 99.1% system, 0.0% nice, 0.6% idle
Mem: 514324k total, 511144k used, 3180k free, 404k buffers
Swap: 514072k total, 514072k used, 0k free, 3996k cached
:!: Das System hat keinen Speicher mehr, sogar der Swap ist aufgebraucht (used/free/buffers). Das System ist nur noch mit dem Herumschaufeln des Swap beschäftigt (user/system).
AS-N wrote:Code: Select all
[...]
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
28101 wwwrun 18 0 6908 1328 556 R 0.8 0.3 0:04.74 httpd2-prefork
28124 wwwrun 20 0 7028 1400 540 R 0.8 0.3 0:05.32 httpd2-prefork
30102 wwwrun 17 0 6476 1092 504 R 0.8 0.2 0:04.54 httpd2-prefork
29175 wwwrun 20 0 6852 1228 532 R 0.8 0.2 0:04.93 httpd2-prefork
27666 wwwrun 20 0 46536 29m 444 R 0.8 5.8 0:13.03 httpd2-prefork
[...]
:!: Hier ist eine Sortierung nach Speicherverbrauch sinnvoll, nicht nach CPU-Verbrauch.
AS-N wrote:So Neustart, folgendes steht in den Logs:
mail
Code: Select all
Jul 13 20:13:52 h9284 popper[30180]: (null) at p54B42C4D.dip0.t-ipconnect.de (84.180.44.77): -ERR POP EOF or I/O Error [popper.c:820]
Jul 13 20:14:02 h9284 popper[30180]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
Jul 13 20:14:02 h9284 popper[30180]: I/O error flushing output to client at p54B42C4D.dip0.t-ipconnect.de [84.180.44.77]: Operation not permitted (1) [pop_send.c:689]
[...]
:roll: Das dürften Folge-Fehler aufgrund des Speicherengpasses sein. Ignorieren.
AS-N wrote:warn
Code: Select all
Jul 13 20:31:15 h9284 kernel: VM: killing process sh
Jul 13 20:31:35 h9284 kernel: VM: killing process confixx_counter
Jul 13 20:31:55 h9284 kernel: VM: killing process httpd2-prefork
Jul 13 20:31:57 h9284 kernel: VM: killing process confixx_counter
Jul 13 20:32:27 h9284 kernel: VM: killing process httpd2-prefork
Jul 13 20:33:32 h9284 kernel: VM: killing process confixx_counter
Jul 13 20:34:43 h9284 kernel: VM: killing process sh
Jul 13 20:34:55 h9284 kernel: VM: killing process sh
Jul 13 20:36:15 h9284 kernel: VM: killing process confixx_counter
Jul 13 20:38:34 h9284 kernel: VM: killing process smtpd
[...]
:arrow: Dem System ist der Speicher ausgegangen, Speicheranforderungen der Programme können nicht mehr erfüllt werden und die Prozesse werden deshalb hart terminiert. Das ist Folge des unter Linux/Unix eingesetzten
memory overcommitments.
AS-N wrote:apache
Code: Select all
66.249.69.26 - - [13/Jul/2005:20:13:12 +0200] "GET /catalog/default.php/cPath/87_172/page/1/sort/4a HTTP/1.0" 200 223 "-" "Googlebot/2.1 (+http://www.googlebot.com/bot.html)"
66.249.69.26 - - [13/Jul/2005:20:13:23 +0200] "GET /catalog/default.php/language/allprods.php HTTP/1.0" 200 223 "-" "Googlebot/2.1 (+http://www.googlebot.com/bot.html)"
66.249.68.133 - - [13/Jul/2005:20:13:08 +0200] "GET /catalog/product_info.php/products_id/2930 HTTP/1.0" 200 223 "-" "Googlebot/2.1 (+http://www.googlebot.com/bot.html)"
:?: Dass ein einfacher Bot-Besuch einen Server in die Knie zwingt, überrascht doch. Trotzdem: Versuche, den Bot zu drosseln oder auszusperren, sei es ganz oder auf eine Reihe von Verzeichnissen/Seiten (Skripte, die viel rechnen).
:!: Es ist hier kein Hardwarefehler ursächlich, sondern eine spezifische Systemüberlastung oder ein Softwarefehler. Evtl. hat eine Anwendung ein
memory leak (Prorammierfehler). Die Hardware zu vergrößern, muss das Problem nicht unbedingt lösen, sollte es aber immerhin verschieben. Erstmal eine softwaremäßige Lösung probieren.