[SOLVED?] write_socket_data bug

[Mike Edmunds]

Fellow sambaites,

Just wait a second now. The problems that you guys report are very
similar to the problems I saw when we implemented 2.0.6 as a PDC in a
mixed NT4.0/W9x environment: odd time-outs, apparently locking of
workstations, etc. We already have our DNS configured to do reverse
lookups and while it did help us find some DNS problems that we were
unaware of previously by examining the samba log files, it did not
resolve the problem to our satifaction. In the end we've abandoned the
PDC jazz for the time being. Note however that our DNS server does not
run on the samba server, but on another linux machine. Samba shouldn't
care where the reverse lookups are happening, should it? Am I missing
something (not being a DNS expert)?

I love this list!

Mike


 Steve McClary wrote:
> 
> This sounds like exactly the solution to the problems I've been having
> - could someone describe the process of adding reverse DNS in simple
> terms for novices like me?
> 
> Many thanks - the list has been quite helpful and I appreciate the
> gathered wisdom of all you subscribers.
> 
> Steve McClary
> 
> At 04:46 PM 11/28/2000 +0100, Otto Giesenfeld wrote:
> 
> > I can confirm that adding reverse address lookup seems to solve the
> > problem. Since we added reverse DNS about a week ago, there has not
> > been a single write_socket_data error message in the samba logs.
> > Many thanks for this useful tip.
> >
> > Otto Giesenfeld
> >
> > > -----Original Message-----
> > > From: Lee Howard [mailto:faxguy at deanox.com]
> > > Sent: Wednesday, November 15, 2000 8:02 PM
> > > To: samba at us5.samba.org
> > > Subject: [SOLVED?] write_socket_data bug
> > >
> > >
> > > Folks, I think that my write_socket_data problems have been
> > > solved thanks
> > > to a good pointer by someone last week on the list.
> > >
> > > The system in question runs named in addition to smb, and I
> > > did not have a
> > > reverse-DNS file set up for the local, private-IP
> > > (192.168.x.x), domain.
> > > Since I did that on Friday afternoon these are my logs:
> > >
> > > [root at virtue samba]# grep "write_socket_data" * | grep
> > "2000/11/13"
> > > log.smb:[2000/11/13 16:01:39, 0]
> > > lib/util_sock.c:write_socket_data(540)
> > > [root at virtue samba]# grep "write_socket_data" * | grep
> > "2000/11/14"
> > > [root at virtue samba]# grep "write_socket_data" * | grep
> > "2000/11/15"
> > > [root at virtue samba]#
> > >
> > > Normally, this system has had about 10 write_socket_data
> > > errors per day
> > > since the errors started occuring, so the logs listed above
> > > show a dramatic
> > > improvement, and my guess would be that I probably won't see
> > > any more of it
> > > in the degree that I have seen it before.
> > >
> > > Thanks all,
> > >
> > > Lee Howard

-- 

**************************************************************************
  Michael S. Edmunds                           GX Technology Corp.
  Center Support Manager                       5847 San Felipe, Suite
3500
  Email: mike at gxt.com                          Houston, TX 77057 
  tel: 713-789-7250                            http://www.gxt.com
  fax: 713-789-7201

        "Silence! I will not tolerate your insolence!" - Dr. Evil 


**************************************************************************