Server re-boot needed

[Glaxono]

The New Telon server really needs a re-boot. As you can see, visitors to the server get hung up in it as the commands don't work.

Hope all is well with the development team!

[Xinux]

Ok server should be back up now. Sorry for the delay.

[John Adams]

Crashed since 3:53pm AZ time Sunday -

Stack

Code: Select all

>	WorldServer.exe!std::_Fetch_add_seq_cst_2(volatile unsigned short * _Tgt, unsigned short _Value) Line 1166	C++
 	WorldServer.exe!std::_Atomic_fetch_add_2(volatile unsigned short * _Tgt, unsigned short _Value, std::memory_order _Order) Line 1188	C++
 	WorldServer.exe!std::atomic_fetch_add_explicit(std::atomic_ushort * _Atom, unsigned short _Value, std::memory_order _Order) Line 1175	C++
 	WorldServer.exe!std::atomic_ushort::fetch_add(unsigned short _Value, std::memory_order _Order) Line 1394	C++
 	WorldServer.exe!Client::GetAndIncrementServerSequence() Line 233	C++
 	WorldServer.exe!Client::PushOutgoing(SOEProtocolData * data, bool dump_packet) Line 362	C++
 	WorldServer.exe!Client::QueuePacket(SOEProtocolData * data, bool dump_packet) Line 296	C++
 	WorldServer.exe!WorldCharacter::LeaveAllChatChannels(bool send_packets) Line 277	C++
 	WorldServer.exe!ChunkServer::DisconnectChunkClient(std::shared_ptr<Client> & chunk_client, unsigned short reason_id) Line 2292	C++
 	WorldServer.exe!CampTimers::Check(ChunkServer * chunk_server) Line 246	C++
 	WorldServer.exe!ChunkServer::Process() Line 227	C++
 	WorldServer.exe!ChunkProcessThread(void * data) Line 110	C++
 	WorldServer.exe!ThreadRun(void * arg) Line 77	C++
 	WorldServer.exe!_callthreadstart() Line 255	C
 	WorldServer.exe!_threadstart(void * ptd) Line 239	C
 	kernel32.dll!76a1338a()	Unknown
 	[Frames below may be incorrect and/or missing, no symbols loaded for kernel32.dll]	
 	ntdll.dll!77c49f72()	Unknown
 	ntdll.dll!77c49f45()	Unknown

[Lokked]

The 12 chunks could be understandable: In the screenshot you've provided, he rifted twice within 5 seconds. Perhaps he was just touring around.

The crash is due to the Server Queueing a packet for a Client object that's been deleted. How that happened, I'll investigate. That player still has his 2 Client Objects alive (WS and Chunk), so I'm guessing a packet was sent from the chunk server that took too long to shut down, to his Chunk Client which had been destroyed.

When he .rifts to 354, below he is being removed from 2 Sea of Kojans (unfortunately named the same, but they are different chunks due to the ports being different). I'm wondering why it took so long to remove him from the first of those Sea of Kojans.

Thanks John. Is this the latest dev build?