Sponsored Content
Full Discussion: Patching error
Operating Systems Solaris Patching error Post 302355157 by gnom on Monday 21st of September 2009 07:24:16 PM
Old 09-21-2009
Patching error

Hi Gurus
I wanted to patch two servers yesterday with the SUN provided patch_cluster for solaris 10

One server is had the same patchlevel before and after patching
Code:
SunOS svr10008 5.10 Generic_125100-10 sun4v sparc SUNW,Sun-Fire-T200

The other had after the patching a different patchlevel
Code:
SunOS svr10009 5.10 Generic_138888-07 sun4u sparc SUNW,Sun-Fire-V890

I am concerned about the many rc 1. I never had them before. A second run of the install_cluster script changed nothing. Smilie

Any advice is much appreciated. Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Patching Solaris

Hi quick and question for the unix expert here i downloaded the lastest patch from sun. i'm ready to patch my production server. should i just patch it as is or go in to init 1 or init S to do the patching. someone told me that you can just patch the server in init 3 and some other... (2 Replies)
Discussion started by: xNYx
2 Replies

2. Solaris

Patching error on Solaris 2.6 - I know the 'fix' - do you?

Patching a Solaris 2.6 server (running application that wasn't approved for anything higher) in single user mode - loading about 120 patches. Following error started occurring after patch 105356-23 /kernel//kernel/strmod/ptem: undefined symbol miocpullup ptem error doing common Actual... (0 Replies)
Discussion started by: RTM
0 Replies

3. Solaris

Can not boot after patching.

Last night I installed some patches by using update manager on my solaris 10 on AMD 64. Now I cannot boot. It is keep failing. I am able to go to failsafe and I am able ot update the boot archieve file but I am not sure what to do after this. I think it is not boot problem, I think my kernel is... (5 Replies)
Discussion started by: saif
5 Replies

4. Solaris

Patching

Hi all, I'm new to Solaris. How can i make sure that all my servers are patched to the same level. When i do a uname -a, i see different level. How can i make sure that they are having the same patches. Any expert to guide me through pls? eg. ServerA#uname -a SunOS ServerA 5.10... (0 Replies)
Discussion started by: ahlude
0 Replies

5. Solaris

Patching

Hi all Ive got 12 odd sun servers, running solars 8, 9 and soon 10. Have to admit I havent patched for years. Infact the last time I did patch a load of servers, sun provided you will a small script which would review the current patch levels, create a xml file that you would use on sunsolve... (3 Replies)
Discussion started by: sbk1972
3 Replies

6. Solaris

Regarding Solaris patching..

Hi Gurus, I am new to solaris patching.. while doing the patching do we need to have the root previligies and also need help while doing patching work if the server has veritas on it........ Thanks in advance.......... (10 Replies)
Discussion started by: samanth009
10 Replies

7. Solaris

Patching utility?

I know the smpatch utility has the set-uid 0 bit on it, so I'm wondering what privileges does it take to use this tool? I don't have to be root do I? How can I let a normal account do maintenance? Thanks in advance. (4 Replies)
Discussion started by: solarisx86
4 Replies

8. Solaris

Solaris Patching.

Hi All, I have a question ? Which all patches need to be applied in single user mode and which all not .Is there any rule all patches need to be applied in /var/tmp.Thanks in advance for answers.:) (1 Reply)
Discussion started by: rama krishna
1 Replies

9. Solaris

Mail loops back to me error in /var/adm/message after patching

Hi, I am getting the below messsage in /var/adm/message after patching but sendmail is working after restoring the backup file. sendmail: q4G7U1Cj014774: SYSERR(root): 127.0.0.1 config error: mail loops back to me (MX problem?) sendmail: q4G801cw025824: SYSERR(root): 127.0.0.1 config... (3 Replies)
Discussion started by: fayaz
3 Replies

10. Solaris

Live Upgrade Patching Error: Unable to write vtoc

Attempting to patch several servers using live upgrade Release: Oracle Solaris 10 8/11 s10x_u10wos_17b X86 Error I'm receiving is in the message in the log below tail -15 /var/svc/log/rc6.log Legacy init script "/etc/rc0.d/K50pppd" exited with return code 0. Executing legacy init... (5 Replies)
Discussion started by: Siralos
5 Replies
platform(4)							   File Formats 						       platform(4)

