Here's a temporary fix if you're running CBA. Execute it globally and it should get them out of the animation.

["CAManBase", "init", {
    params ["_unit"];
    if (animationState _unit == "acinpknlmstpsraswrfldnon") then {
        _unit playMoveNow "amovppnemstpsraswrfldnon";
    };
    _unit addEventHandler ["AnimChanged",{
        params ["_unit","_anim"];
        if (!isPlayer _unit) then {
            if (_anim == "acinpknlmstpsraswrfldnon") then {
                _unit playMoveNow "amovppnemstpsraswrfldnon";
            };
        };
    }];
},true,[],true] call CBA_fnc_addClassEventHandler;

Thanks for the input Freddo. We are not running any mods at the current time. It's a vanilla server and we would like to keep it that way.

Newly created units are spawning in a "reaching down" animation and then staying in that position forever. They are able to fire their weapon but cannot move.

"acinpknlmstpsraswrfldnon"

This is the poison animation. This is the logged animationState when the bug occurs.

BIS needs to fix this. This breaks some very old missions.

There are no server-side or client-side mods. The mission uses a revive module. Not sure if that is vanilla?

Steps to reproduce:

1. launch Domination MP, dedicated linux
2. mission will spawn the first target and sometimes enemies are stuck in hunched/dragging position

This happens on some maps more than others (Altis occasional, CUP/SOG more often).

Sorry this isn't more helpful. This bug just appeared with no obvious code changes in the mission, difficult to track the cause but appeared months ago.

We have also had this happen repeatedly over the last couple of years. We've never been able to get a reliable repro because it seems to just come and go pretty much at random, with no changes at our end. It doesn't seem to depend on a particular mission; it's server-wide when it happens, affecting all loaded missions, and we've never found any one mission that causes it to appear. Sometimes it happens to every unit in a mission, sometimes not. Sometimes it happens only to units created by script after the mission starts, sometimes not.

The shortest list of mods we've had loaded on the server when it happened:
CBA
fa_crosshair (custom crosshairs. Does not change AI or animations)
fa_admin (admin utility. Does not change AI or animations)
FA (minor QoL utility. Does not change AI or animations)
We've had it happen with some other mods like Achilles and LAMBS Danger loaded as well, but these are the only mods that have been loaded every time it happens. Never any content mods.

Most of our missions are built with the FA F3 framework. This doesn't affect AI beyond AI skill settings. It does contain a reference to the dragging animation, but this is never called on the AI - players are given an addAction to let them drag downed players. We've found no correlation there and given the way it works, there's no reason to suspect one.

It's very difficult to test because of the inconsistency with which it happens. We can go months without an incident, and we really have no leads to follow up to make it happen more reliably. We can't dedicate months to regular testing to try and get it to occur, and we can't leave the mods off our server for that long to try and test it purely vanilla. So...I'd love to give you a full repro to nail it down, because it's bloody annoying, but the fact is, the only fact we have is "it does happen".

This occurs with both the 32 and 64 bit Linux server.

The hunchback bug also occurs with civilians. These are spawned in the mission by either 1) civilian module or 2) with createAgent. Very little scripting otherwise, just a couple of event handlers (killed, firedNear) attached to the civilian unit.

The mission ran for several days and each new mission area spawned "hunchback" civilians like the screenshot. All other Blufor and Opfor units behaved normally, only the civilians were broken. That continued until I rebooted the server and the issue disappeared.

Has anyone seen this bug running a Windows server? I have only seen it on Linux servers.

@NikkoJT or anyone else?

I have only observed this on a Linux server, although this is not proof it doesn't happen on Windows since I only regularly play on a Linux server.

In T156969#2217395, @longtime wrote:

The hunchback bug also occurs with civilians. These are spawned in the mission by either 1) civilian module or 2) with createAgent. Very little scripting otherwise, just a couple of event handlers (killed, firedNear) attached to the civilian unit.

The mission ran for several days and each new mission area spawned "hunchback" civilians like the screenshot. All other Blufor and Opfor units behaved normally, only the civilians were broken. That continued until I rebooted the server and the issue disappeared.

this is the dragging animation

I tested the same PBO on Windows and Linux. The bug is easily reproduced on the Linux server. I can't reproduce the bug with Windows server.

I believe this bug only applies to Linux.

I'm afraid

In T156969#2212929, @BIS_fnc_KK wrote:

exact steps repro is needed

@BIS_fnc_KK

I haven't been able to craft a repro for this. I only see it when I run the full mission (Domination) on a dedicated server.

I can reproduce the issue fairly quickly on a public server if it would help the troubleshooting process.

Longtime has switched to Windows servers. Running on Linux appears to cause the hunchbacks. As we are not experiencing the problem any longer we don't have any interest in trying to fix it. However BIS should really try and figure out why their software runs on windows but not Linux servers. Feel free to close this ticket.

Is it 64-bit Linux that is causing it? Did it happen on 32-bit too?

This is a very old bug but we never found any way to reproduce it.
Our QA stumbled onto it on a Vanilla mission once, but then couldn't reproduce it.
I played Arma 3 on my own Linux servers since 2014 and maybe experienced that bug two or three times over all that.
Once we had a mission that was repeatedly broken on one evening, but when we played that exact same mission again one week later, it was fine again.
We thought it was caused by Lambs Danger mod, I don't remember if removing it reliably fixed it for us, that was over a year ago and I didn't see this bug since then.
I have no clue how this happens and without being able to reproduce it its a guessing game on over a million lines of code.

This is an exciting opportunity to squash that bug. :)

I run an instance of an Ubuntu image from the AWS marketplace and use steamcmd for setup. I can give exact steps in AWS or I am happy to provide you with the server credentials so you can observe it directly.

Observe is not enough, I need to reproduce it in debugging environment.
And so far that step has always broken reproducibility. I think its maybe some file corruption issue, that fixes itself if you change mod or build version

Linux + SOG map + Domination

Give it a try, bug is reproduced very often on SOG. It's very rare on Altis.