Michael Joyner
2005-May-01 00:10 UTC
[Samba] every increasing connection count followed by load # overload
I am having a bizarre problem with a samba server here at Edward Waters College. Hopefully someone can give me insight to inform me what to look for. samba version = 3.0.14a SuSE 9.1, up-to-date-via-apt AD/W2K3 (no sp) Winbind using RID algorithm server purpose: HOMES, DESKTOPS, MY DOCUMENTS, PROFILES Quotas are: ON Filesystem: Reiser HW Raid 5 (MegaRaid) 4 logical processors (dual+ht). uname -a: Linux ewc05 2.6.5-7.151-smp #1 SMP Fri Mar 18 11:31:21 UTC 2005 i686 i686 i386 GNU/Linux If the number of connections exceeds 155 (per samba counting), the system load quick escalates to like 700+, and the user count also suddenly skyrockets. a majority of the samba processes seem to get stuck in state "D" inode count usage is unrealisticically high. :) I deleted all the samba db files, no change. If I put in a max connections limit of 155, it doesn't "fork bomb". Where should I start looking? -mjoyner@ewc.edu/mjoyner@vbservices.net
Craig White
2005-May-01 00:33 UTC
[Samba] every increasing connection count followed by load # overload
On Sat, 2005-04-30 at 20:10 -0400, Michael Joyner wrote:> I am having a bizarre problem with a samba server here at Edward Waters > College. > > Hopefully someone can give me insight to inform me what to look for. > > samba version = 3.0.14a > SuSE 9.1, up-to-date-via-apt > AD/W2K3 (no sp) > Winbind using RID algorithm > > server purpose: HOMES, DESKTOPS, MY DOCUMENTS, PROFILES > Quotas are: ON > Filesystem: Reiser > HW Raid 5 (MegaRaid) > > 4 logical processors (dual+ht). > uname -a: > > Linux ewc05 2.6.5-7.151-smp #1 SMP Fri Mar 18 11:31:21 UTC 2005 i686 > i686 i386 GNU/Linux > > If the number of connections exceeds 155 (per samba counting), the > system load quick escalates to like 700+, and the user count also > suddenly skyrockets. a majority of the samba processes seem to get stuck > in state "D" > > inode count usage is unrealisticically high. :) > > I deleted all the samba db files, no change. > > If I put in a max connections limit of 155, it doesn't "fork bomb". > > Where should I start looking? > > -mjoyner@ewc.edu/mjoyner@vbservices.net---- don't know the answer but just an observation - that is a pretty old kernel (and early 2.6 version) - doesn't SuSE have something in the 2.6.10 variety? Craig
Michael Joyner
2005-May-01 15:30 UTC
[Samba] every increasing connection count TERMINAL SERVER
I have a windows 2003 terminal server (sp1) that everytime I logout, the connection is not released. When I log back in, a new connection is created. Repeating this procedure ends up with LOTS of "stale" smbd processes still running. What do I do to fix this? What additional info is needed?
Michael Joyner
2005-May-01 22:23 UTC
[Samba] every increasing connection count TERMINAL SERVER
I have a windows 2003 terminal server (sp1) that everytime I logout, the connection is not released. When I log back in, a new connection is created. Repeating this procedure ends up with LOTS of "stale" smbd processes still running. What do I do to fix this? What additional info is needed?