Our Products:   CompleteFTP  edtFTPnet/Free  edtFTPnet/PRO  edtFTPj/Free  edtFTPj/PRO
0 votes
9k views
in CompleteFTP by (280 points)
Hi Team,

I have been using CompleteFTP for my server for around 2 years.
Early this month my server was restarted due to urgent maintenance.
Later we found that the 'Complete FTP Service' service is running (able to see from windows services mgmt), but from the Complete FTP Manager it is not (as img attaced)
[ img ]

I went to click on the start button and recieved the error message of "Error: Site fialed to start any listeners".
So I went to logs and found following trails:


Server Starting
2012-09-04 17:25:10,671 INFO Server Loading configuration from C:\Documents and Settings\All Users\Application Data\Enterprise Distributed Technologies\Complete FTP\config.sdf
2012-09-04 17:25:29,578 INFO Server Starting server
2012-09-04 17:25:29,578 INFO Server Running as 'NT AUTHORITY\SYSTEM'
2012-09-04 17:25:32,984 DEBUG Server Logging level = ALL
2012-09-04 17:25:32,984 DEBUG Server Checking license
2012-09-04 17:25:32,984 DEBUG Server Production license found
2012-09-04 17:25:32,984 DEBUG Server Initializing process user
2012-09-04 17:25:32,984 DEBUG Server Found server-site: FTP Server
2012-09-04 17:25:32,984 DEBUG Server Creating site: FTP Server
2012-09-04 17:25:33,000 DEBUG Server Starting site: FTP Server
2012-09-04 17:25:33,000 DEBUG ProtocolListener Created listener (FTP:21)
2012-09-04 17:25:33,000 DEBUG ProtocolListener Created listener (SFTP:22)
2012-09-04 17:25:33,140 DEBUG SocketListener Port 22 is busy
2012-09-04 17:25:33,156 ERROR SocketListener Failed to start listener QqLKCsC3sCn2HVDmu7O.Nl3DGGCgR91GxgnDTCc:0
EnterpriseDT.Net.FtpServer.Core.ServerException: Port 22 is unavailable
at mb6xspCt4VKrbqLnUI1.qvSNygCvMSDhXUkC3Qq.MZnWoxE5h()
at WIZYIqCm6X6fKEBb0gX.LRIKdXCPF1ufHhUJVS5.JpFBBOmr5()
2012-09-21 15:34:14,541 DEBUG SocketListener Accepted connection (14983)
2012-09-21 15:34:14,541 INFO FTPConfiguration Using UTF8 encoding
2012-09-21 15:34:14,541 DEBUG FTPSession setting state to AwaitUser
2012-09-21 15:34:14,541 DEBUG FTPConnection CMD< 220-Complete FTP Admin
2012-09-21 15:34:14,556 DEBUG FTPConnection 220 Admin v 2.1.1
2012-09-21 15:34:14,556 VERBOSE FTPConnection [2] OnReceive Begin
2012-09-21 15:34:14,556 DEBUG FTPConnection [2] CMD> USER admin
2012-09-21 15:34:16,822 VERBOSE VirtualPath [2] Created VirtualPath with node '/Admin' and relative path ''
2012-09-21 15:34:16,822 DEBUG UserSession [2] Session user set to 'admin'
2012-09-21 15:34:16,822 DEBUG FTPSession [2] setting state to AwaitPassword
2012-09-21 15:34:16,822 DEBUG FTPConnection [2] CMD< 331 Password required for admin
2012-09-21 15:34:16,822 VERBOSE FTPConnection [2] OnReceive End
EnterpriseDT.Net.FtpServer.Core.ServerException: Port 21 is unavailable
at mb6xspCt4VKrbqLnUI1.qvSNygCvMSDhXUkC3Qq.MZnWoxE5h()
at WIZYIqCm6X6fKEBb0gX.LRIKdXCPF1ufHhUJVS5.JpFBBOmr5()
EnterpriseDT.Net.FtpServer.Core.ServerException: Port 22 is unavailable
at mb6xspCt4VKrbqLnUI1.qvSNygCvMSDhXUkC3Qq.MZnWoxE5h()
at WIZYIqCm6X6fKEBb0gX.LRIKdXCPF1ufHhUJVS5.JpFBBOmr5()
EnterpriseDT.Net.FtpServer.Core.ServerException: Port 21 is unavailable
at mb6xspCt4VKrbqLnUI1.qvSNygCvMSDhXUkC3Qq.MZnWoxE5h()
at WIZYIqCm6X6fKEBb0gX.LRIKdXCPF1ufHhUJVS5.JpFBBOmr5()
EnterpriseDT.Net.FtpServer.Core.ServerException: Port 22 is unavailable
at mb6xspCt4VKrbqLnUI1.qvSNygCvMSDhXUkC3Qq.MZnWoxE5h()
at WIZYIqCm6X6fKEBb0gX.LRIKdXCPF1ufHhUJVS5.JpFBBOmr5()
EnterpriseDT.Net.FtpServer.Core.ServerException: Site failed to start any listeners
at WIZYIqCm6X6fKEBb0gX.LRIKdXCPF1ufHhUJVS5.JpFBBOmr5()
at rIClMXCq1i08LrlAOmu.ODIKHoCceOhrED3jb50.MZnWoxE5h()
at EnterpriseDT.Net.FtpServer.Admin.RemoteAccess.StartSites()
2012-09-21 15:41:20,739 DEBUG SocketListener Accepted connection (14983)
2012-09-21 15:41:20,739 INFO FTPConfiguration Using UTF8 encoding
2012-09-21 15:41:20,739 DEBUG FTPSession setting state to AwaitUser
2012-09-21 15:41:20,739 DEBUG FTPConnection CMD< 220-Complete FTP Admin
2012-09-21 15:41:20,739 DEBUG FTPConnection 220 Admin v 2.1.1
2012-09-21 15:41:20,755 VERBOSE FTPConnection [3] OnReceive Begin
2012-09-21 15:41:20,755 DEBUG FTPConnection [3] CMD> USER admin
2012-09-21 15:41:23,020 VERBOSE VirtualPath [3] Created VirtualPath with node '/Admin' and relative path ''
2012-09-21 15:41:23,020 DEBUG UserSession [3] Session user set to 'admin'
2012-09-21 15:41:23,020 DEBUG FTPSession [3] setting state to AwaitPassword
2012-09-21 15:41:23,020 DEBUG FTPConnection [3] CMD< 331 Password required for admin
2012-09-21 15:41:23,020 VERBOSE FTPConnection [3] OnReceive End
EnterpriseDT.Net.FtpServer.Core.ServerException: Port 21 is unavailable
at mb6xspCt4VKrbqLnUI1.qvSNygCvMSDhXUkC3Qq.MZnWoxE5h()
at WIZYIqCm6X6fKEBb0gX.LRIKdXCPF1ufHhUJVS5.JpFBBOmr5()
EnterpriseDT.Net.FtpServer.Core.ServerException: Port 22 is unavailable
at mb6xspCt4VKrbqLnUI1.qvSNygCvMSDhXUkC3Qq.MZnWoxE5h()
at WIZYIqCm6X6fKEBb0gX.LRIKdXCPF1ufHhUJVS5.JpFBBOmr5()
EnterpriseDT.Net.FtpServer.Core.ServerException: Port 21 is unavailable
at mb6xspCt4VKrbqLnUI1.qvSNygCvMSDhXUkC3Qq.MZnWoxE5h()
at WIZYIqCm6X6fKEBb0gX.LRIKdXCPF1ufHhUJVS5.JpFBBOmr5()
EnterpriseDT.Net.FtpServer.Core.ServerException: Port 22 is unavailable
at mb6xspCt4VKrbqLnUI1.qvSNygCvMSDhXUkC3Qq.MZnWoxE5h()
at WIZYIqCm6X6fKEBb0gX.LRIKdXCPF1ufHhUJVS5.JpFBBOmr5()
EnterpriseDT.Net.FtpServer.Core.ServerException: Port 21 is unavailable
at mb6xspCt4VKrbqLnUI1.qvSNygCvMSDhXUkC3Qq.MZnWoxE5h()
at WIZYIqCm6X6fKEBb0gX.LRIKdXCPF1ufHhUJVS5.JpFBBOmr5()
EnterpriseDT.Net.FtpServer.Core.ServerException: Port 22 is unavailable
at mb6xspCt4VKrbqLnUI1.qvSNygCvMSDhXUkC3Qq.MZnWoxE5h()
at WIZYIqCm6X6fKEBb0gX.LRIKdXCPF1ufHhUJVS5.JpFBBOmr5()
EnterpriseDT.Net.FtpServer.Core.ServerException: Site failed to start any listeners
at WIZYIqCm6X6fKEBb0gX.LRIKdXCPF1ufHhUJVS5.JpFBBOmr5()
at rIClMXCq1i08LrlAOmu.ODIKHoCceOhrED3jb50.MZnWoxE5h()
at EnterpriseDT.Net.FtpServer.Admin.RemoteAccess.StartSites()


I have already checked if any other programs using port 22 (via tcpview.exe) or any firewall blocked (via telnet port 22) locally on the server, but so far I have found none.
Kindly advise on the situation... :cry:

9 Answers

0 votes
by (162k points)
It certainly looks like something else is using ports 21 and 22.

Could you run netstat -a on the command line and send us the output? And send us your config.sdf file?
0 votes
by (280 points)
Sorry for the wait, I managed to get the results as requested:
Follows are the output from netstat -a:
Active Connections

Proto Local Address Foreign Address State
TCP sinccbap2k3p19:ftp sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:ssh sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:http sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:epmap sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:427 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:microsoft-ds sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:1024 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:1025 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:1064 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:1065 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:1112 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:1920 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:2080 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:ms-wbt-server sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:3661 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:4885 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:5988 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:5989 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:6988 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:7756 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:8080 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:9495 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:bpjava-msvc sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:vnetd sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:bpcd sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:vopied sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:14247 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:14248 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:14983 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:25344 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:27000 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:34571 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:34572 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:44970 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:45580 sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:ftp sinccbap2k3p19.sq.com.sg:4640 CLOSE_WAIT
TCP sinccbap2k3p19:http SIA315501.sq.com.sg:1960 ESTABLISHED
TCP sinccbap2k3p19:http SIA315501.sq.com.sg:1961 ESTABLISHED
TCP sinccbap2k3p19:http SIA315504.sq.com.sg:2455 ESTABLISHED
TCP sinccbap2k3p19:http SIA00236D.sq.com.sg:1410 ESTABLISHED
TCP sinccbap2k3p19:http SIA318368.sq.com.sg:2863 ESTABLISHED
TCP sinccbap2k3p19:http SIA318368.sq.com.sg:2864 ESTABLISHED
TCP sinccbap2k3p19:http SIA318371.sq.com.sg:4131 ESTABLISHED
TCP sinccbap2k3p19:http SIA318371.sq.com.sg:4132 ESTABLISHED
TCP sinccbap2k3p19:http SIA00002D.sq.com.sg:4392 ESTABLISHED
TCP sinccbap2k3p19:http SIA00002D.sq.com.sg:4393 ESTABLISHED
TCP sinccbap2k3p19:http SIA00441D.sq.com.sg:51103 ESTABLISHED
TCP sinccbap2k3p19:http SIA00441D.sq.com.sg:51106 ESTABLISHED
TCP sinccbap2k3p19:http SIA315499.sq.com.sg:4465 ESTABLISHED
TCP sinccbap2k3p19:http SIA315499.sq.com.sg:4468 ESTABLISHED
TCP sinccbap2k3p19:http SIA318367.sq.com.sg:3097 ESTABLISHED
TCP sinccbap2k3p19:http SIA318367.sq.com.sg:3101 ESTABLISHED
TCP sinccbap2k3p19:http SIA318370.sq.com.sg:2865 ESTABLISHED
TCP sinccbap2k3p19:http SIA318370.sq.com.sg:2866 ESTABLISHED
TCP sinccbap2k3p19:http SIA00235D.sq.com.sg:2757 ESTABLISHED
TCP sinccbap2k3p19:http SIA00235D.sq.com.sg:2758 ESTABLISHED
TCP sinccbap2k3p19:http SIA00005D.sq.com.sg:3508 ESTABLISHED
TCP sinccbap2k3p19:http SIA00005D.sq.com.sg:3509 ESTABLISHED
TCP sinccbap2k3p19:http SIA02310L.sq.com.sg:50959 ESTABLISHED
TCP sinccbap2k3p19:http SIA02310L.sq.com.sg:50960 ESTABLISHED
TCP sinccbap2k3p19:http SIA02310L.sq.com.sg:50961 ESTABLISHED
TCP sinccbap2k3p19:http SIA315494.sq.com.sg:3230 ESTABLISHED
TCP sinccbap2k3p19:http SIA315494.sq.com.sg:3231 ESTABLISHED
TCP sinccbap2k3p19:http SIA315494.sq.com.sg:3232 ESTABLISHED
TCP sinccbap2k3p19:http SIA315494.sq.com.sg:3233 ESTABLISHED
TCP sinccbap2k3p19:http SIA318366.sq.com.sg:3052 ESTABLISHED
TCP sinccbap2k3p19:http SIA318366.sq.com.sg:3053 ESTABLISHED
TCP sinccbap2k3p19:http SIA05550D.sq.com.sg:49402 ESTABLISHED
TCP sinccbap2k3p19:http SIA00006D.sq.com.sg:4576 ESTABLISHED
TCP sinccbap2k3p19:http SIA00006D.sq.com.sg:4577 ESTABLISHED
TCP sinccbap2k3p19:http SIA00004D.sq.com.sg:2632 ESTABLISHED
TCP sinccbap2k3p19:http SIA00004D.sq.com.sg:2637 ESTABLISHED
TCP sinccbap2k3p19:http SIA315496.sq.com.sg:2287 ESTABLISHED
TCP sinccbap2k3p19:http SIA315496.sq.com.sg:2288 ESTABLISHED
TCP sinccbap2k3p19:http SIA00003D.sq.com.sg:4282 ESTABLISHED
TCP sinccbap2k3p19:http SIA00003D.sq.com.sg:4283 ESTABLISHED
TCP sinccbap2k3p19:http SIA318378.sq.com.sg:2426 ESTABLISHED
TCP sinccbap2k3p19:http SIA318378.sq.com.sg:2427 ESTABLISHED
TCP sinccbap2k3p19:http SIA315497.sq.com.sg:4930 ESTABLISHED
TCP sinccbap2k3p19:http SIA315497.sq.com.sg:4931 ESTABLISHED
TCP sinccbap2k3p19:http SIA00001D.sq.com.sg:1496 ESTABLISHED
TCP sinccbap2k3p19:http SIA00001D.sq.com.sg:1498 ESTABLISHED
TCP sinccbap2k3p19:netbios-ssn sinccbap2k3p19.sq.com.sg:0 LISTENING
TCP sinccbap2k3p19:2080 SIA05676D.sq.com.sg:52465 ESTABLISHED
TCP sinccbap2k3p19:2298 SINCCBAP2K3P17.sq.com.sg:18231 ESTABLISHED
TCP sinccbap2k3p19:2885 SINCCBAP2K3P18.sq.com.sg:18231 ESTABLISHED
TCP sinccbap2k3p19:3097 SINCCBDB2K3P07.sq.com.sg:ms-sql-s ESTABLISHED
TCP sinccbap2k3p19:3099 SINCCBDB2K3P07.sq.com.sg:ms-sql-s ESTABLISHED
TCP sinccbap2k3p19:3101 SINCCBDB2K3P07.sq.com.sg:ms-sql-s ESTABLISHED
TCP sinccbap2k3p19:3129 SINCCBAP2K3P17.sq.com.sg:18231 ESTABLISHED
TCP sinccbap2k3p19:3130 SINCCBAP2K3P17.sq.com.sg:18231 ESTABLISHED
TCP sinccbap2k3p19:3137 SINCCBDB2K3P07.sq.com.sg:ms-sql-s ESTABLISHED
TCP sinccbap2k3p19:3386 SINCCBDB2K3P07.sq.com.sg:ms-sql-s ESTABLISHED
TCP sinccbap2k3p19:ms-wbt-server 192.168.29.141:42761 ESTABLISHED
TCP sinccbap2k3p19:3442 SINCCBAP2K3P17.sq.com.sg:18231 ESTABLISHED
TCP sinccbap2k3p19:3455 SINCCBAP2K3P17.sq.com.sg:18231 ESTABLISHED
TCP sinccbap2k3p19:3715 SINCCBDB2K3P07.sq.com.sg:ms-sql-s ESTABLISHED
TCP sinccbap2k3p19:3717 SINCCBDB2K3P07.sq.com.sg:ms-sql-s ESTABLISHED
TCP sinccbap2k3p19:3845 SINCCBAP2K3P18.sq.com.sg:18231 ESTABLISHED
TCP sinccbap2k3p19:3909 SINCCBAP2K3P18.sq.com.sg:18231 ESTABLISHED
TCP sinccbap2k3p19:3910 SINCCBAP2K3P18.sq.com.sg:18231 ESTABLISHED
TCP sinccbap2k3p19:3915 SINCCBDB2K3P07.
0 votes
by (51.6k points)
Please don't make you config file publicly available as it contains sensitive information!
I've removed the link from your post.