NAME
platform - directory of files specifying supported platforms SYNOPSIS
.platform DESCRIPTION
The Solaris operating environment release includes the .platform directory, a new directory on the Solaris CD image. This directory con- tains files (created by Sun and Solaris OEMs) that define platform support. These files are generically referred to as platform definition files. They provide a means to map different platform types into a platform group. Platform definition files in the .platform directory are used by the installation software to ensure that software appropriate for the architecture of the system will be installed. Sun provides a platform definition file named .platform/Solaris . This file is the only one that can define platform groups to which other platform definition files can refer. For example, an OEM platform definition file can refer to any platform group specified in the Solaris platform definition file. Other platform definition files are delivered by OEMs. To avoid name conflicts, OEMs will name their platform definition file with an OEM- unique string. OEMs should use whatever string they use to make their package names unique. This unique string is often the OEM's stock symbol. Comments are allowed in a platform definition file. A "#" begins a comment and can be placed anywhere on a line. Platform definition files are composed of keyword-value pairs, and there are two kinds of stanzas in the file: platform group definitions and platform identifications. o Platform group definitions: The keywords in a platform group definition stanza are: PLATFORM_GROUP The PLATFORM_GROUP keyword must be the first keyword in the platform group definition stanza. The value assigned to this keyword is the name of the platform group, for example: PLATFORM_GROUP=sun4c The PLATFORM_GROUP name is an arbitrary name assigned to a group of platforms. However, PLATFORM_GROUP typically equals the output of the uname -m command. PLATFORM_GROUP value cannot have white space and is limited to 256 ASCII characters. INST_ARCH The instruction set architecture of all platforms in the platform group, for example: INST_ARCH=sparc The INST_ARCH keyword value must be the value returned by the uname -p command on all platforms in the platform group. o Platform identifications: The keywords in a platform identification stanza are: PLATFORM_NAME The PLATFORM_NAME keyword must be the first keyword in the platform identification stanza. The PLATFORM_NAME is the name assigned to the platform, for example: PLATFORM_NAME=SUNW,SPARCstation-5 Typically, this name is the same as the value returned by the uname -icommand on the machine, but it need not be the same. The PLATFORM_NAME value cannot have white space and is limited to 256 ASCII characters. If it contains paren- theses, it must contain only balanced parentheses. For example. the string "foo(bar)foo" is a valid value for this keyword, but "foo(bar" is not. The other keywords in the platform identification stanza can be in any order, as long as the PLATFORM_NAME keyword is first. PLATFORM_ID The value returned by the uname -i command on the machine, for example: PLATFORM_ID=SUNW,SPARCstation-5 MACHINE_TYPE The value returned by the uname -m command on the machine, for example: MACHINE_TYPE=sun4c IN_PLATFORM_GROUP The platform group of which the platform is a member, for example: IN_PLATFORM_GROUP=sun4c The platform group name must be specified in the same file as the platform identification stanza or in the platform definition file with the name .platform/Solaris . The IN_PLATFORM_GROUP keyword is optional. A platform doesn't have to belong to a platform group. If a plat- form is not explicitly assigned to a platform group, it essentially forms its own platform group, where the platform group name is the PLATFORM_NAME value. The IN_PLATFORM_GROUP value typically equals the output of the uname -m command. IN_PLATFORM_GROUP value cannot have white space and is limited to 256 ASCII characters. INST_ARCH The instruction set architecture of the platform, for example: INST_ARCH=sparc This field is only required if the platform does not belong to a platform group. The INST_ARCH keyword value must be the value returned by the uname -i command on all platforms in the platform group. COMPATIBILITY
The installation program will remain compatible with the old Solaris CD format. If a Solaris CD image does not contain any platform defini- tion files, the installation and upgrade programs will select the packages to be installed based on machine type, that is, the value returned by the uname -p command. EXAMPLES
Example 1: Platform Group Definitions The following example shows platform group definitions from the .platform/Solaris platform definition file. # PLATFORM_GROUP=sun4u INST_ARCH=sparc Example 2: Platform Identification Stanzas The following example shows platform identification stanzas, which define systems that belong in a platform group, from the .plat- form/Solaris platform definition file. # PLATFORM_NAME=SUNW,SunFire PLATFORM_ID=SUNW,SunFire IN_PLATFORM_GROUP=sun4u PLATFORM_NAME=SUNW,Ultra-80 PLATFORM_ID=SUNW,Ultra-80 IN_PLATFORM_GROUP=sun4u # PLATFORM_NAME=SUNW,SunFire PLATFORM_ID=SUNW,SunFire IN_PLATFORM_GROUP=sun4u # PLATFORM_NAME=SUNW,Ultra-80 PLATFORM_ID=SUNW,Ultra-80 IN_PLATFORM_GROUP=sun4u FILES
The .platform directory must reside as /cd_image/Solaris_vers/.platform, where cd_image Is the path to the mounted Solaris CD (/cdrom/cdrom0/s0 by default) or the path to a copy of the Solaris CD on a disk. Solaris_vers Is the version of Solaris, for example, Solaris_2.9. NOTES
Typically, a platform identification stanza contains either a PLATFORM_ID or a MACHINE_TYPE stanza, but not both. If both are specified, both must match for a platform to be identified as this platform type. Each platform identification stanza must con- tain either a PLATFORM_ID value or a MACHINE_TYPE value. If a platform matches two different platform identification stanzas--one which matched on the value of PLATFORM_ID and one which matched on the value of MACHINE_TYPE , the one that matched on PLATFORM_ID will take precedence. The .platform directory is part of the Solaris CD image, whether that be the Solaris CD or a copy of the Solaris CD on a system's hard disk. SunOS 5.10 19 Nov 2002 platform(4)
All times are GMT -4. The time now is 07:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy