sybase probe not starting (red) on Linux RHEL monitoring remote db
search cancel

sybase probe not starting (red) on Linux RHEL monitoring remote db

book

Article ID: 386129

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We have deployed the sybase probe on a RHEL robot and need to monitor a remote sybase DB. 

Despite we have ensured the correct environment variable are configured as per Sybase probe not working - max restarts error - will not run the probe will still never start. 

We have a correctly installed sybase client version installed on the robot and the target DB is up and running. 

Environment

  • DX UIM 23.4.*
  • sybase 4.32
  • OS: RHEL 8.x

Cause

Despite the environment variable on the probe configuration may be pointing to existing and correct paths, the environment variable in the client machine itself may not be set properly. This would cause the issue to crash/not start. 

Resolution

Ensure the environment variables for the sybase DB are correctly set up in the client machine itself. Engage the DB and System team to verify if the sybase client actually works. 

TIPS: 

  • The interfaces file contains the servers the client can connect to.
  • "sybase.sh" is executed to start working with isql to connect to the SYBASE server
  • When testing "isql" if you are seeing thi sissue, you may not able to connect to the sybase server by executing the environment variable:
    Example: 

    isql command will fail with "command not found"


  • This shows the isql is not able to find the path so it says command not found. Similarly the probe will not be able to start.
  • When environment variable are set correctly, isql command would just connect from the client to the DB server and similarly the probe will start. 

Additional Information