Logging
Overview
This article covers the various log files used by SFTP Gateway.
Log file locations
These are the logs of interest when troubleshooting SFTP Gateway:
/opt/sftpgw/log/application.log
/opt/sftpgw/log/sftp-audit.log
/var/log/secure
/var/log/sftpgw/cloudinit.log
The log files within /opt/sftpgw/log/ have a retention of 30 days, or 3 GB (whichever of these comes first).
And this is what these logs do:
application.log
: Java events and errors.sftp-audit.log
: SFTP actions and authentication.secure
: SSH authentication eventscloudinit.log
: Server related issues that happen at first launch
It's often helpful to tail a log file while troubleshooting, to get a sense of timing:
tail -f application.log
Advanced Logging
If you want more verbose logging, insert this property into the /opt/sftpgw/application.properties
file.
logging.level.com.sftpgateway.backend.sftp.logging.MaverickLogService=DEBUG
Note: You can also use TRACE
instead of DEBUG
, but this generates large amounts of output and can fill your disk up in a short period of time.
To apply your change, restart the Java service:
sudo su
service sftpgw-admin-api restart
Journalctl
If you want to get the full Java stack trace you can run this command:
journalctl -u sftpgw-admin-api