Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with executing steamcmd #4065

Open
unkreativ-mp4 opened this issue Sep 13, 2024 · 4 comments
Open

Issue with executing steamcmd #4065

unkreativ-mp4 opened this issue Sep 13, 2024 · 4 comments

Comments

@unkreativ-mp4
Copy link

I installed FEX using the quick start command in the read.me, I also installed SteamCMD and checked that the files are there. However if I try executing steamcmd.sh I get the following error:

Invalid or Unsupported elf file.
This is likely due to a misconfigured x86-64 RootFS
Current RootFS path set to ''
RootFS path doesn't exist. This is required on AArch64 hosts
Use FEXRootFSFetcher to download a RootFS

I tried both using the rootfs as extracted and "as is" using FEXRootFSFetcher. I use Ubuntu 22.04.4 on a free tier oracle server, if this helps.
The content of the Config.json file is : {"Config":{"RootFS":"Ubuntu_22_04"}}
There is also a folder /home/ubuntu/.fex-emu/RootFS/Ubuntu_22_04 with contents that look like an Ubuntu image.

Thank you for any help.

@Sonicadvance1
Copy link
Member

Sounds like you're switching users at some point, since the rootfs install is per-user. Which would lead the additional user to not have a rootfs.
A bunch of these copy-paste steamcmd setup guides ask you to change to a steam user, is this what is occuring?

@unkreativ-mp4
Copy link
Author

I used the commands below to install steamcmd I and should be logged in only as the "ubuntu" user

cd /tmp
curl -sSL -o steamcmd.tar.gz https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz
mkdir -p /mnt/server/steamcmd
tar -xzvf steamcmd.tar.gz -C /mnt/server/steamcmd
cd /mnt/server/steamcmd

@Sonicadvance1
Copy link
Member

That seems to work fine here, maybe FEXServer has a stale configuration running, can try to do a quick FEXServer -k in order to kill the current active FEXServer, letting it reload the config.

@unkreativ-mp4
Copy link
Author

That sadly didn't help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants