How to resolve EOF Exception in server monitors in Applications Manager

How to resolve EOF Exception in server monitors in Applications Manager

If the server that you want to monitor throws an EOF exception, while you're trying to add it as a monitor, or when Applications Manager is trying to login, you will need to check the error trace.
Navigate to /var/log/secure or /var/log/auth.log directory in the target server and check the error trace in the log file. If you find a trace similar to the one given below, then the problem must be for that specific user only.

Sample trace:

Oct 12 18:34:30 linuxsvr sshd[38320]: Accepted publickey for apmanuser from 10.13.13.13 port 54464 ssh2

Oct 12 18:34:30 linuxsvr sshd[38320]: pam_unix(sshd:session): session opened for user apmanuser by (uid=0)

Oct 12 18:34:48 linuxsvr sshd[38322]: Received disconnect from 10.13.13.13: 11: The user disconnected the application

Oct 12 18:34:48 linuxsvr sshd[38320]: pam_unix(sshd:session): session closed for user apmanuser

Oct 12 18:38:46 linuxsvr sshd[38467]: pam_access(sshd:account): access denied for user `apmanuser' from `monitoringserver'

Oct 12 18:38:46 linuxsvr sshd[38467]: pam_sss(sshd:account): Access denied for user apmanuser: 10 (User not known to the underlying authentication module)

Oct 12 18:38:46 linuxsvr sshd[38468]: fatal: Access denied for user apmanauser by PAM account configuration



Solution:

 

1. Open the access.conf  file in the /etc/security directory in the server that you're trying to monitor.
Check the line given below in that file.

# All other users should be denied to get access from all sources.

#- : ALL : ALL


2. In order to avoid the error, we have to explicitly allow the the Applications Manager user to connect to the monitoring server.
Eg.

+ : <apmanuser >: <monitoringserver>,monitoringserver,..ext

Here, apmanuser  is the username which is configured in the monitor.
monitoringserver  is hostname/IP of the Applications Manager server.

You can replace it with the specific username and IP address and add it to the file below the line given in Step 1.


3. If you do not find a trace in /var/log/secure file similar to the one mentioned in the beginning, try the steps given in this KB. If that doesn't work either, please contact our support team ( appmanager-support@manageengine.com) along with the files specified below so we can analyze the problem and get back to you..
  1. Support information file  
  2. Output of the SSH Troubleshoot.bat script

                  New to ADManager Plus?

                    New to ADSelfService Plus?