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
ris(8)							      System Manager's Manual							    ris(8)

NAME
ris - Remote installation services (RIS) utility SYNOPSIS
/usr/sbin/ris /usr/sbin/ris -a client -h hwaddr [-i profset] -p path,prod[,prod]... [-t nettype] /usr/sbin/ris -l /usr/sbin/ris -m client [-h hwaddr] [-i profset] [-p path,prod[,prod]...] [-t nettype] /usr/sbin/ris -r client /usr/sbin/ris -s OPTIONS
Invoke the ris utility without arguments to display the RIS Utility Main Menu and start an interactive session. Refer to the DESCRIPTION section for more information. Use the -h option to specify the RIS client's hardware network address in the form xx-xx-xx-xx-xx-xx, where x is a hexadecimal character. The -h option is mandatory with the -a operand and optional with the -m operand. Use the -i option to spec- ify an installation profile set to use when you install software from a RIS area onto a RIS client. The -i option is optional with the -a and -m operands. Use the -p option to specify the RIS area and one or more comma-separated products (prod) that the RIS client is autho- rized to install from the RIS server. The -p option is mandatory with the -a operand and optional with the -m operand. Use risN.arch to specify the RIS area (path), where N is an integer (0 or higher) indicating an existing RIS area on your RIS server, and arch is the system architecture, such as alpha. For example, ris2.alpha specifies a RIS area. One or more products (prod) are specified as product_N, where N is an integer (1 or higher) indicating a software product that you have installed in a RIS area on your server. For example, product_1 specifies a RIS area. Use the -t option to specify the network type nettype. Valid values are ethernet and ieee802 (token ring). The -t option is optional with the -a and -m operands. OPERANDS
client -h hwaddr [-i profset] -p path,prod[,prod]... [-t nettype] Adds a RIS client. The client argument is the network-recognized host name of the RIS client. List registered RIS clients. client [-h hwaddr] [-i profset] [path,prod[,prod]...] [-t nettype] Modifies a RIS client. The client argument is the network-recognized host name of the RIS client. Removes a RIS client. The client argument is the network-recognized host name of the RIS client. Shows software products in RIS environments. DESCRIPTION
The ris utility manages remote installation services (RIS), letting you install software from a RIS server over a TCP/IP local area network to a RIS client. You can install the base operating system or optional products with the ris utility. You also can add, list, modify and delete RIS clients, and install, show, and delete software products in RIS areas. Refer to the RESTRICTIONS section for more information. With no arguments, the /usr/sbin/ris command displays the RIS Utility Main Menu for an interactive RIS session. # /usr/sbin/ris *** RIS Utility Main Menu *** a) ADD a client d) DELETE software products i) INSTALL software products l) LIST registered clients m) MODIFY a client r) REMOVE a client s) SHOW software products in remote installation environments x) EXIT Enter your choice: Available menu options depend upon previous actions, and choices not preceded by key letters are not available. For example, you cannot list, modify, or remove clients until you add a RIS client. In that case, the m, l, and r key letters are not displayed in front of their respective options, as shown in the following example: *** RIS Utility Main Menu *** a) ADD a client d) DELETE software products i) INSTALL software products ) LIST registered clients ) MODIFY a client ) REMOVE a client s) SHOW software products in remote installation environments x) EXIT Enter your choice: The ris utility uses the /usr/var/adm/ris directory as a base. When you install the first software product, the ris utility creates a RIS area on the disk. RIS areas are named risN.arch, where N is a sequentially-assigned integer starting with 0, and arch identifies the client's machine architecture, such as alpha. The first RIS area for Alpha clients is named ris0.alpha. Additional areas can be set up for the same architecture or other client architectures for organizational or performance reasons. A RIS area contains one or more software products. Each product includes software subsets that can be installed on authorized RIS clients over a local area network. Once software products are installed into a RIS area, RIS clients registered for that RIS area can use the setld utility over the network to install software from their RIS area. You must use the ris utility interactively to set up a RIS area. After you set up a RIS area on the RIS server, you can use the -a, -l, -m, -r, and -s command line operands to manage RIS clients and display information. The ris utility uses the /usr/var/adm/ris/clients/risdb database file to manage multiple clients. RESTRICTIONS
Tru64 UNIX RIS servers cannot install the base operating system on RIS clients that do not support the BOOTP Internet Boot Protocol. EXAMPLES
Invoke the ris utility with no arguments to start an interactive session: # /usr/sbin/ris *** RIS Utility Main Menu *** Choices without key letters are not available. a) ADD a client d) DELETE software products i) INSTALL software products l) LIST registered clients m) MODIFY a client r) REMOVE a client s) SHOW software products in remote installation environments x) EXIT Enter your choice: You must use an interactive session to install or delete software products. After a RIS area is set up on the RIS server, you can use the -a, -l, -m, -r, and -s command line operands to manage RIS clients and display information. The following examples show how to use command line arguments to manage a client named stlouis. These examples assume that /usr/sbin is in your path. Backslashes () indicate line continuation and are not part of the command syntax. Adding a RIS Client Use the following syntax to add a RIS client: ris -a client -h addr -p path,prod[,prod][,prod]... Add RIS client stlouis and allow that client to install a product over the network: # ris -a stlouis -h xx-xx-xx-xx-xx-xx -p ris0.alpha,product_1 Modifying a RIS Client Use the following syntax to modify a RIS client: ris -m client [-h addr] [-ppath,prod[,prod][,prod]...] Modify RIS client stlouis and allow it to install an additional product over the network: # ris -m stlouis -p ris0.alpha,product_2 Removing a RIS Client Use the following syntax to remove a RIS client: ris -r client Remove RIS client stlouis: # ris -r stlouis FILES
Base directory for remote installation areas Directory for database Remote installation information database Directory containing configu- ration description files (CDF) used for installation cloning. SEE ALSO
Commands: setld(8), bootpd(8) Sharing Software on a Local Area Network Installation Guide Installation Guide -- Advanced Topics ris(8)
All times are GMT -4. The time now is 02:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy