-
Notifications
You must be signed in to change notification settings - Fork 1
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
Server completely un-joinable after restart, corrupted .explored files? #18
Comments
Oooh thats interesting. So far I had only one other user run into the same problem and I thought it was an issue with the used docker image (which was pterodactyl), but I couldnt for the life of me reproduce it, unfortunately he turned inactive. I'll take a look at everything and try to reproduce it, I hope I can catch that slippery bug this time. The bug report is certainly extremely useful, thank you :) Cheers I'll be pasting the report about the same bug from NexusMods here so I have it in one place
|
Looks like this is why I had to disable the mod on my server. I assumed it was due to the newest update being incompatible with the patch, but after removing the .explored file, I'm able to use the mod again. Something I noticed about the issue is the valheim server process RAM usage would quickly explode to 100% and essentially stall out my 4GB VPS instance. I wonder if my machine had more RAM it would be able to get the server up and running? I'm running an ubuntu based VPS with the dedicated server setup through LGSM (https://linuxgsm.com/lgsm/vhserver/) |
He, that could certainly be it, and I can reproduce that. I wonder where I screwed that up, wow. I'll take a look in 2 hours, but that should definitely not be happening but thats atleast something thats somehow easy to find/track |
Ok so it seems like its related to how much data is in the shared map-- Me and my friends all did a bunch of exploring late last night, as well as synced all of our maps with the server for the first time. After the reboot that night, my DigitalOcean droplet (2CPU/4GB RAM) was totally unresponsive, to the point where I couldn't even connect an SSH session. But since then I reproduced the issue a few times without any performance issues by starting the server, connecting to sync my map, and then restarting the server. |
Greetings, I put out a rc-1.2.1 which should fix that issue: https://github.com/Mydayyy/Valheim-ServerSideMap/releases/download/rc1-1.2.1/ServerSideMap.zip What went wrong?
Found that out via https://stackoverflow.com/a/8613300 If you can spare a minute I'd be happy to know whether the new RC works for you. I didn't notice any memory overhead anymore. Cheers Edit: Also @brahaney: In case the new RC works for you, you should be able to plop the old .explored files right back in. I checked them and they are not damaged. |
It's fixed! Amazing. Thanks for the speedy response, we were really excited to use this mod! Feel free to ping me if you've got new versions or features to test. |
Glad to hear! I released 1.2.1 as a new version on NexusMods and Thunderstore. If you're already running the rc1-1.2.1 there's no need to update, there weren't any changes except a formal release. Incredible sorry for this bug, thank you for the great report! Cheers |
First off-- love the mod concept. Until a restart it works great! My friends and I were loving the sharing. If theres any way I can help to further debug this or anything please let me know. I'm a Software Engineer in Test so, testing/debugging is my jam. Is there a way to activate like a debug mode for BepInEx or just this mod, to get some logging from the events I describe below? Currently nothing at all happens in the logs.
The issue
This issue is consistently replicable in my environment. I have not yet tried isolating just this mod to replicate but if I have time to do so I will post my findings.
My server is scheduled to do check for updates nightly, which currently results in a restart. Each morning this results in being completely unable to reconnect to the server. There are no errors in the server log or client log-- when connecting, instead of prompting for my password, I get the following two screens:
The connection issue applies to all users, not only users with the mod installed. One of our players is still running completely vanilla client and cannot connect either once this issue begins.
I've deduced this to be an issue with SSM. It's the only mod I had added since the crashes started, and I can resolve the issue without removing the mod from the server or by simply deleting or moving
Wootheim2.mod.serversidemap.explored
and restarting.This issue has replicated each time my server has restarted to check for updates, and can be replicated in my environment below with a simple
docker-compose restart
command.I have also attached two of the "corrupted" (I guess?)
.explored
files, not sure if they're helpful.wootheim-explored-files.zip
Environment
latest version of Valheim dedicated server, linux (containerized in docker), with only a handful of mods:
5.4.8.0
0.9.4
1.1.2
run by this docker imagerc1-1.2.0
&1.2.0
) (default config, no pin sharing)I also attached my zipped config directory in case anything in there helps.
wootheim-config.zip
I run the entire thing in docker, using mbround18/valheim docker image and the following
docker-compose.yml
The text was updated successfully, but these errors were encountered: