theblueone

^Title. As someone who played the mod since 1.7.2.5 through to 1.7.7.1, I'm near speechless. It saddens me as to what people made out of this mod. Wanting to play the mod again after a long break, I try to find me a populated server using DayZ Commander. I'm having a hard time, and it pretty much puts me off seeing all these ridiculous, "easy mode", so not DayZ servers. Freaking Wasteland with zombies.

Sounds exactly like what the problem is. Though, was this auth stuff in 1.7.4.4 or only since recently? If it's new, I think it'd be a better idea just to scrap this whole new login thing and go back to something stable?

I disagree to this. I have changed the timeout to 90s and people are still getting the error after that, and it seems as if there's no working cleanup for anything other than loot, which is sad. Though I'm not sure if this is supposed to be server side or DayZ. We have described the issue, I have provided logs, that may or may not provide useful info because of their nature, though we have identified the issue which should be enough for you to look into. My system should be able to handle 50 people fine, and it does. I want to outline again that it is only since 1.7.6.1 that you apparently need dual xeon's to run. Hundreds of DayZ servers around the world are having this issue, but not many decides to report it. As said before I haven't ever ran an official server, so I cannot provide anything specific. But maybe there is someone that is having this issue with the official hive? I hope so, and I hope they are willing to provide all the logs needed, or we won't get this fixed it seems. EDIT: Just read facoptere's post, fingers crossed :P

repo's closed now, but used to be here: https://github.com/fred41/DayzPerformanceUpgrades by fred41.

In 1.7.4.4, I have tried this so called "better" login process that is now implemented in DayZ, and had the same exact problem, also, vehicle fixing wasn't working. So with this version, I tried to use an older one, it worked, but like I said, it's a bad fix that is broke a lot more than working. But yea, it's the new login process that's causing it. I'm pretty sure. I'm yet to gather log information, as there's nothing in there mostly but stuff that suggest that player sync failed, or something along the lines. 1.7.5.1 had the crow issue, now 1.7.6.1 has this. And there is no problems with my version of hive. That new login process should've been avoided. I have also find out that this is less of an issue on a high end system. My server doesn't lag, but it gets overloaded, just like any other server. The more horsepower the lesser of an issue this is. But I shouldn't need a system better than mine to run a DayZ server anyhow, so I stand by my point. This login system needs to go fast, and it's a DayZ issue.

I am referring to "Something went wrong, please disconnect and try again!" as the error, but I do usually get some errors in the log. I'll build up all of those and PM you with as much information as I can get.

Every 3 hours on a good day, usually every 50 minutes because of people spawning in the debug. Server also has 50 people throughout the day and runs smooth when it does, if we don't get the error. But today we had the error occur already every single restart, like 1 hour in. I think I'm done with running it, no more patience tbh..I can start PM'ing you releavant info, stuff from the logs. I'm not good with github and don't know how to use it. EDIT: The problem appears to be not the delay in logging in, but something broken in the process. People can still log in if they press esc a couple of times which will make them spawn in the debug, depending on the server load, it can take from 30s to a minute for them to spawn. But that shouldn't happen, anyways. I have tried using the publicEH.sqf found in dayz_code\init, from version 1.7.5.1. That made things better, but the problem still occurs, and seems to be a lot more random. The behaviour: 1.7.6.1 publicEH: People start spawning in debug after 30-50 mins of server uptime, always occuring. 1.7.5.1 publicEH: 5/10 times it will break completely and spawn people in debug, without the ability to spawn by waiting (whereas 1.7.6.1 one, you can spawn after waiting), but then, 5/10 times it will go the 3 hours without breaking. I don't know what to try anymore, nothing seems to stop me losing players over this. And the most annoying part is that it's like 50/50, some servers get it, some don't. But I've seen enough get it to say it's a DayZ problem. Believe me, I switched hive's, switched out files, tried fixing stuff with the little knowledge that I have in SQF scripting. I'm all out of ideas.

And I don't think you run a demanding server that get's empty because of the issues caused by this untested release. I just want to get this problem across to the devs so they fix it asap. If that bothers you, no offence.

This whole food thing is ridiculous. The point is that the devs are implementing a bunch of useless stuff and then releasing an untested, broken update. This is what it's about, at least for me. And, R4Z0R49, publicEH is broken. Please fix it. I'm not even sure if you're aware of the game breaking "Requesting Authentication" issue, but I hope you are. It's a freaking headache for myself and hundreds out there that are trying to run a server. Apologies if I may have come across rude, but I am beyond frustrated because of this broken update. P.S Everyone needs to stop suggesting shit and let these guys focus on FIXING it first. 1.7.2.5 Alpha 1.7.2.6 Alpha 1.7.3 Beta 1.7.4.4 Full release 1.7.5.1 Pre-Alpha 1.7.6.1 Pre-Alpha

Yet again the same problem.. I am posting/bumping regarding this again, in hopes that the devs can realise that this is a broken update and should've never been released..Need a fix asap.

It's a DayZ problem, not his. Hope devs can fix it already, it's a headache for a lot of server admins.