Yeah, don't do this.

Post by **John Adams** » Thu Jan 15, 2015 3:54 pm

So, I moved NT back to the VM (on ESX) and sent Cyrcle out to destroy the world. He's reporting being stuck, and I do see spam on the screen -- although you are right, it is no longer red

Looked something like this:
[quote]15:49:21.101 D Command Player 'Cyrcle' .rift to chunk 'Khal' (85)
15:49:21.133 I UDP New client connected from 76.189.152.250:55749
15:49:21.133 I UDP Received session request from 76.189.152.250:55749 with connection ID 1675041952
15:49:21.367 I Chunk New Session: Account ID: 42 Session ID: 'utokf1jh3h3bgahe47e7563p67'
15:49:21.570 I UDP Client from 76.189.152.250:55749 set to disconnect : Application
15:49:21.585 I UDP New client connected from 76.189.152.250:55750
15:49:21.585 I UDP Received session request from 76.189.152.250:55750 with connection ID 1682521067
15:49:21.866 I Chunk New Session: Account ID: 42 Session ID: 'utokf1jh3h3bgahe47e7563p67'
15:49:23.535 I UDP Client from 76.189.152.250:55750 set to disconnect : Application
15:49:23.551 15:49:23.551 I I UDP Chunk New client connected from 76.189.152.250:55751
Chunk shutdown cancelled for Stiirhad.
15:49:23.551 I UDP Received session request from 76.189.152.250:55751 with connection ID 1715513208
15:49:23.816 15:49:23.816 I I Chunk UDP New Session: Account ID: 42 Session ID: 'utokf1jh3h3bgahe47e7563p67'
Client from 76.189.152.250:54644 has been removed.
15:49:24.003 15:49:24.003 I I UDP UDP New client connected from 76.189.152.250:55752
Client from 76.189.152.250:55751 set to disconnect : Application
15:49:24.003 I UDP Received session request from 76.189.152.250:55752 with connection ID 1723328463
15:49:24.066 I Chunk Chunk shutdown cancelled for Khal.
15:49:24.268 I Chunk New Session: Account ID: 42 Session ID: 'utokf1jh3h3bgahe47e7563p67'
15:49:24.284 I UDP Client from 76.189.152.250:55749 has been removed.
15:49:24.440 15:49:24.440 I I UDP UDP Client from 76.189.152.250:55752 set to disconnect : Application
New client connected from 76.189.152.250:55753
15:49:24.440 I UDP Received session request from 76.189.152.250:55753 with connection ID 1730471438
15:49:24.705 I Chunk New Session: Account ID: 42 Session ID: 'utokf1jh3h3bgahe47e7563p67'
15:49:24.908 I UDP Client from 76.189.152.250:55753 set to disconnect : Application
15:49:24.924 I UDP New client connected from 76.189.152.250:55754
15:49:24.924 I UDP Received session request from 76.189.152.250:55754 with connection ID 1738572412
15:49:25.173 I Chunk New Session: Account ID: 42 Session ID: 'utokf1jh3h3bgahe47e7563p67'
15:49:25.376 I UDP Client from 76.189.152.250:55754 set to disconnect : Application
15:49:25.392 I UDP New client connected from 76.189.152.250:55755
15:49:25.392 I UDP Received session request from 76.189.152.250:55755 with connection ID 1746555737
15:49:25.719 I Chunk New Session: Account ID: 42 Session ID: 'utokf1jh3h3bgahe47e7563p67'
15:49:26.000 15:49:26.000 15:49:27.420 15:49:27.326 15:49:27.857 15:49:26.000 I I I I I I UDP UDP Chunk UDP
Chunk UDP New client connected from 76.189.152.250:55756
Client from 76.189.152.250:55755 set to disconnect : Application
Starting chunk shutdown timer for Isle of Dawn.
Client from 76.189.152.250:55753 has been removed.
Shutdown timer expired. Shutting down The Tomb of Lord Tsang.
Client from 76.189.152.250:55750 has been removed.
15:49:28.262 I UDP 15:49:28.262 Received session request from 76.189.152.250:55756 with connection ID 1756824814
I UDP 15:49:28.262 Client from 76.189.152.250:55751 has been removed.
I UDP 15:49:28.278 Client from 76.189.152.250:55752 has been removed.
I UDP Client from 76.189.152.250:55754 has been removed.
15:49:28.293 I UDP Received session request from 76.189.152.250:55756 with connection ID 1756824814
15:49:28.309 I UDP Received session request from 76.189.152.250:55756 with connection ID 1756824814
15:49:28.325 I Chunk Starting chunk shutdown timer for Nexus.
15:49:28.527 I Chunk New Session: Account ID: 42 Session ID: 'utokf1jh3h3bgahe47e7563p67'
15:49:28.824 D Chunk control_text='Ω'
15:49:28.824 E Chunk Received client control text that we don't know how to handle: Ω
0000: 00 09 00 03 01 00 08 00 - 00 00 00 00 0F 40 00 04 .............@..
0010: 00 02 D4 23 ...#
15:49:30.290 I UDP Client from 76.189.152.250:55755 has been removed.
15:49:34.846 I Chunk Shutdown timer expired. Shutting down Ceros Isle.[/quote]
The logs are overwriting themselves probably from different threads, but you get the idea. No red, but the same White (Info) that went along with the old red.

Cyrcle can tell you more of what he was doing.

Post by **Cyrcle** » Thu Jan 15, 2015 4:33 pm

I originally froze trying to break the server by making the following macro and spamming it:

Code: Select all

/say .rift 1
/say .rift 270
/say .rift 38
/say .rift khal

That is what froze me. Then I exited game through the escape menu. I logged back in fine. Typed in .rift khal. Crashed to desktop. Logged in, had no nameplate info (had Solo & no character icon). Also had no hot bar and could not talk in NT chat. Logged out via esc menu. Logged back in. Working as normal. =]

Post by **Xinux** » Thu Jan 15, 2015 4:48 pm

Not sure what that client was sending but here is the unreal packet through vgtesty.

Code: Select all

0000:   00 09 00 03 01 00 08 00 00 00 00 00 0F 40 00 04 .............@..
0010:   00 02
BITSTREAM DATA:
********* NEW BITSTREAM SECTION *********
SECTION TYPE: BUNCH | Total Bistream Length: 56 | PacketID: -1 | isControl: True | isOpen: True | isClose: True | isReliable: True
Channel Index: 0 | Channel Sequence: 0 | Channel Type: 1 | Data Length: 0 | Header Pos: 56
CONTROL CHANNEL | Channel Text Follows | Bits After Text: -8

=============== END 0x01 PACKET ===============

Post by **Lokked** » Thu Jan 15, 2015 5:00 pm

These last few posts could be their own thread. This won't have anything to do with Resending Packets, rather, WorldServer doesn't elegantly handle many different chunkings spammed at it (and I think this is going on my low priority list. When would this ever happen?).

Post by **John Adams** » Thu Jan 15, 2015 5:19 pm

Never. Trying to crash the server by .rifting multiple times should not even be a test, because that certainly should not work (shaking finger at Cyrcle, however creative that might be).

I'll split the posts off.

Post by **Cyrcle** » Thu Jan 15, 2015 5:29 pm

So, what exactly did I do? Lol.

Post by **John Adams** » Thu Jan 15, 2015 5:33 pm

Did you think putting 4 rifts in a macro would rift you once, completely. Then again, completely... etc? haha, no it fired them all off in the same millisecond and blew up your connection

Don't do that.

In fact, avoid . dot commands when stress testing, they are not meant to be stressed out When stress testing VGOEmulator, just use the normal game mechanics, because that's the only thing we guarantee to work properly.

Post by **Cyrcle** » Thu Jan 15, 2015 5:38 pm

[quote="John Adams"]Did you think putting 4 rifts in a macro would rift you once, completely. Then again, completely... etc? haha, no it fired them all off in the same millisecond and blew up your connection

Don't do that.

In fact, avoid . dot commands when stress testing, they are not meant to be stressed out When stress testing VGOEmulator, just use the normal game mechanics, because that's the only thing we guarantee to work properly.[/quote]
Aw, but I was sure it was going to break the server!

Isn't .rifting to multiple zones (not like my macro) supposed to stress the server?

Post by **John Adams** » Thu Jan 15, 2015 5:49 pm

[quote="Cyrcle"]Isn't .rifting to multiple zones (not like my macro) supposed to stress the server?[/quote]
No, only me.

Post by **Lokked** » Thu Jan 15, 2015 7:29 pm

Lol. Good thread.

I'm pleased to hear the server passed Cyrcle's "Stress Test" and reacted appropriately by kicking him, then making him think it forgot what he did to it by allowing him to log back in a couple times, while crashing or castrating him.

VGOEmulator.net

Yeah, don't do this.

Yeah, don't do this.

Re: ResendPackets()

Re: ResendPackets()

Re: ResendPackets()

Re: ResendPackets()

Re: Yeah, don't do this.

Re: Yeah, don't do this.

Re: Yeah, don't do this.

Re: Yeah, don't do this.

Re: Yeah, don't do this.