Troubleshooting the Installation

This chapter describes how to troubleshoot the Orbix, OrbixWeb registration, and Solaris installations. This chapter also provides troubleshooting information for a possible CIPM fonts problem.

Troubleshooting the Orbix Installation

If you encounter a problem during the Orbix software installation, the installer may display one of the following error messages:

putit failed, please manually register NS
Failed to start Orbix, please start Orbix and register NS

If you receive one of these error messages, you must shut down the orbixd process and manually register the Name Server, as described in this section:

Shutting Down the Orbix Process

This procedure assumes that the Orbix process is running.

To shut down the Orbix process, follow these steps:

Step 1 Log in as the orbixadm user.

Step 2 From the terminal window from which you launched Orbix, execute the killit NS command.

Step 3 Discover the process ID of the Orbix process.

ps -ef | grep orbixd

Step 4 Issue the kill process_ID command for each Orbix process listed.

Registering the Name Server Manually

To manually register the Name Server, issue the following command sequence:

Step 1 Source the environment file for the Orbix software. Depending on which shell you run, the filename is either setenvs.csh or setenv.sh

Step 2 orbixd &

Step 3 putit NS /opt/orbixadm/orbix/Orbix3/bin/ns

Step 4 chmodit NS i+all

Step 5 chmodit NS l+all

Step 6 Now you can start the VPNSC: MPLS Solution software.

You can skip the Orbix startup procedure.

Troubleshooting the OrbixWeb Registration

Symptom

After three start attempts, one or more servers are in a disabled state

The reason for the failures is a server registration bug in OrbixWeb that causes missed hearbeats, specifically due to a COMM_FAILURE, such as the following:

Warning:
Heartbeat failed due to exception:
org.omg.CORBA.COMM_FAILURE:localhost/2013

The text "localhost/nnnn" indicates this problem.

This problem occurs if there is old server registration information in some files in the OrbixWeb installation.

Solution

The simplest way to make sure you do not encounter this problem is to reinstall OrbixWeb instead of reusing an old OrbixWeb installation. Be sure to remove the old installation before you reinstall the new version of OrbixWeb.

If you must reuse the existing OrbixWeb installation, run the following commands (assuming IT_CONFIG_PATH is set as your OrbixWeb installation directory). These commands remove the incorrect OrbixWeb registrations.

Step 1 On the VPN Solutions Center 1.2 workstation, open the terminal window where Orbix is running.

Step 2 If not already logged in as orbixadm in this window, do so now.

Step 3 Change directory to the following path:

cd $IT_CONFIG_PATH/Repositories/ImpRep

Step 4 Run the following command to remove the incorrect registrations:

rm DataSetServer.imp \
log.imp \
CVPIMServer.imp \
mibpoller.imp \
VpnInvServer.imp \
DIPMServer.imp \
watchdog.imp \
EventGateway.imp \
CNGSServer.imp \
TaskServer.imp

The next time the Watchdog starts, it adds the correct registration information.