IBM Support

KV1 Agent DataProvider Log show java exception

Troubleshooting


Problem

V1 Monitoring Agent for Linux Kernel-based Virtual Machines not showing data in TEP

Symptom

Several logs including kv1_data_provider_<Instance>_startup.log included this message:

2015-03-02 16:02:02 1 SEVERE:
FactoryInterfaceController$3.uncaughtException: Uncaught exception in thread 1.
java.lang.UnsatisfiedLinkError: Unable to load library 'virt':
libvirt.so: cannot open shared object file: No such file or directory
Stack trace:
com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:164)
com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:237)
com.sun.jna.Library$Handler.<init>(Library.java:140)
com.sun.jna.Native.loadLibrary(Native.java:375)
com.sun.jna.Native.loadLibrary(Native.java:360)
org.libvirt.jna.Libvirt.<clinit>(Unknown Source)
java.lang.J9VMInternals.initializeImpl(Native Method)
java.lang.J9VMInternals.initialize(J9VMInternals.java:236)
org.libvirt.Connect.<clinit>(Unknown Source)
java.lang.J9VMInternals.initializeImpl(Native Method)
java.lang.J9VMInternals.initialize(J9VMInternals.java:236)

com.ibm.tivoli.monitoring.agent.kv1.kvm.Connection.open(Connection.java:71)
com.ibm.tivoli.monitoring.agent.kv1.kvm.DataSource.connect(DataSource.java:100)
com.ibm.tivoli.monitoring.agent.kv1.itm.DataProvider.addDataSource(DataProvider.java:160)
com.ibm.tivoli.monitoring.agent.kv1.itm.FactoryInterfaceController.setup DataProvider(FactoryInterfaceController.java:711)
com.ibm.tivoli.monitoring.agent.kv1.itm.FactoryInterfaceController.serviceRequests(FactoryInterfaceController.java:618)
com.ibm.tivoli.monitoring.agent.kv1.itm.FactoryInterfaceController.main(FactoryInterfaceController.java:860)
2015-03-02 16:02:31 36 SEVERE:
FactoryInterfaceController$3.uncaughtException: Class loading error; cannot continue. Ensure that manageontap.jar is in the data provider's classpath.

*******

The log HOSTNAME_<Instance>_kv1agent_HEXDATE-01.log
shows the agent connect to TEMS and then stops showing additional data. No other errors are shown.

Cause

The libvirt java client cannot find the libvirt shared library.

Environment

- Redhat


- ITM 06.30.02.00
- V1 Monitoring Agent for Linux Kernel-based Virtual Machines 07.20.00.00 201302070855

Resolving The Problem

This problem can be caused by a lack of access to, or an improper configuration of, libvirt. In this case the error message reported it cannot open libvirt.so which is part of libvirt system shared library.

- Verify libvirt is installed. For most Redhat environments, it's part of OS installation.

- Verify the shared library search path is set properly.

- Search for libvirt.so on the system. Once it is located, add the relative folder to shared library search path.

For example, you could use Linux utility "ldconfig" to do the configuration.

- After the change, run utility "virsh" to verify the configuration with the command
# virsh -c <hypervisor URI>

If the IP address of hypervisor is 1.1.1.1, the hypervisor URI will be :
qemu+ssh://[email protected]/system

- If the configuration is good, it will run well without error or ask for password.

- If the previous change is verified to have worked, restart agent.

This should resolve the problem. If you continue to have problems contact IBM Support.

[{"Product":{"code":"SS9U76","label":"Tivoli Monitoring for Virtual Environments"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"VMWare","Platform":[{"code":"PF016","label":"Linux"}],"Version":"7.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg21699999