[Bug]: Valheim

[nathanrhart]

Panel Version

1.10.1

Wings Version

1.7.0

Service

valheim

Modified

No, I did not modify the egg

Expected Behavior

expect the server to start, but it just gets stuck.

Actual Behavior

container@pterodactyl~ Server marked as starting... steam user is not set.

Using anonymous user.

WARNING: setlocale('en_US.UTF-8') failed, using locale: 'C'. International characters may not work. Redirecting stderr to '/home/container/Steam/logs/stderr.txt' src/tier0/threadtools.cpp (3743) : Assertion Failed: Failed to create thread (error 0x1) assert_20221209160418_4.dmp[22]: Uploading dump (out-of-process) /tmp/dumps/assert_20221209160418_4.dmp

assert_20221209160418_4.dmp[22]: Finished uploading minidump (out-of-process): success = no

assert_20221209160418_4.dmp[22]: error: Couldn't resolve host name

assert_20221209160418_4.dmp[22]: file ''/tmp/dumps/assert_20221209160418_4.dmp'', upload no: ''Couldn't resolve host name''

Steps To Reproduce

using latest valheim egg, server gets stuck on 'Starting' forever. Is there something I'm missing that isn't explained in the egg README?

Install logs

https://pteropaste.com/mqr6fy/

[gOOvER]

Thats not an egg issue. Fix your server

[credomane]

Gotta explain with more than "Fix your server". I just added this egg and made a new valhiem server and having this exact issue.

Fix what server? the physical server running docker/wings? The particular virtual server aka the "docker instance"? Or the valhiem server itself? So many possibilities.

My panel and daemon are both 1.11.0

[nathanrhart]

Hi Credomane, just letting you know I'm still working on this. I've tried: ~ valheim egg ~ valheim plus egg ~ valheim egg with a pull request to use latest additions ~ updating to latest panel + wings ~ tried downloading the server manually into the docker instance (via SFTP), and running again. ~ sudo apt-get install --reinstall libc6-i386 ~ I had some success replacing docker_images: "ghcr.io\/parkervcp\/games:valheim": "ghcr.io\/parkervcp\/games:valheim" for "ghcr.io\/parkervcp\/games:source" (in the egg.json), but I myself couldn't connect to the server. This almost confirms it's a docker_image issue. ~ spinning up a server on tin (not in pterodactyl) and seeing if it is an OS/Kernel issue (this worked)

I've been ill so unable to continue this, but from research I'm planning: ~ seeing if the issue is to do with 'turbo' settings in the BIOS ~ seeing if it's a network configuration issue (all IP's are set to 0.0.0.0 on pterodactyl, maybe valheim doesn't like that?)

Let me know if you figure something out.

[toster234]

I had the same problem.

apt update
apt upgrade

try this should help :)

[nathanrhart]

Boy do I feel dumb! an apt update, apt upgrade and reboot solved it! Thanks kind user!

[credomane]

For me it was the sudo apt-get update && sudo apt-get upgrade plus reboot from the day before that trigger my problem but it wasn't until the following afternoon I discovered something was wrong while trying to install and setup a valhiem egg. So after a day of messing around I managed to get things working for now but I'm super confused on just wtf is/was going on.

What was really throwing me off and made this take so long to figure out was the already existing servers for minecraft, factorio and 7dtd were working just fine, start/stop/restart all working, but creating a new server for valhiem gave the thread error. Later I discovered making a new server for any egg would result in the "create thread error" not just the valhiem egg. I don't recall how I even got to this next point but I began investigating/messing with cgroups. Even though docker claims cgroupv2 support and docker info was showing it was using cgroupsv2 through systemd it was not working correctly with v2 all the time or at least not after the updates it wasn't. docker run hello-world always ran with cgroupsv1 or cgroupsv2 but the stuff made by pterodactyl? I had to switch to cgroupsv1 to make any newly created servers work. The crazy thing is after switching to cgroupsv1 and then switching back to cgroupsv2 in the name of testing even the existing pterodactyl servers that were working before with cgroupsv2 no long worked and all eggs began giving the error that specifically calls out an issue with cgroupsv2.

No clue why I was originally getting the error listed in this bug report instead of the normal error that specifically calls out a cgroup issue right in the error message. It wasn't until I tried switching to cgroupsv1 that everything magically started working but when switching back to cgroupsv2 I started getting the error message specifically about cgroups. So the whole cgroupsv2 -> v1 -> v2 broke all the previously existing eggs that were working just fine. So I have no idea if cgroups were my issue all along or if the cgroup version swapping fix the original issue and gave me a new one. I'm so confused on what the hell is/was going on. The most I managed to discover is docker run hello-world always worked on either cgroup version but the pterodactyl servers only work (now) on cgroupsv1. So I'm staying on cgroupsv1 for now. Maybe some day I'll try to figure it out. This whole thing has just reaffirmed the belief I've held for nearly a decade and that is docker is a giant PITA and I'd never touch it if it wasn't for pterodactyl being so awesome.