NIS client issue after network cutt-off

[Antonio Egea]

Hello all and thank you for your time.

We are having a NIS issue after a network cutt-off. We have an important user (application managing) that are not recognized by the system.
a ypcat passwd | grep works perfectly so maybe it is not related with NIS at all.

With a ps -ef the user does not appear, only the uid, so maybe it is an automount problem?

Any help will be welcome, thank you all.

[Dennis Handly]

Every so often I've had NIS fail such that when I listed a directory I got numeric UIDs. I don't think I tried ypcat passwd.

To fix it, I just stop and start NIS.

[Peter Nikitka]

Hi,

check the passwd + group entries in
/etc/nsswitch.conf
for the order and type of the name resolutions:
Perhaps NIS is outconfigured ...

mfG Peter

[Dennis Handly]

>ME: To fix it, I just stop and start NIS:
/sbin/init.d/nis.client stop
/sbin/init.d/nis.client start

[Antonio Egea]

Thank you for your responses. We are working with the WTEC so when we have some more info or teh resolution I will post it.

The NIS client has been stopped and started a lot of times, I thought the pwgrd daemon would be root cause but looks like it is not.

[Antonio Egea]

Ok, all the process started working after some days, exactly as the last time. We don't know why this happened and couldn't do the proper tests. If this happens again and we can find the issue I will update you. Thank you!