Issues in creating server monitor
Please do test credentials before adding a particular monitor.
Troubleshooting the SSH Configuration :
I cannot add remote server monitor using SSH password authentication
Please follow our suggestions below,
1) When adding that server monitor, please specify the correct command prompt value, which is the last character in your command prompt after connecting to that server with that appropriate username
Connect to the remote Linux/Freebsd/Mac OS/HP UX/Solaris server and check the command prompt. Default value is $ and possible values are > or # etc
2) In the server which you are trying to monitor through SSH, the PasswordAuthentication variable should be set as 'yes' in the sshd_config file and it should be uncommented
To ensure this, access the file /etc/ssh/sshd_config (or /etc/sshd_config file) and verify the value of PasswordAuthentication variable. If it is set as 'no', modify it to 'yes' , uncomment that line and restart the SSH daemon using the command /etc/rc.d/sshd restart
3) Applications Manager can not add the server monitor (even though SSH2 is running) if the entry in </etc/ssh/sshd_config> (or /etc/sshd_config file) is 'Protocol 2,1'
Change the entry as below in the /etc/ssh/sshd_config file (or /etc/sshd_config file), uncomment that line and then restart SSH2 daemon
protocol 2
4) Add the below lines in the /etc/ssh/sshd_config file (or /etc/sshd_config file) in the remote server which are trying to add in Applications Manager and restart the SSH Daemon using the command /etc/rc.d/sshd restart (comment the lines if they are already present)
#Default Encryption algorithms and Message Authentication codes
#Ciphers aes128-ctr,aes128-cbc,arcfour,3des-cbc,blowfish-cbc
#MACS hmac-md5,hmac-sha1,hmac-sha1-96,hmac-md5-96
Note: You have to take a backup of the original file before modification
If you still have issues send below information to appmanager-support@manageengine.com for further troubleshooting
1) Send us complete output for the AppManagerHome\bin\ServerSSHTroubleshoot.bat or ServerSSHTroubleshoot.sh script with remote server hostname or IP address. Follow the below link for the usage of the command
2) Send us copy of /etc/ssh/sshd_config file (or /etc/sshd_config) from the remote server which are trying to add in Applications Manager via SSH
3) Open command prompt in remote server that you are trying to monitor in Applications Manager with SSH
uname -a
/sbin/ifconfig -a
dladm show-link
hostname
4) Open command prompt in Applications Manager host and execute below command with remote server hostname or ipaddress and send us the screenshot of the output
telnet <hostname> <ssh_port>
Example:
telnet app-centos 22
5) Open command prompt in Applications Manager host and execute below commands with remote server hostname and ipaddress and send us the screenshot of the output
ping hostname
nslookup hostname
ping ipaddress
nslookup ipaddress
6) Try to add the server monitor in Applications Manager a couple of times and then immediately create a new support information file and upload it to our ftp.Refer the below link for steps to create support information file and uploading it.
7) Check if you are able to connect with the same username & password using any other SSH client tool other than Applications Manager.
Troubleshooting the SNMP Configuration :
I am not able to view the Data in SNMP mode - getting "No data Available" message. What should I do?.
Solution:
Execute the script snmpwalk.bat / .sh under AppmanagerHome/bin/troubleshooting folder
Send the output you get, to appmanager-support@manageengine.com.
New to ADSelfService Plus?
Related Articles
Mail Server Monitor - Troubleshooting
Common Mail Server Monitor Errors and Troubleshooting Guide 1. Unknown Host Error Description: This error occurs when the mail client cannot resolve the hostname of the mail server to an IP address. The issue typically arises from DNS resolution ...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 URL Monitor
Here are few of the common errors you may come across in URL monitor, we have mentioned the steps you can follow to troubleshoot them. General troubleshooting for URL monitor Ensure that the URL is accessible from the server in which Applications ...REST API Monitor - FAQS
1. What should I do when Basic Authentication fails in REST API monitor? Verify if the credentials provided in the Applications Manager are correct. Try if sending username and password in Authorization request header works Get an BASE-64 encoded ...Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...