Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Server & Application Monitor (SAM) > Data source name or default driver issue with CentOS and SAM component monitors

Data source name or default driver issue with CentOS and SAM component monitors

Updated: 2-23:2017

Overview

When attempting to use SAM component monitors and templates with a CentOS Linux-based computer, you may receive the following error: Data source name not found and no default driver specified. The Linux-based computer being monitored may not have the required ODBC or MySQL drivers installed on the system. For full details for Linux configurations, see Linux system configurations for Component Monitors.

To resolve, verify if the correct drivers are installed and defined and the user account and credentials are assigned to the component monitors.

Environment

  • SAM 6.3 and later
  • Orion agent for Linux

 

Cause 

The Linux-based computer being monitored by SAM may not have the correct drivers installed and configured or the credentials may not be assigned to the component monitors.

 

Resolution

Locating the issue may require investigating:

  • The installed drivers
  • The credentials and privileges
  • What drivers and credentials are configured on the system
  • If the server can run commands against the DB using the credentials and driver

Verify the CentOS system has the mysql-connector-odbc installed. Use the following command to receive a package and version name on the target Linux-based computer: rpm -q mysql-connector-odbc

 

Verify you have the appropriate credentials assigned for each component monitor.

  1. On the Web Console, click Settings > All Settings > SAM Settings > Manage Templates.
  2. Search for the SAM template. Select and click Edit.
  3. Select the component monitor to check assigned credentials.
  4. To modify, click Assign Credentials, enter credentials, and click OK.
  5. Test the template.

 

If you continue to encounter issues, verify the appropriate driver is defined on the CentOS system to match the connection string.

For example:

cat /etc/odbcinst.ini
[MySQL]
Description=ODBC for MySQL
Driver=/usr/lib/x86_64-linux-gnu/odbc/libmyodbc.so
Setup=/usr/lib/x86_64-linux-gnu/odbc/libodbcmyS.so
UsageCount=1
[MySQL ODBC 5.3 Unicode Driver]
Driver=/usr/lib/x86_64-linux-gnu/odbc/libmyodbc.so
Setup=/usr/lib/x86_64-linux-gnu/odbc/libodbcmyS.so
UsageCount=1

 

Attempt running SQL commands using a Command Line Interface on the CentOS system with a command that specifies the driver, credentials, and database. If the command works locally on the CentOS system, you can verify those settings in SAM for the component monitors. 

 

 

Last modified
15:31, 24 Feb 2017

Tags

Classifications

Public