Sponsored Content
Operating Systems Solaris NIS broken after installing patch cluster on Solaris 10 Post 303042107 by ron323232 on Saturday 14th of December 2019 10:59:42 PM
Old 12-14-2019
NIS broken after installing patch cluster on Solaris 10

Hi,
I installed Solaris 10 recommended patch cluster (patch bundle of 400+ patches). After reboot global zone is fine, but a lot of services was in uninitialized state. I had to run /lib/svc/bin/restore_repository and then services came online.
Now I can't login to server with NIS account because this server can't get any output from ypwhich, though connectivity seems to be okay to both NIS master servers.
Code:
# ypwhich
Domain pre.dcpoint.com not bound on e522-db23-prod.
# domainname
pre.xypoint.com
# svcs nis/client
STATE STIME FMRI
online 18:13:35 svc:/network/nis/client:default
# cat /var/yp/binding/pre.xypoint.com/ypservers
nis-master1
nis-master2
# rpcinfo -T tcp nis-master1 100004
program 100004 version 1 ready and waiting
program 100004 version 2 ready and waiting
# rpcinfo -T udp nis-master1 100004
program 100004 version 1 ready and waiting
program 100004 version 2 ready and waiting
# rpcinfo -T tcp nis-master2 100004
program 100004 version 1 ready and waiting
program 100004 version 2 ready and waiting
# rpcinfo -T udp nis-master2 100004
program 100004 version 1 ready and waiting
program 100004 version 2 ready and waiting
#

Please help
 

8 More Discussions You Might Find Interesting

1. Solaris

Download patch cluster

Does anyone have an alternate site to download J2SE Solaris Recommended Patch Cluster for Solaris 8. Sun does not let me download the patches unless I have a support contract. I do not. Our software is legal, but our support contract wore out. I need this patchset to avoid downloading 30... (6 Replies)
Discussion started by: hshapiro
6 Replies

2. Solaris

patch cluster question.

What if ,all of my patches in solaris10 05/08 there are not find following: 118731-01 122660-10 119254-59 138217-01 .... about 30 How i can fill up 30 patches? Do command patchadd separetely for everyone? Or make all patch cluster in S mode? Do it in global? I must stop zones befor patchadd... (0 Replies)
Discussion started by: sotich82
0 Replies

3. Solaris

Issue while installing: Solaris 10 SPARC Recommended Patch Cluster (2009.10.23)

Hello, As explained, I've encountered an issue while installing Solaris 10 SPARC Recommended Patch Cluster (2009.10.23). Actually, patch no 120011-14 stops with the following error: ERROR: attribute verification of </var/run/.patchSafeMode/root/usr/bin/passwd> failed file type <f>... (6 Replies)
Discussion started by: a.mauger
6 Replies

4. Solaris

Solaris patch cluster installation error

Hi Admins, I came across an error while installing patch cluster on solaris. # ./installcluster --s10cluster ERROR: Another instance of an install script is already running for target boot environment '/'. I did killed the related processes. Now there is no any process running from ps... (1 Reply)
Discussion started by: snchaudhari2
1 Replies

5. Solaris

Cannot mount Veritas volumes after cluster patch.

I am working with a Sun StoredgeTek 6540 disk array connected to two Sun 490 servers. After taking one of the 490 nodes on the cluster down to single user mode I proceeded to install the latest cluster patch from Oracle. After the patch was completed the system rebooted, failed to rejoin the... (2 Replies)
Discussion started by: buggin
2 Replies

6. Solaris

Recommended Patch Cluster Using ZFS Snapshots

I have a question regarding installing recommended patch clusters via ZFS snapshots. Someone wrote a pretty good blog about it here: Initial Program Load: Live Upgrade to install the recommended patch cluster on a ZFS snapshot The person's article is similar to what I've done in the past. ... (0 Replies)
Discussion started by: christr
0 Replies

7. Solaris

Oracle stopped updating Solaris 10 recommended patch cluster ?

Dear All, Has Oracle stopped updating Solaris 10 recommended patch cluster ? From suport.oracle.com i could see the last patch bundle was released on 11th july and there has been no updates after that. Does anyone know about any official announcement from oracle on this ? Thanks ... (1 Reply)
Discussion started by: abhi_8029
1 Replies

8. Red Hat

Broken Centos Cluster

Hi Guys, Hopefully this is just a quick one - but you never know. I have/had a Centos Cluster running a Netbackup server - I've had an outage and we seem to have lost a node. As a consequence I'm in a bit of a quandary, not familiar with this software either. The server is a Dell PowerEdge... (0 Replies)
Discussion started by: gull04
0 Replies
smosservice(1M)                                           System Administration Commands                                           smosservice(1M)

NAME
smosservice - manage OS services SYNOPSIS
/usr/sadm/bin/smosservice subcommand [ auth_args] -- [subcommand_args] DESCRIPTION
The smosservice command manages OS services. smosservice subcommands are: add Adds the specified OS services. delete Deletes the specified OS services. list Either lists all the installed OS services for the server if you do not specify a hostname, or lists the OS services for the specified diskless client if you do specify a hostname. patch Manages patches on all existing diskless clients. For example, you can use this subcommand to initially establish a patch spool directory on an OS server. Then, you can apply the patch to the spool area, verifying the patch as needed. Once the patch exists in the spool area, you can apply the patch to the clone area. In addition, you can migrate the patched clone area to clients. OPTIONS
The smosservice authentication arguments, auth_args, are derived from the smc(1M) arg set and are the same regardless of which subcommand you use. The smosservice command requires the Solaris Management Console to be initialized for the command to succeed (see smc(1M)). After rebooting the Solaris Management Console server, the first Solaris Management Console connection might time out, so you might need to retry the command. The subcommand-specific options, subcommand_args, must come after the auth_args and must be separated from them by the -- option. auth_args The valid auth_args are -D, -H, -l, -p, -r, and -u; they are all optional. If no auth_args are specified, certain defaults will be assumed and the user may be prompted for additional information, such as a password for authentication purposes. These letter options can also be specified by their equivalent option words preceded by a double dash. For example, you can use either -D or --domain. -D | --domain domain Specifies the default domain that you want to manage. The syntax of domain is type:/host_name/domain_name, where type is nis, nis+, dns, ldap, or file; host_name is the name of the machine that serves the domain; and domain_name is the name of the domain you want to manage. (Note: Do not use nis+ for nisplus.) If you do not specify this option, the Solaris Management Console assumes the file default domain on whatever server you choose to man- age, meaning that changes are local to the server. Toolboxes can change the domain on a tool-by-tool basis; this option specifies the domain for all other tools. -H | --hostname host_name:port Specifies the host_name and port to which you want to connect. If you do not specify a port, the system connects to the default port, 898. If you do not specify host_name:port, the Solaris Management Console connects to the local host on port 898. You may still have to choose a toolbox to load into the console. To override this behavior, use the smc(1M) -B option, or set your console preferences to load a "home toolbox" by default. -l | --rolepassword role_password Specifies the password for the role_name. If you specify a role_name but do not specify a role_password, the system prompts you to sup- ply a role_password. Passwords specified on the command line can be seen by any user on the system, hence this option is considered insecure. -p | --password password Specifies the password for the user_name. If you do not specify a password, the system prompts you for one. Passwords specified on the command line can be seen by any user on the system, hence this option is considered insecure. -r | --rolename role_name Specifies a role name for authentication. If you do not specify this option, no role is assumed. -u | --username user_name Specifies the user name for authentication. If you do not specify this option, the user identity running the console process is assumed. -- This option is required and must always follow the preceding options. If you do not enter the preceding options, you must still enter the -- option. subcommand_args Note: Descriptions and other arg options that contain white spaces must be enclosed in double quotes. o For subcommand add: -h (Optional) Displays the command's usage statement. -o os_server (Optional) Specifies the name of the host where the OS service filesystems reside. If this option is not specified, the host will be the same as that specified in the smc(1M) -D option. This option is useful in the event that the name service server and the OS server are not the same machine. -x mediapath=path Specifies the full path to the Solaris CD image. -x platform=platform Specifies the OS service to add. The instruction architecture, machine class, OS, and version are given in the form: instruction_set.machine_class.Solaris_os_version for example, sparc.sun4m.Solaris_9 -x cluster=cluster Specifies the Solaris cluster to install. For example, SUNWCall. -x locale=locale[locale, . . .] (Optional) Specifies the locales to install from the specified cluster. A comma-delimited list of locales can be specified. o For subcommand delete: -h (Optional) Displays the command's usage statement. -o os_server (Optional) Specifies the name of the host where the OS service filesystems reside. If this option is not specified, the host will be the same as that specified in the smc(1M) -D option. This option is useful in the event that the name service server and the OS server are not the same machine. -x rmplatform=platform Specifies the OS service to remove. The instruction architecture, machine class, OS, and version are given in the form: instruction_set.machine_class.Solaris_os_version for example, sparc.all.Solaris_9. Note: Only a machine class of all is supported. o For subcommand list: -h (Optional) Displays the command's usage statement. -o os_server (Optional) Specifies the name of the host where the OS service filesystems reside. If this option is not specified, the host will be the same as that specified in the smc(1M) -D option. This option is useful in the event that the name service server and the OS server are not the same machine. o For subcommand patch: -a patch_directory/patch_ID Adds the specified patch, patch_ID, to the spool directory. patch_directory specifies the source path of the patch to be spooled which includes the patchid directory name. Patches are spooled to /export/diskless/Patches/. If the patch being added obsoletes an existing patch in the spool, the obsolete patch is moved to the archive area, /export/diskless/Patches/Archive (to be restored if this new patch is ever removed). -h (Optional) Displays the command's usage statement. -m (Optional) Synchronizes spooled patches with offline copies of each diskless client OS service on the server. Spooled patches and applied patches are compared so that newly spooled patches can be installed and patches recently removed from the spool can be backed out. This option does not apply to patches directly to diskless client OS services or diskless clients; the -u option must be used to update the services and clients with the changes. Clients are not required to be down at this time, as all patching is done off line. Note: The server is fully available during this operation. -P Lists all currently spooled patches with an associated synopsis. The list is split up into sections detailing the patches for each OS and architecture in this format: Solaris os_rel1 architecture1: patchid Synopsis patchid Synopsis ...... Solaris os_rel1 architecture2: patchid Synopsis ...... -r patchid Removes the specified patchid from the spool if it is not a requirement for any of the other patches in the spool. All archived patches that were obsoleted by the removed patch are restored to the spool. -U (Optional) Updates all diskless client OS services and diskless clients with any changes after synchronizing patches with the -m option. Clients must be brought down during this operation. Once execution has completed, each client should be booted again. EXAMPLES
Example 1: Creating a new OS service The following command adds an OS service for Solaris 9 for the sun4u machine class where the OS server is not using a name service: example% /usr/sadm/bin/smosservice add -- -x mediapath=/net/imageserver/5.8/sparc -x platform=sparc.sun4u.Solaris_9 -x cluster=SUNWCXall -x locale=en_US The following command adds an OS service for Solaris 9 for the sun4u machine class where the OS server is using NIS, the NIS server is nis- server, the OS server is osserver, and the port to which you connect on osserver is 898: example% /usr/sadm/bin/smosservice add -D nis:/nisserver/my.domain.com -- -H osserver:898 -- -x mediapath=/net/imageserver/5.8/sparc -x platform=sparc.sun4u.Solaris_9 -x cluster=SUNWCXall -x locale=en_US -o osserver In the preceding example, the OS service is placed in /export on osserver, while the hosts.byaddr, ethers, and bootparams maps are updated on the NIS server. Example 2: Deleting an OS service The following command deletes the OS service for Solaris 9 for the sun4u machine class where the OS server is using NIS, the NIS server is nisserver, and the OS server is osserver: example% /usr/sadm/bin/smosservice delete -D nis:/nisserver/my.domain.com -- -x rmplatform=sparc.all.Solaris_9 -o osserver Example 3: Listing installed OS services The following command lists the OS services installed on the machine, osserver: example% /usr/sadm/bin/smosservice list -D file:/osserver/osserver -- -o osserver ENVIRONMENT VARIABLES
See environ(5) for a description of the JAVA_HOME environment variable, which affects the execution of the smosservice command. If this environment variable is not specified, the /usr/java1.2 location is used. See smc(1M). EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 Invalid command syntax. A usage message displays. 2 An error occurred while executing the command. An error message displays. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWdclnt | +-----------------------------+-----------------------------+ SEE ALSO
smc(1M), smdiskless(1M), attributes(5), environ(5) SunOS 5.10 19 Dec 2001 smosservice(1M)
All times are GMT -4. The time now is 10:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy