htop - Vll kann jemand mal drüber schauen

Quali

Quali

New Member
Ich habe irgendwie die Befürchtung, das irgendwas nicht mit dem Server stimmt, ich finde der ist etwas doll überlastet. Deshalb hab ich euch erstmal ein htop screen hochgeladen, vll kann sich das ja jemand mal anschauen und mir sagen was er oder sie davon hält.

Vielen dank im voraus.

Wenn ihr was vermutet, dann bitte gleich mit passendem Ansatz. DANKE
 

Attachments

  • htop.png
    htop.png
    172.3 KB · Views: 440
Ich würd mal sagen dein Webserver lastet deinen Server voll aus. :rolleyes: Du musst also irgendwo massig Zugriffe auf ne Webseite haben (access-log).
 
Es sind ca. 300-350 gleichzeigit online, aber kann das schon das Ende für den Server sein?

Mein cpu

model name : AMD Athlon(tm) Dual Core Processor 4850e
stepping : 2
cpu MHz : 2494.590


Was mich interessiert, was bedeuten die roten Zahlen? oder auch ttymon tymon, was ist das?

Hab da noch was in einer error.log gesehen was genau ist das oder bedeutet das.

Code: 
2010-01-05 19:05:46: (mod_fastcgi.c.3299) response not received, request sent: 1238 on socket: unix:/var/customers/tmp/lighttpd-fcgi-sock-lighttpd-9 for /miiwars/modules/core/ajax_core.php , closing connect$
2010-01-05 19:05:46: (mod_fastcgi.c.1761) connect failed: Connection refused on unix:/var/customers/tmp/lighttpd-fcgi-sock-lighttpd-9
2010-01-05 19:05:46: (mod_fastcgi.c.2930) backend died; we'll disable it for 5 seconds and send the request to another backend instead: reconnects: 0 load: 10
2010-01-05 19:06:26: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:06:27: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:06:34: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:06:34: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:06:34: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:06:52: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:06:53: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:06:53: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:06:53: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:06:53: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:06:59: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:07:00: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:07:00: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:07:00: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:07:06: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:07:06: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:07:06: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:07:13: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:07:13: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:07:13: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:07:13: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:07:13: (server.c.1258) NOTE: a request for /index.php?page=Index timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:07:27: (server.c.1258) NOTE: a request for /wcf/images/Wii-Homebrew-Winter-NEW/bodyMittag.png timed out after writing 20328 bytes. We waited 360 seconds. If this a problem increase server.max-$
2010-01-05 19:07:32: (server.c.1258) NOTE: a request for /index.php timed out after writing 310980 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:08:55: (mod_fastcgi.c.2489) unexpected end-of-file (perhaps the fastcgi process died): pid: 32096 socket: unix:/var/customers/tmp/lighttpd-fcgi-sock-lighttpd-9
2010-01-05 19:08:55: (mod_fastcgi.c.3299) response not received, request sent: 1554 on socket: unix:/var/customers/tmp/lighttpd-fcgi-sock-lighttpd-9 for /index.php , closing connection
2010-01-05 19:08:55: (mod_fastcgi.c.1761) connect failed: Connection refused on unix:/var/customers/tmp/lighttpd-fcgi-sock-lighttpd-9
2010-01-05 19:08:55: (mod_fastcgi.c.2930) backend died; we'll disable it for 5 seconds and send the request to another backend instead: reconnects: 0 load: 3
2010-01-05 19:08:55: (mod_fastcgi.c.2698) child signaled: 11
2010-01-05 19:10:04: (server.c.1258) NOTE: a request for /index.php timed out after writing 91476 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:12:36: (mod_fastcgi.c.1761) connect failed: Connection refused on unix:/var/customers/tmp/lighttpd-fcgi-sock-lighttpd-6
2010-01-05 19:12:36: (mod_fastcgi.c.2930) backend died; we'll disable it for 5 seconds and send the request to another backend instead: reconnects: 0 load: 5
2010-01-05 19:14:00: (server.c.1258) NOTE: a request for /miiwars/miiwars_sig.php?userID=9 timed out after writing 17940 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2010-01-05 19:14:01: (server.c.1258) NOTE: a request for /wcf/images/Wii-Homebrew-Winter-NEW/footerContainer.png timed out after writing 13068 bytes. We waited 360 seconds. If this a problem increase server$
2010-01-05 19:20:33: (mod_fastcgi.c.2489) unexpected end-of-file (perhaps the fastcgi process died): pid: 31523 socket: unix:/var/customers/tmp/lighttpd-fcgi-sock-lighttpd-8
2010-01-05 19:20:33: (mod_fastcgi.c.3252) child exited, pid: 31523 status: 0
2010-01-05 19:20:33: (mod_fastcgi.c.3299) response not received, request sent: 1742 on socket: unix:/var/customers/tmp/lighttpd-fcgi-sock-lighttpd-8 for /index.php , closing connection
 
Last edited by a moderator:
Die roten zahlen (2h,1h) geben an wie lange der Prozess schon in Stunden läuft, weil ja von Haus aus nur Minuten/Sekunden angegeben werden.

Die roten Zahlen in der "NI"-Spalte geben den Nice-Wert des Prozesses an. Darum handelt es sich um eine Priorisierung. Kannst dich ja mal bei Google/Wikipedia einlesen. ;)
 
@ simonZ ich meine natürlich die Zahlen im Screenshot

Aber allgemein kann man da nichts schlimmes oder ungewöhnliches ersehen?
 
Außer den ressourcenhungrigen PHP Prozessen ist dort nichts auffälliges.
 
- Wie groß sind die Log-Files deiner Dienste (Webserver etc.)?
- Verwendest du Log-Rotate?
- Da scheint ein rsync zu laufen, läuft der "ständig" oder nur ab und an?
- Was läuft denn insgesamt auf der Kiste? Ein Webserver samt MySQL, damit Webseiten angezeigt werden können oder wird da noch mehr betrieben? :)

Mir fällt im Übrigen auch auf, dass die PHP-Prozesse schon sehr ressourcenlastig sind. Darf ich fragen, zu welchen Scripten die gehören bzw. was die machen? Das ist schon abartig :D
 
Da ich echt nen Anfänger bin kann ich das im Detail und in Worte gar nicht so fassen. Ich suche an dieser Stelle vll jemanden der mal per Team Viewer oder auch Skype + meine schöne Web cam mal auf mein Monitor gucken würde, damit man gemeinsam das Problem beheben könnte oder zumindest einen Grund findet. :o
 
Ich empfehle dir, dich nach jemanden umzusehen, der dir da langfristig unter die Arme greift, wenn du dich da nicht so gut auskennst :)
 
You must log in or register to reply here.
Back
Top