Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > Connector will not start or will stop after starting

Connector will not start or will stop after starting

Created by Jason Dee, last modified by MindTouch on Jun 23, 2016

Views: 1,218 Votes: 1 Revisions: 6

Overview

When trying to start a connector, you notice that the status icon remains grey, indicating it does not start, or will turn green briefly before turning back to grey, indicating it started and stopped.

Environment

All LEM versions

Cause 

There is an issue with the connector's configuration.

Resolution

Verify that the configuration of your connector is accurate

  1. Double-click on the connector to view its settings.
  2. Verify that the log file path is complete and accurate. If there is any doubt, simply copy and paste the source path to your log file to this field.
  3. Verify that the Output, nDepth Host, nDepth Port, and Sleep Time fields are at their default values.
  4. If there are additional fields unique to this connector, such as New File Name Interval or Time Zone, verify they are also configured accurately for your environment.

 

Determine if you are using the proper connector

A lot of connectors can be similar in name or description. Have another look through the list to see if there is something similar that might be a better fit to your device or application. If you see one that could potentially be a fit, it does not hurt to create and try it.

 

This particular connector may have special configuration requirements

Some of the more complicated connectors (such as database connectors like SQL, IIS, Cisco IDS/IPS, etc) may have special configuration considerations. Try searching our knowledge base for the name of that specific device or application to see if there is an article dedicated to it.

 

The last thing you can try is simply deleting and recreating the same connector. If the XML code had a flaw somewhere, that would clear it.

 

If none of these options help out at all, please contact SolarWinds Support.

Last modified

Tags

Classifications

Public