Headless Client kicked to lobby repeatedly 1.0.4.1

[scender]

Hello there!

 

I am having some issues ever since upgrading the server to 1.0.4.1

 

We run a headless client to offload the AI on our server, and after updating it seems to be getting kicked to lobby repeatedly. This only happens for our HeadlessClient, or any dedicated client we have connect to the server. I should add that the following lines are the only indication of these disconnects, there is no BE kick or connection loss.

 

12:19:01 "DISCONNECT: HeadlessClient (XXXXXXXX) Object: HeadlessClient, _characterID: 0 at loc [13612.1,3064.58,0.00120544]"
12:19:01 "ERROR: Cannot Sync Character HeadlessClient as no characterID"

It appears that the HC is not fully loading into the server, so gets kicked to lobby. The problem with this is every time the HC reconnects after being kicked, the AI spawns are ran again and it degrades server performance immensely as the HC offloads ownership to the server.

 

I have applied a CA folder fix posted on the git, as well as removed the folder. Doing both of those allowed regular players to connect and load in fine, just not our HC. The HC can be seen in game when he loads in to spawn the AI, he just doesn't stick around...

 

Still trying many things like vanilla server install with HC as the only addition, I will report my findings if any.

 

Any help or guidance would be much appreciated, as I have exhausted much resources trying to fix this. Thank you!

[(GSG) Az]

I had a script error in my variables.sqf causing a similar issue after the upgrade. Try starting with a clean RPT file and scan for errors, I am sure you will find one :) Also, try running the HC from a new instance of dayz epoch;

Find the @Dayz_Epoch folder
Copy it
Paste it
This should make a folder called @Dayz_epoch copy(1)
Rename it to: @Dayz_Epoch_HC
Change your HC launch params to -mod=@Dayz_Epoch_HC

[scender]

 

I had a script error in my variables.sqf causing a similar issue after the upgrade. Try starting with a clean RPT file and scan for errors, I am sure you will find one :) Also, try running the HC from a new instance of dayz epoch;

Find the @Dayz_Epoch folder
Copy it
Paste it
This should make a folder called @Dayz_epoch copy(1)
Rename it to: @Dayz_Epoch_HC
Change your HC launch params to -mod=@Dayz_Epoch_HC

 

Thank you for the reply :) I have no custom variables currently, so I have ruled that out. I have also tried reinstalling the beta, making a second epoch folder with _HC appended. The disconnects still happen, and the HC is getting stuck in debug.

 

Here is from the client RPT when it happens:

(*the "no speaker given" line changes, its a new name each time)

No speaker given for Anthony Hirasaki
Group B 1-1-A (0x1aed9900) - network ID 2:11847
 - no main subgroup
Network simulation, time = 0.372
Group B 1-1-A (0x1aed9900) - network ID 2:11847
 - no main subgroup
Group B 1-1-A (0x1aed9900) - network ID 2:11847
 - no main subgroup
Group B 1-1-A (0x1aed9900) - network ID 2:11847
 - no main subgroup
Group B 1-1-A (0x1aed9900) - network ID 2:11847
 - no main subgroup
Group B 1-1-A (0x1aed9900) - network ID 2:11847
 - no main subgroup
Group B 1-1-A (0x1aed9900) - network ID 2:11847
 - no main subgroup
Group B 1-1-A (0x1aed9900) - network ID 2:11847
 - no main subgroup

Here is the Server RPT lines with UID replaced by XXXXXXX:

 7:10:10 "get: STRING (XXXXXXXX), sent: STRING (XXXXXXXX)"
 7:10:10 "DISCONNECT: HeadlessClient (XXXXXXXX) Object: B 1-1-A:1 (HeadlessClient) REMOTE, _characterID: 0 at loc [20387,-5039.4,145.094]"
 7:10:10 "ERROR: Cannot Sync Character HeadlessClient as no characterID"
 7:10:10 Client: Remote object 2:19 not found
 7:10:10 Client: Remote object 2:20 not found
 7:10:10 Client: Remote object 2:21 not found

Those are the only indications of any errors within the RPT or other log files.

 

Disabling mods 1 by 1 but nothing has effected it. I was under the impression the Remote object not found errors were network related, but I don't know really what the error messages mean. These messages are the same for connecting to the server via localhost, and remote via another admins PC/my PC.

 

Not really sure what changes were made between 1.0.4 > 1.0.4.1 that would affect the connectivity of HC. Looking at the files didn't turn up much of an answer, i'm really at my wits end here.

[scender]

Fixed the problem! Thanks to this for the hint: https://github.com/vbawol/DayZ-Epoch/commit/f482bf2677fd7a2516a67343a732e7239331c1aa

 

I guess I found the fix too late, and now 1.0.4.2 is out ^^  Thanks anyways folks

[Donnovan]

What was the problem, scender?

[Donnovan]

This problem happens allways to me if i start the server+hc with the Windows Task Manager. If i start it by double clicking the .bat file, everything runs ok!

 

Here my .bat file:

@echo off
 
tasklist | find "arma2oaserver.exe"
if "%ERRORLEVEL%"=="0" Goto end1
timeout 5
start "arma2" /high "C:\servidor_hc\Arma 2 Operation Arrowhead\arma2oaserver.exe" -port=2302 -noPause -nosound "-config=instance_11_Chernarus\config.cfg" "-cfg=instance_11_Chernarus\basic.cfg" "-profiles=instance_11_Chernarus" -name=instance_11_Chernarus "-mod=@DayZ_Epoch;@DayZ_Epoch_Server;"
:end1
 
tasklist | find "ArmA2OA.exe"
if "%ERRORLEVEL%"=="0" Goto end2
timeout 5
start "arma2hc" /high "C:\Program Files (x86)\Steam\steamapps\common\Arma 2 Operation Arrowhead\arma2oa_be.exe" 0 0 -port=2302 -password=XXX -noPause -nosound -skipintro -nosplash -client -connect=127.0.0.1 "-mod=@dayz_epoch;" -name=HeadlessClient -profiles=HeadlessClient
:end2
 
tasklist | find "Bec.exe"
if "%ERRORLEVEL%"=="0" Goto end3
timeout 5
start "Bec" /normal "c:\servidor_hc\Bec\Bec.exe" -f Config.cfg
:end3
 
exit