test

Solaris 10 5/09 Release Notes

System Cannot Communicate With ypbind After Upgrade (6488549)

This bug occurs during an upgrade from Solaris 10 Hardware 2 release to the current Solaris 10 5/09 release.

In the Solaris 10 Hardware 2 release, the name_service.xml file for any name service, such as NIS, NIS+, FILES, or LDAP is as follows:


# ls -l name_service.xml
lrwxrwxrwx   1 root     root     10 Apr 10 16:26 name_service.xml -> ns_files.xml

If the name service is NIS, the name_service.xml file links to ns_files.xml. However, the contents of the ns_files.xml are the same as ns_nis.xml.


  # cat /etc/release
                     Solaris 10 3/05 HW2 s10s_hw2wos_05 SPARC
           Copyright 2005 Sun Microsystems, Inc.  All Rights Reserved.
                        Use is subject to license terms.
                           Assembled 26 September 2005
  # cd /var/svc/profile
  # ls -l name_service.xml ns_files.xml ns_nis.xml
  lrwxrwxrwx   1 root   other    12 May 21 04:06 name_service.xml -> ns_files.xml
  -r--r--r--   1 root   sys     779 May 21 04:25 ns_files.xml
  -r--r--r--   1 root   sys     779 Jan 21  2005 ns_nis.xml
  #
  # diff ns_files.xml ns_nis.xml
  # diff name_service.xml ns_nis.xml

In the above output, the ns_nis.xml and ns_files.xml files are the same. This means that the name_service.xml file symbolically links to the wrong name service file. The name_service.xml file links to ns_files.xml. Instead, the name_service.xml file should link to the ns_nis.xml.

Note –

The fix for CR 6411084, the SUNWcsr install or postinstall script, creates the correct link only if name_service.xml is not a link file. If name_service.xml is already a symbolic link file, as in the Solaris 10 Hardware 2 release, the fix for CR 6411084 will not work.

After an upgrade from Solaris 10 Hardware 2 to the current Solaris 10 5/09 release, the following message is displayed on the console or logged in the messages file:


Oct 23 12:18:45 vt2000a automount[301]: [ID 366266 daemon.error] 
can't read nis map auto_master: can't communicate with ypbind - retrying

Also, the /network/nis/client:default service is offline.

Workaround: Choose one of the following workarounds: