On 7/12/2022 at 10:07 AM, ich777 said:

Haven't got time to look into this, also don't know what 7DtD have to do with ArmA3.

These are two different engines from what I know.

 

I will fix this but I'm very busy at the moment in real life and this will take some time.

Any news for this issue?

1 hour ago, John2222 said:

Any news for this issue?

No, other priorities currently, this is on my todo list but I haven't got time for this, maybe next week.

18 hours ago, ich777 said:

Please look at the third recommended post on top of this thread, the path has changed a bit since the empty world that you are experiencing is actually caused by the developers from Valheim because they changed where and how the worlds are saved and in my opinion they simply messed up.

If you want to generate a world I would recommend doing that on your PC and moving the files then over like described in the third recommended post.

 

BTW you can configure the Backups how you want, for example you can configure them to keep a backup for a week or month and take only every 5 hours a backup, that's up to you.

 

Just in case there was any kind of miscommunication, I am NOT blaming you for the world wipeout.    I hope you didn't take it that way.  I know it was the developers.

 

Furthermore, I didn't know you could configure the backups.  Your container has been so rock solid since I installed it, I just kind of "fired and forgot" about looking into anything of that nature.

I was curious if any one had gotten the Space engineers one going. I installed the docker from CA, but can not figure out how to connect to it or manage it.

3 hours ago, CoZ said:

Just in case there was any kind of miscommunication, I am NOT blaming you for the world wipeout.    I hope you didn't take it that way.  I know it was the developers.

No worries, I just wanted to point that out...

 

3 hours ago, CoZ said:

Furthermore, I didn't know you could configure the backups.

You maybe have to pull a fresh copy from the CA App to see all the available options now if you are using the container from the beginning on since my templates don't update on it's own.

30 minutes ago, Spaceghost said:

Space engineers

This container is not created by me nor is it supported by me and so you are basically in the wrong support thread.

 

@fiR3W4LL is the maintainer of that template, but he dosn't have a support thread here? May I ask why @fiR3W4LL?

Sorry about that I had seen a few pages back that it was brought up and just assumed it was yours. I will go see what info I can find appreciate the help.

On 7/20/2022 at 8:54 AM, John2222 said:

Any news for this issue?

Have you yet tried to change the variable 'FORCE_X86' to 'false'?

 

I have no issue running the server in X64 mode, every time I try to copy over the 32bit version from steamclient.so it says that it can't find the steamclient.so for X86, is the new beta maybe 64bit only?

 

Can you please ask the developers which steamclient.so is needed to run the application in 32bit mode or maybe the 32bit mode in the beta branch isn't ready or fully implemented?

I have a project Zomboid server i was wondering if there was a way to change the mode from apocalypse

1 hour ago, Bobulator said:

I have a project Zomboid server i was wondering if there was a way to change the mode from apocalypse

I really don't know if that's possible in multiplayer games.

Aren't the game modes are exclusive to single player games?

You can change most of the settings in the file settings.ini

I'm not too familiar with modding most of the servers.

Here is also the official Dedicated Server Wiki from ProjectZomboid: Click maybe you find what you are looking in there.

 

Please stop the server in the first place if you change any configuration files.

On 7/23/2022 at 2:06 PM, ich777 said:

Have you yet tried to change the variable 'FORCE_X86' to 'false'?

 

I have no issue running the server in X64 mode, every time I try to copy over the 32bit version from steamclient.so it says that it can't find the steamclient.so for X86, is the new beta maybe 64bit only?

 

Can you please ask the developers which steamclient.so is needed to run the application in 32bit mode or maybe the 32bit mode in the beta branch isn't ready or fully implemented?

I tried x64. It doesn't run on my CPU.

I don't think it is 64bit only because there other 32bit users who runs without problems.

 

I search in the dev discord for "steamclient". There wasn't matches in the near time that sounds related. It is not a problem with the game/engine itself. It seems (as you say), that the steamclient.so cannot be found. That was already my guess. So i searched in the web and found a similiar problem with an other game. The solution was to set a symlink. Maybe this is here also the solution. I saw that in the general "steamcmd" folder (not that one in the "gamefiles" folder) there is a 32bit folder with a steamclient.so.  Maybe it is needed to set in 32bit mode a symlink to this file?
Or maybe steamclient.so has to "force" to 32bit also in some kind?
Can you give this a try? If this wouldn't work i will ask the devs (but i have not much hope because it sounds more like a problem of the container than the game itself). Maybe there is a 32bit user with container in dev build around there.

Edited July 25, 20223 yr by John2222

13 minutes ago, John2222 said:

The solution was to set a symlink. Maybe this is here also the solution. I saw that in the general "steamcmd" folder (not that one in the "gamefiles" folder) there is a 32bit folder with a steamclient.so.  Maybe it is needed to set in 32bit mode a symlink to this file?
Or maybe steamclient.so has to "force" to 32bit also in some kind?

I've already tried this and this is how it currently works with the exception that it is copied over and no symlink is set but that makes no difference at all.

2 minutes ago, ich777 said:

I've already tried this and this is how it currently works with the exception that it is copied over and no symlink is set but that makes no difference at all.

I wrote the problem to the devs. There are newer versions of the profiling build but i cannot test this before weekend. So let's see what happen.

Just now, John2222 said:

I wrote the problem to the devs. There are newer versions of the profiling build but i cannot test this before weekend. So let's see what happen.

The main issue that I have is that they ship in the folder linux64 all files for the 64bit version but there is no linux32 folder where the files for the 32bit version are.

It makes also no difference when I put the 32bit steamclient.so from the steamcmd/linux32 folder in the main or in another folder, I've even tried to change the LD_LIBRARY_FOLDER...

 

Please trust my, if I try something like this, I really try almost everything...

8 minutes ago, ich777 said:

The main issue that I have is that they ship in the folder linux64 all files for the 64bit version but there is no linux32 folder where the files for the 32bit version are.

It makes also no difference when I put the 32bit steamclient.so from the steamcmd/linux32 folder in the main or in another folder, I've even tried to change the LD_LIBRARY_FOLDER...

 

Please trust my, if I try something like this, I really try almost everything...

Nichts anderes hätte ich angenommen.
One idea do i have: Can you start the profiling container and look into the logs? Because there were update in the last days. Maybe it is fixed. The hope dies at last.

Edited July 25, 20223 yr by John2222

11 minutes ago, ich777 said:

The main issue that I have is that they ship in the folder linux64 all files for the 64bit version but there is no linux32 folder where the files for the 32bit version are.

It makes also no difference when I put the 32bit steamclient.so from the steamcmd/linux32 folder in the main or in another folder, I've even tried to change the LD_LIBRARY_FOLDER...

 

Please trust my, if I try something like this, I really try almost everything...

I've read something in the discord about a problem with the manifest. Maybe this would help to update this manifest-thing?!?

5 minutes ago, John2222 said:

One idea do i have: Can you start the profiling container and look into the logs? Because there were update in the last days. Maybe it is fixed. The hope dies at last.

I have to try this tomorrow, had a lot of work to do lately for Unraid (changes for all plugins for 6.11+) and also in real life it was a bit challenging...

1 minute ago, ich777 said:

I have to try this tomorrow, had a lot of work to do lately for Unraid (changes for all plugins for 6.11+) and also in real life it was a bit challenging...

Yeah i understand. No worries. RL is most important.

14 hours ago, John2222 said:

Yeah i understand. No worries. RL is most important.

Still no dice with the latest version:

10:55:17 MovesType CfgMovesMaleSdr load time 4680.0 ms
10:55:17 BattlEye Server: Initialized (v1.217)
dlopen failed trying to load:
steamclient.so
with error:
steamclient.so: cannot open shared object file: No such file or directory
[S_API FAIL] SteamAPI_Init(): Sys_LoadModule failed to load: steamclient.so
[S_API FAIL] SteamAPI_Init() failed
10:55:17 Initializing Steam server failed
Arma 3 Console version 2.08.149723 x86 : port 2302
10:55:17 Host identity created.

 

Maybe you can ask where the steamclient.so has to be located and from where it needs to be copied over, I copy it over from the steamcmd/linux32 directory to the main directory.

 

 

However the 64bit version is working fine:

10:56:55 MovesType CfgMovesMaleSdr load time 3365.0 ms
10:56:55 BattlEye Server: Initialized (v1.217)
CAppInfoCacheReadFromDiskThread took 1 milliseconds to initialize
CApplicationManagerPopulateThread took 0 milliseconds to initialize (will have waited on CAppInfoCacheReadFromDiskThread)
RecordSteamInterfaceCreation (PID 333): SteamGameServer012 / GameServer
RecordSteamInterfaceCreation (PID 333): SteamUtils009 / Utils
Setting breakpad minidump AppID = 107410
10:56:55 Game Port: 2302, Steam Query Port: 2303
10:56:55 Initializing Steam server - Game Port: 2302, Steam Query Port: 2303
RecordSteamInterfaceCreation (PID 333): SteamGameServer012 / GameServer
RecordSteamInterfaceCreation (PID 333): SteamUtils009 / Utils
RecordSteamInterfaceCreation (PID 333): SteamNetworking005 / Networking
RecordSteamInterfaceCreation (PID 333): SteamGameServerStats001 / GameServerStats
RecordSteamInterfaceCreation (PID 333): STEAMHTTP_INTERFACE_VERSION002 / HTTP
RecordSteamInterfaceCreation (PID 333): STEAMINVENTORY_INTERFACE_V002 / Inventory
RecordSteamInterfaceCreation (PID 333): STEAMUGC_INTERFACE_VERSION010 / UGC
RecordSteamInterfaceCreation (PID 333): STEAMAPPS_INTERFACE_VERSION008 / Apps
Arma 3 Console version 2.08.149723 x64 : port 2302
10:56:55 Host identity created.
10:56:55 Connected to Steam servers

 

48 minutes ago, ich777 said:

Still no dice with the latest version:

10:55:17 MovesType CfgMovesMaleSdr load time 4680.0 ms
10:55:17 BattlEye Server: Initialized (v1.217)
dlopen failed trying to load:
steamclient.so
with error:
steamclient.so: cannot open shared object file: No such file or directory
[S_API FAIL] SteamAPI_Init(): Sys_LoadModule failed to load: steamclient.so
[S_API FAIL] SteamAPI_Init() failed
10:55:17 Initializing Steam server failed
Arma 3 Console version 2.08.149723 x86 : port 2302
10:55:17 Host identity created.

 

Maybe you can ask where the steamclient.so has to be located and from where it needs to be copied over, I copy it over from the steamcmd/linux32 directory to the main directory.

 

 

However the 64bit version is working fine:

10:56:55 MovesType CfgMovesMaleSdr load time 3365.0 ms
10:56:55 BattlEye Server: Initialized (v1.217)
CAppInfoCacheReadFromDiskThread took 1 milliseconds to initialize
CApplicationManagerPopulateThread took 0 milliseconds to initialize (will have waited on CAppInfoCacheReadFromDiskThread)
RecordSteamInterfaceCreation (PID 333): SteamGameServer012 / GameServer
RecordSteamInterfaceCreation (PID 333): SteamUtils009 / Utils
Setting breakpad minidump AppID = 107410
10:56:55 Game Port: 2302, Steam Query Port: 2303
10:56:55 Initializing Steam server - Game Port: 2302, Steam Query Port: 2303
RecordSteamInterfaceCreation (PID 333): SteamGameServer012 / GameServer
RecordSteamInterfaceCreation (PID 333): SteamUtils009 / Utils
RecordSteamInterfaceCreation (PID 333): SteamNetworking005 / Networking
RecordSteamInterfaceCreation (PID 333): SteamGameServerStats001 / GameServerStats
RecordSteamInterfaceCreation (PID 333): STEAMHTTP_INTERFACE_VERSION002 / HTTP
RecordSteamInterfaceCreation (PID 333): STEAMINVENTORY_INTERFACE_V002 / Inventory
RecordSteamInterfaceCreation (PID 333): STEAMUGC_INTERFACE_VERSION010 / UGC
RecordSteamInterfaceCreation (PID 333): STEAMAPPS_INTERFACE_VERSION008 / Apps
Arma 3 Console version 2.08.149723 x64 : port 2302
10:56:55 Host identity created.
10:56:55 Connected to Steam servers

 

Hi,

 

some suggestions from the discord:

* Use the steamclient.so that is shipped with the arma directory (no copying over from the steamcmd folder). Someone use this (version from 2020) and said it work with 32bit version.
* rights problem or steamclient.so is not flagged as executable
 

In general he said, that the steamclient.so has to be right next to be the arma executable. no special folder is needed.

 

Greetings

Edited July 26, 20223 yr by John2222

18 minutes ago, John2222 said:

* Use the steamclient.so that is shipped with the arma directory (no copying over from the steamcmd folder). Someone use this (version from 2020) and said it work with 32bit version.

Already tried.

 

18 minutes ago, John2222 said:

* rights problem or steamclient.so is not flagged as executable

Permissions are set to 770 and to the corresponding user.

 

19 minutes ago, John2222 said:

In general he said, that the steamclient.so has to be right next to be the arma executable. no special folder is needed.

By default it is but it doesn't work, will investigate further.

It's kind of funny because the current version works on both 32bit and 64bit with my container but the beta branch doesn't...

 

So from my side it seems that something else in terms of the application or the way how ArmA3 works must have changed but if they say it's an issue from the container I must be missing something...

7 hours ago, ich777 said:

Already tried.

 

Permissions are set to 770 and to the corresponding user.

 

By default it is but it doesn't work, will investigate further.

It's kind of funny because the current version works on both 32bit and 64bit with my container but the beta branch doesn't...

 

So from my side it seems that something else in terms of the application or the way how ArmA3 works must have changed but if they say it's an issue from the container I must be missing something...

Maybe some 32bit libraries are missing?

Yeah it is interresting. But if we can fix it in advance, then maybe on the next normal update it would be running out of the box.

Edited July 26, 20223 yr by John2222

Another way of testing:
Can you create a "non-container" arma server for testing? Only delete that the container (and its components) are the problem?

Edited July 26, 20223 yr by John2222

8 hours ago, ich777 said:

Already tried.

 

Permissions are set to 770 and to the corresponding user.

 

By default it is but it doesn't work, will investigate further.

It's kind of funny because the current version works on both 32bit and 64bit with my container but the beta branch doesn't...

 

So from my side it seems that something else in terms of the application or the way how ArmA3 works must have changed but if they say it's an issue from the container I must be missing something...

On the discord there are some one that can reproduce this problem. This seems not an issue from your docker. We will see.

8 minutes ago, John2222 said:

On the discord there are some one that can reproduce this problem. This seems not an issue from your docker. We will see.

Jup, I think they are missing something. Nothing has changed in my container.

 

If you know somehing let me know.