Search the VMware Knowledge Base (KB)
View by Article ID

No events, tasks, and alarms are received from vCenter in Log Insight 3.6 (2147969)

  • 0 Ratings

Symptoms

  • After upgrading to vRealize Log Insight 3.6, you see that vSphere Integration is successful but no events, tasks and alarms are received from vCenter.

  • In the /storage/var/loginsight/runtime.log file, you see entries similar to:

    [2016-11-21 11:56:44.156+0000] ["ScheduledPluginServiceScheduledTask-thread-1"/10.61.0.80 ERROR] [com.vmware.loginsight.scheduled.ScheduledPluginService] [Failed to run '/usr/lib/loginsight/application/3rd_party/bin/java -DLOGINSIGHT_HOME=/usr/lib/loginsight -cp /usr/lib/loginsight/application/etc/plugins/vsphere/* -Xmx1024M com.vmware.loginsight.vsphere.events.VimEventMonitor --single-run --host localhost --port 9240 --url vcenter.company.com --username user --encrypted-password <redacted> --metadata-dir /storage/core/loginsight/var/plugins/vsphere --tags source_vc=vcenter1,source_vc=vcenter1' exitCode=1 stdout='' stderr='log4j:WARN No appenders could be found for logger (com.vmware.loginsight.vsphere.events.VimEventMonitor).
    log4j:WARN Please initialize the log4j system properly.
    log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
    Exception in thread "main" java.lang.NoClassDefFoundError: com/fasterxml/jackson/databind/JsonNode
            at com.vmware.loginsight.commons.tagging.TagUtils.tagsStringToTagsMap(TagUtils.java:74)
            at com.vmware.loginsight.vsphere.events.VimEventMonitor.parseCommandOptions(VimEventMonitor.java:506)
            at com.vmware.loginsight.vsphere.events.VimEventMonitor.main(VimEventMonitor.java:803)
    Caused by: java.lang.ClassNotFoundException: com.fasterxml.jackson.databind.JsonNode
            at java.net.URLClassLoader.findClass(Unknown Source)
            at java.lang.ClassLoader.loadClass(Unknown Source)
            at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
            at java.lang.ClassLoader.loadClass(Unknown Source)
            ... 3 more]
    [2016-11-21 11:56:44.158+0000] ["ScheduledPluginServiceScheduledTask-thread-1"/10.61.0.80 INFO] [com.vmware.loginsight.notifications.AlertNotifier] [Alert recently sent, skipping notification: vCenter collection failed]

    Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue occurs due to duplicate tag name defined in the VIP tags and vSphere Integration tags.

For example:

source_vc=vcenter1 is specified in both VIP tags and vSphere Integration tags.

Resolution

This is a known issue affecting vRealize Log Insight 3.6.

Currently, there is no resolution.

To work around this issue, remove the duplicate tag from either the VIP or the vSphere Integration tags.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: