GIM install stuck in PENDING INSTALL

Technote (troubleshooting)


Problem(Abstract)

InfoSphere Guardium Installation Manager (GIM) client failed to register after installation of the Guardium GIM client. Error "GIM Client failed to register (500, read timeout)" appears in the Central GIM log.

Symptom

"GIM Client failed to register (500, read timeout)" error is logged in the Central GIM log on the database server after installing the Guardium GIM client.


Cause

Any of the following:


1. The IP address or host name of the g-machine is invalid in the GIM Client configuration.

2. The GIM Client is pointing to a Central Manager unit instead of to the Managed Unit.

3. Port 8081 is blocked by the firewall.

4. The GIM servlet is not running on the Managed Unit.


Diagnosing the problem

1. on the GIM Client system, run command:
'< gim modules install dir>/UTILS/current/files/bin/configurator.sh - get GIM'
Check value for parameter GIM_URL. Make sure the IP address or hostname is correct, not misspelled, and that you can ping to it.

2. If the g-machine is a Managed Unit (managed by a Central Manager), make sure GIM_URL is set to the IP address or hostname of the Guardium g-machine (Collector), and not to the Central Manager.

3. run iptraf cli command on the Guardium appliance (g-machine) and make sure that it is receiving traffic from the GIM Client host on port 8081.


Resolving the problem

1. On the GIM Client system, run command:
'< gim modules install dir>/UTILS/current/files/bin/configurator.sh - get GIM'
Check value for parameter GIM_URL. Make sure it is not incorrect or misspelled and that you can ping to it. Correct and problems in the IP address or hostname if needed. Check with your network administrator if you can not pint to it.

2. If GIM_URL is set to the Central Manager Unit, change it to point to the g-machine (Collector). To do this, run '< gim modules install dir>/UTILS/current/files/bin/configurator.sh -set GIM_URL ' to set GIM_URL to the IP address or hostname of the g-machine and then restart gim_client.pl process (just kill it and it will automatically restart).

3. If 'iptraf' does not show receiving traffic on port 8081 from the GIM Client host, contact your network administrator to make changes in the firewall settings to allow traffic between the g-machine and the GIM Client host on this port.

4. To resolve the case that GIM servlet (running on the g-machine) is down, restart the gui on the g-machine ( login as 'cli' to the appliance and run command: 'restart GUI'). This will trigger a restart of the GIM servlet.

Rate this page:

(0 users)Average rating

Document information


More support for:

InfoSphere Guardium
InfoSphere Guardium Database Activity Monitor

Software version:

8.0, 8.0.1, 8.2

Operating system(s):

AIX, HP-UX, Linux, Solaris

Reference #:

1597699

Modified date:

2012-08-02

Translate my page

Machine Translation

Content navigation