Enable SSH debug logs for RSA Authentication Manager 8.x
Originally Published: 2015-12-17
Article Number
Applies To
RSA Product/Service Type: RSA Authentication Manager
RSA Version/Condition: 8.x
Issue
Server unexpectedly closed network connection
Tasks
- Logon to the local console as rsaadmin.
- Change to the root user.
- Open etc/ssh/sshd_config in a text editor such as vi.
login as: rsaadmin Using keyboard-interactive authentication. Password: <enter operating system password> Last login: Wed Jan 8 13:53:21 2020 from jumphost.vcloud.local RSA Authentication Manager Installation Directory: /opt/rsa/am rsaadmin@am82p:~> sudo su - root rsaadmin's password: <enter operating system password> am82p:~ # vi /etc/ssh/sshd_config
- Press i to enter Insert mode.
- Change the LogLevel value from INFO to VERBOSE (or DEBUG for more information).
# Logging # obsoletes QuietMode and FascistLogging #SyslogFacility AUTH LogLevel VERBOSE
- Save the change by pressing Esc then :wq! to save and close.
- Restart sshd:
am82p:~ # sudo service sshd restart Shutting down the listening SSH daemon done Checking for missing server keys in /etc/ssh Starting SSH daemon done
- Log data for sshd is written to the /var/log/messages log file
Values that can be used for LogLevel are: QUIET, FATAL, ERROR, INFO, VERBOSE, DEBUG, DEBUG1, DEBUG2 and DEBUG3
Resolution
Please note that the error message usually occurs due to a network timeout or interruption, so please perform other network related checks between the SSH client and the RSA Authentication Manager instance.
