Cipher

April 8th - 7:20 PM EST Updated server to fix the client crash that was occurring in Valkyrie Twins near "In Memory of Yoko". Removed authcode requirement for PTR registration. Increased max player limit to 400 (up from 32 for internal testing).

The PTR server is back online as of 6:05 PM EST.

The PTR has been shut down as of 2:35 PM EST to allow us to add more memory to the server. I will reply back to this topic and let you guys know when the server is back up. Thanks again for all of the help and effort you guys are putting in.

Some kind of client-side hard freeze seems to have occurred. The Client<->Proxy communications returned an error which means that the sockets were closed in an unconventional and unintentional way (such as a process freezing or crashing). Client-side issues like this will be investigated soon as it's a totally different type of debugging. Thanks!

The login server restarts itself every couple of minutes (just in case something went awry) and, even though this process is pretty quick, it is possible that you happened to have tried logging in during it's restart. Logs don't show anything for this since authentication on login screen is done directly from Client->Login server. I've had this happen once before and it's quite rare but not something we can avoid unless we increase the time between restarts. Thanks!

It looks like something may have been reset with your ethernet adapter or something. Both the Client<->Proxy communication and Proxy<->Server communication were cut at the same time which I haven't seen happen in logs before. Will investigate further if it happens again. Thanks for the report.

Looks like this was a run of the proxy before the latest update. The latest update attempts to fix the problem that your logs showed, but we'll see. Thanks!

Here's a screenshot of the file entropy / count of each byte value (0-255) in one log which shows why compression won't really work (note that each value is equally present, due to the encryption, meaning there are no values which are more common than others, including values used for text or other data): The encryption is done at the stream level, so I could probably just introduce some kind of stream compression such that it is Log data -> Compression -> Encryption -> File (although the logging format is actually already very efficient for most logging events). This would increase CPU load by a decent amount but would produce smaller files. Not sure if the CPU load is worth it though.

They're encrypted in a way that the likelyhood of repeat data is very very low. In this case uploading a log is not necessary. I would just delete/remake the character without one of the guild or restricted decals. Thanks.

Notice in the "Read This" thread says to stay out of VT. There's a high likelyhood that the character that crashed is going to be stuck in that sector until I teleport it out. If this is the case then let me know which character this happened to and I'll teleport it back to a station. Thanks.

The PTR is up 24/7 until we're sure that everything is working great. I'm sending you a PM now.

Was this a client crash (client just closes) or was this a disconnect / you stopped being able to to stuff? Thanks Edit: Logs seem to indicate that you disconnected and failed to reconnect to the server so the proxy went ahead and finished the log and terminated the client (which would make it appear like a hard crash on your end, I should add a popup message when it does this). The specific error thrown makes it look like it was a network issue between you and the server.

I've figured out what caused this and pushed a proxy update to test a possible fix. If this does not work then I will push another proxy update that is a sure-fire fix albeit not a preferable one.

We've made a lot of progress on patching bugs out but we still need more people actively flying around to be sure we've tackled all of them. If helping us test is something you're interested in then please don't hesitate to reply to this thread or send me a message on the Forums and I'll get you on the PTR server ASAP. Thanks!

Hard crash by client that doesn't seem to have been caused by the proxy or server (The proxy got WSAECONNRESET on Client connections, indicating that the socket was suddenly closed in an unconventional and unintentional way, which means that the process crashed). This is not something that we'll be able to investigate during this PTR but something that I plan to address soon. How often do hard-crashes like this happen? Thanks for the report.

It did, I was stressing it doing a gate raid to test a bug theory I had for why crashes are occurring during raids. It's starting back up now but I'm going to hammer it again after it's up so it may or may not go down (Hoping it doesn't, I'm throwing more resources at the problematic piece of code now)

Same server-side crash that we encountered during Gate Raid. Added some logging to the code and added an extra check to it but I may end up needing to rewrite that bit of code (it's older code). Server is booting back up now.

Server crash. Currently investigating the problem and will start it back up ASAP.

April 7th - 2:30 PM EST Updated the proxy to rework some code and add additional logging around a problematic spot indicated by logs. April 7th - 5:00 PM EST Updated server to allocate more memory to sector events. Tested a gate raid after restarting with this change and no crashes occurred. April 7th - 9:00 PM EST Updated the proxy to test a experimental fix for a Client<->Proxy communication problem. I don't expect it to work, but I do have a way to fix it if it doesn't.

Your configuration files are in the <E&B Install>/Data/client/output folder. You should copy this folder over to the same location on your new PC.

Good to hear! The logs that everyone is posting have been a major help in identifying and fixing problems.

Both of your recent reports seem to indicate that the proxy locked up in the same function. Rewrote some of the code there and added extra logging in latest proxy update. Thanks.

Both of your recent reports seem to indicate that the proxy locked up in the same function. Rewrote some of the code there and added extra logging in latest proxy update. Thanks.

Just got home and checked - the server did crash. The bug which caused the crash has been fixed. Sorry about that.

Possible that the server is down. Will investigate when I get home. Thanks.