Closed thevisad closed 11 years ago
I have this issue. "Waiting for server to start authentification" and then just black screen. Clean server with "Custom Inventory". My RPT file - http://hostr.co/FKJTc51ETPyJ
I was seeing the same issue last night, I couldn't find any rpt errors relating to it though, the OnDisconnect errors I was seeing are unrelated I assumed as they were for players who were able to login
Clean server too with just the custom inventory plugin enabled, sometimes it stuck at waiting for server others at requesting character data.
Same, I'm having this issue (Dayz10k talked about being a server-monitor issue, which could be the case atleast with buildings package). I've tried with custom inventory only, aswell.
RPT logs: http://pastebin.com/MgppEMez
So is everyone having the problems building with the custom inventory package?
Because if so I know what the first thing I'm trying tonight is....
when I run the server on 1.7.7 or 1.7.7.1 I got error addon 'dayz_anim' requires addon 'CA_CommunityConfigurationProject_E' it's normal? before on 1.7.6.1 I never seen this error I have installed Arma2 and Arma2 OA in same folder
Skynet dev, please don't start writing about other errors than the one specified. The solution for that error is on the opendays support forum.
I'm going to try running a fully vanilla aswell Seaweed. Will report back here.
CaptainMack I writed this error because I think this error is linked on problem with stuck on authentication And me interesting if somebody have same error
I fixed the mission dayz_anim file, however i was still getting it. I've now tried re-downloading the newest file from this git and updated with the 1.7.7.1 files. Build with no packages I keep getting the "Retrying authentication". Seems like there's an undefined error now: http://pastebin.com/MbJY4Jdj
EDIT: Got it working on 1.7.7.1 files after people updated their DayZ manually.
@CaptainMack Reality has been updated to 1.7.7.1
if you are using lingor 2.3.1 just edit the RealityCPWorlds.cfg and set Lingor to 1771
After updating the Reality Server files and built without any packages, I got working game, (when I run the server anyway I got the error addon 'dayz_anim' requires addon 'CA_CommunityConfigurationProject_E' but I think is not critical but very bad for auto-restarting) so I think problem was with some package
Just do this! To fix the CommunityConfigurationProject_E bug do the following.
Go to "...\Expansion\beta\expansion\addons" Copy these three files: communityconfigurationproject_e.pbo communityconfigurationproject_e.pbo.bi.bisign communityconfigurationproject_e.pbo.bi2.bisign Then navigate to "...\Expansion\Addons" and paste the three "communityconfigurationproject_e" files that you have copied to your clipboard. CREDITS TO FatalWaffles!
@CraftLourens yes I confirm it working, now I can run my server without this error Thanks.
:3 А ты же русский,а я забыл,спасибо за классную админ панель,я слал деньги,жаль что проект умер.
Some of the errors I see that people have posted are not related to the login process. The following is a known issue with official right now and can be safely ignored.
23:49:11 File z\addons\dayz_server\compile\server_onPlayerDisconnect.sqf, line 21
@CraftLourens Yes, I'm Russian, but we need talk here only in english. About my admin panel, maybe I will continue to work on it, but then users should pay for my admin panel, so will see. If you want talk about this, please write on my email
I think I caught the package which produces the problem. name is ssZedsMessagings only with this package players will stuck on authentication and after will get black screen For now without this package all is ok, and I can play on my server
This is really interesting. I have people using this build line and being able to get into the servers properly.
perl build.pl --world chernarus --serverversion 1771 --with-wrecks --with-carepkgs --with-killmsgs --with-ssZedsMessaging --with-buildings --with-invcust --instance 1
I wish I could give you something more constructive, but it seems temperamental.... I originally loaded the update last night, ran for 5 hours with only minor hiccups (some players had the bug but relogging seemed to fix it). Then the server restarts and no one can login again. I got in once after 4 attempts eventually. No changes were made in between besides disabling the antitp script in the mission file, I even tried reverting that change but the logins continued to fail.
I was on 10ks release at the time, I'm going to try your latest code today, I tried building with invcust and killmsgs yesterday.
@thevisad I built via RCP maybe important the sequence of packages as it once was, try build it self via RealityCP with ssZedsMessaging
"I think I caught the package which produces the problem. name is ssZedsMessagings only with this package players will stuck on authentication and after will get black screen For now without this package all is ok, and I can play on my server" I using clean server with custom invertory andhave issue.
@skynetdev can you send me your server file? In the command line version, if you do not specify a server version to use it will auto drop to 174 and build it with that. I want to see if that's the same thing the CP is doing to your files.
@thevisad yes sure, this is working version without ssZedsMessaging and ssZeds and killmsg, and built via CP http://rghost.ru/46881437
I tried only with package ssZedsMessaging and it's working, hmm I think this package produces problem with other package. I need to find which one.
@thevisad I think I found look at this: All this combinations I made via CP ssZedsMessaging = working ssZedsMessaging + Wreks = working ssZedsMessaging + Wreks + CustomInvetory = working ssZedsMessaging + Wreks + CustomInvetory + CarePackages = wokring ssZedsMessaging + Wreks + CustomInvetory + CarePackages + building = not working
ssZedsMessaging + building = not working (here is the server file http://rghost.ru/46882029 for not working version)
Wreks + CustomInvetory + CarePackages + building = working
so I think ssZedsMessaging + building = problem
thats sir, I will dig into this a bit further
Sigh, so I build it with those that were not working? Mine works.
@thevisad I think enough to test ssZedsMessaging + building
how many of you are using anti hack scripts?
I know its a little late on this.. however.. i just re downloaded the script and i am getting this problem. i think it has to be the HiveExt not connecting to the database correctly.. I had it working with an older 1.7.7.1 server files and getting the error "HiveExt: [Error] Error executing |CHILD:305::[25,[1664.63,3978.4,-0.000427246]]:1:|"...
The new scripts seems like it is not getting char creation information.
My server is a Fresh DB Fresh arma2 + oa + dayz install no scripts and both battleye enabled and disabled.
child:305 is not char information, its vehicle updates to the database and is fixed in the latest build of Reality.
I understand that. However since then when you fixed it, The server, at least for me, broke. When i get the black screen you can hit G and have your gear show up but nothing is in it at all. I cant connect to the server via in-game rcon but i get time and weather information. and if i hit Esc twice i can move around but i cant not see my self in 3rd person. So i never receive from the server and data base info for my Char.
Update--- also no char info is stored in the data base after i close my client down. not even a uid
Update-- Sorry if this comes off harsh in any way. I respect and aprecate the work you put in to this and the times you spend.
Anti hacks are known to cause an issue, without anti hacks or REsec (in the init.sqf of the mission file) everything works perfectly fine. Those having this issue need to remove one or the other, or both.
I had exactly the same problem as @skynetdev and I've tried to build
perl build.pl --world chernarus --serverversion 1771 --with-wrecks --with-carepkgs --with-messaging --with-buildings --instance 1
and it helped, no more stuck in authentication screen. If I use ssZeds feature, no matter or just ssZeds or ssZedsMessaging - I get stuck again.
Users are reporting that they are stuck on authentication, others indicating no issues on server. Will need some detailed reports from those having issues.