How do I troubleshoot syslog issues for MetaDefender Managed File Transfer?
This article applies to all MetaDefender Managed File Transfer (MFT) releases.
When configuring syslog, you may encounter some issues if MFT or the environment is configured wrong. Please follow this troubleshooting guide to remediate these issues.
Syslog is configured on MFT server, but no logs have been received on the syslog server.
Troubleshoot: First, open MFT logs to determine if there are any relevant error messages to narrow down the potential causes. Please refer to How do I find all the MFT logs and their functionality? for more info on these logs.
Next, verify that MFT server is sending syslog:
- The syslog port is open and reachable: 514.
- Verify that the syslog configuration (IP address, port) is correct on MFT web management console.
- Set up packet capture on the server running MetaDefender product to see if syslog messages are being sent out on the configured syslog port and protocol (default is UDP port 514).
- You can use pktmon (Windows built-in), tcpdump (Linux built-in), or other packet capture software such as WireShark.
If there are no messages received on the syslog server, or if packet capture doesn’t show any traffic sent on syslog port, you may need to double check syslog configurations, and/or check network connection between the MFT server and the syslog server.
If Further Assistance is required, please proceed to create a support case or chat with our support engineer.