We're had some recurring problems with nmbd's on Solaris 2.7 and Irix 6.5 failing to renew their WINS registrations in a timely manner causing the records to become tombstoned. While we've solved it by issuing "pkill" and "killall", respectively, of nmbd nightly from root's crontab, I wanted to alert the authors and other administrators to the problem so similar workarounds can be implemented where appropriate and, hopefully, a fix can be implemented into 2.0.7 before its release. I've been conducting some tests to try to improve responsiveness for our clients. We are using ATM connected servers - and in lieu of MPOA, I've been experimenting with multihoming the systems on each subnet. I've tried a number of combinations of interface settings in an attempt to get all the interfaces (LANE and CLIP) to register in WINS and I'm unable to do so. I've tried specifying the interfaces as "el* ci*", "el0 el1 el1:1 ci0", "x.x.x.x/24 y.y.y.y/24", but no combination has successfully registered all IP addresses in WINS. Scott =============================================================== Scott Armstrong In the days before volcanoes Department of the Army were invented, lava had to be Night Vision and Electronic hand carried down from the Sensors mountain and poured on the AMSEL-RD-NV-SSA-NS sleeping villagers. 10221 Burbeck Road This took a great deal of Ft. Belvoir, VA 22060-5806 time. armstron@NVL.ARMY.MIL Voice (703) 704-1764 Fax (703) 704-1953 <<Armstrong, Scott.vcf>> -------------- next part -------------- A non-text attachment was scrubbed... Name: Armstrong, Scott.vcf Type: application/octet-stream Size: 538 bytes Desc: not available Url : http://lists.samba.org/archive/samba/attachments/20000329/0b482378/ArmstrongScott.obj
"Armstrong, Scott" wrote:> > We're had some recurring problems with nmbd's on Solaris 2.7 and Irix 6.5 > failing to renew their WINS registrations in a timely manner causing the > records to become tombstoned. While we've solved it by issuing "pkill" and > "killall", respectively, of nmbd nightly from root's crontab, I wanted to > alert the authors and other administrators to the problem so similar > workarounds can be implemented where appropriate and, hopefully, a fix can > be implemented into 2.0.7 before its release.Can you investigate what TTL is being returned to the nmbd from the WINS server when it registers a name ? The way the code works is it registers the name, requesting a time to live of "max ttl" from the smb.conf (3 days by default), and then gets the TTL from the WINS reply packet and sets that as the internal "death time", and then sets the "refresh time" to be half the returned value from the WINS server. Thus nmbd should refresh its names in plenty of time (that's the theory). If this is failing I'd like to track it down. Regards, Jeremy Allison, Samba Team. -- -------------------------------------------------------- Buying an operating system without source is like buying a self-assembly Space Shuttle with no instructions. --------------------------------------------------------
I am seeing the same problem with nmbd failing to renew WINS
registrations. The server is running Solaris 2.6, and I am running
Samba 2.0.6 nmbd and smbd from inetd.
Everything works well for a while. The renewal interval on the WINS
server is set to 144 hours (six days). The time is moved back regularly
through the day (it keeps it six days out, I don't see it doing the
"refresh" at half the interval as you mention). The Samba server
appears to reregister every 20 minutes. Then the date stops getting
moved back, and the registration entries are eventually tombstoned. The
nmbd appears to still be carrying out its other functions, but it has
stopped registering with the WINS server.
"Armstrong, Scott" wrote:
>
> We're had some recurring problems with nmbd's on Solaris 2.7
and Irix 6.5
> failing to renew their WINS registrations in a timely manner
causing the
> records to become tombstoned. While we've solved it by
issuing "pkill" and
> "killall", respectively, of nmbd nightly from root's
crontab, I wanted to
> alert the authors and other administrators to the problem so
similar
> workarounds can be implemented where appropriate and,
hopefully, a fix can
> be implemented into 2.0.7 before its release.
Can you investigate what TTL is being returned to the nmbd
from the WINS server when it registers a name ?
The way the code works is it registers the name, requesting
a time to live of "max ttl" from the smb.conf (3 days by
default), and then gets the TTL from the WINS reply packet and
sets that as the internal "death time", and then sets the
"refresh time" to be half the returned value from the
WINS server.
Thus nmbd should refresh its names in plenty of time (that's
the theory). If this is failing I'd like to track it down.
Regards,
Jeremy Allison,
Samba Team.
--
--------------------------------------------------------
Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.
--------------------------------------------------------
--
---------------------------------------------------------------------
Jay D. Anderson John Deere Davenport Works
Jay@Deere.com P.O. Box 4198
Phone: 319.388.4268 Fax: 319.388.4159 Davenport, Iowa 52808
http://www.dw.deere.com/~hz01930 http://www.geneseo.net/~jaya
| I am seeing the same problem with nmbd failing to renew WINS | registrations. The server is running Solaris 2.6, and I am running | Samba 2.0.6 nmbd and smbd from inetd. Hmmn: I'm not sure I'd want to run nmbd it from inetd, it might have too much latency and miss UDP packets. This would give you intermittancies... Just for stability's sake, consider running it as a daemon. --dave (who loves inetd, but not for everything...) c-b -- David Collier-Brown in Boston Phone: (781) 442-0734, Room BUR03-3632