ultimz

Upgraded and all went well. Thanks to all that contributed to this release!

Upgraded from 6.12.10 to 6.12.11 - no issues experienced. Thanks so much to everyone who worked on this!

Will do. Thanks @Squid

Hi, Hope someone can assist me. I am seeing the following error: /var/log is getting full (currently 100 % used) If I check the log I think it's due to this: Jun 18 03:31:42 Server-Unraid nginx: 2024/06/18 03:31:42 [error] 29546#29546: nchan: Out of shared memory while allocating message of size 14853. Increase nchan_max_reserved_memory. Jun 18 03:31:42 Server-Unraid nginx: 2024/06/18 03:31:42 [error] 29546#29546: *5801161 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Jun 18 03:31:42 Server-Unraid nginx: 2024/06/18 03:31:42 [error] 29546#29546: MEMSTORE:00: can't create shared message for channel /disks Jun 18 03:31:43 Server-Unraid nginx: 2024/06/18 03:31:43 [crit] 29546#29546: ngx_slab_alloc() failed: no memory Jun 18 03:31:43 Server-Unraid nginx: 2024/06/18 03:31:43 [error] 29546#29546: shpool alloc failed Jun 18 03:31:43 Server-Unraid nginx: 2024/06/18 03:31:43 [error] 29546#29546: nchan: Out of shared memory while allocating message of size 14853. Increase nchan_max_reserved_memory. Jun 18 03:31:43 Server-Unraid nginx: 2024/06/18 03:31:43 [error] 29546#29546: *5801163 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Jun 18 03:31:43 Server-Unraid nginx: 2024/06/18 03:31:43 [error] 29546#29546: MEMSTORE:00: can't create shared message for channel /disks Jun 18 03:31:44 Server-Unraid nginx: 2024/06/18 03:31:44 [crit] 29546#29546: ngx_slab_alloc() failed: no memory Jun 18 03:31:44 Server-Unraid nginx: 2024/06/18 03:31:44 [error] 29546#29546: shpool alloc failed Diagnostic logs attached. I am rebooting now. server-unraid-diagnostics-20240620-1912.zip

Thanks @JorgeB!

Thanks @JorgeB! I was able to do a clean shutdown and checked cables. Server came back up and just had to rebuild disk3. Appreciate the assistance with this. Attached fresh diagnostics. server-unraid-diagnostics-20240606-0549.zip

Hi, I woke up to a read error and a disk that had been disabled so trying to figure out what to do. I have pulled Diagnostics (attached) and am trying to stop the array to shut down the server to check cables but the server doesn't want to stop the array... I can still logon to the server but it's not behaving correctly (e.g. CPU stats show no activity on home page). Trying to stop the array and it comes up with a Proceed or Cancel but if I click Proceed it doesn't do anything. Any assistance would be appreciated. Thanks server-unraid-diagnostics-20240605-1636.zip

I am now running 8.1.127 Is that normal behavior for the container to show it has an update even though my tag is set to 11notes/unifi:8.1.113-unraid? Seems strange...

Hi, I have my repository/tag set to 11notes/unifi:8.1.113-unraid Noticed this morning that the container said it had an update available. Did the update and the version (specified in the container) updated to 8.1.127 yet my repository/tagtag is still set to 11notes/unifi:8.1.113-unraid Is this normal? Edit: everything seems to be working fine after the update

Update went through smoothly. Thanks to the Unraid team

Just moved to this docker from the unsupported one. Thanks it seems to have worked without any issues. I did change port 1900 to 1901 to match my old docker settings. Also had to backup from v7.3.83 and do the restore on v7.5.187 which seemed to work fine as well.

Sorry my bad... I was trying to access the gui through NPM and that was stopped when I stopped the array... I had to use the IP.

Hi, I was about to do the upgrade to 6.12.6 but when trying to stop the array (running 6.12.4) it got stuck on "Stopping services"... now I can't get into the GUI but I have managed to get into the shell and download diagnostics which are attached. Is anyone able to help me figure out why it's stuck? I was going to reboot the server using powerdown -r but can wait. server-unraid-diagnostics-20240125-0839.zip

Thanks again @yogy - seems to have worked... I'll test and post back if I pick up any issues. I have just set WEBSOCKET_ENABLED to false and removed the port mapping for 3012

Perfect thanks @yogy that worked

@yogy does the docker variable (ADMIN_TOKEN) also need to be updated?

Hi, Running the latest version of Vaultwarden and I enabled the push notifications as well. I am also using Nginx Proxy Manager to expose it (with just https and nothing on 3012) I can see from the logs that I am getting these errors: [2023-11-20 12:42:12.277][rocket::server][ERROR] Upgraded websocket I/O handler failed: WebSocket protocol error: Sending after closing is not allowed Is there something I need to configure on NPM or Vaultwarden?

Hi all, Hoping someone can help me with a weird issue. I use Ombi with Jellyfin users that access with their Jellyfin accounts. Recently I have had an issue with Jellyfin users who can't authenticate: fail: Ombi.Api.Api[1000] StatusCode: Unauthorized, Reason: Unauthorized, RequestUri: https://jf.(domain)/users/authenticatebyname fail: Microsoft.AspNetCore.Identity.UserManager[0] Jellyfin Login Failed Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: E. Path '', line 0, position 0. at Newtonsoft.Json.JsonTextReader.ParseValue() at Newtonsoft.Json.JsonReader.ReadForType(JsonContract contract, Boolean hasConverter) at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent) at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType) at Newtonsoft.Json.JsonSerializer.Deserialize(JsonReader reader, Type objectType) at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings) at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings) at Ombi.Api.Api.Request[T](Request request, CancellationToken cancellationToken) at Ombi.Api.Jellyfin.JellyfinApi.LogIn(String username, String password, String apiKey, String baseUri) in /home/runner/work/Ombi/Ombi/src/Ombi.Api.Jellyfin/JellyfinApi.cs:line 74 at Ombi.Core.Authentication.OmbiUserManager.CheckJellyfinPasswordAsync(OmbiUser user, String password) in /home/runner/work/Ombi/Ombi/src/Ombi.Core/Authentication/OmbiUserManager.cs:line 232 warn: Ombi.Controllers.V1.TokenController[0] Local users work fine. Any ideas what the issue could be? The username and password is definitely correct.

@KluthR I just wanted to say thanks for your hard work on supporting the old plugin for so long and this awesome new one. Appreciate it!

SOLVED - seems tdarr_node is linked to the same logs folder. Hi, I'm picking up an error when backing up tdarr - anyone have any idea of what could be causing the file to get modified while the docker is stopped? here are the logs [03.10.2023 02:40:49][ℹ️][tdarr] Stopping tdarr... done! (took 4 seconds) [03.10.2023 02:40:53][ℹ️][tdarr] Should NOT backup external volumes, sanitizing them... [03.10.2023 02:40:53][ℹ️][tdarr] Calculated volumes to back up: /mnt/user/appdata/tdarr/logs, /mnt/user/appdata/tdarr/server, /mnt/user/appdata/tdarr/configs [03.10.2023 02:40:53][ℹ️][tdarr] Backing up tdarr... [03.10.2023 02:41:22][ℹ️][tdarr] Backup created without issues [03.10.2023 02:41:22][ℹ️][tdarr] Verifying backup... [03.10.2023 02:41:58][❌][tdarr] tar verification failed! Tar said: tar: Removing leading `/' from member names; mnt/user/appdata/tdarr/logs/Tdarr_Node_Log.txt: Mod time differs; mnt/user/appdata/tdarr/logs/Tdarr_Node_Log.txt: Size differs [03.10.2023 02:42:15][ℹ️][tdarr] Starting tdarr... (try #1) done!

Thanks @SimonF that worked!

Hi @SimonF Thanks for assisting with this. I also passed through a USB controller to the VM... would the upgrade to 6.12.4 impacted the bind? I see this under system devices and it's not ticked to bind selected at boot for my VM to use it (but my GPU entries are ticked): [1022:145f] 0b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 xHCI Compliant Host Controller Bus 005 Device 001 Port 5-0 ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001 Port 6-0 ID 1d6b:0003 Linux Foundation 3.0 root hub Would ticking the entry and binding selected at boot fix my issue and get me back to where I was?

Hi, I am getting the following error when I reboot my server: Event: VM Autostart disabled Subject: vfio-pci-errors Description: VM Autostart disabled due to vfio-bind error Importance: alert Please review /var/log/vfio-pci-errors The only log entry in that file is Error: Device 0000:0a:00.3 does not exist, unable to bind device Both the VMs that I have start up fine manually (1 has a GPU passed through to it)... could it be an issue with the GPU? [10de:1b82] 03:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] (rev a1) [10de:10f0] 03:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1) I have attached the diagnostic file. Thanks in advance for the assistance! server-unraid-diagnostics-20231001-2053.zip

Upgraded from 6.11.5 to 6.12.4 - was pretty seamless. Just had to reinstall 2 plugins (gpustat and NUT) and also change docker to use ipvlan as it picked up a few traces. Thanks to all the devs for their hard work. Appreciated!

Sure thanks - I don't mind sharing it then (took a quick look at the file). I've filtered out just for that time period. syslog.log