TheBrian

I didn't find any update feature or script. This is what I did for a manual update: maybe it will help someone. I'm new to Minecraft. If it updates often, I'll get a script together. 1. stop the container 2. ssh root@<my unraid raid server> 3. cd /mnt/user/appdata/<my minecraft container config directory>/minecraft 4. wget https://launcher.mojang.com/v1/objects/0a269b5f2c5b93b1712d0f5dc43b6182b9ab254e/server.jar -O minecraft_server.jar 5. chmod 775 minecraft_server.jar && chown nobody:users minecraft_server.jar 6. start the container -Brian

Hi all, I'm having cert issues now with this Sonarr container. It looks like this new version of the container doesn't trust let's encrypt CAs. The previous container was running for 3+ years without this issue. Were the anchors removed? Error] X509CertificateValidationService: Certificate validation for https://sab.xxxxxxx.com/api?mode=addfile&cat=tv&priority=-100&apikey=xxxxxxxxxxxxxxxxxxxxx&output=json failed. RemoteCertificateChainErrors [Info] RssSyncService: RSS Sync Completed. Reports found: 209, Reports grabbed: 0, Reports pending: 109 [Error] X509CertificateValidationService: Certificate validation for https://sab.xxxxxxxxxxxx.com/api?mode=version&apikey=xxxxxxxxxxxxxxxxxxxx&output=json failed. RemoteCertificateChainErrors [Error] Sabnzbd: Unable to connect to SABnzbd, certificate validation failed. [v3.0.5.1144] NzbDrone.Core.Download.Clients.DownloadClientUnavailableException: Unable to connect to SABnzbd, certificate validation failed. ---> System.Net.WebException: Error: TrustFailure (Authentication failed, see inner exception.): 'https://sab.xxxxxxxxxx.com/api?mode=get_config&apikey=xxxxxxxxxxxxxxx&output=json' ---> System.Net.WebException: Error: TrustFailure (Authentication failed, see inner exception.) ---> System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception. ---> Mono.Btls.MonoBtlsException: Ssl error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED [Warn] SonarrErrorPipeline: Invalid request Validation failed: -- Host: Unable to connect to SABnzbd -- : Test was aborted due to an error: Unable to connect to SABnzbd, certificate validation failed. Thanks!

Thanks, I appreciate the help. I'll take a look at the posts and poke around a bit more.

Thanks for the support. I wiped my steamcmd and serverfiles directories and started over. I left the steamcmd var default and pointed the serverfiles to a different directory under /mnt/cache as you suggested. This time the logs appears to look better but still contains loads of errors. (Filename: ./Runtime/Export/Debug/Debug.bindings.h Line: 35) 02/13/2021 12:30:25: failed to load MyWorld but now I see this, which I've never seen before. CAppInfoCacheReadFromDiskThread took 0 milliseconds to initialize CApplicationManagerPopulateThread took 0 milliseconds to initialize (will have waited on CAppInfoCacheReadFromDiskThread) RecordSteamInterfaceCreation (PID 115): SteamGameServer012 / GameServer RecordSteamInterfaceCreation (PID 115): SteamUtils009 / Utils Setting breakpad minidump AppID = 892970 RecordSteamInterfaceCreation (PID 115): SteamGameServer012 / GameServer RecordSteamInterfaceCreation (PID 115): SteamUtils009 / Utils RecordSteamInterfaceCreation (PID 115): SteamNetworking005 / Networking RecordSteamInterfaceCreation (PID 115): SteamGameServerStats001 / GameServerStats RecordSteamInterfaceCreation (PID 115): STEAMHTTP_INTERFACE_VERSION002 / HTTP RecordSteamInterfaceCreation (PID 115): STEAMINVENTORY_INTERFACE_V002 / Inventory RecordSteamInterfaceCreation (PID 115): STEAMUGC_INTERFACE_VERSION010 / UGC RecordSteamInterfaceCreation (PID 115): STEAMAPPS_INTERFACE_VERSION008 / Apps 02/13/2021 12:30:25: Server ID 90071992547409920 I also see 2457/udp open, but nothing appears in the server list yet. This may be the 25+ minute delay point. It would be great to see "Server is running" in the logs. I'm not familiar with steamcmd, but I suppose there's a way to see if the server is healthy via the container console. PORT STATE SERVICE 2457/udp open|filtered rapido-ip MAC Address: 02:42:02:02:14:22 (Unknown)

