Solaris / OpenSolarisThis forum is for the discussion of Solaris, OpenSolaris, OpenIndiana, and illumos.
General Sun, SunOS and Sparc related questions also go here. Any Solaris fork or distribution is welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
SOLUTION: Fsck'ed each workstation, sys-unconfigured them, started with fresh hostname/NIS/etc info, and all is well. Had to vi a few lines in /etc/resolv.conf, but other than that, working as intended. This is maybe not the best way to do it, but they work.
After a scheduled power outage at a site I regularly visit, 3 Solaris 8 boxes fail to connect to the NIS server after they've come back online. The systems completely hang at 'WARNING: Failed to connect to NIS server, blah blah'.
The NIS domain is simply 'domain4', and the Solaris workstations themselves can ping the NIS servers just fine, but NIS times out every time the workstations are rebooted.
All 3 boxes exhibit the same exact behavior - they boot, hang when they get to NIS.
I've moved /etc/rc2.d/S71rpc for a while to try and troubleshoot, but that's got me nowhere.
I need two and maybe three extra sets of eyes to figure this one out.
Distribution: Solaris 11.4, Oracle Linux, Mint, Debian/WSL
Posts: 9,789
Rep:
Unless you have other NIS clients working fine with the NIS server, I would have a look at it. Being able to ping it doesn't imply the NIS service works.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.