topic ypclient startup fail when booting in Operating System - Linux

ypclient startup fail when booting

Kinmax — Wed, 28 Apr 2004 04:53:09 GMT

Dear all:
I have a xw4100 with RH7.3 installed.
ypclient start up fail when booting ,but after system is ready, I can start it up (# ypbind) manually and works fine.
Any suggestion?

thanks

Re: ypclient startup fail when booting

Alexander Chuzhoy — Wed, 28 Apr 2004 05:05:34 GMT

It probably needs a particular service to startup before it.
Find the ypclient script in /etc/rc3.d/

and rename it to a bigger number.
For example from S68scriptname
to S90scriptname.

Re: ypclient startup fail when booting

Roberto Polli — Wed, 28 Apr 2004 07:33:14 GMT

Posting meaningful logfiles could help to help.
Which error does it return?
Is portmap ok?
Is nis server listed in /etc/hosts?
Is nis started after network setup?

Please, post errors.

Peace, R.

Re: ypclient startup fail when booting

Steven E. Protter — Wed, 28 Apr 2004 11:00:16 GMT

This is almost always an environment problem.

At the command prompt as root:

env > /tmp/regenv.txt

In the startup script

env > /tmp/startenv.txt

boot the box

log on as root

cd /tmp
diff regenv.txt startenv.txt

Modify the startup script until all environment variables are consistent.

Then it will probably start.

I know its a lot of work, and probably won't earn me a rabbit, but sometimes you just have to do it the hard way.

SEP

Re: ypclient startup fail when booting

Kinmax — Thu, 13 May 2004 22:52:31 GMT

Hi all:
the error message is something like " can not connect with NIS server, timeout"
the hostname of NIS server is already in /etc/hosts.
I found that there's 2 way to make it work.

1. rename to a bigger number S90 as Alexander said.
or
2. add an entry in script
sleep 20
so it probebly network problem.

Next time I'll try the "hard way"

Thanks All

Re: ypclient startup fail when booting

Kinmax — Thu, 13 May 2004 23:01:25 GMT

Re: ypclient startup fail when booting

George Liu_4 — Fri, 27 Aug 2004 15:09:49 GMT

I had a similar problem, and fixed with the modification of yp.conf

using NIS server IP instead of server hostname