Thanks for attaching my log as a file. I'll do that from now on. I set: SteamCMD: /mnt/user/appdata/37648-valheim1 ServerFiles: /mnt/user/appdata/37648-valheim1 Server Name: Valheim Home World Name: MyHome Server Password: MyPassword (my actual password is 8 chars letters and numbers) Public Server: 1 Debug Log Output: true

I had it blank and then set it to 8 chars. Is this long enough?

Has anyone had issues with the Valheim container constantly looping through the startup process and never starting properly? I enabled debug: Valheim.log

I'm glad it's useful. I haven't seen these errors before. Did they start after you installed the intel-gpu-telegraf container or after the upgrade of unraid?

This should be easy enough. I'll take a look.

Certainly! I'll see if I can update the GitHub with the dashboards I use. I'll link them here when I get them uploaded.

Very cool! It's great seeing someone else can use it. Thanks for the Grafana adds. If you don't mind, I may add some of these details to the main post and Docker page. You discovered I'm using the "exec" function of Telegraf. -Brian

Hi all, I figured I would share the container I put together, maybe someone else will find it useful. The goal: See the utilization of the Intel iGPU in my Grafana dashboard. The how: Create a container running a tiny script to manipulate the output of intel_gpu_top and have Telegraf send it to a InfluxDB instance. The result: Docker template repo to add to your Unraid repo list: https://github.com/brianmiller/docker-templates (the container is called 'intel-gpu-telegraf') Docker Hub repo: https://hub.docker.com/r/theoriginalbrian/intel-gpu-telegraf Docker GitHub: https://github.com/brianmiller/docker-intel-gpu-telegraf Currently, the container looks for the "Video/0" engine within the iGPU. If there's a desire to pull this into the Unraid template UI and make it editable, let me know. It shouldn't be difficult too do. -Brian

I just installed the 6.8.0-rc3 release. /dev/dri now appears and the Plex container is using it. The CPU doesn't even blip when I hit it with 3 4k streams, transcoding down to 480p. Fantastic!

That works too

Now that 6.7 is out with kernel 4.19, will we see kernel 4.20 in the next release?

Are you guys seeing the PMS docker container fail to upgrade? Atempting to upgrade to: 1.15.3.876-ad6e39743 https://downloads.plex.tv/plex-media-server/1.15.3.876-ad6e39743/plexmediaserver_1.15.3.876-ad6e39743_amd64.deb 2019-04-09 14:18:05 ERROR 404: Not Found. It looks like the folks at Plex changed their path? https://downloads.plex.tv/plex-media-server-new/1.15.3.876-ad6e39743/debian/plexmediaserver_1.15.3.876-ad6e39743_amd64.deb Update: I selected "force update" and Unraid redeployed the container. All is well now. Something changed on the Plex side as well as something on the container side. Unfortunately, Unraid didn't update the container nor did it believe it was outdated. My version was set to "latest" too.

I'm looking forward to Kernel 4.20 for the i9-9900k iGPU driver support.

Do we know yet if the next version of Unraid will come with kernel 4.20? I'm looking forward to the i915 driver supporting the i9-9900k igpu.

Super simple and flawless upgrade from 6.6.5. Thank you.

When do we get kernel 4.20? Really looking forward to the i9-9900k GPU driver. :)

It looks like the GPU in the 9900k is only supported in 4.20+. The top image is from the i915 dev channel I found and the bottom image is from my unraid 6.6.5 system running the 9900k. Any idea when unraid will support kernel 4.20+? Edit: Just came to the sad realization the latest stable kernel is 4.19 .

It looks like the GPU in the 9900k is only supported in 4.20+. The top image is from the i915 dev channel I found and the bottom image is from my unraid 6.6.5 system running the 9900k. Edit: Just came to the sad realization the latest stable kernel is 4.19

I just installed 6.6.5 with the 9900k and I'm having the same issue. I started another thread last night "missing /dev/dri". I'll take a look at the kernels after 4.18 to see if the GPU is supported yet.

This is my first time using unraid. My sole goal is to replace an old ESXi system that has been running a Plex VM for the last 5 years. The new system is a MSI A-390 PRO motherboard with a i9-9900k CPU. I can't seem to get hardware transcoding working with the Plex container. Here are the steps I've taken: Enabled the IGPU in the BIOS Appended "i915.alpha_support=1" to the initrd line in syslinux.cfg Appended the modprobe i915 and chmod commands to the go file Added the --device line to the docker config When I manually run "modprobe i915" i see the module being loaded with lsmod, but the device "/dev/dri" doesn't appear. Is the i9-9900k IGPU supported? Any help is appreciated. -Brian