CORBA 2.3.3 Administration Guide (NonStop CORBA 2.3.3+)

Appendix E. Troubleshooting
Prev Next
Appendix E. Troubleshooting
Table of Contents
Detecting and Fixing Problems
Is NonStop CORBA Running?
Cannot Start CORBA Server
Shared Library ioser12 Could Not Be Found
Cannot Stop CORBA Server
Cannot Run Client (COMM_FAILURE)
Verifying TCP/IP Configuration
NonStop CORBA Listening on the Wrong Socket
Event Channels Do Not Work
Troubleshooting Servers
Troubleshooting Problems Starting NonStop Services for CORBA
Troubleshooting NonStop CORBA
Also see the Tracing and Debugging section of the NonStop CORBA 2.3 Programmer's Guide for C++ and NonStop CORBA
2.3 Programmer's Guide for Java.
Detecting and Fixing Problems
The following topics discuss how to detect and fix problems that arise when running NonStop CORBA client and server
programs. It is assumed that the NonStop CORBA programs were compiled successfully.
Is NonStop CORBA Running?
Problem: You want to know whether NonStop CORBA is running on your system.
Solution: Type the following command:
ps e | grep nsd
You should see output similar to this:
56996660 ? 00:00 /usr/tandem/nsdoms/bin/ilsd
33095692 ? 00:00 /usr/tandem/nsdoms/bin/name_servant
84090631 ? 00:00 /usr/tandem/nsdoms/bin/lsd
66650123 ? 00:00 /usr/tandem/nsdoms/bin/cs
33095693 ? 00:00 /usr/tandem/nsdoms/bin/EventService
33095695 ? 00:00 /usr/tandem/nsdoms/bin/ird
If you do not t see output like this, you can start the NonStop CORBA processes with the following command from an OSS
window:
nsdstart
Explanation: When NonStop CORBA processes are not running, some services needed by clients and servers are not
available. For example, an application that uses the Naming Service requires the name_servant process, a part of NonStop