Jump to content
Sign in to follow this  
soppa

[1.5.3] Hive auth looping

Recommended Posts

After updated server to 1.5.3 it wont let ANY user to log in.

When 1 user connects, hive auth keeps authenticating SUCCESSFULLY 50 times same person without letting him to phase2.

Reverting server back to 1.5.2, everything works fine.

Here is logfile from loop (RPT):

 3:25:37 Error in expression <
waitUntil{(diag_tickTime - _startTime) > 2};

while {true} do {
scopeName "pipe>
3:25:37 Error position: <> 2};

while {true} do {
scopeName "pipe>
3:25:37 Error Generic error in expression
3:25:37 File z\addons\dayz_code\compile\server_hiveReadWrite.sqf, line 27
3:25:37 Suspending not allowed in this context
3:25:37 Error in expression <
waitUntil{(diag_tickTime - _startTime) > 2};

while {true} do {
scopeName "pipe>
3:25:37 Error position: <> 2};

while {true} do {
scopeName "pipe>
3:25:37 Error Generic error in expression
3:25:37 File z\addons\dayz_code\compile\server_hiveReadWrite.sqf, line 27
3:25:38 Suspending not allowed in this context
3:25:38 Error in expression <
waitUntil{(diag_tickTime - _startTime) > 2};

while {true} do {
scopeName "pipe>
3:25:38 Error position: <> 2};

while {true} do {
scopeName "pipe>
3:25:38 Error Generic error in expression

And here is code which is different from 1.5.2 in file server_hiveReadWrite.sqf:


Line 26: _startTime = diag_tickTime;
Line 27: waitUntil{(diag_tickTime - _startTime) > 1};

Variable _startTime gets value diag_tickTime

then wait until difference between these values are greater than 1?

How it can be different if variable value has been synced one line earlier?

This looks like identical problem what we have fixed from arma2oa server code with Dwarden and Bebul on February:

http://forums.bistudio.com/showthread.php?131050-ARMA-2-Operation-Arrowhead-Linux-Server-beta-1-60-89244

//Soppa

Share this post


Link to post
Share on other sites

You are running the development release candidate of 1.5.3

the full release of 1.5.3 does not have diag_tickTime

Server hosters need to be careful they are not pulling builds off the dev files, as these will generally only work on development boxes. Redownload dayz_code from the main box.

Share this post


Link to post
Share on other sites

You are running the development release candidate of 1.5.3

the full release of 1.5.3 does not have diag_tickTime

Server hosters need to be careful they are not pulling builds off the dev files' date=' as these will generally only work on development boxes. Redownload dayz_code from the main box.

[/quote']

Ok thanks.

//Soppa

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×