Page MenuHomeFeedback Tracker

Server: Can't connect after Update to 1.38
Closed, ResolvedPublic


FIX until BIS fixes finaly:
THX Actium

i have just updated my servers running on Linux via SteamCMD.
Now I and other players can't connect to the servers. We get kicked right after joining the server.
I've already reinstalled and updated the servers again.
It didn't help.

I've also set up an Vanilla-Server on a differnet machine.

While checking the installation I've found a missmatch between the versionnumbers of the server and client.

Ingame it shows the that I have the right game version (1.38).


Legacy ID
Operating System
Windows 7
Steps To Reproduce

Set up an Linux-based Dedicated Server

Event Timeline

Dorbedo edited Steps To Reproduce. (Show Details)Jan 21 2015, 6:44 PM
Dorbedo edited Additional Information. (Show Details)
Dorbedo set Category to Server.
Dorbedo set Reproducibility to Always.
Dorbedo set Severity to None.
Dorbedo set Resolution to Open.
Dorbedo set Legacy ID to 1521435925.May 7 2016, 8:08 PM
Dorbedo edited a custom field.

Yep, same here. Running server that claims to be (./arma3server --version) 1.38.128937

No player can connect. server running on 64bit CentOs

delenda added a subscriber: delenda.May 7 2016, 8:08 PM

Same here, running it on Ubuntu 14.04.1 LTS 64bit dedicated server.

Get "you were kicked off the game" after updating Server & Client.

Can confirm I'm getting the following: cannot open shared object file: No such file or directory

The seems to have new shared libaries as a dependency, including X11, OpenAL, pulse, and the GNOME network manager... which is pretty crap for a linux dedicated server and shouldn't be necessary at all.

cuel added a subscriber: cuel.May 7 2016, 8:08 PM
cuel added a comment.Jan 21 2015, 7:50 PM

Same here.

Nife added a subscriber: Nife.May 7 2016, 8:08 PM
Nife added a comment.Jan 21 2015, 7:51 PM

+1 - This is a serious problem and an urgent fix would be very appreciated.

profan added a subscriber: profan.May 7 2016, 8:08 PM

Can confirm this is a problem, server sitting on Debian Wheezy 64bit, having some curious dependencies as TheConen noted.

Ralpha added a subscriber: Ralpha.May 7 2016, 8:08 PM

Same problem. Server boots up as normal.

Known issue listed in Spotrep-00038 do not solve it. (

  • steam_appid.txt -> this change right. content is: 107410
  • vanilla server doesn't work.
  • -mod=curator;kart;heli;dlcbundle: doesn't do much different.

Here is server log if it helps.
Look normal, apart from 'arma 3' 'NOT FOUND'.
modDir is wrong here. path is just ./addons/
dlcbundle folder does not exist eater but don't think that matters.

"Attempt to override final function - rsc*" is not normal.

Ok, my Servers are back online.
I added the following libs:


At least it worked on my System. But I still get the same errors like Ralpha. Exept the missing lib.

EDITED - thx Ralpha

jayjay added a subscriber: jayjay.May 7 2016, 8:08 PM

Same here, Debian Wheezy 64bit, Server starts but you get kicked off. Seems like steamapi isn't loading.

[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
dlopen failed trying to load:
with error: cannot open shared object file: No such file or directory
[S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local

Tried to install but its installed already.

Need a fix or workaround, please help.

Same here on a openSUSE Tumbleweed 64bit server. Mine is already up again, too. As Dorbedo already wrote, you need to install the missing libraries. Naming conventions might be different from one to another distribution.

If you have a 64bit installation, you need to install the 32bit versions of the libraries.

Installing all those dependencies is not an option - a display server on a linux root server is, mildly said, rubbish and installing two network managers at once has the potential to cause serious problems.

For sure it is not nice, but the other option is to wait for an update from BIS. ;) Don't know why you are using network manager on a server. ;)

lubreex added a subscriber: lubreex.May 7 2016, 8:08 PM

same here Dorbedo fix is working. For me only libusb missing.

At least a chance for the Backup to be needed ;)

I hope BIS will work on this Problem and I won't have to stick with this forever.

domiac added a subscriber: domiac.May 7 2016, 8:08 PM

Running Ubuntu 14.04.1 LTS 64 bit server. After loads of apt-get install (thanks Dorbedo), I was still getting " cannot open shared object file: No such file or directory" and players kicked off just after joining. This error was related to

First I tried to add symbolic link like this: "ln -s /lib/x86_64-linux-gnu/ /lib/x86_64-linux-gnu/", it did not work.

Then I did something dreadful, I used hexeditor to change to in and finally got it working.

Note, I do not recommend this to anybody but decided to share this in case someone else needs a workaround for their server.

domiac I think you have to do apt-get install libudev0:i386 otherwise it will install 64 bit version of the library.

There is no such thing (anymore) as 32 bit libudev0 for my distro / version. Hence I had to do an ugly hack and force steam to use a bit newer version.

Thanks Dorbedo for your post.

After trying a lot I saw you typed the i386 wrong. (you types i368)

After running (as root):
'apt-get install libx11-6:i386 libusb-1.0-0:i386 libopenal1:i386 libglib2.0-0:i386 libdbus-glib-1-2:i386 libnm-glib4:i386'
and 'apt-get update'

I rebooted the servers and it worked.

thanks a lot!

Actium added a subscriber: Actium.May 7 2016, 8:08 PM

You do not need to install the insane dependencies of the broken Simple replace it with the from your SteamCMD installation.

I just filed a more accurate bug report, which describes above fix: #0022391

Fix confirmed. Copied linux32/ to arma3 dir and started the server.

Actium, you are my hero :). This hopefully should work until BI fixes it.

i get this error now.

[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
Setting breakpad minidump AppID = 107410

but its working somehow

Thx Actium for your work.

You're welcome guys.

@jayjay: You can easily ignore "SteamAPI_IsSteamRunning() failed". I've been getting it for quite some time. It means there's no instance of the Steam Client running, which is only logical, because it's a server, not a desktop machine running the Linux version of the Steam Client.

Much appreciated Actium, will test it and if it feel stable then I will clean my server packages.

Would be great to get an more official word from the development team on why this happened and which workaround now is the safest (+ are they going to fix this on later versions).

@domiac :

the right place to tweak 32 bit libs is in no way the x86_64 folder!
I did the following to get it to work:

cd /lib/i386-linux-gnu/
ln -s

I think this issue can be marked as resolved, problem is already solved since a few updates ago.

Actium added a comment.Apr 9 2015, 3:45 AM

Yep, this has been fixed for 2+ months now. Just another example for how little attention the bugtracker receives from BI staff ...

dedmen closed this task as Resolved.May 18 2020, 9:37 AM
dedmen updated the task description. (Show Details)
dedmen changed Resolution from Open to Unable To Duplicate.
dedmen edited Additional Information. (Show Details)
dedmen set Operating System to Windows 7.
dedmen changed Resolution from Unable To Duplicate to Fixed.