Freeze on Detecting Wan IP

Think you've found a bug? Post a description here.

Moderator: Serin

Post Reply
azeari
Posts: 2
Joined: Sun Aug 12, 2007 6:33 am

Freeze on Detecting Wan IP

Post by azeari » Sun Aug 12, 2007 6:40 am

Well it just appeared to freeze everytime i restarted the server, and after some trial and error, the autodetect WAN IP seems to be causing this issue.
[2007-08-12 18:24:39]: SYSTEM [Server] - TLS/SSL support initialized
[2007-08-12 18:24:39]: SYSTEM [Server] - Vendor: AuthenticAMD
[2007-08-12 18:24:39]: SYSTEM [Server] - CPU:
[2007-08-12 18:24:39]: SYSTEM [Server] - Number of Processors: 1
[2007-08-12 18:24:39]: SYSTEM [Server] - Operating System: Microsoft Windows XP Professional
[2007-08-12 18:24:39]: SYSTEM [Server] - Additional Info: Service Pack 2 (Build 2600)
[2007-08-12 18:24:39]: SYSTEM [Server] -
[2007-08-12 18:24:39]: SYSTEM [Server] - Cerberus FTP Server started
[2007-08-12 18:24:39]: SYSTEM [Server] - Local Host: ****
[2007-08-12 18:24:39]: SYSTEM [Server] -
[2007-08-12 18:24:39]: SYSTEM [Server] -
[2007-08-12 18:24:39]: SYSTEM [Server] - Local Interface 0 located at 10.80.88.102
[2007-08-12 18:24:39]: SYSTEM [Server] - Listening on Port 21
[2007-08-12 18:24:39]: SYSTEM [Server] -
[2007-08-12 18:25:12]: SYSTEM [Server] - Attempting to detect WAN IP...
The symptoms appear as Cerberus.exe consuming 100% of the cpu time and becoming unresponsive immediately after startup, and the log shows tt its stuck at the detect WAN IP stage.

Also, netstat reveals this..
TCP ****:4091 server49.tchmachines.com:http ESTABLISHED
TCP ****:4092 server49.tchmachines.com:http TIME_WAIT

it appears as though cerberus freezes up while waiting for the 2nd TCP connection in question here

User avatar
Serin
Site Administrator
Posts: 1785
Joined: Sat Jan 01, 2005 6:57 pm
Location: United States
Contact:

Post by Serin » Mon Aug 20, 2007 5:41 pm

Hello,

Yes, the HTTP implementation in the current version might not be the most reliable. I've switched to a third party HTTP library for the upcoming version which should be a bit better.


However, the request should eventually timeout.

azeari
Posts: 2
Joined: Sun Aug 12, 2007 6:33 am

Post by azeari » Wed Aug 22, 2007 6:28 am

oh ya.. i'll like to add that when running the setup wizard, it detects the WAN ip flawlessly. the problem only manifests when the server is restarted with the auto-detect WAN ip checked

Post Reply