-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 20 Aug 2007, at 16:39, Koos van den Hout wrote: >> I know very little about ntp apart from what it does - but I have a >> server in the pool. I may already have given you an adequate >> description of my problem :) > > Well, you forgot to mention where you went from 'ntpd dies' to > 'lots of > traffic'. Those two should not be related because a stock ntpd does > not > use a lot of memory in client tracking.
That was cargo-culted clutching at straws I'm afraid. > In fact, with the number of clients you get from the pool, the > fixed-size > 'recently seen' list from ntpd just overflows. Right. >> Since joining the pool the server has been dying quite regularly. >> I've tracked the problem down to ntpd - the kernel reports out of >> memory just before the box dies - and the process id it mentions >> turns out to be ntpd in each case. > > Or, the Linux OOM process-killer (out of memory) selects ntpd as > target > because it fits the criteria of the OOM process-killer. What are > the exact > loglines surrounding the end of the ntpd process? Typically nothing (just -- MARK --) before. And about 25% of the time it happens the box dies shortly afterwards - within a minute or so as far as I can tell. - -- Andy Armstrong, hexten.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGyblVwoknRJZQnCERAuduAJ9Q/oB8pcigKG0KG+rTo21NJ+CEogCaAnkW kBfV6fnpHEUOJEeblj889AQ= =TQUE -----END PGP SIGNATURE----- _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
