Hello all. After some time of work (6-10 hours) getstream is using more and more CPU. 4001 port is's getstream http port. In netstat i see tcp 0 1268 91.195.130.31:4001 10.14.6.1:1377 ESTABLISHED tcp 0 0 91.195.130.31:4001 91.195.130.6:58613 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:60152 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:57914 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:60662 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:57871 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:54752 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:53901 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:55924 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:52924 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:54316 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:50204 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:52204 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:50307 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:56403 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:62940 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:55930 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:57432 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:60124 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 10.17.22.18:1306 ESTABLISHED tcp 0 0 91.195.130.31:4001 91.195.130.6:61980 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:64454 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:55625 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:63652 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:55026 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:54688 TIME_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:60779 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:65447 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:55456 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:53125 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:56196 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:49223 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:51167 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:64003 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:63269 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:55914 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:50343 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:55794 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:49277 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:56049 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:60786 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:56362 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:64356 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:62902 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:63787 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:62045 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:51401 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:56473 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:61882 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:63184 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:64347 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:58215 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 10.11.78.12:2123 ESTABLISHED an more more kernel 2.6.27.7-9, opensuse 11.
On Mon, Feb 23, 2009 at 11:34:40AM +0300, Лавкин Михаил wrote:
Subject: Bug
Hello all.
After some time of work (6-10 hours) getstream is using more and more CPU.
4001 port is's getstream http port.
In netstat i see
tcp 0 1268 91.195.130.31:4001 10.14.6.1:1377 ESTABLISHED tcp 0 0 91.195.130.31:4001 91.195.130.6:58613 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:60152 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:57914 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:60662 CLOSE_WAIT tcp 0 0 91.195.130.31:4001 91.195.130.6:57871 CLOSE_WAIT
Thats interesting - What client are you using for taking content from the http port? This really sounds like a bug in getstream not beeing able to detect some odd way to close the http connection but it should take more cpu cycles as tcp connections which do not take data should be dropped after HTTP_MAX_QUEUED bytes and HTTP_MAX_OVERFLOW trys to write something to it ... Did getstream mention something that it closed/dropped the http connection? It should do so when started with -d or something ... I retried both ways to drop the connection by using: wget -O /dev/null http://stream2:8001/radio/einslive And then either pressing ctrl-c which is a tcp-fin which immediatly lets the connection drop or by pressing ctrl-z which simply doesnt ack any packets anymore - this takes a little longer to drop as libhttp.c/output_http start queueing data a little after which it drops the connection because of buffer overflow. In both bases getstream successfully closes the tcp socket so no CLOSE_WAIT sockets show up ... You might want to set DEBUG in libhttp.c (right at the top) and try around until you get a CLOSE_WAIT socket and show the output. Flo -- Florian Lohoff flo@rfc822.org +49-171-2280134 Those who would give up a little freedom to get a little security shall soon have neither - Benjamin Franklin
participants (2)
-
Florian Lohoff -
Лавкин Михаил