For the latest information about upgrade support beginning with the Solaris 10 10/08 release, see Changes in Upgrade Support for Solaris Releases.
This section describes upgrade bugs. Some might occur while you are upgrading to Solaris 10 OS. Others might occur after you have completed upgrading.
During system upgrade to the Solaris 10 10/08 OS, the /etc/services and /etc/inet/services files are removed when the SUNWsmbar is installed. The following error messages are displayed on the system console upon reboot:
line1-v215 console login: Oct 6 15:40:57 inetd[457]: Property 'name' of instance svc:/network/stdiscover:default is missing, inconsistent or invalid Oct 6 15:40:57 inetd[457]: Property 'proto' of instance svc:/network/stdiscover:default is missing, inconsistent or invalid Oct 6 15:40:57 inetd[457]: Invalid configuration for instance svc:/network/stdiscover:default, placing in maintenance Oct 6 15:40:57 inetd[457]: Property 'name' of instance svc:/network/stlisten:default is missing, inconsistent or invalid Oct 6 15:40:57 inetd[457]: Property 'proto' of instance svc:/network/stlisten:default is missing, inconsistent or invalid Oct 6 15:40:57 inetd[457]: Invalid configuration for instance svc:/network/stlisten:default, placing in maintenance |
Workaround: To prevent removal of the /etc/services and /etc/inet/services during OS upgrade perform the following steps:
Stop all running Samba services:
#svcadm disable samba:default swat:default wins:default winbind:default |
Uninstall the SUNWsmbar package before upgrading the OS:
#pkgrm SUNWsmbar |
Upgrade the OS to the Solaris 10 10/08 release.
Re-install the SUNWsmbar package:
#pkgadd SUNWsmbar |
The shutdown command might cause the system to hang after it is upgraded to the Solaris 10 10/08 release. The hang occurs while the svc.startd daemon halts system services.
The Sun Java Web Console debug log file at /var/log/webconsole/console/console_debug_log displays if the web console service is cycling, starting and stopping.
Workaround: Type the following commands:
/usr/share/webconsole/private/bin/wcremove -i console svcadm clear system/webconsole:console smcwebserver start |
The wcremove command removes the server domain instance that was created for that specific console. When the console is restarted, a new domain instance is created.
When the lucreate and lumake commands are used on non-global zones which are not in the running state, the commands might not execute successfully. The contents of the original non-global zone and the copy might differ. Users might be unable to log in to the zone's console using the zlogin command. The following error message is displayed while using the zlogin command:
zlogin: makeutx failed |
The diagnostic output of the lucreate and lumake commands do not display any errors.
Workaround: Ensure that all non-global zones are in the running state before using the lucreate and lumake commands.
Upgrading to the Solaris 10 10/08 release using Solaris Live Upgrade, from the previous Solaris 8 and Solaris 9 releases fails. The install images compression file is now unzipped by using the 7za utility. The SUNWp7zip package is not included in the Solaris 8 and 9 releases. As a result, Solaris Live Upgrade fails.
Workaround: Choose one of the following workarounds:
Workaround 1: To upgrade your current Solaris 8 OS to the Solaris 10 10/08 release using Solaris Live Upgrade, perform the following steps:
For SPARC systems– Solaris Live Upgrade from the Solaris 8 release to the Solaris 10 10/08 release is supported. For step-by-step procedures on how to use Solaris Live Upgrade, see http://www.sun.com/bigadmin/features/articles/live_upgrade_patch.jsp.
For x86 systems– Solaris Live Upgrade from the Solaris 8 release to the Solaris 10 10/08 release is not supported. Instead, use the standard upgrade procedure or perform a Solaris Live Upgrade from the Solaris 8 OS to the Solaris 9 OS or to the Solaris 10 OS. Then you can perform a Solaris Live Upgrade from the Solaris 9 release or the Solaris 10 release to the Solaris 10 10/08.
Workaround 2: To upgrade your current Solaris 9 OS to the Solaris 10 10/08 release using Solaris Live Upgrade, apply the following patches:
For SPARC systems– 137477-01 or later
For x86 systems– 137478-01 or later
Workaround 3: To upgrade your current Solaris 10 OS to the Solaris 10 10/08 release by using Solaris Live Upgrade, apply the following patches:
For SPARC systems– 137321-01 or later
For x86 systems– 137322-01 or later
Various processes running in non-global zones using /tmp might crash after the zone has been upgraded using Solaris Live Upgrade. The upgrade process changes permissions on the /tmp directory which leads to applications failures. Users will see drwxr-xr-x permissions instead of the correct drwxrwxrwx permissions.
Workaround: Choose one of the following workarounds:
Workaround 1: Before activating the new boot environment, perform the following steps:
Mount the disk:
# mount /dev/dsk/c1t1d0s6 /mnt |
Fix the permissions:
# chmod 1777 /mnt/zone/*/root/tmp |
Then unmount the disk:
# umount /mnt |
This workaround fixes all zones at once.
Workaround 2: If you have already booted the new boot environment, log in to the system as the root user. Halt the zone and manually set correct permissions on the /tmp directory. Type the following command:
# chmod 1777 /path/root/tmp |
where path is the zone's zonepath.
Disk space reallocation (DSR) upgrade with zones fails if zones are installed in the /opt directory. Upgrade might fail during the restoration of the DSR archive. In some cases, the upgrade might be successful, but the system cannot be rebooted.
Workaround: Ensure that the root file system is not 100% full before upgrade. Remove some files before upgrade so that the root slice is less than 90% full.
When you upgrade Solaris Trusted Extensions from the Solaris 10 11/06 or Solaris 10 8/07 release to the current Solaris 10 10/08 release, unwanted localized Solaris Trusted Extensions packages are installed on your system. This bug occurs because the Solaris Trusted Extensions installer in theSolaris 10 11/06 or Solaris 10 8/07 releases installs localized packages by default. No error message is displayed.
Workaround: Before upgrading Solaris Trusted Extensions to the current release, remove the following localized Solaris Trusted Extensions packages:
SUNWjdtts |
SUNWkdtts |
SUNWjmgts |
SUNWkmgts |
SUNWjtsman |
SUNWktsu |
SUNWjtsu |
SUNWodtts |
SUNWtgnome-l10n-doc-ja |
SUNWtgnome-l10n-ui-ko |
SUNWtgnome-l10n-ui-it |
SUNWtgnome-l10n-ui-zhHK |
SUNWtgnome-l10n-ui-sv |
SUNWtgnome-l10n-ui-es |
SUNWtgnome-l10n-doc-ko |
SUNWtgnome-l10n-ui-ptBR |
SUNWtgnome-l10n-ui-ja |
SUNWtgnome-l10n-ui-zhTW |
SUNWtgnome-l10n-ui-zhCN |
SUNWtgnome-l10n-ui-fr |
SUNWtgnome-l10n-ui-de |
SUNWtgnome-l10n-ui-ru |
This bug occurs during an upgrade from Solaris 10 Hardware 2 release to the current Solaris 10 10/08 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.
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 10/08 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:
Workaround 1: Before an upgrade, remove the /var/svc/profile/name_service.xml file.
Workaround 2: After an upgrade, change the /var/svc/profile/name_service.xml link to the correct ns_<xxx>.xml file, based on the name service.
A non-global zone that has been installed but never booted or made ready prevents a system from being upgraded correctly. No error message is displayed.
Workaround:
If such a zone is found, the zone should be made ready and then halted prior to starting the upgrade. For example:
global# zoneadm -z myzone ready ; zoneadm -z myzone halt |
Upgrading a Solaris 10 3/05 system or a Solaris 10 1/06 system to the Solaris 10 10/08 release with non-global zones might cause the SMF service that mounts local file systems to fail in the non-global zones. As a result, other services in the non-global zones might fail to start.
After upgrading a Solaris 10 system with non-global zones to the Solaris 10 10/08 release, services might be in the maintenance state. For example:
# zlogin myzone svcs -x svc:/system/filesystem/local:default (local file system mounts) State: maintenance since Wed May 24 13:18:06 2006 Reason: Start method exited with $SMF_EXIT_ERR_FATAL. See: http://sun.com/msg/SMF-8000-KS See: /var/svc/log/system-filesystem-local:default.log Impact: 18 dependent services are not running. (Use -v for list.) |
Workaround:
Reboot the non-global zone from the global zone. For example:
global# zoneadm -z myzone reboot |
In this Solaris 10 release, Solaris Volume Manager displays device ID output in a new format. Solaris 9 9/04 OS, which introduced device ID support in disk sets, does not recognize the new format. When you upgrade to Solaris 10 OS from the Solaris 9 9/04 release, device IDs that are associated with existing disk sets are not updated in the Solaris Volume Manager configuration. If you need to revert to Solaris 9 9/04 OS, configuration changes made to disk sets after the upgrade might not be available to Solaris 9 9/04 OS. For more information, see Chapter 25, Troubleshooting Solaris Volume Manager (Tasks), in Solaris Volume Manager Administration Guide.
The upgrade progress bar does not appear when you use the Solaris Live Upgrade software in the following manner:
You use the Solaris 10 10/08 CD media to upgrade the OS.
You upgrade a boot environment by using the luupgrade command with the following options:
-i to install from the CD media
-O “-nodisplay -noconsole” to run the installer on the second CD in text mode and without user interaction
You are upgrading to the Solaris 10 10/08 software from the following releases:
Solaris 9 release
Solaris 10 release
For example, if you run the following command, the progress bar should be displayed after you see the following output:
Running installer on BE s10u1. |
However, the bar fails to appear.
# luupgrade -i -n s10u1 -s /net/installsrv/export/s10u1 -O "-nodisplay -noconsole" Validating the contents of the media /net/installsvr/export/s10u1. The media is a standard Solaris media. The media contains a standard Solaris installer. The media contains Solaris 3 version 10. Mounting BE s10u1. Running installer on BE s10u1. |
No error message is displayed.
Workaround: Use the prstat command. This command enables you to watch the progress while packages are being added during the installation.
If you use Solaris Live Upgrade to upgrade from the Solaris 8 or Solaris 9 releases to Solaris 10 OS, obsolete uninstaller programs are not removed. These uninstaller programs from the previous OS remain in the system's /var/sadm/prod directory.
The following obsolete uninstallers are not removed.
uninstall_Alternate_Pathing_2_3_1.class uninstall_CDRW_1_1.class o uninstall_CDRW_1_0.class uninstall_Bonus_Localization_-_Catalan_CDE_Desktop.class uninstall_Bonus_Localization_-_Polish_CDE_Desktop.class uninstall_Bonus_Localizations_-_Russian_CDE_Desktop.class uninstall_Capacity_on_Demand_1_0.class uninstall_Java3D_1_3_1.class uninstall_Java3D_1_3.class uninstall_Java3D_1_2_1_04.class uninstall_Java3D_1_2_1_03.class uninstall_Lights_Out_Management_2_0.class uninstall_Man_Page_Supplement.class uninstall_OpenGL_1_3.class uninstall_OpenGL_1_2_3.class uninstall_Netra_ct_Platform_1_0.class uninstall_Netra_t11xx_Alarms_2_0.class uninstall_Netscape_6_2_3.class uninstall_Netscape_6_2_1_Beta.class uninstall_PC_launcher_1_0_2.class uninstall_PC_launcher_1_0_1_PCfileviewer_1_0_1.class uninstall_RSC_2_2_2.class uninstall_RSC_2_2_1.class uninstall_RSC_2_2.class uninstall_ShowMeTV_1_3.class uninstall_Solaris_9_French_Localization.class uninstall_Solaris_9_German_Localization.class uninstall_Solaris_9_Hong_Kong_Traditional_Chinese_Localization.class uninstall_Solaris_9_Italian_Localization.class uninstall_Solaris_9_Japanese_Localization.class uninstall_Solaris_9_Korean_Localization.class uninstall_Solaris_9_Simplified_Chinese_Localization.class uninstall_Solaris_9_Spanish_Localization.class uninstall_Solaris_9_Swedish_Localization.class uninstall_Solaris_9_Traditional_Chinese_Localization.class uninstall_Solaris_On_Sun_Hardware_Documentation.class uninstall_Sun_Hardware_AnswerBook.class uninstall_SunATM_5_0.class uninstall_SunATM_5_1.class uninstall_SunFDDI_PCI_3_0.class uninstall_SunFDDI_SBus_7_0.class uninstall_Sun_Fire_880_FC-AL_Backplane_Firmware_1_0.class uninstall_Sun_Fire_B10n_Load_Balancing_Blade_1_1.class uninstall_SunForum_3_1.class uninstall_SunForum_3_2.class uninstall_SunHSI_PCI_3_0.class uninstall_SunHSI_SBus_3_0.class uninstall_SunScreen_3_2.class uninstall_SunVTS_5_1_PS6.class uninstall_SunVTS_5_1_PS5.class uninstall_SunVTS_5_1_PS4.class uninstall_SunVTS_5_1_PS3.class uninstall_SunVTS_5_1_PS2.class uninstall_SunVTS_5_1_PS1.class uninstall_SunVTS_5_0.class uninstall_System_Management_Services_1_4.class uninstall_System_Management_Services_1_3.class uninstall_System_Management_Services_1_2.class uninstall_System_Service_Processor_3_5.class uninstall_WBEM_DR_1_0.class uninstall_Web_Start_Wizards_SDK_3_0_2.class uninstall_Web_Start_Wizards_SDK_3_0_1.class uninstall_Web_Start_Wizards_SDK.class uninstall_XML_Libraries_2_4_12.class |
Workaround: After you upgrade the system, manually remove the obsolete uninstallers in the /var/sadm/prod directory.
This Solaris 10 release introduces changes in pam_ldap functionality. When you upgrade to the current release, pam_ldap configurations in your existing pam.conf configuration file are not updated to reflect these changes. If pam_ldap configuration is detected, the CLEANUP file that is generated at the end of the upgrade contains the following notification:
/etc/pam.conf please examine/update the pam_ldap configuration because its functionality has changed, refer to pam_ldap(5) documentation for more information |
Workaround: After the upgrade, examine /etc/pam.conf. If necessary, modify this file manually to be compatible with the new functionalities of pam_ldap. The modifications involve password prompting such as the use_first_pass and try_first_pass options as well as password updates. For more information about updating pam.conf, refer to the pam_ldap(5) man page and documentation.
When using the Solaris Live Upgrade luupgrade(1M) command with the -i option to complete an upgrade of an inactive boot environment, the text that the installers display might be unreadable in some languages. The text is corrupted when the installers request fonts that do not exist on the older release that is on the current boot environment.
Workaround: Choose one of the following workarounds:
Use a combined network installation image to do the installation.
Enable the C locale by setting the environment variable on your system.
When you upgrade from the Solaris 8 software to the Solaris 10 release, a problem is encountered when the SUNWjxcft package is removed. The following error message is recorded in the upgrade_log file:
Removing package SUNWjxcft: Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.upr Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.scale Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.alias Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.upr Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.scale Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.alias Removal of <SUNWjxcft> was successful |
Workaround: Ignore the error message.
If you upgrade to the Solaris 10 release on a system that is running a third-party Secure Shell, such as OpenSSH from the /etc/init.d/sshd daemon, the upgrade disables the existing Secure Shell daemon. During an upgrade, Solaris 10 software overwrites the contents of /etc/init.d/sshd.
Workaround: Choose one of the following workarounds:
If you do not want the Secure Shell protocol server program on your system, do not install the SUNWsshdr and SUNWsshdu packages during the upgrade.
If you do not want the Secure Shell protocol server or client programs on your system, do not install the Secure Shell Cluster (SUNWCssh) during the upgrade.
If the /export directory is near full capacity when you upgrade to the Solaris 10 release, space requirements for /export are miscalculated. The upgrade then fails. This problem commonly occurs if a diskless client is installed. Another instance of when the problem occurs is when third-party software is installed in the /export directory. The following message is displayed:
WARNING: Insufficient space for the upgrade. |
Workaround: Before you upgrade, choose one of the following workarounds:
Rename the /export directory temporarily, until the upgrade is completed.
Temporarily comment out the /export line in the /etc/vfstab file until the upgrade is completed.
If /export is a separate file system, then unmount /export before you perform the upgrade.
If your system currently supports diskless clients that were installed with the Solstice AdminSuiteTM 2.3 Diskless Client tool, you must perform the following two steps:
Delete all existing diskless clients that are the same Solaris version and architecture as the server.
Install or upgrade to the Solaris 10 release.
For specific instructions, see the System Administration Guide: Basic Administration.
If you attempt to install the Solaris 10 software over existing diskless clients, the following error message might be displayed:
The Solaris Version (Solaris version-number) on slice <xxxxxxxx> cannot be upgraded. There is an unknown problem with the software configuration installed on this disk. |
In this error message, version-number refers to the Solaris version that is currently running on your system. <xxxxxxxx> refers to the slice that is running this version of the Solaris software.