-
-
Notifications
You must be signed in to change notification settings - Fork 832
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
[Bug]: Using Console command ./rustserver console shows error/misconfiguration #4511
Comments
Forgot to add logs.. Here you go. rustserver-game.log |
Any fix? Same problem, server is working fine, but i cant get into console |
Im also stuck with the same problem 😄 |
Seems to be related to some permission issues perhaps? I am able to run the server using the dedicated sh file in the server's directory (/home/rustserver/serverfiles/) like so:
Server boots fine. But when running with LinuxGSM I am stuck at the exact same point as you. |
Found the issue 😄It's related to this part of the launch parameters:
Seems removing it allows the server to continue running. I'm not familiar with LinuxGSM, is it possible to disable this parameter 🙂? Or perhaps it indeed is an issue with permissions? |
More investigation proves the log is indeed working and the server is starting 🙂 Simply nothing being printed when attaching to the server console. Solution:run the server and wait 20-30 minutes. Server should be up and running after a while. Tail this file:
to follow the latest logs. |
This still a problem. |
User story
As a bug, I want the bug to be looked over sometime, so that other people can have a better experience than I did.
Game
Rust
Linux distro
Ubuntu 22.04
Command
command: console
Further information
After running the console command "./rustserver console" and saying yes it loads the console and brings this up instead of showing the actual console. I can connect to the Rust server just fine, but I cannot access the console to give myself owner or edit my oxide plugins.
Relevant log output
Steps to reproduce
The text was updated successfully, but these errors were encountered: