starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 06:05:57 +03:00

[GH-ISSUE #825] Rust Server Not Working #661

New issue

Closed

opened 2026-02-27 02:02:59 +03:00 by kerem · 23 comments

kerem commented

2026-02-27 02:02:59 +03:00

Owner

Originally created by @neondiamonds on GitHub (May 22, 2016).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/825

I've been trying to set up a Rust server on Ubuntu 14.04.4 x64 and Can't seem to get it to work. I followed every step on the LGSM site and have also made a completely new server and reinstalled it.

Whenever I do ./rustserver start I get

./rustserver start
/home/rustserver/lgsm/functions/logs.sh: line 22: fn_printinfo: command not found

[ OK ] Starting rust-server: Rust

And then when I do ./rustserver monitor I get

./rustserver monitor
/home/rustserver/lgsm/functions/logs.sh: line 22: fn_printinfo: command not found

[ FAIL ] Monitor rust-server: Checking session: FAIL
[ OK ] Starting rust-server: Rust

If anyone can help that'd be great. Thank you in advanced.

Originally created by @neondiamonds on GitHub (May 22, 2016). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/825 I've been trying to set up a Rust server on Ubuntu 14.04.4 x64 and Can't seem to get it to work. I followed every step on the LGSM site and have also made a completely new server and reinstalled it. Whenever I do `./rustserver start` I get > ./rustserver start > /home/rustserver/lgsm/functions/logs.sh: line 22: fn_printinfo: command not found > > [ OK ] Starting rust-server: Rust And then when I do `./rustserver monitor` I get > ./rustserver monitor > /home/rustserver/lgsm/functions/logs.sh: line 22: fn_printinfo: command not found > > [ FAIL ] Monitor rust-server: Checking session: FAIL > [ OK ] Starting rust-server: Rust If anyone can help that'd be great. Thank you in advanced.

kerem closed this issue

2026-02-27 02:02:59 +03:00

kerem commented

2026-02-27 02:02:59 +03:00

Author

Owner

@UltimateByte commented on GitHub (May 22, 2016):

I need to investigate through that

I tried to replicate, full log here : http://pastebin.com/H4LPBNMM

@UltimateByte commented on GitHub (May 22, 2016): I need to investigate through that I tried to replicate, full log here : http://pastebin.com/H4LPBNMM

kerem commented

2026-02-27 02:02:59 +03:00

Author

Owner

@UltimateByte commented on GitHub (May 22, 2016):

Maybe try to run update-functions twice. Seemed to fix some stuff for me.
Is this a new server or an existing one you made some time ago ?

@UltimateByte commented on GitHub (May 22, 2016): Maybe try to run update-functions twice. Seemed to fix some stuff for me. Is this a new server or an existing one you made some time ago ?

kerem commented

2026-02-27 02:02:59 +03:00

Author

Owner

@UltimateByte commented on GitHub (May 22, 2016):

I just fixed the core_function errors, quite simple.
github.com/dgibbs64/linuxgsm@d72602c5c6

The new LGSM is working fine for me with my Rust server.
Keep me tuned after running update-functions a second time. :)

@UltimateByte commented on GitHub (May 22, 2016): I just fixed the core_function errors, quite simple. https://github.com/dgibbs64/linuxgsm/commit/d72602c5c64fb6823b84e5936dd452d427faed07 The new LGSM is working fine for me with my Rust server. Keep me tuned after running update-functions a second time. :)

kerem commented

2026-02-27 02:02:59 +03:00

Author

Owner

@neondiamonds commented on GitHub (May 22, 2016):

Yes This Is A New Server, Let me Try What You Did

@neondiamonds commented on GitHub (May 22, 2016): Yes This Is A New Server, Let me Try What You Did

kerem commented

2026-02-27 02:02:59 +03:00

Author

Owner

@neondiamonds commented on GitHub (May 22, 2016):

Just Tried It, Same Problem.
http://pastebin.com/vKC6HDVM

@neondiamonds commented on GitHub (May 22, 2016): Just Tried It, Same Problem. http://pastebin.com/vKC6HDVM

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (May 22, 2016):

Maybe try the manual way.

./rustserver stop
rm -R functions/ lgsm/
./rustserver start

@UltimateByte commented on GitHub (May 22, 2016): Maybe try the manual way. ``` ./rustserver stop rm -R functions/ lgsm/ ./rustserver start ```

kerem commented

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

Author

Owner

@neondiamonds commented on GitHub (May 22, 2016):

Removed it and still have the same problem...

@neondiamonds commented on GitHub (May 22, 2016): Removed it and still have the same problem...

kerem commented

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

Author

Owner

@neondiamonds commented on GitHub (May 22, 2016):

Any info I can give you to help you help me?

@neondiamonds commented on GitHub (May 22, 2016): Any info I can give you to help you help me?

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (May 22, 2016):

OK i've been able to replicate the issue. Hold on.

@UltimateByte commented on GitHub (May 22, 2016): OK i've been able to replicate the issue. Hold on.

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (May 22, 2016):

OK, missing fn_printinfo fixed (was renamed with fn_print_info ), just need to prevent monitor function from moving logs to the logs folder, as this should only happen upon start.

@UltimateByte commented on GitHub (May 22, 2016): OK, missing fn_printinfo fixed (was renamed with fn_print_info ), just need to prevent monitor function from moving logs to the logs folder, as this should only happen upon start.

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (May 22, 2016):

btw, Monitor rust-server: Checking session: FAIL > not related to the script.
Those errors are not harmful. So there might be another issue with your server. We'll check logs soon.

@UltimateByte commented on GitHub (May 22, 2016): btw, Monitor rust-server: Checking session: FAIL > not related to the script. Those errors are not harmful. So there might be another issue with your server. We'll check logs soon.

kerem commented

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

Author

Owner

@neondiamonds commented on GitHub (May 22, 2016):

Alright, that fixed the problem. However, now when I do ./rustserver start I get

./rustserver start
-su: fork: Cannot allocate memory

@neondiamonds commented on GitHub (May 22, 2016): Alright, that fixed the problem. However, now when I do `./rustserver start` I get > ./rustserver start > -su: fork: Cannot allocate memory

kerem commented

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

Author

Owner

@neondiamonds commented on GitHub (May 22, 2016):

I've also gotten

./rustserver start
/home/rustserver/lgsm/functions/check_permissions.sh: fork: Cannot allocate memory

@neondiamonds commented on GitHub (May 22, 2016): I've also gotten > ./rustserver start > /home/rustserver/lgsm/functions/check_permissions.sh: fork: Cannot allocate memory

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (May 22, 2016):

OK, everything's fixed for me.
./rustserver uf

Now if you still have errors like that, it's more likely that the issue comes from your system.
free -m
ps auxn | grep Rust (watch out, hide your rcon password !)
Outputs ?

@UltimateByte commented on GitHub (May 22, 2016): OK, everything's fixed for me. `./rustserver uf` Now if you still have errors like that, it's more likely that the issue comes from your system. `free -m` `ps auxn | grep Rust` (watch out, hide your rcon password !) Outputs ?

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (May 22, 2016):

Just committed the fix, so if you've been too fast, update your functions right now :p

@UltimateByte commented on GitHub (May 22, 2016): Just committed the fix, so if you've been too fast, update your functions right now :p

kerem commented

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

Author

Owner

@neondiamonds commented on GitHub (May 22, 2016):

free -m
total used free shared buffers cached
Mem: 993 934 59 5 0 18
-/+ buffers/cache: 914 79
Swap: 0 0 0

@neondiamonds commented on GitHub (May 22, 2016): > free -m > total used free shared buffers cached > Mem: 993 934 59 5 0 18 > -/+ buffers/cache: 914 79 > Swap: 0 0 0

kerem commented

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

Author

Owner

@neondiamonds commented on GitHub (May 22, 2016):

./rustserver uf
-su: fork: Cannot allocate memory

@neondiamonds commented on GitHub (May 22, 2016): > ./rustserver uf > -su: fork: Cannot allocate memory

kerem commented

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

Author

Owner

@neondiamonds commented on GitHub (May 22, 2016):

I'll try to delete this server and try it on a new machine. Thank you for your help so far, I'll let you know if I have issues on the new machine. What OS Do you recommend I Use?

@neondiamonds commented on GitHub (May 22, 2016): I'll try to delete this server and try it on a new machine. Thank you for your help so far, I'll let you know if I have issues on the new machine. What OS Do you recommend I Use?

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (May 22, 2016):

It doesn't explain the "cannot allocate memory" error upon update-functions, but are your seriously trying to run a rust server with a 1GB RAM machine ?
What's your weed ? I want the same.

@UltimateByte commented on GitHub (May 22, 2016): It doesn't explain the "cannot allocate memory" error upon update-functions, but are your seriously trying to run a rust server with a 1GB RAM machine ? What's your weed ? I want the same.

kerem commented

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

Author

Owner

@neondiamonds commented on GitHub (May 22, 2016):

The thing is, It worked before, very well infact. After I tried to mod it, it broke so I attempted to reinstall and It didn't work at all

@neondiamonds commented on GitHub (May 22, 2016): The thing is, It worked before, very well infact. After I tried to mod it, it broke so I attempted to reinstall and It didn't work at all

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (May 22, 2016):

Well, maybe watch my full tutorial on oxide forum, it's a sticky post, there's even a video, it might help. It also gives a way to automate Oxide updates.

I recommend Debian 8, 64 bits. Simple, efficient, no crapware, best way to go for me ;) @dgibbs64 would probably recommend Ubuntu, but i like him anyways :p
But Rust takes up 4 to 7GB RAM with a 4000 units map, so keep that in mind.

Thank you for reporting those small bugs !
If you need more help, afterwards, please use the steam group, we'll be glad to help as long as you give some logs and relevant info.

Cheers ! :)

@UltimateByte commented on GitHub (May 22, 2016): Well, maybe watch my full tutorial on oxide forum, it's a sticky post, there's even a video, it might help. It also gives a way to automate Oxide updates. I recommend Debian 8, 64 bits. Simple, efficient, no crapware, best way to go for me ;) @dgibbs64 would probably recommend Ubuntu, but i like him anyways :p But Rust takes up 4 to 7GB RAM with a 4000 units map, so keep that in mind. Thank you for reporting those small bugs ! If you need more help, afterwards, please use the steam group, we'll be glad to help as long as you give some logs and relevant info. Cheers ! :)

kerem commented

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

Author

Owner

@UltimateByte commented on GitHub (May 22, 2016):

http://oxidemod.org/threads/setting-up-a-rust-server-with-linux-and-lgsm.16528/

@UltimateByte commented on GitHub (May 22, 2016): http://oxidemod.org/threads/setting-up-a-rust-server-with-linux-and-lgsm.16528/

kerem commented

2026-02-27 02:03:00 +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.