-
-
Notifications
You must be signed in to change notification settings - Fork 23
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]: cannot start rust server due to tail looking in wrong folders #55
Comments
kunihir0
changed the title
[Bug]: cannot start rust server
[Bug]: cannot start rust server due to tail looking in wrong folders
Jan 4, 2024
still doesn't work, same errors regardless of the image I pull or build |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
User story
just trying to create a new rust server but upon first installation command start fails becasue of tail looking at the wrong location for logs
Game
rust
Linux distro
Ubuntu 22.04
Command
command: start
Further information
so I am using docker linux gsm when I create a new container the problem persists. tail is looking for the wrong log file in the wrong place.
I have also tried to update the lsgm using
PS C:\Users\Tamik> docker exec -it --user linuxgsm HOA_RUSTs ./rustserver update-lgsm
but that didn't really do much to solve the problem but instead create a new errorhere is the docker-compose.yml
and here is the Dockerfile.rust
so I think the linuxgsm app itself one of the files is causing that problem rather than docker
I even updated the rust server itself using to make sure nothing on that side was causing anything.
Relevant log output
Steps to reproduce
No response
edit:
the folder an files do exist
I will update in a bit I am gonna remove the logs folder and retry that
edit 2:
So I updated the lgsm and that still didn't work so after I deleted logs and that caused it to revert the error msg to
edit 3:
let me retry with debug mode I just saw that that in the troubleshooting guide myb
edit 4:
debug mode didn't really work as it just hung on initialization after the unity options flags
The text was updated successfully, but these errors were encountered: