TerraMaster Forum

Posted: **08 Sep 2026, 19:10**

UPS WalleCube W150

lsusb

Posted: **09 Sep 2026, 08:03**

What specific version of TOS are you currently running?

To help us analyze the communication issue with your WalleCube W150 device, please keep the UPS connected, open the Terminal app on your TOS desktop, execute the following commands in order, and share the outputs with us:

Code: Select all

journalctl -u [email protected]
journalctl -u nut-server.service
journalctl -u nut-monitor.service

Posted: **09 Sep 2026, 15:35**

version of TOS: 7.0.1169

@TNAS:/# journalctl -u [email protected]
-- No entries --

@TNAS:/# journalctl -u nut-server.service
Sep 08 14:17:11 TNAS systemd[1]: Starting Network UPS Tools - power devices information server...
Sep 08 14:17:11 TNAS nut-server[29980]: Limit Soft Limit Hard Limit Units
Sep 08 14:17:11 TNAS nut-server[29980]: Max open files 1048576 1048576 files
Sep 08 14:17:11 TNAS systemd[1]: Started Network UPS Tools - power devices information server.
Sep 08 14:17:11 TNAS nut-server[29979]: Network UPS Tools upsd 2.8.3 release
Sep 08 14:17:11 TNAS nut-server[29979]: WARNING: /etc/nut/upsd.conf is world readable (hope you don't have passwords there)
Sep 08 14:17:11 TNAS upsd[29979]: WARNING: /etc/nut/upsd.conf is world readable (hope you don't have passwords there)
Sep 08 14:17:11 TNAS nut-server[29979]: listening on localhost port 3493
Sep 08 14:17:11 TNAS upsd[29979]: listening on localhost port 3493
Sep 08 14:17:11 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 14:17:11 TNAS nut-server[29979]: Found 1 UPS defined in ups.conf
Sep 08 14:17:11 TNAS upsd[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 14:17:11 TNAS upsd[29979]: Found 1 UPS defined in ups.conf
Sep 08 14:17:11 TNAS nut-server[29979]: WARNING: /etc/nut/upsd.users is world readable (hope you don't have passwords there)
Sep 08 14:17:11 TNAS upsd[29979]: WARNING: /etc/nut/upsd.users is world readable (hope you don't have passwords there)
Sep 08 14:17:11 TNAS nut-server[29979]: Running as foreground process, not saving a PID file
Sep 08 14:17:11 TNAS nut-server[29979]: upsnotify: notify about state NOTIFY_STATE_READY_WITH_PID with libsystemd: was requested, but not running as a service unit now, will not spam more about it
Sep 08 14:17:11 TNAS nut-server[29979]: upsnotify: failed to notify about state NOTIFY_STATE_READY_WITH_PID: no notification tech defined, will not spam more about it
Sep 08 14:17:11 TNAS nut-server[29979]: upsnotify: logged the systemd watchdog situation once, will not spam more about it
Sep 08 14:17:11 TNAS upsd[29979]: Running as foreground process, not saving a PID file
Sep 08 14:17:11 TNAS upsd[29979]: upsnotify: notify about state NOTIFY_STATE_READY_WITH_PID with libsystemd: was requested, but not running as a service unit now, will not spam more about it
Sep 08 14:17:11 TNAS upsd[29979]: upsnotify: failed to notify about state NOTIFY_STATE_READY_WITH_PID: no notification tech defined, will not spam more about it
Sep 08 14:17:11 TNAS upsd[29979]: upsnotify: logged the systemd watchdog situation once, will not spam more about it
Sep 08 14:17:30 TNAS systemd[1]: Reloading Network UPS Tools - power devices information server...
Sep 08 14:17:30 TNAS nut-server[30043]: Network UPS Tools upsd 2.8.3 release
Sep 08 14:17:30 TNAS nut-server[29979]: mainloop: Interrupted system call
Sep 08 14:17:30 TNAS nut-server[29979]: SIGHUP: reloading configuration
Sep 08 14:17:30 TNAS nut-server[29979]: WARNING: /etc/nut/upsd.conf is world readable (hope you don't have passwords there)
Sep 08 14:17:30 TNAS nut-server[29979]: Applying debug level 0 from original command line arguments
Sep 08 14:17:30 TNAS nut-server[29979]: WARNING: /etc/nut/upsd.users is world readable (hope you don't have passwords there)
Sep 08 14:17:30 TNAS upsd[29979]: mainloop: Interrupted system call
Sep 08 14:17:30 TNAS systemd[1]: Reloaded Network UPS Tools - power devices information server.
Sep 08 14:17:30 TNAS upsd[29979]: SIGHUP: reloading configuration
Sep 08 14:17:30 TNAS upsd[29979]: WARNING: /etc/nut/upsd.conf is world readable (hope you don't have passwords there)
Sep 08 14:17:30 TNAS upsd[29979]: Applying debug level 0 from original command line arguments
Sep 08 14:17:30 TNAS upsd[29979]: WARNING: /etc/nut/upsd.users is world readable (hope you don't have passwords there)
Sep 08 14:22:12 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 14:22:12 TNAS upsd[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 14:27:13 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 14:27:13 TNAS upsd[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 14:32:13 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 14:32:13 TNAS upsd[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 14:37:13 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 14:37:13 TNAS upsd[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 14:42:13 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 14:42:13 TNAS upsd[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 14:47:14 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 14:47:14 TNAS upsd[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 14:52:14 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 14:52:14 TNAS upsd[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 14:57:14 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory

Sep 08 16:32:20 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 16:32:20 TNAS upsd[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 16:37:20 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 16:37:20 TNAS upsd[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 16:42:20 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 16:42:20 TNAS upsd[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 16:47:20 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 16:47:20 TNAS upsd[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 16:52:21 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 16:52:21 TNAS upsd[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 16:57:21 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 16:57:21 TNAS upsd[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 17:02:21 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 17:02:21 TNAS upsd[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 17:07:22 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 17:07:22 TNAS upsd[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 08 17:12:22 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 09 09:33:17 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 09 09:33:17 TNAS upsd[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 09 09:38:17 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 09 09:38:17 TNAS upsd[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 09 09:43:18 TNAS nut-server[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory
Sep 09 09:43:18 TNAS upsd[29979]: Can't connect to UPS [ups] (/run/nut/blazer_usb-ups): No such file or directory

@TNAS:/# journalctl -u nut-monitor.service
-- No entries --

Posted: **09 Sep 2026, 16:26**

Judging from the logs, there may be some issues with the current NUT service.
Please run the following two commands to check the status of the NUT service:

Code: Select all

systemctl status nut-server.service

Code: Select all

systemctl status nut-monitor.service

You can also use the following two commands to restart the NUT service:

Code: Select all

systemctl restart nut-server.service

Code: Select all

systemctl restart nut-monitor.service

Posted: **09 Sep 2026, 16:50**

systemctl status nut-server.service

nut-server.service - Network UPS Tools - power devices information server
Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2026-09-09 12:38:39 +04; 7min ago
Docs: man:upsd(8)
https://www.networkupstools.org/histori ... /upsd.html
man:ups.conf(5)
https://www.networkupstools.org/histori ... .conf.html
man:upsd.conf(5)
https://www.networkupstools.org/histori ... .conf.html
man:upsd.users(5)
https://www.networkupstools.org/histori ... users.html
man:nut.conf(5)
https://www.networkupstools.org/histori ... .conf.html
Process: 293254 ExecStartPre=/usr/bin/systemd-tmpfiles --create /usr/lib/tmpfiles.d/nut-common-tmpfiles.conf (code=exited, status=0/SUCCESS)
Process: 293255 ExecStart=/usr/sbin/upsd -F (code=exited, status=1/FAILURE)
Process: 293256 ExecStartPost=/bin/grep -E Units|Max open files /proc/${MAINPID}/limits (code=exited, status=0/SUCCESS)
Main PID: 293255 (code=exited, status=1/FAILURE)
CPU: 9ms

Sep 09 12:38:39 TNAS systemd[1]: nut-server.service: Scheduled restart job, restart counter is at 5.
Sep 09 12:38:39 TNAS systemd[1]: Stopped Network UPS Tools - power devices information server.
Sep 09 12:38:39 TNAS systemd[1]: nut-server.service: Start request repeated too quickly.
Sep 09 12:38:39 TNAS systemd[1]: nut-server.service: Failed with result 'exit-code'.
Sep 09 12:38:39 TNAS systemd[1]: Failed to start Network UPS Tools - power devices information server.

systemctl status nut-monitor.service
nut-server.service - Network UPS Tools - power devices information server
Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2026-09-09 12:38:39 +04; 7min ago
Docs: man:upsd(8)
https://www.networkupstools.org/histori ... /upsd.html
man:ups.conf(5)
https://www.networkupstools.org/histori ... .conf.html
man:upsd.conf(5)
https://www.networkupstools.org/histori ... .conf.html
man:upsd.users(5)
https://www.networkupstools.org/histori ... users.html
man:nut.conf(5)
https://www.networkupstools.org/histori ... .conf.html
Process: 293254 ExecStartPre=/usr/bin/systemd-tmpfiles --create /usr/lib/tmpfiles.d/nut-common-tmpfiles.conf (code=exited, status=0/SUCCESS)
Process: 293255 ExecStart=/usr/sbin/upsd -F (code=exited, status=1/FAILURE)
Process: 293256 ExecStartPost=/bin/grep -E Units|Max open files /proc/${MAINPID}/limits (code=exited, status=0/SUCCESS)
Main PID: 293255 (code=exited, status=1/FAILURE)
CPU: 9ms

Sep 09 12:38:39 TNAS systemd[1]: nut-server.service: Scheduled restart job, restart counter is at 5.
Sep 09 12:38:39 TNAS systemd[1]: Stopped Network UPS Tools - power devices information server.
Sep 09 12:38:39 TNAS systemd[1]: nut-server.service: Start request repeated too quickly.
Sep 09 12:38:39 TNAS systemd[1]: nut-server.service: Failed with result 'exit-code'.
Sep 09 12:38:39 TNAS systemd[1]: Failed to start Network UPS Tools - power devices information server.
MaxBoroda@TNAS:/# systemctl status nut-monitor.service
● nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller
Loaded: loaded (/lib/systemd/system/nut-monitor.service; disabled; vendor preset: enabled)
Active: active (running) since Wed 2026-09-09 12:07:54 +04; 41min ago
Docs: man:upsmon(8)
https://www.networkupstools.org/histori ... psmon.html
man:upsmon.conf(5)
https://www.networkupstools.org/histori ... .conf.html
man:nut.conf(5)
https://www.networkupstools.org/histori ... .conf.html
Main PID: 285865 (upsmon)
Tasks: 2 (limit: 8990)
Memory: 1.0M (available: 1.2G)
CPU: 984ms
CGroup: /system.slice/nut-monitor.service
├─285865 /lib/nut/upsmon -F
└─285866 /lib/nut/upsmon -F

Sep 09 12:48:40 TNAS nut-monitor[294895]:
Sep 09 12:48:40 TNAS nut-monitor[294895]: 2026-09-09 12:48:40.920 [INFO] main.go:83: -------------------------------------------------
Sep 09 12:48:40 TNAS nut-monitor[294895]: 2026/09/09 12:48:40 failed to read config file: unexpected end of JSON input
Sep 09 12:48:40 TNAS nut-monitor[294894]: exec_cmd(/usr/bin/upsctl nocomm) returned 1
Sep 09 12:48:40 TNAS upssched[294894]: exec_cmd(/usr/bin/upsctl nocomm) returned 1
Sep 09 12:48:40 TNAS nut-monitor[294893]: Warning: no shutdown command defined!
Sep 09 12:48:45 TNAS nut-monitor[285866]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused
Sep 09 12:48:50 TNAS nut-monitor[285866]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused
Sep 09 12:48:55 TNAS nut-monitor[285866]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused
Sep 09 12:49:00 TNAS nut-monitor[285866]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused

Posted: **09 Sep 2026, 17:49**

Through the terminal, the system detects the UPS. But when launching the settings via the graphical interface, the window with the blue cursor freezes again (the screenshot is in the very first post).

upsc myups@localhost

Init SSL without certificate database
battery.capacity: 100
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 5
battery.current: 0.001
battery.mfr.date: OPEN
battery.runtime: 7881
battery.temperature: 33.00
battery.type: LiFePO4
battery.voltage: 13.59
device.mfr: WalleCube
device.model: Smart UPS W150
device.serial: E4B323497450
device.type: ups
driver.debug: 0
driver.flag.allow_killpower: 0
driver.name: usbhid-ups
driver.parameter.interrupt_pipe_no_events_tolerance: -1
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 5
driver.parameter.port: auto
driver.parameter.synchronous: auto
driver.state: quiet
driver.version: 2.8.3
driver.version.data: openUPS HID 0.5
driver.version.internal: 0.62
driver.version.usb: libusb-1.0.25 (API: 0x01000109)
input.current: 1.988
input.voltage: 12.46
output.current: 2.017
output.voltage: 12.27
ups.mfr: WalleCube
ups.model: Smart UPS W150
ups.productid: d005
ups.serial: E4B323497450
ups.status: OL
ups.vendorid: 04d8

Posted: **09 Sep 2026, 17:57**

@TNAS:/# journalctl -u [email protected]
-- No entries --
@TNAS:/# journalctl -u nut-server.service
-- No entries --
@TNAS:/# journalctl -u nut-monitor.service
-- No entries --

Posted: **09 Sep 2026, 18:26**

We need to examine this issue remotely. Please visit the link below and contact our online support team to schedule a remote session:
https://salesiq.zohopublic.com/signatur ... 97d0be8892

Posted: **09 Sep 2026, 18:55**

Thnks

TerraMaster Forum

[Help] F2-424 freezes when accessing the UPS.

[Help] F2-424 freezes when accessing the UPS.

Re: [Help] F2-424 freezes when accessing the UPS.

Re: [Help] F2-424 freezes when accessing the UPS.

Re: [Help] F2-424 freezes when accessing the UPS.

Re: [Help] F2-424 freezes when accessing the UPS.

Re: [Help] F2-424 freezes when accessing the UPS.

Re: [Help] F2-424 freezes when accessing the UPS.

Re: [Help] F2-424 freezes when accessing the UPS.

Re: [Help] F2-424 freezes when accessing the UPS.