These lines:
TCP sinccbap2k3p19:ftp sinccbap2k3p19.sq.com.sg:0 LISTENING 
TCP sinccbap2k3p19:ssh sinccbap2k3p19.sq.com.sg:0 LISTENING

indicate there's something using the FTP port.

I suggest downloading Microsoft's TcpView to find out what it is.

- Hans (EnterpriseDT)
0 votes
by (280 points)
Hi,
Thank you for your support. We have find out the port actually holding by 'zombie' process due to last reset.
But why I am still able to telnet that port?

P/S: is the nick support2 also from your team?
0 votes
by (51.6k points)
I presume that the reason why you can telnet to the port is that the process is actually still running. What's the name of the process?

Yes, support2 is one of our team. He's camping at the moment. Last time I heard from him he was on top of a mountain, which is the nearest place he could get mobile reception.

- Hans (EnterpriseDT)
0 votes
by (280 points)
The zomebie process seems to be an instance of Complete FTP Service.
We have no ideas why it happened.
Perhaps by them time of restarting the machine, there was actually an active connection being opened....
We will keep monitor and share if we manage to find out the real culprit.
Again, thanks for your support. :)
0 votes
by (51.6k points)
So, is it working now?
0 votes
by (280 points)
Yes, back to business.
I stopped the sevice, and closed the application. Then, killed the zombie process.
Finally tried to start the server agian.
0 votes
by (51.6k points)
Please let us know if this happens again.

- Hans (EnterpriseDT)

Categories

...