Hi I have a problem with samba 2.2.2. (see below) I'm sure it's easy to solve but I can't figure out what to do. The thing I find confusing is that the newer and more powerful server can't perform as good as the old one. Any ideas? /Jonas Story: We had all our user homes on a Sun Ultra 2 (solaris 2.6, 30Gb store) and samba 2.0.6, and all was fine. But we ran out of disk and moved all homes to a Sun e420 (solaris 8, 100Gb store) and samba 2.2.0. Then the troubles began, at least ones a week people cant mount their shares and the NT account gets locked. When this happens the user receive a message "Out of connections". The clients are ~30 NT 4.0. I have "upgraded" to Samba 2.2.2 but the fault remains. Config: # Global parameters [global] workgroup = foo netbios name = foodoo security = SERVER encrypt passwords = Yes password server = somentserver log level = 2 max log size = 50 os level = 0 preferred master = False local master = No domain master = False wins server = 192.168.1.1 deadtime = 15 interfaces = qfe0 [homes] read only = No [home] path = /home/loke read only = No
On Wednesday 19 December 2001 05:54, Jonas Nilsson wrote:> Hi > I have a problem with samba 2.2.2. (see below) I'm sure it's easy to > solve but I can't figure out what to do. The thing I find confusing is > that the newer and more powerful server can't perform as good as the old > one. Any ideas? > > /Jonas > > Story: > We had all our user homes on a Sun Ultra 2 (solaris 2.6, 30Gb store) and > samba 2.0.6, and all was fine. > But we ran out of disk and moved all homes to a Sun e420 (solaris 8, > 100Gb store) and samba 2.2.0. Then the troubles began, at least ones a > week people cant mount their shares and the NT account gets locked. When > this happens the user receive a message "Out of connections". The > clients are ~30 NT 4.0. I have "upgraded" to Samba 2.2.2 but the fault > remains.Did you just copied entire filesystem to new box or no? If you don't, you have different configs, samba versions, libc versions etc. It can be very time consuming but with (much of) mix and match you can identify what exactly caused this. I'd suggest cloning entire 'old' installation onto new box and testing that first. When you'll find out the cause, tell us too, ok? -- vda
Well, I was having similar issues here. Andrew Bartlett and I worked through some of the issues here. Are you using any *NIX machines to connect to this samba server? Can you grab CVS and compile the tdbdump tool that is in the samba-2.2.2/source/tdb directory and do a dump of the sessionid.tdb: tdbdump sessionid.tdb > dumpfilename as it appears that the issue for me was that I was having Samba clients spawn off hundreds or even thousands of sessions in the sessionid.tdb and it reached it's maximum of 3000. This happens for me most often when I have an application accessing a large number of realitively small files at the same time. If you don't have anybody going at Samba from *NIX it still might be useful to see if there are a large number of sessions in the tdb. That might point to something other than the Samba client code. Thanks, Chris Tooley On Wed, 2001-12-19 at 01:54, Jonas Nilsson wrote:> Hi > I have a problem with samba 2.2.2. (see below) I'm sure it's easy to > solve but I can't figure out what to do. The thing I find confusing is > that the newer and more powerful server can't perform as good as the old > one. Any ideas? > > /Jonas > > Story: > We had all our user homes on a Sun Ultra 2 (solaris 2.6, 30Gb store) and > samba 2.0.6, and all was fine. > But we ran out of disk and moved all homes to a Sun e420 (solaris 8, > 100Gb store) and samba 2.2.0. Then the troubles began, at least ones a > week people cant mount their shares and the NT account gets locked. When > this happens the user receive a message "Out of connections". The > clients are ~30 NT 4.0. I have "upgraded" to Samba 2.2.2 but the fault > remains. > > Config: > # Global parameters > [global] > workgroup = foo > netbios name = foodoo > security = SERVER > encrypt passwords = Yes > password server = somentserver > log level = 2 > max log size = 50 > os level = 0 > preferred master = False > local master = No > domain master = False > wins server = 192.168.1.1 > deadtime = 15 > interfaces = qfe0 > > [homes] > read only = No > > [home] > path = /home/loke > read only = No > > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba