PlaneShift

Development => Development Deliberation => Topic started by: Uyaem on May 24, 2005, 07:59:32 pm

Title: Can't connect to local server
Post by: Uyaem on May 24, 2005, 07:59:32 pm

For the past 5 or 6 weeks, whenever I run a server and try to connect to it, I get the \"waiting on server data\" on the client side, the server console constantly outputs:

Code: [Select]

Could not get client by num
until the connection attempt times out.
I have followed the guide, and managed to successfully set up a server in the past, I have no clue why this is happening locally but not on the official server (I can connect there without any problems with both the windows and the linux client). Any people from a remote destination could not connect either.
The client shows a ping, after the timeout it gives me the standard error message (the server is not up or not reachable).

The system I built the server on is an AMD64 running a 32bit gentoo with kernel 2.6.10

Any help appreciated. :)

Title:
Post by: AryHann on May 25, 2005, 08:13:42 am

From what I have seen from the commits, blueCommand has recently inserted some code for this problem.
Now, I don\'t remember exactly *when* he did the commit, but you can check the history.txt and see when there is that commit.

Ary

Title:
Post by: Wired_Crawler on July 14, 2005, 09:16:18 pm

Hmm... I am not a programer, so I find it little weird.
Probably You already know this, it is somehow related to debugging code. When I give --enable-debug to configure script, I can connect to server without problems. Without this option I get \"couldn\'t get client by num...\" on the server console, and client can not connect.

Title:
Post by: AryHann on July 14, 2005, 09:53:14 pm

Yes, it is a known issue. You have that problem if you compile in release mode.