ypclient startup fail when booting

[Kinmax]

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

[Alexander Chuzhoy · Accepted solution]

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.

[Roberto Polli]

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.

[Steven E. Protter]

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

[Kinmax]

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

[Kinmax]

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 a lot

[George Liu_4]

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

using NIS server IP instead of server hostname