Sponsored Content
Full Discussion: Communication Failures
Operating Systems HP-UX Communication Failures Post 302138354 by barun agarwal on Monday 1st of October 2007 08:20:02 AM
Old 10-01-2007
Communication Failures

HI ALL,
I have been trying to install a particular software using remote linux server.
some thing like this:
rsh <host ID> /usr/sbin/swinstall -x autoreboot=true -s /tmp/<software> <Product name>.

The problem is whenever I try to install the product through a shell script the installation fails with the following the error message.

======= 09/25/07 09:31:44 MDT BEGIN swinstall SESSION
(non-interactive) (jobid=lca0226-0180)

* Session started for user "root@lca0226".

* Beginning Selection
ERROR: RPC exception: "Communications failure (dce / rpc)" 09/25/07
09:32:19 MDT
ERROR: Could not start a management session for "lca0226:/". The
system administrator for host "lca0226" may have disabled the
swagentd daemon or there may be a networking problem affecting
the operation. If the swagentd daemon has been disabled, it
can be enabled by the system administrator on "lca0226" by
setting the "SW_ENABLE_SWAGENTD" entry in
/etc/rc.config.d/swconfig to "1" and executing
"/usr/sbin/swagentd -r".
* Target connection failed for "lca0226:/".
ERROR: More information may be found in the daemon logfile on this
target (default location is lca0226:/var/adm/sw/swagentd.log).
* Selection had errors.



======= 09/25/07 09:32:19 MDT END swinstall SESSION (non-interactive)
(jobid=lca0226-0180)


But the same command goes through if i use it directly at the shell prompt.

Any guesses why am I getting such error??
 

10 More Discussions You Might Find Interesting

1. Solaris

Core dump failures

Does anyone have a list of error codes when core dumps fail? What is error 4? I also have another box that does error-2 occasionally. if anyone has a list of these error codes, it would be appreciated, thanks! I have the error below: NOTICE: core_log: ns-admin core dump failed,... (2 Replies)
Discussion started by: BG_JrAdmin
2 Replies

2. UNIX for Dummies Questions & Answers

Restarting jobs after failures

Hi, I have a script which has a for loop in it. In that for loop are names of files that are going to be processed. For example, for file in file1 file2 file3 file4 do (something) done Let's say that this script gets executed and it fails at 'file2'. Is there a way that I can actually... (10 Replies)
Discussion started by: hern14
10 Replies

3. Shell Programming and Scripting

Display login failures

How to display failled login in a file. i.e when there occurs a login failure,the login failed date and time should be printed in that file.. (0 Replies)
Discussion started by: aravind007
0 Replies

4. Solaris

Prediction of failures

Any diagnostic tool to do predictive check on all the SUN hard disks before it fails, as a preventive measure? Meaning, is there any tool that can really check for hdd which are failing/or "will fail soon" for Sun servers? (12 Replies)
Discussion started by: incredible
12 Replies

5. Solaris

Solaris 10 svcs failures

upon rebooting the solaris 10 system, all the services went offilne or uninitialised. If I break the SVM mirror and reboot the system with the raw device, all services are up. Once I recreate a fresh mirror(metadevices) and reboot, it goes offline again. Needed to do svcadm clear <service> to bring... (16 Replies)
Discussion started by: incredible
16 Replies

6. Shell Programming and Scripting

Capture linking failures

Hi all, I have a script file that has numerous linking commands (ln -s) and currently there is no checking to see if the linking is successful or not and I need to implement something that checks if any of the linking failed and report a failure. The method I can think of is a small function... (3 Replies)
Discussion started by: zmfcat1
3 Replies

7. Shell Programming and Scripting

Need to Capture Sql Failures

Hi guys, I am inserting and updating records in Oracle database using shell Script based on business logic. Now Whenever the insert or Update fails, i want to capture it. i tried to capture the return code ($?), but it is not reflecting it.... (3 Replies)
Discussion started by: mac4rfree
3 Replies

8. Solaris

Solaris 10 svcs failures

I have a solaris 10 machine that was working fine until the system crashed after a power failure. Now, after the system boots up, several services go into maintenance mode. offline 8:54:59 svc:/milestone/multi-user-server:default offline 8:54:59... (15 Replies)
Discussion started by: krishani3831
15 Replies

9. Solaris

11.0 to 11.2 update failures

Attempting to update an 11.0 server with many non-global zones installed. pkg publisher is pkg.oracle.com/solaris/support. FMRI = pkg://solaris/entire@0.5.11,5.11-0.175.1.15.0.4.0:20131230T203500Z When we run pkg update --accept the server contacts oracle, checks packages, finds about 700... (4 Replies)
Discussion started by: CptCarrot
4 Replies

10. Solaris

Pkgadd failures with Solaris 11

I have some simple package installations that have worked in previous versions of Solaris just fine. I can install the packages, then install newer versions right over the top without error. In previous versions I had to specify the -G option during the installation in order for this to work. ... (0 Replies)
Discussion started by: moondog25
0 Replies
swjob(1M)																 swjob(1M)

NAME
swjob, sd - display and monitor job information, create and remove jobs; invoke graphical user interface to display and monitor job infor- mation and create and remove jobs, respectively SYNOPSIS
attribute] session_file] jobid_file] session_file] target_file] option=value] option_file] [jobid(s)] target_selections] [XToolkit Options] option=value] option_file] Remarks o The command invokes an interactive interface to the same functionality that provides. See below for more details. o This command supports operation on remote systems. See below for details. o For an overview of all SD commands, see the sd(5) man page by typing on the command line. DESCRIPTION
The command displays job information and removes jobs. It supports these features: o Display the current install jobs, copy jobs, and other SD jobs initiated by the SD commands. o Specify a specific job to list or remove. o Display the command logfile for a specific job. o Display the target logfile for a specific target. Remote Operation You can enable Software Distributor (SD) to manage software on remote systems. To let the root user from a central SD controller (also called the central management server or manager node) perform operations on a remote target (also called the host or agent): 1) Set up the root, host, and template Access Control Lists (ACLs) on the remote machines to permit root access from the controller sys- tem. To do this, run the following command on each remote system: NOTES: o controller is the name of the central management server. o If remote system is 11.00, make sure SD patch PHCO_22526 or a superseding patch is installed on remote system before running o If remote system is older than 11.00 or for some other reason does not have in place, copy script from an 11.11 or higher system to the remote system. 2) and have enhanced GUI interfaces for remote operations. Enable the enhanced GUIs by creating the file on the controller. Use this command: NOTE: You can also set up remote access by using directly on the remote machines to grant root or non-root access to users from the con- troller system. Interactive Operations The command is an interactive interface for monitoring and scheduling software jobs. It provides the same functionality as the command. You can also use to invoke the and GUIs. If you have enabled SD's remote operations features, and provide enhanced GUIs to support operations on remote targets. See above for details about enabling remote operations and the enhanced GUIs. Options When no options or operands are specified, lists the jobs that exist on the local host. These jobs may be pending, active, in the back- ground or completed. The command supports the following options: XToolKit Options The command supports a subset of the standard XToolkit options to control the appearance of the system GUI. The sup- ported options are: and See the X(1) man page by typing for a definition of these options. Runs the command in interactive mode (invokes the GUI.) (Using this option is an alias for the command.) See the and headings above for details. Applies to target lists as a shorthand for Causes to remove the specified job(s). Causes to list all available attributes, one per line. The option applies only to the default list. Each job has its own set of attributes. These attributes include such things as job title, schedule date, or results. The option selects a specific attribute to display. You can specify multi- ple options to display multiple attributes. See also sd(4) for details on these attributes. This option applies only to the default list. The logfiles summarizing a job or detailing target actions can be displayed using if is specified and no other attribute is specified (that is, no other attribute may be specified). Save the current options and operands to session_file. You can enter a relative or absolute path with the file name. The default directory for session files is You can recall a session file with the option. Read the list of jobids from jobid_file instead of (or in addition to) the command line. Read the list of target_selections from target_file instead of (or in addition to) the command line. Set the session option to value and override the default value (or a value in an alternate option_file specified with the option). Multiple options can be specified. Execute based on the options and operands saved from a previous session, as defined in session_file. You can save session information to a file with the option. Read the session options and behaviors from option_file. Operands The command supports two types of operands: followed by These operands are separated by the "at" character. This syntax implies that the command operates on "jobid at targets". o The command supports the following syntax for each job id: o target selections: The command supports the following syntax for each target selection: o target selections with IPv6 address: The command on HP-UX Release 11i v3 supports IPv6 address in the target selections. The syntax is: If both the hostname and the path are specified, then the first occurrence of a slash is treated as the separator. The IPv6 address can optionally be enclosed in a pair of square brackets and EXTERNAL INFLUENCES
Default Options In addition to the standard options, several SD behaviors and policy options can be changed by editing the default values found in: the system-wide default values. the user-specific default values. Values must be specified in the defaults file using this syntax: The optional prefix denotes one of the SD commands. Using the prefix limits the change in the default value to that command. If you leave the prefix off, the change applies to all commands. You can also override default values from the command line with the or options: The following section lists all of the keywords supported by the command. If a default value exists, it is listed after the The policy options that apply to are: The location for SD logfiles and the default parent directory for the installed software catalog. The default value is for normal SD operations. When SD operates in nonprivileged mode (that is, when the default option is set to o The default value is forced to o The path element is replaced with the name of the invoking user, which SD reads from the system password file. o If you set the value of this option to path, SD replaces with the invoking user's home directory (from the system pass- word file) and resolves path relative to that directory. For example, resolves to the directory in your home direc- tory. SD's nonprivileged mode is intended only for managing applications that are specially designed and packaged. This mode cannot be used to manage the HP-UX operating system or patches to it. For a full explanation of nonprivileged SD, see the available at the web site. See also the option. Causes a target agent to exit if it has been inactive for the specified time. This can be used to make target agents more quickly detect lost network connections since RPC can take as long as 130 minutes to detect a lost connection. The recommended value is the longest period of inactivity expected in your environment. For command line invocation, a value between 10 minutes and 60 minutes is suitable. A value of 60 min- utes or more is recommended when the GUI will be used. The default of 10000 is slightly less than 7 days. Controls the time in minutes to cache and re-use the results of hostname or IP address resolution lookups. A value of 0 disables the facility to cache and re-use lookup results. The maximum value allowed is 10080 minutes, which is one week. A value of: disables the lookup caching mechanism. is the maximum value allowed. Defines the attributes which will be listed for each job when no option is specified. Each attribute included in the definition is separated by <tab> or <space>. Any attributes, except may be included in the definition. If a particular attribute does not exist for an object, that attribute is silently ignored. Defines the protocol sequence(s) and endpoint(s) on which the daemon listens and the other commands contact the daemon. If the connection fails for one protocol sequence, the next is attempted. SD supports both the tcp and udp protocol sequence on most platforms. See the sd(5) man page by typing for more information. Relative length of the communications timeout. This is a value in the range from 0 to 9 and is interpreted by the DCE RPC. Higher values mean longer times; you may need a higher value for a slow or busy network. Lower values will give faster recognition on attempts to contact hosts that are not up or not run- ning Each value is approximately twice as long as the preceding value. A value of 5 is about 30 seconds for the protocol sequence. This option may not have any noticeable impact when using the protocol sequence. This option controls SD's nonprivileged mode. This option is ignored (treated as true) when the invoking user is super-user. When set to the default value of true, SD operations are performed normally, with permissions for operations either granted to a local super-user or set by SD ACLs. (See swacl(1M) for details on ACLs.) When set to false and the invoking user is local and is not super-user, nonprivileged mode is invoked: o Permissions for operations are based on the user's file system permissions. o SD ACLs are ignored. o Files created by SD have the uid and gid of the invoking user, and the mode of created files is set according to the invoking user's umask. SD's nonprivileged mode is intended only for managing applications that are specially designed and packaged. This mode cannot be used to manage the HP-UX operating system or patches to it. For a full explanation of nonprivileged SD, see the available at the web site. See also the option. Defines the default target_selections. There is no supplied default. If there is more than one target selection, they must be separated by spaces. Controls the verbosity of the output (stdout). A value of: disables output to stdout. (Error and warning messages are always written to stderr). enables verbose messaging to stdout. Session File Each invocation of the command defines a job display session. The invocation options, source information, software selections, and target hosts are saved before the installation or copy task actually commences. This lets you re-execute the command even if the session ends before proper completion. Each session is automatically saved to the file This file is overwritten by each invocation of You can also save session information to a specific file by executing with the session__file option. A session file uses the same syntax as the defaults files. You can specify an absolute path for the session file. If you do not specify a directory, the default location for a session file is To re-execute a session file, specify the session file as the argument for the session__file option of Note that when you re-execute a session file, the values in the session file take precedence over values in the system defaults file. Likewise, any command line options or parameters that you specify when you invoke take precedence over the values in the session file. Environment Variables SD programs are affected by external environment variables. SD programs that execute control scripts set environment variables for use by the control scripts. does not set environmental variables, but it uses them. Environment variables that affect the SD commands: Determines the language in which messages are displayed. If is not specified or is set to the empty string, a default value of is used. See the lang(5) man page by typing for more information. NOTE: The language in which the SD agent and daemon log messages are displayed is set by the system configuration vari- able script, For example, must be set to or to make the agent and daemon log messages display in Japanese. Determines the locale to be used to override any values for locale categories specified by the settings of or any environment variables beginning with Determines the interpretation of sequences of bytes of text data as characters (for example, single versus multibyte characters in values for vendor-defined attributes). Determines the language in which messages should be written. Determines the format of dates (create_date and mod_date) when displayed by Used by all utilities when displaying dates and times in and Determines the time zone for use when displaying dates and times. Signals The command catches the signals SIGQUIT and SIGINT. If these signals are received, prints a message, sends a Remote Procedure Call (RPC) to the daemons to wrap up, and then exits. Each agent will complete the list task before it wraps up. OPERATION
Different views of the job information are available. The types of listings that can be selected are given below. o Default Listing o Target Listing o Logfile Listing Default Listing If is invoked with no options or operands, it lists all jobs that are on the local host. This listing contains one line for each job. The line includes the job tag attribute and all other attributes selected via the option. Listing jobs on a remote controller is not supported. If a jobid is given, information for only that job is displayed. Status Listing If a or is given, the targets for that job and their status are displayed. By default the status information includes Type, State, Progress and Results. Logfile Listing One of the attributes "log" encompasses a variety of logfile types. The type of logfile returned when the is given depends on the operands given. The types of logfiles: No target_selections Show the controller logfile (default). @ target Show the agent logfile. RETURN VALUES
The command returns: The job information was successfully listed or the job was successfully removed. The list /remove operation failed for all jobids. The list /remove operation failed for some jobids. DIAGNOSTICS
The command writes to stdout, stderr, and to the agent logfile. Standard Output All listings are printed to stdout. Standard Error The command writes messages for all WARNING and ERROR conditions to stderr. Logging The command does not log summary events. It logs events about each read task to the logfile associated with each target_selection. swagentd Disabled If the daemon has been disabled on the host, it can be enabled by the host's system administrator by setting the entry in to and executing EXAMPLES
To list all of the jobs that exist on the local host: To show the scheduled date for job hostA-0001: For job hostA-0001 list the targets and their status: or For job hostA-0001 list the controller log: For job hostA-0001 list the targetA agent log: FILES
Contains the user-specific default values for some or all SD options. Contains the master list of current SD options (with their default values). The directory which contains all of the configurable (and non-configurable) data for SD. This directory is also the default location of logfiles. Contains the active system-wide default values for some or all SD options. The directory which contains the information about all active and complete install jobs, copy jobs, and other jobs initiated by the SD commands. AUTHOR
was developed by the Hewlett-Packard Company. SEE ALSO
install-sd(1M), swacl(1M), swagentd(1M), swask(1M), swconfig(1M), swcopy(1M), swinstall(1M), swlist(1M), swmodify(1M), swpackage(1M), swreg(1M), swremove(1M), swverify(1M), sd(4), swpackage(4), sd(5). available at SD customer web site at swjob(1M)
All times are GMT -4. The time now is 02:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy