Maximum Session IDs

[Andrew Bartlett]

Chris Tooley wrote:
> 
> On Wed, 2001-12-05 at 06:30, Andrew Bartlett wrote:
> > Chris Tooley wrote:
> > >
> > > On Mon, 2001-12-03 at 15:23, Andrew Bartlett wrote:
> > > > Chris Tooley wrote:
> > > > >
> > > > > Sorry forgot the subject, Evolution dumped on me in the middle of composing the first time round.
> > > > >
> > > > > I'm getting the following errors.  How do I get rid of the max on
> > > > > session IDs?
> > > > >
> > > > > [2001/12/03 09:11:00, 1] smbd/session.c:session_claim(88)
> > > > >   session_claim: out of session IDs (max is 3000)
> > > > > [2001/12/03 09:11:00, 1] smbd/password.c:register_vuid(316)
> > > > >   Failed to claim session for vuid=100
> > > > > [2001/12/03 09:11:51, 2] smbd/reply.c:reply_sesssetup_and_X(980)
> > > > >   Defaulting to Lanman password for tlowke
> > > > > [2001/12/03 09:11:51, 1] smbd/session.c:session_claim(88)
> > > > >   session_claim: out of session IDs (max is 3000)
> > > > > [2001/12/03 09:11:52, 1] smbd/password.c:register_vuid(316)
> > > > >   Failed to claim session for vuid=100
> > > > > [2001/12/03 09:11:52, 2] smbd/server.c:exit_server(458)
> > > > >   Closing connections
> > > > >
> > > > > I'm running samba 2.2.2 on RedHat 6.2 with kernel 2.2.19.  I've
> > > > > restarted samba and that seems to have fixed the problem temporarily.
> > > >
> > > > OK, do you really have 3000 users logged into your server?
> > >
> > > No, more like about 30.  It's happening about every 3 or 4 hours though.
> > >
> > > >
> > > > If not, we have a bug in there somehwere...
> > > >
> > > Crap, this just started happening, and it's going to severely hamper my
> > > job.
> > >
> > > Thanks for looking into it.  Let me know what you need.
> >
> > This smells like TDB corruption.
> >
> > We increment the counter until we get a number that we can correctly
> > store.  So, if nothing can be stored at all, then you get that error.
> >
> > Check your disk space for the samba locks directory.
> It's installed as a RedHat RPM.  Since installing 2.2.2 I've seen slowly
> degrading Network performance and this Maximum Session ID's issue.
> Restarting Samba seems to fix both temporarily.  At the moment I've had
> to set a cron job to restart Samba every morning and evening.  That
> doesn't stop the Session ID's problem from stopping things during the
> middle of the day though.  Should I destroy the stuff (except smbpasswd)
> in /etc/samba/ and build them up again?  I've only got one Win2k box to
> add to the domain.
> 
> [user at server user]$ df
> Filesystem           1k-blocks      Used Available Use% Mounted on
> /dev/md1                521684     75216    419968  15% /
> /dev/md0                 23239      8082     13957  37% /boot
> /dev/md2               1035596    783804    199184  80% /usr
> /dev/md3                380760    191034    170053  53% /var
> /dev/md4                256586        84    243254   0% /tmp
> /dev/md5               6048196   3838580   1902384  67% /home
> /dev/md7              29538324  15955972  12081888  57% /mnt/amoadata

Hmm.

Shut down Samba, delete /var/locks/samba/sessionid.tdb. 

Try to reproduce.

Turn up the log level, and give me a some logs of the code just before
it thinks its out of sessionids.

Maybe you could drop past the #samba-technical IRC channel - This kind
of issue bothers me and I would like it squashed dead.

Finally, download the current SAMBA_2_2 cvs branch (pserver.samba.org
for details) and see if it still occours.

Andrew Bartlett

-- 
Andrew Bartlett                                 abartlet at pcug.org.au
Manager, Authentication Subsystems, Samba Team  abartlet at samba.org
Student Network Administrator, Hawker College   abartlet at hawkerc.net
http://samba.org     http://build.samba.org     http://hawkerc.net