Frenzy servers hang on Refinery

On our Frenzy community servers (various OS/hardware), we experience a server hang after starting to fight bots on the Refinery (Security) map. This occurs regardless of whether the map was started via map vote or admin panel map change.

To reproduce the issue, start a Frenzy server and change the map to Refinery (perhaps starting on Refinery would be sufficient). Spawn in to start the game, then run forward and kill some bots. The server will then hang, causing a lengthy timeout for all connected players.

While there don't appear to be any log messages that are specific to the server hang, here are the logs leading up to it. Note the errors about avoiding a loop; could the hang be caused by such a loop?

[2019.06.22-20.49.30:270][853]LogAI: Error: ERROR: Behavior BotBehavior_Investigate_2 just switched but is finishing on the initial Update. Check your conditions to avoid a loop.
[2019.06.22-20.49.30:271][853]LogAI: Error: ERROR: Behavior BotBehavior_Investigate_2 just switched but is finishing on the initial Update. Check your conditions to avoid a loop.
[2019.06.22-20.49.30:272][853]LogAI: Error: ERROR: Behavior BotBehavior_Investigate_2 just switched but is finishing on the initial Update. Check your conditions to avoid a loop.
[2019.06.22-20.49.30:273][853]LogAI: Error: ERROR: Behavior BotBehavior_Investigate_2 just switched but is finishing on the initial Update. Check your conditions to avoid a loop.
[2019.06.22-20.49.34:392][ 93]LogInventory: Warning: Unable to equip "BP_Melee_Machete_C_1", already selected.
[2019.06.22-20.49.34:904][123]LogInventory: Warning: Unable to equip "BP_Melee_Machete_C_6", already selected.
[2019.06.22-20.49.38:164][312]LogGameMode: Warning: AINSMultiplayerMode::RespawnBot - Deleting existing pawn before respawn
[2019.06.22-20.49.38:187][312]LogInventory: Warning: SelectFirstAvailableInventoryItem - Unable to find item to equip
[2019.06.22-20.49.38:268][317]LogInventory: Warning: Unable to equip "BP_Melee_Machete_C_4", already selected.
[2019.06.22-20.49.39:036][362]LogInventory: Warning: Unable to equip "BP_Melee_Machete_C_2", already selected.
[2019.06.22-20.49.43:927][647]LogInventory: Warning: Unable to equip "BP_Melee_Machete_C_5", already selected.
[2019.06.22-20.49.46:745][812]LogInventory: Warning: Unable to equip "BP_Melee_Machete_C_3", already selected.
[2019.06.22-20.49.47:266][842]LogAI: Error: ERROR: Behavior BotBehavior_Blink_1 just switched but is finishing on the initial Update. Check your conditions to avoid a loop.
[2019.06.22-20.49.47:520][857]LogInventory: Warning: Unable to equip "BP_Melee_Machete_C_0", already selected.

Installed build ID: 3936323

last edited by JoeK5142

Thank you @JoeK5142
It will be passed on to the dev team. Is this hang recurring?

No problem, @Raibi; thanks for the response. Yes, it seems to be 100% reproducible (i.e. no one can currently play Refinery on Frenzy mode).

I’m getting same issue I’m using host service nfoservers and when I use the rule set checkpoint frenzy and start server with refinery it hangs after 10 seconds of game play I have to alt tab out to leave server and when I log into my game control panel server shows I’m still in there . Can’t figure if it’s a command line issue or the game ini file . But I’ve seen and played on other server using this mode without issues.

Here is my current MapCycle.txt to mitigate this issue by removing Refinery (may help others).

(Scenario="Scenario_Farmhouse_Checkpoint_Security",Mode="CheckpointFrenzy")
(Scenario="Scenario_Crossing_Checkpoint_Security",Mode="CheckpointFrenzy")
(Scenario="Scenario_Hideout_Checkpoint_Security",Mode="CheckpointFrenzy")
(Scenario="Scenario_Precinct_Checkpoint_Security",Mode="CheckpointFrenzy")
(Scenario="Scenario_Summit_Checkpoint_Security",Mode="CheckpointFrenzy")
(Scenario="Scenario_Outskirts_Checkpoint_Security",Mode="CheckpointFrenzy")
(Scenario="Scenario_Ministry_Checkpoint_Security",Mode="CheckpointFrenzy")

Thx joe I’ll give that a try

This seems resolved! Tested with server version 1.3.1 (build ID 4060136).

Thanks, @Raibi and team!