Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

dicry

Members
  • Joined

  • Last visited

  1. Have you successfully switched to Stable Diffusion with Flux support?
  2. sent 613 bytes received 12 bytes 1,250.00 bytes/sec total size is 1,012,797 speedup is 1,620.48 removing folder /config/02-sd-webui/webui/embeddings and create symlink moving folder /config/02-sd-webui/webui/models/ESRGAN to /config/models/upscale sending incremental file list sent 38 bytes received 12 bytes 100.00 bytes/sec total size is 0 speedup is 0.00 removing folder /config/02-sd-webui/webui/models/ESRGAN and create symlink moving folder /config/02-sd-webui/webui/models/BLIP to /config/models/blip sending incremental file list According to the log output here, it seems that there is a problem: ESRGAN folder, it seems that there is a connection error here At the same time, how to switch to the branch https://github.com/lllyasviel/stable-diffusion-webui-forge.git? I need to use the plugin https://github.com/lllyasviel/sd-forge-layerdiffuse
  3. Thank you very much, it displays perfectly now. I get an immediate response from you every time. grateful! ! ! This is the best community of developers I've come across since using unraid! 🤝🤝🤝
  4. Now I can see UPS LOAD, but it is still incomplete.
  5. This is additional information
  6. According to your instructions, it is now running normally, but I cannot see: NOMINAL POWER UPS LOAD UPS LOAD POWER FACTOR information. At the same time, according to the web page you provided, V3 can also run normally. But currently only the SNMP method is most suitable for my working style. Is there any way to improve it?
  7. May 22 13:38:49 Tower rc.nut: Writing NUT configuration... May 22 13:39:27 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update May 22 13:41:04 Tower rc.nut: Updating permissions for NUT... May 22 13:41:04 Tower rc.nut: Checking if the NUT Runtime Statistics Module should be enabled... May 22 13:41:04 Tower rc.nut: Enabling the NUT Runtime Statistics Module... May 22 13:41:05 Tower rc.nut: Stopping the NUT services... May 22 13:41:07 Tower rc.nut: Can't open /var/run/nut/snmp-ups-ups.pid: No such file or directory May 22 13:41:07 Tower rc.nut: Can't open /var/run/nut/snmp-ups-192.168.50.199.pid either: No such file or directory May 22 13:41:07 Tower rc.nut: Network UPS Tools - UPS driver controller 2.8.2 May 22 13:42:56 Tower ool www[1692]: /usr/local/emhttp/plugins/nut-dw/scripts/start May 22 13:42:56 Tower rc.nut: WARNING: NUT was user-configured to disable power management for all USB devices. May 22 13:42:56 Tower rc.nut: WARNING: NUT is now forcing all USB devices to permanent [on] power state as requested... May 22 13:42:57 Tower rc.nut: Writing NUT configuration... May 22 13:43:28 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update May 22 13:45:12 Tower rc.nut: Updating permissions for NUT... May 22 13:45:12 Tower rc.nut: Checking if the NUT Runtime Statistics Module should be enabled... May 22 13:45:12 Tower rc.nut: Enabling the NUT Runtime Statistics Module... May 22 13:45:58 Tower rc.nut: Startup timer elapsed, continuing... May 22 13:45:58 Tower rc.nut: Driver [ups] PID 26668 initially exceeded maxstartdelay and is still starting May 22 13:45:58 Tower rc.nut: Network UPS Tools - UPS driver controller 2.8.2 May 22 13:49:14 Tower rc.nut: No supported device detected at [ups] (host 192.168.50.199) May 22 13:49:14 Tower rc.nut: Network UPS Tools - Generic SNMP UPS driver 1.31 (2.8.2) May 22 13:57:59 Tower ool www[15025]: /usr/local/emhttp/plugins/nut-dw/scripts/stop May 22 13:58:00 Tower rc.nut: Writing NUT configuration... May 22 13:58:30 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update May 22 14:00:17 Tower rc.nut: Updating permissions for NUT... May 22 14:00:17 Tower rc.nut: Checking if the NUT Runtime Statistics Module should be enabled... May 22 14:00:17 Tower rc.nut: Enabling the NUT Runtime Statistics Module... May 22 14:00:18 Tower rc.nut: Stopping the NUT services... May 22 14:00:20 Tower rc.nut: Can't open /var/run/nut/snmp-ups-ups.pid: No such file or directory May 22 14:00:20 Tower rc.nut: Can't open /var/run/nut/snmp-ups-192.168.50.199.pid either: No such file or directory May 22 14:00:20 Tower rc.nut: Network UPS Tools - UPS driver controller 2.8.2 May 22 14:18:45 Tower ool www[5571]: /usr/local/emhttp/plugins/nut-dw/scripts/start May 22 14:18:45 Tower rc.nut: WARNING: NUT was user-configured to disable power management for all USB devices. May 22 14:18:45 Tower rc.nut: WARNING: NUT is now forcing all USB devices to permanent [on] power state as requested... May 22 14:18:46 Tower rc.nut: Writing NUT configuration... May 22 14:19:32 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update May 22 14:19:47 Tower dhcpcd[2490]: bond1: failed to renew DHCP, rebinding May 22 14:19:47 Tower dhcpcd[2490]: bond1: leased 192.168.50.109 for 7200 seconds May 22 14:20:32 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update May 22 14:21:01 Tower rc.nut: Updating permissions for NUT... May 22 14:21:01 Tower rc.nut: Checking if the NUT Runtime Statistics Module should be enabled... May 22 14:21:01 Tower rc.nut: Enabling the NUT Runtime Statistics Module... May 22 14:21:47 Tower rc.nut: Startup timer elapsed, continuing... May 22 14:21:47 Tower rc.nut: Driver [ups] PID 27409 initially exceeded maxstartdelay and is still starting May 22 14:21:47 Tower rc.nut: Network UPS Tools - UPS driver controller 2.8.2 May 22 14:25:02 Tower rc.nut: No supported device detected at [ups] (host 192.168.50.199) May 22 14:25:02 Tower rc.nut: Network UPS Tools - Generic SNMP UPS driver 1.31 (2.8.2) May 22 14:39:25 Tower ool www[22665]: /usr/local/emhttp/plugins/nut-dw/scripts/start May 22 14:39:25 Tower rc.nut: WARNING: NUT was user-configured to disable power management for all USB devices. May 22 14:39:25 Tower rc.nut: WARNING: NUT is now forcing all USB devices to permanent [on] power state as requested... May 22 14:39:26 Tower rc.nut: Writing NUT configuration... May 22 14:39:34 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update May 22 14:41:34 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update May 22 14:41:40 Tower rc.nut: Updating permissions for NUT... May 22 14:41:40 Tower rc.nut: Checking if the NUT Runtime Statistics Module should be enabled... May 22 14:41:40 Tower rc.nut: Enabling the NUT Runtime Statistics Module... May 22 14:42:26 Tower rc.nut: Startup timer elapsed, continuing... May 22 14:42:26 Tower rc.nut: Driver [ups] PID 1311 initially exceeded maxstartdelay and is still starting May 22 14:42:26 Tower rc.nut: Network UPS Tools - UPS driver controller 2.8.2 May 22 14:45:41 Tower rc.nut: No supported device detected at [ups] (host 192.168.50.199) May 22 14:45:41 Tower rc.nut: Network UPS Tools - Generic SNMP UPS driver 1.31 (2.8.2) May 22 14:46:27 Tower ool www[27261]: /usr/local/emhttp/plugins/nut-dw/scripts/stop May 22 14:46:28 Tower rc.nut: Writing NUT configuration... May 22 14:46:34 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update May 22 14:48:46 Tower rc.nut: Updating permissions for NUT... May 22 14:48:46 Tower rc.nut: Checking if the NUT Runtime Statistics Module should be enabled... May 22 14:48:46 Tower rc.nut: Enabling the NUT Runtime Statistics Module... May 22 14:48:47 Tower rc.nut: Stopping the NUT services... May 22 14:48:49 Tower rc.nut: Can't open /var/run/nut/snmp-ups-ups.pid: No such file or directory May 22 14:48:49 Tower rc.nut: Can't open /var/run/nut/snmp-ups-192.168.50.199:161.pid either: No such file or directory May 22 14:48:49 Tower rc.nut: Network UPS Tools - UPS driver controller 2.8.2 May 22 14:49:01 Tower ool www[14930]: /usr/local/emhttp/plugins/nut-dw/scripts/start May 22 14:49:01 Tower rc.nut: WARNING: NUT was user-configured to disable power management for all USB devices. May 22 14:49:01 Tower rc.nut: WARNING: NUT is now forcing all USB devices to permanent [on] power state as requested... May 22 14:49:02 Tower rc.nut: Writing NUT configuration... May 22 14:49:35 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update May 22 14:51:15 Tower rc.nut: Updating permissions for NUT... May 22 14:51:15 Tower rc.nut: Checking if the NUT Runtime Statistics Module should be enabled... May 22 14:51:15 Tower rc.nut: Enabling the NUT Runtime Statistics Module... May 22 14:52:01 Tower rc.nut: Startup timer elapsed, continuing... May 22 14:52:01 Tower rc.nut: Driver [ups] PID 31670 initially exceeded maxstartdelay and is still starting May 22 14:52:01 Tower rc.nut: Network UPS Tools - UPS driver controller 2.8.2 May 22 14:55:17 Tower rc.nut: No supported device detected at [ups] (host 192.168.50.199:161) May 22 14:55:17 Tower rc.nut: Network UPS Tools - Generic SNMP UPS driver 1.31 (2.8.2) This is a log, and the MIB file is attached for your reference. I am currently using 192.168.50.199:161 but still unable to connect. UPS-RFC1628-MIB.zip
  8. The SNMP address in the image is 192.168.50.199, and SNMP has been configured. However, I can't enable it in Unraid. I suspect it's due to incorrect settings, but I haven't been able to find the reason. At the same time, I found in the Hardware Compatibility List that the Huawei UPS5000-E supports the SNMP-UPS driver, while my UPS2000-A series only supports the Huawei-UPS2000 driver.
  9. Thanks!!!
  10. Thank you for your help, it is now working correctly. I have another question: I am currently using a 2303 to USB adapter, but I have an additional SNMP intelligent card. However, according to the Hardware Compatibility List, it seems that the UPS2000-A series does not support the SNMP intelligent card. I am not sure if it will still work properly if I switch to the SNMP card.
  11. I am using the Huawei UPS2000-A-2KTTS | 2KVA / 1600W with a built-in battery tower UPS, but when I use the NUT Device Scanner, it shows the following message: NO DEVICES FOUND Please visit the 'Driver Guide' and manually choose the recommended driver for your UPS. In case of persisting problems please try another physical port, cable or the 'Support Thread'. However, I checked the compatibility on the NUT Hardware Compatibility List and found that my UPS is supported. I am not sure what is wrong or if my settings are incorrect. I would appreciate any help with this issue.
  12. Using TCMalloc: libtcmalloc_minimal.so.4 Python 3.11.6 | packaged by conda-forge | (main, Oct 3 2023, 10:40:35) [GCC 12.3.0] Version: v1.6.0-2-g4afaaf8a Commit hash: 4afaaf8a020c1df457bcf7250cb1c7f609699fa7 Installing open_clip WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Hit:1 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease Reading package lists... Building dependency tree... Reading state information... 11 packages can be upgraded. Run 'apt list --upgradable' to see them. WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
  13. Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: shared memory zone "memstore" was locked by 11283 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: worker process 11284 exited on signal 6 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: shared memory zone "memstore" was locked by 11284 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: worker process 11292 exited on signal 6 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: shared memory zone "memstore" was locked by 11292 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: worker process 11319 exited on signal 6 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: shared memory zone "memstore" was locked by 11319 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: worker process 11334 exited on signal 6 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: shared memory zone "memstore" was locked by 11334 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: worker process 11364 exited on signal 6 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: shared memory zone "memstore" was locked by 11364 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: worker process 11369 exited on signal 6 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: shared memory zone "memstore" was locked by 11369 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: worker process 11402 exited on signal 6 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: shared memory zone "memstore" was locked by 11402 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: worker process 11422 exited on signal 6 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: shared memory zone "memstore" was locked by 11422 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: worker process 11447 exited on signal 6 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: shared memory zone "memstore" was locked by 11447 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: worker process 11461 exited on signal 6 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: shared memory zone "memstore" was locked by 11461 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: worker process 11479 exited on signal 6 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: shared memory zone "memstore" was locked by 11479 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: worker process 11513 exited on signal 6 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: shared memory zone "memstore" was locked by 11513 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: worker process 11543 exited on signal 6 Aug 5 19:31:47 Tower nginx: 2023/08/05 19:31:47 [alert] 10996#10996: shared memory zone "memstore" was locked by 11543 Aug 6 10:41:18 Tower nginx: 2023/08/06 10:41:18 [alert] 30230#30230: *7160 open socket #26 left in connection 14 Aug 6 10:41:18 Tower nginx: 2023/08/06 10:41:18 [alert] 30230#30230: *7162 open socket #27 left in connection 15 Aug 6 10:41:18 Tower nginx: 2023/08/06 10:41:18 [alert] 30230#30230: aborting Aug 6 10:42:57 Tower kernel: veth74ae1e5: renamed from eth0 Aug 6 10:44:18 Tower nginx: 2023/08/06 10:44:18 [alert] 7954#7954: *8891 open socket #26 left in connection 12 Aug 6 10:44:18 Tower nginx: 2023/08/06 10:44:18 [alert] 7954#7954: aborting Aug 6 10:47:18 Tower nginx: 2023/08/06 10:47:18 [alert] 19847#19847: *10564 open socket #30 left in connection 10 Aug 6 10:47:18 Tower nginx: 2023/08/06 10:47:18 [alert] 19847#19847: aborting Aug 6 10:50:18 Tower nginx: 2023/08/06 10:50:18 [alert] 32061#32061: *12349 open socket #27 left in connection 24 Aug 6 10:50:18 Tower nginx: 2023/08/06 10:50:18 [alert] 32061#32061: *12343 open socket #4 left in connection 27 Aug 6 10:50:18 Tower nginx: 2023/08/06 10:50:18 [alert] 32061#32061: aborting Aug 6 10:51:25 Tower kernel: eth0: renamed from vethc244b4f Aug 6 10:52:21 Tower kernel: kvm: already loaded vendor module 'kvm_amd' Aug 6 10:53:18 Tower nginx: 2023/08/06 10:53:18 [alert] 7824#7824: *12937 open socket #17 left in connection 13 Aug 6 10:53:18 Tower nginx: 2023/08/06 10:53:18 [alert] 7824#7824: *12939 open socket #26 left in connection 14 Aug 6 10:53:18 Tower nginx: 2023/08/06 10:53:18 [alert] 7824#7824: aborting
  14. This is the result of the output 00:1c.5 PCI bridge: Intel Corporation Comet Lake PCIe Port #6 (rev f0)
  15. 00:1c.5 PCI bridge: Intel Corporation Comet Lake PCIe Port #6 (rev f0) This seems to be an onboard device, and I don't know how to determine which device it is?

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.