John2222

Members
  • Posts

    38
  • Joined

  • Last visited

Everything posted by John2222

  1. Surprisingly a new arma 3 profiling branch executable was released today. First users reported that it worked.
  2. Good news. The devs have found the issue. It was (as i understand) a using of RUNPATH instead of RPATH. They posted a hotfix but there will be next week shipped a fixed version anyhow. So It would say let's wait till next week.
  3. On the discord there are some one that can reproduce this problem. This seems not an issue from your docker. We will see.
  4. 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?
  5. 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.
  6. 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
  7. Yeah i understand. No worries. RL is most important.
  8. I've read something in the discord about a problem with the manifest. Maybe this would help to update this manifest-thing?!?
  9. 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.
  10. 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.
  11. 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.
  12. I've done some search for the problem in the 32bit log: "steamclient.so: cannot open shared object file: No such file or directory": It seems there is some symlink missing or the rights are not set correctly. https://community.7daystodie.com/topic/19590-dlopen-failed-trying-to-load-steamclientso-fixed/
  13. Server runs locally, but: I am kicked because of steam ticket. But reload of steam doesn't help. Maybe this is the Propblem (see last lines of your x86 log): 13:42:09 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 The steamclient.so is updated in the gamefile folder. I've started one of the old docker and there is no such errors in the log.
  14. This happens in the beta branch, not the stable. I posted the start line in my first post for this issue: " If you want to try it by yourself, here is the starting line for the GAME_ID parameter: 233780 -beta profiling -betapassword CautionSpecialProfilingAndTestingBranchArma3 " And I start in 32bit "mode". This issue will be a problem for the stable, when the next update is delivered by BI. And this will be happen soon(couple of weeks) as i know. I load the beta testing branch and also the profiling/performance branch to give feedback to the devs for the supported 32bit linux versions.
  15. Another possible fix can maybe this: https://askubuntu.com/questions/575505/glibcxx-3-4-20-not-found-how-to-fix-this-error/582910#582910 This means to install/upgrade libstdc++6 as i understand. Because the issues seems not with glibc but with glibc++.
  16. I'm on 6.10.3 Iv'e got some answers from the devs: "We recently updated our Linux builder, as we kept running into odd compiler errors and bugs. We should be building all 32bit and 64bit binaries for Linux on the new builder from now on, which builds using glibc 2.28. We won't be using new versions of glibc, because as of 2.31 they got rid of some -ffinite-math-only stuff needed by one of the libraries we use." So this means the actual debian version (bullseye) is too new (because of GlibC 2.31), right?
  17. I've done some search. Is it possible to install * GCC 4.9.0 and * GCC 5.1.0 into the container? They come with these files https://gcc.gnu.org/onlinedocs/libstdc++/manual/abi.html
  18. What do you mean with "deprecate"? You will update it to a newer distro or stop the support? Bookworm is using 2.33 experimental is using 2.34 Would it help to change to "Bookworm" if the arma guys would reduce to 2.33 or is it also okay to use experimental with 2.34?
  19. Hi, in arma 3 32bit linux profiling branch the compiler was updated. Now the container throws this: ./arma3server: /serverdata/serverfiles/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by ./arma3server) ./arma3server: /serverdata/serverfiles/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by ./arma3server) ./arma3server: /serverdata/serverfiles/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by ./arma3server) The guys in the arma discord said, the container has to be updated. So i am now here If you want to try it by yourself, here is the starting line for the GAME_ID: 233780 -beta profiling -betapassword CautionSpecialProfilingAndTestingBranchArma3 Greetings BTW: In the beta branch there is this fix implemented: - Fixed: Game was unable to launch on CPUs from 2008 or earlier So maybe the 64bit problem have a chance to be fixed for many users. (I will try it if container is running again in beta branch)
  20. Hi, Arma 3 i have managed to download mods by usercript. It downloads this in the ..\appdata\arma3\gamefiles_5\steamapps\workshop\content\107410 folder. I want this in "gamefiles/mods/Modname" folder. I tried this with symlink over your krusader docker but this doesn't seem to work. arma 3 does not find the folder/link. Do i need root for this operation?
  21. THX you very much. I can connect to the server now. Additional i would ask for a QoL variable: For the server the dev provides a special executable in various forms. Today i rename the executables like the vanilla executable and so the server starts with this. For convinience reasons it would be great to have a variable in the docker container to define the executable name. So a switching between the starting executables would be more nice and i does'n have to overwrite the vanilla exe.
  22. Oh thank you very much. With the question of the processor i meant the other guy with problems. Thing with Arma is, that the 32bit executable is running with Phenom II, the 64 doesn't. At the moment the container is running with the 32bit per default. So my suggestions is to set the executables on 64bit but make it in the "edit"-Site of the contaier selectable (for both, steamclient and arma exe). BTW: Last week Bohemia makes in his "performamance" exes some tweaks for better performance on more low end maschines. So it would make sense to support maschines like the phenoms a littlle more.
  23. The Phenom has not all newer instruction sets, for example AVX is missing. I think thats the problem with some 64 apps. So i do your suggestions (again): * deleted steamcmd folder * deleted all .so files from arma folder (so also steamclient.so) * i deleted also the profile folder * force update i tried at the first try , so i skipped. Nothing has changed. 17:26:26 MovesType CfgMovesMaleSdr load time 20909.0 ms dlopen failed trying to load: steamclient.so with error: steamclient.so: wrong ELF class: ELFCLASS64 [S_API FAIL] SteamAPI_Init(): Sys_LoadModule failed to load: steamclient.so [S_API FAIL] SteamAPI_Init() failed 17:26:27 Initializing Steam server failed Arma 3 Console version 2.06.148470 x86 : port 2302 17:26:27 Mission DynBulwarks_dev_20200817_WMod_0v7.vn_khe_sanh read from bank. 17:26:27 mpmissions\__cur_mp.vn_khe_sanh\mission.sqm/Mission/Entities/Item47/Entities/Item1.type: Unknown enum value Land 17:26:27 Host identity created. 17:26:27 Mission DynBulwarks_dev_20200817_WMod_0v7.vn_khe_sanh: Number of roles (13) is different from 'description.ext::Header::maxPlayer' (12) Can you tell, what was the change from the last docker update?