Solstice Enterprise Manager 4.1 Troubleshooting Guide

Chapter 8

Troubleshooting SEM CORBA Administration Problems

This chapter provides information on resolving Common Object Request Broker Architecture (CORBA) Gateway process and administration situations encountered with Solstice EM.

This chapter describes the following topics:

• Section 8.1 Troubleshooting Gateway Processes
• Section 8.2 Problems Starting the SEM CORBA Gateway
• Section 8.3 Problems Connecting to the CORBA Gateway
• Section 8.4 Problems Connecting to the Event Gateway

8.1 Troubleshooting Gateway Processes

When troubleshooting CORBA Gateways the first thing to do would be to check the log files associated with the CORBA Gateway processes. These files contain the error messages that are logged by the gateway. TABLE 8-1 lists the log files that are generated by default by the CORBA Gateway. These files are located at:

/var/opt/SUNWconn/em/debug/

You can specify different files to be used as log files by changing the values of the log file configuration variables.

TABLE 8-1   SEM CORBA Gateway Log Files

File	Description
em_corba_epr.log	Event Port Registry log file
em_corba_rgw.log	Request Gateway log file
em_corba_mgw.log	Metadata Gateway log file
em_corba_eds1.log	CORBA EDS 1 log file
em_corba_eds2.log	CORBA EDS 2 log file

8.1.1 Locating Vendor Specific Log Files

The above files are located in/var/opt/SUNWconn/em/debug/ directory.

TABLE 8-2   Vendor Specific Log Files

File	Description
cos_naming.log	Naming Service log file
osagent.log	OSAGENT log file (VisiBroker specific)

8.2 Problems Starting the SEM CORBA Gateway

Problem: When you attempt to start CORBA Gateway services for Orbix you get the error message:

- could not load naming: missing shlib_name config variable
ERROR: could not load naming: missing shlib_name config variable

Probable Cause: The Orbix runtime environment has not been setup on the machine where the SEM CORBA Gateway is being started.

Solution: Install Orbix runtime environment on the machine and then start the CORBA Gateway. Please refer to Chapter 3 in CORBA Gateway Administration Guide for details.

8.3 Problems Connecting to the CORBA Gateway

Problem: When you try connecting to the CORBA Gateway, you get the error message:

Could not get the root naming context

Probable Cause:

• Naming service is not running on the server side.
• Mismatch of EM_CNS_PORT variable between client and server sides.
• The client has not sourced em_corba_env.sh environment file.

Solutions:

1. Run em_services -start -debug to start the service on the server side.

2. On the client side source /opt/SUNWConn/em/bin/em_corba.env.csh and run client.

Problem: You get the following error message when you try connecting to the CORBA Gateway:

VisiBroker: Unable to locate agent. Will try every 15 seconds to locate agent

DSUser:: Unable to contact agent. Make sure there is an agent running on this network

Probable Causes:

• Mismatch of env variable "OSAGENT_PORT between the client and server.
• OSAGENT daemon is not running on the server side.

Solutions:

1. Source /opt/SUNWConn/em/bin/em_corba.env.csh on the client side as well to ensure that the env variables are same on both sides.

2. Start em_services on server side by executing following command:

em_services -start -debug

8.4 Problems Connecting to the Event Gateway

Problem: While accessing the Event Gateway channel on a client machine you get the error message:

Obtained 0 Event Channels
FAILED to setup_event_channel: CORBA::BAD_PARAM
CORBA::BAD_PARAM

Terminating...

Probable Cause: VisiBroker/Orbacus specific event service is not running.

Solution:

1. If server side is up and running, then on the client side ensure that the event services is started.
As an example vendor specific event services is started in the following way:

• % events <testChannel> for VisiBroker
  
• % eventserv -i for Orbacus

2. Run your client program.