Page MenuHomeFeedback Tracker

(1.0.0.80) {Conflict - Everon} [Vanilla] Can't connect to community server - "Caught request on locked player!"
Reviewed, NormalPublic

Description

How the player sees it

The server worked for several days without rebooting

Server logs:

Details

Severity
None
Resolution
Open
Reproducibility
N/A
Operating System
Windows 7
Category
General
Steps To Reproduce
  1. Start server with Conlfict Everon
  2. Play the same mission on it for a while
  3. In a few days, similar errors will start to appear

It might depend on how many players are playing.

Event Timeline

Geez changed the task status from New to Reviewed.Jan 9 2024, 11:45 AM
PR9INICHEK renamed this task from (1.0.0.80) {Conflict - Everon} [Vanilla] Can't connect to community server to (1.0.0.80) {Conflict - Everon} [Vanilla] Can't connect to community server - "Caught request on locked player!".Jan 23 2024, 7:52 AM

It happened again

Virtual Machine Exception

Reason: Caught request on locked player!

Maybe this helps

May be related to T178392

logs_2024-01-28_19-06-48

Same for 1.0.0.95

logs_2024-02-06_16-04-31

logs_2024-02-09_23-21-12

Maybe relates to this problem

First time server crashed

Same problem for 1.1.0.8

logs_2024-02-20_17-04-13

PR9INICHEK added a comment.EditedOct 8 2024, 6:50 PM

Same behaviour for 1.2.1.86

Maybe this info helps:

01.10 2024 06:06:03
Virtual Machine Exception

Reason: SCR_SpawnPoint reservation for playerId: 9 failed!

Class:      'SCR_CampaignSpawnPointGroup'
Entity id:2305843009213694809

Function: 'ReserveFor_S'
Stack trace:
scripts/Game/GameMode/Respawn/SCR_SpawnPoint.c:197 Function ReserveFor_S
scripts/Game/Respawn/RequestHandling/Implementation/SpawnPointSpawn/SCR_SpawnPointSpawnHandlerComponent.c:108 Function SpawnEntity_S
scripts/Game/Respawn/RequestHandling/Base/SCR_SpawnHandlerComponent.c:102 Function HandleRequest_S
scripts/Game/Respawn/RequestHandling/Implementation/SpawnPointSpawn/SCR_SpawnPointSpawnHandlerComponent.c:48 Function HandleRequest_S
scripts/Game/Respawn/RequestHandling/Base/SCR_SpawnRequestComponent.c:366 Function ProcessRequest_S
scripts/Game/Respawn/RequestHandling/Implementation/SpawnPointSpawn/SCR_SpawnPointSpawnRequestComponent.c:81 Function Rpc_RequestRespawn_S

Runtime mode
CLI params: config /home/armarexpserver/serverfiles/armarserver_config.json profile /home/armarexpserver/serverfiles/profiles/server maxFPS 60

logs_2024-09-23_07-11-59

1.2.1.173

It seems that the problem has gone away.

The server has been running for several days and has not encountered this error yet.

We need to observe for some time.