starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 22:25:59 +03:00

[GH-ISSUE #1171] Critical Rust issue (starting today) #913

New issue

Closed

opened 2026-02-27 02:54:17 +03:00 by kerem · 20 comments

kerem commented

2026-02-27 02:54:17 +03:00

Owner

Originally created by @Dids on GitHub (Nov 3, 2016).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1171

Once todays update hits, it will most definitely break everything, as there's an issue with shared library paths, and the only way around that is to manually set the library path, specifically for libsteam_api64.so and Steam-related stuff.

Here's a simple sample on how to fix it for a standard installation of Rust:

#!/bin/bash

# Do not remove this line
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:`dirname $0`/RustDedicated_Data/Plugins/x86_64

# Start the server (note that the -logfile argument is used to log to console)
./RustDedicated -batchmode +server.identity "my_server_identity" +server.hostname "My Server Name" +server.description "My Server Description" -logfile 2>&1

For LGSM, I noticed that if you append the path to the executable= line, it'll work fine.
Here's a quick sed for that (adjust to match your path):

sed -i -e 's#executable="./RustDedicated"#executable="LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/rustserver/serverfiles/RustDedicated_Data/Plugins/x86_64 ./RustDedicated"#g' rustserver

Originally created by @Dids on GitHub (Nov 3, 2016). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1171 Once todays update hits, it will most definitely break everything, as there's an issue with shared library paths, and the only way around that is to manually set the library path, specifically for `libsteam_api64.so` and Steam-related stuff. Here's a simple sample on how to fix it for a standard installation of Rust: ``` #!/bin/bash # Do not remove this line export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:`dirname $0`/RustDedicated_Data/Plugins/x86_64 # Start the server (note that the -logfile argument is used to log to console) ./RustDedicated -batchmode +server.identity "my_server_identity" +server.hostname "My Server Name" +server.description "My Server Description" -logfile 2>&1 ``` For LGSM, I noticed that if you append the path to the `executable=` line, it'll work fine. Here's a quick sed for that (adjust to match your path): ``` sed -i -e 's#executable="./RustDedicated"#executable="LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/rustserver/serverfiles/RustDedicated_Data/Plugins/x86_64 ./RustDedicated"#g' rustserver ```

kerem

2026-02-27 02:54:17 +03:00

closed this issue
added the
type: bug
label

kerem commented

2026-02-27 02:54:18 +03:00

Author

Owner

@Dids commented on GitHub (Nov 3, 2016):

While this does fix the path issue, some users are also seeing segfaults. Not sure if LGSM related or not.

@Dids commented on GitHub (Nov 3, 2016): While this does fix the path issue, some users are also seeing segfaults. Not sure if LGSM related or not.

kerem commented

2026-02-27 02:54:18 +03:00

Author

Owner

@testler2 commented on GitHub (Nov 3, 2016):

Hello, How can i fix my problem?
command_debug.sh: line 105: 26808 Segmentation fault ${executable} ${parms}

@testler2 commented on GitHub (Nov 3, 2016): Hello, How can i fix my problem? command_debug.sh: line 105: 26808 Segmentation fault ${executable} ${parms}

kerem commented

2026-02-27 02:54:18 +03:00

Author

Owner

@UltimateByte commented on GitHub (Nov 4, 2016):

Facepunch...

@UltimateByte commented on GitHub (Nov 4, 2016): Facepunch...

kerem commented

2026-02-27 02:54:18 +03:00

Author

Owner

@cedarlug commented on GitHub (Nov 4, 2016):

@testler2 - Adding the LD_LIBRARY_PATH to the executable in the rustserver script seems to be the fix for my deployment. No segfaults yet.

Specficially:

rustserver@gamerig:~$ grep LD_LIBRARY rustserver
executable="LD_LIBRARY_PATH=$LD_LIBRARY_PATH:`dirname $0`/RustDedicated_Data/Plugins/x86_64 ./RustDedicated"
rustserver@gamerig:~$

Not so sure that it's the LGSM fix, however.

@cedarlug commented on GitHub (Nov 4, 2016): @testler2 - Adding the LD_LIBRARY_PATH to the executable in the `rustserver` script seems to be the fix for my deployment. No segfaults yet. Specficially: ``` bash rustserver@gamerig:~$ grep LD_LIBRARY rustserver executable="LD_LIBRARY_PATH=$LD_LIBRARY_PATH:`dirname $0`/RustDedicated_Data/Plugins/x86_64 ./RustDedicated" rustserver@gamerig:~$ ``` Not so sure that it's the LGSM fix, however.

kerem commented

2026-02-27 02:54:18 +03:00

Author

Owner

@UltimateByte commented on GitHub (Nov 4, 2016):

Relevant links

http://oxidemod.org/threads/problem-with-the-latest-rust-update-on-linux.21769/
http://steamcommunity.com/groups/linuxgsm/discussions/0/282992646966882793/

@UltimateByte commented on GitHub (Nov 4, 2016): Relevant links http://oxidemod.org/threads/problem-with-the-latest-rust-update-on-linux.21769/ http://steamcommunity.com/groups/linuxgsm/discussions/0/282992646966882793/

kerem commented

2026-02-27 02:54:18 +03:00

Author

Owner

@Dids commented on GitHub (Nov 4, 2016):

From what I've witnessed, the segfaults seem to be affecting OVH servers, more accurately those using OVH's custom kernel.

@Dids commented on GitHub (Nov 4, 2016): From what I've witnessed, the segfaults seem to be affecting OVH servers, more accurately those using OVH's custom kernel.

kerem commented

2026-02-27 02:54:18 +03:00

Author

Owner

@Dids commented on GitHub (Nov 4, 2016):

Note that steamclient.so was also moved from RustDedicated_Data/Plugins/x86_64 to the root directory, which I've heard breaks LGSM so it halts instead of showing any errors. Copying/moving that back to the plugins directory should fix that.

@Dids commented on GitHub (Nov 4, 2016): Note that `steamclient.so` was also moved from `RustDedicated_Data/Plugins/x86_64` to the root directory, which I've heard breaks LGSM so it halts instead of showing any errors. Copying/moving that back to the plugins directory should fix that.

kerem commented

2026-02-27 02:54:18 +03:00

Author

Owner

@melvinlemoine commented on GitHub (Nov 5, 2016):

Hello, I moved steamclient.so to RustDedicated_Data/Plugins/x86_64 but error persist

@melvinlemoine commented on GitHub (Nov 5, 2016): Hello, I moved steamclient.so to RustDedicated_Data/Plugins/x86_64 but error persist

kerem commented

2026-02-27 02:54:18 +03:00

Author

Owner

@Dids commented on GitHub (Nov 5, 2016):

You will also need the LD_LIBRARY_PATH fix from above.

EDIT: Just to update everyone, Facepunch knows about the issue and is trying to find a fix. It's related to the new Steamworks update/library.

@Dids commented on GitHub (Nov 5, 2016): You will also need the `LD_LIBRARY_PATH` fix from above. **EDIT**: Just to update everyone, Facepunch knows about the issue and is trying to find a fix. It's related to the new Steamworks update/library.

kerem commented

2026-02-27 02:54:18 +03:00

Author

Owner

@melvinlemoine commented on GitHub (Nov 5, 2016):

I execute grep LD_LIBRARY_PATH rustserver and grep LD_LIBRARY rustserver.
And I moved steamclient.so.
But the problem persist

@melvinlemoine commented on GitHub (Nov 5, 2016): I execute grep LD_LIBRARY_PATH rustserver and grep LD_LIBRARY rustserver. And I moved steamclient.so. But the problem persist

kerem commented

2026-02-27 02:54:18 +03:00

Author

Owner

@Dids commented on GitHub (Nov 5, 2016):

@MelvynSaytek grep doesn't actually edit anything, it's used for searching.

The rustserver script has a line similar to this:
executable="./RustDedicated"

This needs to be changed to include the path to the Rust plugins, like this:

executable="LD_LIBRARY_PATH=$LD_LIBRARY_PATH:`dirname $0`/serverfiles/RustDedicated_Data/Plugins/x86_64 ./RustDedicated"

So, edit the file and make sure it's exactly as above, and it should work.

EDIT: Fixed path.

@Dids commented on GitHub (Nov 5, 2016): @MelvynSaytek grep doesn't actually edit anything, it's used for searching. The `rustserver` script has a line similar to this: `executable="./RustDedicated"` This needs to be changed to include the path to the Rust plugins, like this: ``` executable="LD_LIBRARY_PATH=$LD_LIBRARY_PATH:`dirname $0`/serverfiles/RustDedicated_Data/Plugins/x86_64 ./RustDedicated" ``` So, edit the file and make sure it's exactly as above, and it should work. **EDIT**: Fixed path.

kerem commented

2026-02-27 02:54:18 +03:00

Author

Owner

@melvinlemoine commented on GitHub (Nov 5, 2016):

it's work thank you very much !!

@melvinlemoine commented on GitHub (Nov 5, 2016): it's work thank you very much !!

kerem commented

2026-02-27 02:54:18 +03:00

Author

Owner

@UltimateByte commented on GitHub (Nov 8, 2016):

So, just reproduced the issue.
Will try the fix to eventually commit this to master. I'm surprised nobody pull requested a fix already. Maybe you guys like the lack of competition with other servers.

@UltimateByte commented on GitHub (Nov 8, 2016): So, just reproduced the issue. Will try the fix to eventually commit this to master. I'm surprised nobody pull requested a fix already. Maybe you guys like the lack of competition with other servers.

kerem commented

2026-02-27 02:54:18 +03:00

Author

Owner

@UltimateByte commented on GitHub (Nov 9, 2016):

Fixed with the executable commands.
Working on a fresh install.

@UltimateByte commented on GitHub (Nov 9, 2016): Fixed with the executable commands. Working on a fresh install.

kerem commented

2026-02-27 02:54:18 +03:00

Author

Owner

@dashdanw commented on GitHub (Nov 9, 2016):

this may not work on newer systems since you're not allowed to edit LD_LIBRARY_PATH, you may need to export it at the top of the script as mentioned above or included in your rustserver users bashrc

@dashdanw commented on GitHub (Nov 9, 2016): this may not work on newer systems since you're not allowed to edit LD_LIBRARY_PATH, you may need to export it at the top of the script as mentioned above or included in your rustserver users bashrc

kerem commented

2026-02-27 02:54:18 +03:00

Author

Owner

@UltimateByte commented on GitHub (Nov 9, 2016):

@dashdanw What are you calling "newer systems" ?
Because i just tested that on Debian 8. At least it will fix some (most ?) of the issues.

@UltimateByte commented on GitHub (Nov 9, 2016): @dashdanw What are you calling "newer systems" ? Because i just tested that on Debian 8. At least it will fix some (most ?) of the issues.

kerem commented

2026-02-27 02:54:19 +03:00

Author

Owner

@cedarlug commented on GitHub (Nov 9, 2016):

@UltimateByte "newer systems" == Windows 10 - it won't work there.

Seriously though, @dashdanw what are you referring to? Your statement makes no sense.

@cedarlug commented on GitHub (Nov 9, 2016): @UltimateByte "newer systems" == Windows 10 - it won't work there. Seriously though, @dashdanw what are you referring to? Your statement makes no sense.

kerem commented

2026-02-27 02:54:19 +03:00

Author

Owner

@Dids commented on GitHub (Nov 9, 2016):

@cedarlug @UltimateByte Maybe he's referring to security features of some OS's, but even then, wouldn't LD_LIBRARY_PATH simply be "local" (user bound)?

At any rate, this is fixed, awesome and thank you.

@Dids commented on GitHub (Nov 9, 2016): @cedarlug @UltimateByte Maybe he's referring to security features of some OS's, but even then, wouldn't LD_LIBRARY_PATH simply be "local" (user bound)? At any rate, this is fixed, awesome and thank you.

kerem commented

2026-02-27 02:54:19 +03:00

Author

Owner

@UltimateByte commented on GitHub (Nov 9, 2016):

Thanks a lot to you @Dids for pointing out the fix. You rock man !

@UltimateByte commented on GitHub (Nov 9, 2016): Thanks a lot to you @Dids for pointing out the fix. You rock man !

kerem commented

2026-02-27 02:54:19 +03:00

Author

Owner

@lock[bot] commented on GitHub (Jul 19, 2018):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock[bot] commented on GitHub (Jul 19, 2018): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.