[WINDOWS] Starting a second server instance failed

Niteruner
New face
Posts: 1
Joined: Tue Apr 28, 2015 8:39 am

[WINDOWS] Starting a second server instance failed

Postby Niteruner » Tue Apr 28, 2015 8:57 am

When starting a second instance of the dedicated server, I am getting the following error;

UNASSIGNED_SYSTEM_ADDRESS

37.120.xxx.xxx (IP Adress redacted)

Starting dedicated server.
Initializing server...
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)
SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted.
at System.Net.Sockets.Socket.Bind (System.Net.EndPoint local_end) [0x00000] in <filename unknown>:0
at System.Net.Sockets.UdpClient.InitSocket (System.Net.EndPoint localEP) [0x00000] in <filename unknown>:0
at System.Net.Sockets.UdpClient..ctor (System.Net.IPEndPoint localEP) [0x00000] in <filename unknown>:0
at localLANfinder.startDiscoverableLANserver () [0x00000] in <filename unknown>:0
at SERVER_connect.startServer () [0x00000] in <filename unknown>:0
at INIT.Start () [0x00000] in <filename unknown>:0

The client and server Ports differ from the first instance, I also tried it with defferent users.

It seems, that the server only checks the IP, not the port, so only one instance is possible with the same IP.

User avatar
dez
L.F.A. TEAM
Posts: 412
Joined: Thu Jun 02, 2005 11:16 pm
Contact:

Re: [WINDOWS] Starting a second server instance failed

Postby dez » Sat May 02, 2015 6:47 pm

should be fixed now if
usingMultipleServerInstances is set to True in serverSettings.txt


Return to “bug reports”

Who is online

Users browsing this forum: No registered users and 1 guest

cron