Tools
Serv-U Gateway Server had intermittent service outages, sporadically stop listening on passive ports
This article described an issue when the Serv-U Gateway Server had intermittent service outages, sporadically stop listening on passive ports.
First published date
Last published date
Overview
In this issue, the Serv-U Gateway Server had intermittent service outages. From the Logs, it was behaving abnormally and stop listening on selective passive ports.
[01] Wed 24Jun20 23:23:26 - Stopped listening for PASV FTP connections through GATEWAY (17x.xx.xx.xx port 1180) on port number 10537, IP 17x.xx.xx.xx [01] Wed 24Jun20 23:23:26 - Stopped listening for PASV FTP connections through GATEWAY (17x.xx.xx.xx port 1180) on port number 10529, IP 17x.xx.xx.xx [01] Wed 24Jun20 23:23:42 - Listening for PASV FTP connections on GATEWAY (17x.xx.xx.xx port 1180) port number 10502, IP 17x.xx.xx.xx [01] Wed 24Jun20 23:23:42 - HTTPS server listening on GATEWAY (17x.xx.xx.xx port 1180) port number 443, IP 17x.xx.xx.xx [01] Wed 24Jun20 23:23:42 - Listening for PASV FTP connections on GATEWAY (17x.xx.xx.xx port 1180) port number 10504, IP 17x.xx.xx.xx
Product section
Cause
A possible customer environment issue. The Serv-U MFT Server configured in a cluster environment, and the node crashed.
Resolution
1. Rebuild a new Gateway Server
2. Install the Gateway Application and restore the backup files
Pre-Implementation Steps:
- The files that must be backed up before the upgrade are the following:
- Serv-U-Gateway-ID.txt
Windows: C:\ProgramData\RhinoSoft\Serv-u Gateway
Linux: /usr/local/Serv-U Gateway
- Accept-Public-IP-CIDRs.txt
Windows: C:\ProgramFiles\RhinoSoft\Serv-u Gateway
Linux: /usr/local/Serv-U Gateway
Implementation Steps:
- Download the installer from the Customer Portal
- Login to Serv-U Gateway Server
- Install the Serv-U Gateway Application
Windows:
https://support.solarwinds.com/SuccessCenter/s/article/Serv-U-Gateway-installation-for-Windows
Linux:
https://support.solarwinds.com/SuccessCenter/s/article/Install-Serv-U-on-Linux
- Stop Serv-U service on the new server.
- Restore the backup files from pre-implementation Steps (Serv-U-Gateway-ID.txt, Accept-Public-IP-CIDRs.txt).
- Start the Serv-U service.
3. Test the new server.