palworld-server-docker
palworld-server-docker copied to clipboard
thijsvanloef
Synology NAS OODLE messages
OODLE USAGE WARNING : Destination buffer appears to be in uncached or write-combined memory! This is extremely slow. See "How do I decompress to graphics memory quickly?" in the Oodle FAQ. (Usage warnings can be disabled via Oodle_SetUsageWarnings.)
after running the server for a while in Synology, this error message will pop up in log,
Server is still able to have players but extreme rubber banding and glitches would start to happen.
Have you checked the in use memory when this happens? The dedicated server process appears to have a memory leak and will often reach 20gb+ every day.
out of 32 gigs of ram, usage is usually 12-16gb on the process it self which saturates around 20gb out of 32gb of ram, It happens more quicker when more than one player is logged in
I see it too, it happens immediately on server startup. It's not specific to this container. https://www.reddit.com/r/Palworld/comments/1ahaip7/palworld_linux_server/
Happened to me as well, been running it on 923+ with 32Gigs of RAM.
My temporary fix to this is to schedule restarts few times a day to clear the mem.
Can you tell me how to auto restart
On Sat, Feb 10, 2024 at 5:48 AM ssenrober @.***> wrote:
Happened to me as well, been running it on 923+ with 32Gigs of RAM.
My temporary fix to this is to schedule restarts few times a day to clear the mem.
— Reply to this email directly, view it on GitHub https://github.com/thijsvanloef/palworld-server-docker/issues/301#issuecomment-1936970339, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFR6D3R5VG7OHKZZJVNBXKTYS5GATAVCNFSM6AAAAABC4GKPPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWHE3TAMZTHE . You are receiving this because you authored the thread.Message ID: @.***>
Can you tell me how to auto restart … On Sat, Feb 10, 2024 at 5:48 AM ssenrober @.> wrote: Happened to me as well, been running it on 923+ with 32Gigs of RAM. My temporary fix to this is to schedule restarts few times a day to clear the mem. — Reply to this email directly, view it on GitHub <#301 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFR6D3R5VG7OHKZZJVNBXKTYS5GATAVCNFSM6AAAAABC4GKPPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWHE3TAMZTHE . You are receiving this because you authored the thread.Message ID: @.>
so basically you can set up auto scripts under the synology control panel and go for the task scheduler, setup the period you want and draft a command like this
docker restart container_name
hope this will help but it's more of a temporary fix to me, pretty sure there's a better fix than this
You can also set automatic reboots in the container: https://palworld-server-docker.loef.dev/guides/automatic-reboots
