The new RC build downloaded from Steam seems to segfault on startup.
I tried wiping the directory clean and starting over, but that seemed not to work.
I ran it through gdb to grab a backtrace, I'll attach the log.
The new RC build downloaded from Steam seems to segfault on startup.
I tried wiping the directory clean and starting over, but that seemed not to work.
I ran it through gdb to grab a backtrace, I'll attach the log.
Simply start the server with or without parameters.
I get the segfault even if I launch it without any parameters as well.
This is still an issue after 1.70 release today.
It seems like Linux dedicated servers are not working at all.
openSUSE 13.2 "Harlequin" x64
kernel: 3.16.7-53-desktop
Same segmentation fault issue as above.
This is awful and has to be hotfixed asap.
I can confirm the issue on a freshly installed Arma 3 Linux server and an existing server with and without mods.
Ubuntu 16.04.2 LTS
kernel: 4.4.0-59-generic
Confirm the same on openSuse Leap 42.2 x64
Starting arma3server without params:
... 18:52:24 InitSound ... 18:52:24 InitSound - complete 18:52:24 Dedicated host created. 18:52:24 PhysX3 SDK Init started ... 18:52:24 PhysX3 SDK Init ended. 18:52:26 Warning Message: You cannot play/edit this mission; it is dependent on downloadable content that has been deleted. a3_characters_f 18:52:26 Loading movesType CfgGesturesMale 18:52:26 MovesType CfgGesturesMale load time 54 ms 18:52:26 Loading movesType CfgMovesMaleSdr 18:52:32 MovesType CfgMovesMaleSdr load time 5979 ms 18:52:32 BattlEye Server: Initialized (v1.215) 18:52:32 Host identity created. [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed. Segmentation fault
All folders/permissions are checked. Server worked fine before update to v1.70
Call of steamcmd.sh:
Redirecting stderr to '/root/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...applicationmanager.cpp (3415) : Assertion Failed: CApplicationManager::GetMountVolume: invalid index applicationmanager.cpp (3415) : Assertion Failed: CApplicationManager::GetMountVolume: invalid index applicationmanager.cpp (3578) : Assertion Failed: m_vecInstallBaseFolders.Count() > 0 OK. Steam>
same with debian 8 as well
18:36:40 Loading movesType CfgGesturesMale
18:36:40 MovesType CfgGesturesMale load time 50 ms
18:36:40 Loading movesType CfgMovesMaleSdr
18:36:44 MovesType CfgMovesMaleSdr load time 4573 ms
18:36:44 BattlEye Server: Initialized (v1.215)
18:36:44 Host identity created.
[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
Segmentation fault (core dumped)
And there it is again.. Another non-minor issue that was known well before release and it still got released and now we are doomed till BI does something.
The same here
Ubuntu server 14.2
Arma3server
13:18:44 Loading movesType CfgGesturesMale
13:18:44 MovesType CfgGesturesMale load time 41 ms
13:18:44 Loading movesType CfgMovesMaleSdr
13:18:49 MovesType CfgMovesMaleSdr load time 4658 ms
13:18:49 BattlEye Server: Initialized (v1.215)
13:18:49 Host identity created.
[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
Same error here since 1.70.
[613242.610126] arma3server[1019]: segfault at 1 ip 000000009aad9bd6 sp 00000000f52f97a0 error 4 in steamclient.so[99ea5000+10b3000]
Ubuntu 16.04.2 LTS
Based on this information I was able to do so:
cd /home/steam/steamcmd
cp linux32/steamclient.so arma3
work for me !
this workaround lets the server start without crashing but trying to connect kicks me off saying that steam authentication failed.
My guess is the server has no connection to the steam servers to auth people
Confirm, this fixed issue for me too, Thanks a lot!
However, I have x64 linux system so I did:
rm /path/to/arma3/steamclient.so ln -s /home/steam/steamcmd/linux64/steamclient.so /path/to/arma3/steamclient.so
Thanks! This is working for me also.
In case a bit more detail would help anyone else, rename or delete the current steamclient.so in the Arma server directory and replace it with a copy or symlink (preferable) to the one provided by steamcmd. In the case of LGSM setups, this looks like:
cd /home/arma3server/serverfiles
mv steamclient.so steamclient.so.bak
ln -s ../steamcmd/linux32/steamclient.so
It's just a warning, not error. I had this message on every start before v1.70 update and server works fine.
Ignore my comment above. Using the shortcut worked wonders. Though you'd have to use the x86 version of steam afaik. Arma doesn't speak to the x64 steamclient
My script kept replacing the steamclient.so when I restarted by doing another update :( So now I do the ln in the shellscript before launch but after version check. All is good now, thanks :)
! In T124761#1604484, @kagotza8 wrote:
Though you'd have to use the x86 version of steam afaik. Arma doesn't speak to the x64 steamclient
Doublechecked it. Clients can connect and play on server without a problems.
Also confirming that it works, thanks. Just make sure to use the 'linux32/steamclient.so' version.
My server starts successfully, even though I have some new minor issues that didn't exist before the DLC update ...
I have the same.... On Linux Debian 8.7
how can i solved it??? or comes soon a hotfix???
I can also confirm sym linking the steamclient.so from the linux32 directory worked for me.
I am running Debian 8 this also fixed it for me:
cd /home/arma3server/serverfiles mv steamclient.so steamclient.so.bak ln -s ../steamcmd/linux32/steamclient.so
Thx guys! Hopefully BI will release something quick to fix that.
Of course we are expecting a definitive solution from Boehmia, but we know that linux users are always left last in the priorities
Symlink or copying isn't a FIX it's just a temporary prothesis to just run a server. My community has major problem, because right now we can't play missions including DAC, after update they cant generate waypoints - on windows server there is no such problem
Supposed to be fixed on dev branch according to the changelog.
18-05-2017
ENGINE
Fixed: Linux Dedicated Server was refusing to start (https://feedback.bistudio.com/T124761)
After the Hotfix update it still works for me. So that apparently has the correct files in it now.