Dedicated Sever failed to start after newest update (not fixed)

No, the developer wrote that they are aware of the bug and will patch it in the next update.

3 minutes ago, Redakted said:

No, the developer wrote that they are aware of the bug and will patch it in the next update.

update was, but nothing has changed

Please try updating to version 288704, and post any new logs if it still doesn't work.

It still does not work. 

 

server_log_caves.txt

server_log_master.txt

20 minutes ago, V2C said:

Please try updating to version 288704, and post any new logs if it still doesn't work.

Now everything works, thanks.

FYI, The bug has not been fixed. Been running servers for 3 years. From what I have read it seems to be a issue with CAVE servers.

I just want to point out that some Dedicated servers are not working after the latest update.

Those include:

My own dedicated server running at 5000+ days, US region; 

Another dedicated server running at 15000+ days, US region;

We are all long term endless dedicated servers.

There are a few other dedicated servers disappeared too, I believe they are from the US region as well( based on their pings).

I have removed the caves server and just tried to launch the surface world server by itself, and my dedicated server is still not showing up in the lobby.

 

 

server_log.txt

Master Log
http://upload.clanhost.com.au/files/1538875362.txt

Caves Log
http://upload.clanhost.com.au/files/1538875316.txt

UPDATE: Tried to run a server with default values no caves..... no success. Region aws/Sing

c_connect("IP address", port, "password")

Connecting manually works fine. This has to be a master server issue or the client unable to display the server list correctly.

Edited October 7, 2018 by ADFSniper

After some digging on the master server, this is a client issue not sending server data to the master server correctly or at all.

18 hours ago, ADFSniper said:

After some digging on the master server, this is a client issue not sending server data to the master server correctly or at all.

What do you mean? Is there a workaround?

 

Try connecting to your server manually  IP:PORT.

I don't believe your servers not starting, just not being listed on the masterserver.