"Prompt not matching the target server" alerts in Servers
Critical Alert: Prompt not matching the target server. Kindly check whether the given Command Prompt is correct.
This alert is generated when the target server's prompt does not match the prompt value configured during monitor addition.
Possible Cause
If the user's password has expired, the monitored server may prompt the user to change the password during login. In such cases, the prompt is not returned, triggering the alert.
Troubleshooting Steps
- Verify the SSH Connection:
- Attempt to establish an SSH connection to the monitored server using the user account configured in Applications Manager.
- Use an SSH tool (e.g: PuTTY) or the ServerSSHTroubleshoot.bat file for troubleshooting.
- For detailed steps on executing the ServerSSHTroubleshoot.bat file, refer here.
- Check for Prompt or Warnings:
- Ensure that the SSH connection is established successfully and the expected prompt value is returned.
- If the server displays messages like "Password expired" or prompts to reset the password, update the password accordingly.
- After resetting the password, verify if the alerts have been cleared in Applications Manager.
Note: These alerts may also occur when public key authentication is used. Certain SSH related system configurations may restrict server access until the expired password is reset.
New to ADSelfService Plus?
Related Articles
How to find Command Prompt value for server monitors in Applications Manager
To add a server monitor with SSH/Telnet in Applications Manager, you need to specify the Command Prompt value. You can find this value in two ways: 1. From the target server: In the server that you want to monitor, open a command prompt window. The ...DNS Monitor - Troubleshooting
Common DNS Monitor Errors and Troubleshooting Guide 1. Host Not Found Description: The DNS server was unable to locate the requested lookup address. Possible Causes: This may happen if the hostname is incorrect, the domain does not exist, or there is ...Troubleshooting Bad Request and Internal Server error
When a server responds with a Bad Request (400) or Internal Server Error (500), it typically indicates issues with how the request is being made or processed. The reasons for these errors can vary, but the most common causes are: Incorrectly ...Troubleshooting 'Failed to Negotiate Algorithms' Alerts in SSH Monitoring
Failed to Negotiate Algorithms – Critical Alerts in SSH Mode The "failed to negotiate algorithms" exception occurs when an SSH client and server cannot agree on a common cryptographic algorithm for secure communication. This prevents the SSH ...How can I troubleshoot the issue when attempting to add a PostgreSQL Database server, but encountering a failure with an error message prompt?
While attempting to add a PostgreSQL database monitor, if you encounter any errors, please follow the steps below based on the specific error received: Host not valid. Kindly check the host name given or PostgreSQL production server is down or The ...