Jump to content

uCoreX

Members
  • Posts

    94
  • Joined

Everything posted by uCoreX

  1. Hi, 1. Done that couple of times 2. Tested with: Microsoft Edge, Firefox, Google Chrome, LibreWolf and Brave. 3. Tested from 3 different computers also.
  2. Hi, My backup unraid server is a clean install with everything default. And i'm using pfsense firewall. And I also have played around with: Settings > Network Settings > eth0 > Enable Bridging = NO/YES Docker settings, nSettings > Docker > Host access to custom networks = Enabled/Disable On my primary server running v.6.12.3 never had MACVLAN crashes. Tested to upgrade to 6.12.4. Then this problem start. That's why I'm testing my backup server instead, and have the same problem. Two very different hardware here. From my Primary unRaid Server: (6.12.3)
  3. Hi, Any news around this issue? I just tested to upgrade my unraid backup server. Same problem, almost 20 sec to access the dashboard tab. Here is my test server: unRaid Basic: HP ProLiant ML350p G8 | 128GB DDR3 ECC | 2 x Intel Xeon E5-2697v2 No plugins or containers are installed on this server. I have removed all, well the only plugin I have installed now is "Community Applications"
  4. After updating to version 2023.10.29 I start receiving this error: Oct 29 22:38:36 Tower nginx: 2023/10/29 22:38:36 [error] 17053#17053: *10094889 open() "/usr/local/emhttp/plugins/gpustat/images/Threadfin.png" failed (2: No such file or directory) while sending to client, client: 10.15.10.20, server: , request: "GET /plugins/gpustat/images/Threadfin.png HTTP/2.0", host: "10.15.20.100:5001", referrer: "https://10.15.20.100:5001/Dashboard"
  5. Make sure you have booth GPU selected in the GPU Statistics. In the Dashboard:
  6. Update 2: I did a clean install of 6.12.4 and just copied my plus.key and network.cfg from my backup. The GUI felt much faster, but not so fast as 6.12.3. After I did some changing in the network settings: Disable bridging, using bonding since I have multiple interfaces (eth0 and eth1) Settings > Network Settings > eth0 > Enable Bonding = Yes Settings > Network Settings > eth0 > Enable Bridging = No Edit VM Manager to use vhost0. Docker settings, nSettings > Docker > Host access to custom networks = Enabled Saved the settings, and back to slow gui again. Take much longer - around 15 seconds to open the Dashboard So I go back to 6.12.3. That one was working great. With Bridging enable and use of br0. Never seen any call traces because of this. Update 1: I tried again today to upgrade to 6.12.4. Sorry to say, same problem again. Takes 7 - 11 seconds to open the Dashboard. Can't see anything in the: htop at that time. Only did an inspection in the browser. This time I disable autostart of Docker and VM. Only the array was started. I don't see any special errors in the syslog either. Update 3: Revert back to 6.12.3. Here is the dashboard.
  7. I'm gonna give 6.12.4 another shoot later. First time I run into some problems, i have posted in the bug reports. So I had to revert back to 6.12.3.
  8. This going to be a problem for me. I'm running VM's on my unraid with Network Source: br0. So I can give every VM a static ip address. So I can RDP to my Windows 10 VM. So how do I gonna resolve this with bridging disable? My win 10 vm:
  9. Hi, Any news around my issue, Did you found something wrong in my diagnostics?
  10. Hi, after upgrading from 6.12.3 to 6.12.4 my Webui has been very slow. Special on docker tab and dashboard. Takes almost 12 sec before the page is visible. I can see my CPU are wokring MUCH more when i try to open DOCKER tab or the Dashboard. Never seen a behaver like this before. I tried to stop Array, but Dashboard is still slow 12 seconds to open it, normally it tooks 2 seconds. Tried to remove some plugins, but still the same EDIT 1: After removing more plugins and multiple reboots. The issue is till there. EDIT 2: I decide to revert back to 6.12.3. And guess what, it working normally again, fast like it always was So can someone please explain me why I had this kind of issue with 6.12.4 ? EDIT 3: Tested v.6.12.5 RC 1 and the latest version released yesterday, v.6.12.5. It's still the same. Adding the diagnostics from my backup server (Galactica)
  11. I took the risk and updated now,. Seems to my everything went smoothly. Only one thing i noticed, the DOCKER page took much longer time to open, hmmm That's probably why? It took 12 sec top open the DOCKER tap.
  12. Hi, Is this update gonna make some problems for me when I'm running like this? I do have ab firewall that don't like when I use IPVLAN... when you have over 30 containers and all of the came up with same MAC address with different IP, I had problems to access my containers. That's why I use MACVLAN. Never hade any CALL TRACES error before. Almost all my containers are using br0 network.
  13. Thank you very much for this update. Everything seems to work perfectly. I used to get this message after upgrade to v. 6.12.X But it seems to work after an reboot then.
  14. I have the same problem, I have an HP Proliant ML 350p G8
  15. Hi, Anyone still using ML350p G8 with Unraid? Is it working? I've got my hands on an ML350p G8 with 2 x E2697v2 with 128GB ECC memory with P420i controller with HBA mode enabled.
  16. Hi, I'm trying to figure out how to put the right numbers in the driver.parameter.runtimecal: = AAA,100,BBB,50 I have PowerWalker UPS VFI1500 CGPF1 https://powerwalker.com/product/10122109/ What is the right value for me, on AAA and BBB ?
  17. Can't update to newest version. When i go to APPS. But nothing in PLUGINS. Still stuck on version 2023.02.17
×
×
  • Create New...