No I don't think this indicates orphaned sockets, having many sockets for
mysql in the state TIME_WAIT state is quite normal, as a socket has to be
created for every connection and once a connection is established the socket
goes into a TIME_WAIT state( i am not sure for how long though), the 'show
processlist' only lists all the threads currently running..
JFYI
Socket: an end point for communication ( IP & Port)
Thread: quite similar to a process , a process can have multiple threads
....

Kishore Jalleda


On 2/1/06, Logg, Connie A. <[EMAIL PROTECTED]> wrote:
>
> Two days ago, a system that has been running fine started crashing...It
> could be for a variety of reasons which I am researchinig. However (running
> mysql 5.0.18) I notice the following from netstat:
> tcp        0      0 iepm-bw.slac.stanford.:1000 iepm-bw.slac.stanford:38672
> ESTABLISHED
> tcp        0      0 iepm-bw.slac.stanford.:1000 iepm-bw.slac.stanford:38775
> TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford.:1000 iepm-bw.slac.stanford:38781
> TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38780
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38781
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38782
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38783
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38776
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38777
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38778
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38779
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38772
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38773
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38774
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38768
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38769
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38770
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38771
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38764
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38765
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38766
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38760
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38761
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38762
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38763
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38756
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38757
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38758
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38759
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38752
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38753
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38754
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38755
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38748
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38749
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38750
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38751
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38744
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38745
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38746
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38747
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38742
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38743
> iepm-bw.slac.stanford.:1000 TIME_WAIT
> tcp        0      0 iepm-bw.slac.stanford:38672
> iepm-bw.slac.stanford.:1000 ESTABLISHED
>
> One of the messages in /var/log/messages is too many orphaned sockets.  Do
> the above indicate orphaned sockets? I logged into mysql root and did a
> 'show full processlist' and there were only one or two mysql processes.  Can
> someone explain why there might be so many tcp sockets taken up to connect
> to mysql (which is running on port 1000).
>
> Thanks, Connie Logg
> SLAC
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]
>
>

Reply via email to