Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU |
On Mon, 17 Mar 2008 10:53:32 -0400 Matthew Gillen <[hidden email]> wrote: > Jerry Feldman wrote: > > We are using NIS in our office to serve our 6 people on our 5 servers. > > Up until last week I was using the IA64 system as the NIS server, but > > that system every once in a while tends to lock out the console. But, > > YP was very stable. I moved NIS over to an x86_64 system running RHEL 4 > > update 3. Every once in a while the clients report an RPC timeout and a > > YPBINDPROC_DOMAIN: Domain not found. All 5 systems are connected > > directly to a GB switch. I saw this happen once last week shortly > > after I moved YP, but the system that was affected had not mounted its > > NFS mounts. I am seeing the following messages on the NIS server. > > Mar 17 08:17:12 boslc03 ypserv[31495]: children is below 0 (-115)! > > I'd whip out wireshark/tcpdump and look for strange things. On a parallel > track, it's pretty easy to set up NIS slaves, so you might want to make one or > more of your other servers able to answer NIS questions if the master isn't > available.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |