Gromit83

UPDATE: I removed the unnassigned drives plugin and did the AMD CPU power setting thingy for Ryzen. Seems to be stable now. UPDATE2: Since I got asked about the AMD power thingy Link: AMD power setting thingy for Ryzen ORIGINAL: I'm having these errors after 6.12.5. It ran stable since before 6.12.4 I think. Thought it was my NVME adapter so fleshed out 250 Euros for a QNAP one. Guess I could have saved that money. This error also brings down the cache drives and makes the GUI mostly non responsive. The server also won't power down with the power button. A hard reset tho makes everything work for 2-3 days and then just comes crashing down. Turned on logging to the flash drive, but the log has nothing of interest really. Only this. Making me believe it's some pluginerror as described above here. Here are the plugins I use: Server log from flashdrive.

Are there any issues with EAC files? Now getting this error and I have never encountered this before. (ANd yes my temp folders are correctlly mapped. EAE timeout! EAE not running, or wrong folder? EDIT: Did some more digging. Stopped the server and deleted everything in /mnt/appdata/binhex-plexpass/Plex Media Server/Codecs to force Plex to redownload the codecs and everything is up and running again. Best regards

Hi. Is it possible to update the minecraft bedrock server image to make a backup of the server logs? As it is now it dissappears on reboot. on startup I get this messange NO LOG FILE! - Failed to up file descriptor limit Operation not permitted NO LOG FILE! - setting up server logging... Also the description is pointing to a webhook at port 9010, but that's outdated maybe or just for the java version? tyty for an awesome docker.

Next big release is 1.19 anyway around june 7 so Im guessing they won't update 1.18 anymore until then unless there is some grave error or security flaw. I will keep that to mind

I tried setting the game version parameter to the concrete server version: 1.18.33.02 That worked actually.

Just FYI for those running Minecraft. Somehow the latest setting installed a 1.19 beta version. You will need to revert to 1.18