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

[BUG] no server running on /tmp/tmux-997/default - Valheim #3397

Closed
marcleblanc2 opened this issue Mar 22, 2021 · 8 comments
Closed

[BUG] no server running on /tmp/tmux-997/default - Valheim #3397

marcleblanc2 opened this issue Mar 22, 2021 · 8 comments

Comments

@marcleblanc2
Copy link

marcleblanc2 commented Mar 22, 2021

$ ./vhserver st
[  OK  ] Updating vhserver: Checking for update: SteamCMD

No update available
* Local build: 6315977
* Remote build: 6315977
* Branch: public
https://steamdb.info/app/896660/

[ .... ] Starting vhserver: marctestno server running on /tmp/tmux-997/default
[ FAIL ] Starting vhserver: Unable to start marctest

User Story

As a LinuxGSM user and Valheim server admin, I want LinuxGSM to be able to successfully start the Valheim server.

Basic info

  • Distro: [Ubuntu, 20.04 LTS, amd64, focal image build on 2021-03-15]
  • Game: [Valheim]
  • Command: [command_start.sh]
  • LinuxGSM version: [v21.2.2]
  • ldd (Ubuntu GLIBC 2.31-0ubuntu9.2) 2.31
  • tmux 3.0a
  • AWS EC2, t3.medium, 2 vCPUs, 4 GiB RAM, gp3 SSD

Further Information

I see the back and forth of adding and removing the double quotes on this line, to fix one game but break another. With the double quotes, I wasn't able to start the Valheim server, so I removed them, and it works.

command_start.sh#L75
tmux new-session -d -x ${sessionwidth} -y ${sessionheight} -s ${sessionname} ${preexecutable} ${executable} ${startparameters} 2> "${lgsmlogdir}/.${selfname}-tmux-error.tmp"

This seems related to:

To Reproduce

Steps to reproduce the behaviour:

  1. $ ./vhserver st

Expected behaviour

Game server starts

@deathstar
Copy link

I tried to use the update command as well and the server is not updating. Since the client auto-updates through steam, I am now getting "incompatible version" and valheim is no longer playable :(. Please let me know how I can update my valheim server. Thank you!

@deathstar
Copy link

Figured it out. Since I had modified and used serverfiles/start_server.sh to start the server, this instance did not auto-update like i had enabled. The proper way to manage the valheim server is by using ./vhserver start, after using the template from ~/lgsm/config-default/config-lgsm/vhserver/_default.cfg, i was able to create my config in ~/lgsm/config-lgsm/vhserver/vhserver.cfg which will be referenced when using ./vhserver start.

@dvankley
Copy link

dvankley commented Apr 3, 2021

@marcleblanc2 Your fix also gets the server running for me, but it appears to mess up the command parsing so that quoted options passed to valheim_server.x86_64 get mangled, i.e. server name and save file location.

@dvankley
Copy link

dvankley commented Apr 3, 2021

Now I put the quotes back and it works? Guess I need to investigate more...

@MrDanOak
Copy link

MrDanOak commented Sep 5, 2021

can confirm your fix works for me as well @marcleblanc2. Strange that this is an issue.

@purplg
Copy link

purplg commented Sep 14, 2021

I also had this issue and the fix @marcleblanc2 posted resolved the issue, the real culprit for me was having a single quote ' in my server name. The arguments passed to the server get passed as single quotes, for example ./valheim_server.x86_64 -name 'Someone's Server'.

My solution was just removed the ' in the title.

@Claiyc
Copy link
Member

Claiyc commented Mar 23, 2022

Does not seem to be an issue (anymore). Probably fixed by #3370

@Claiyc Claiyc closed this as completed Mar 23, 2022
@github-actions
Copy link
Contributor

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

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants