TerraMaster Forum

Posted: **26 Jul 2025, 19:42**

You might also want to see this:

systemctl status [email protected]
● [email protected] - Network UPS Tools - device driver for ups
     Loaded: loaded (/lib/systemd/system/[email protected]; disabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Sat 2025-07-26 12:36:51 BST; 714ms ago
       Docs: man:upsdrvsvcctl(8)
             https://www.networkupstools.org/historic/v2.8.3/docs/man/upsdrvsvcctl.html
             man:ups.conf(5)
             https://www.networkupstools.org/historic/v2.8.3/docs/man/ups.conf.html
             man:nut.conf(5)
             https://www.networkupstools.org/historic/v2.8.3/docs/man/nut.conf.html
    Process: 38613 ExecStartPre=/usr/bin/systemd-tmpfiles --create /usr/lib/tmpfiles.d/nut-common-tmpfiles.conf (code=exited, status=0/SUCCESS)
    Process: 38614 ExecStart=/bin/sh -c NUTDEV="`/usr/libexec/nut-driver-enumerator.sh --get-device-for-service ups`" && [ -n "$NUTDEV" ] || { echo "FATAL: Could not find a NUT device section for service unit ups" >&2 ; exit 1 ; } ; exec /usr/sbin/upsdrvctl  start "$NUTDEV" (code=exited, status=1/FAILURE)
        CPU: 86ms

This is from client running 6.0.750. The result is slightly different on 6.0.694
The file that I think is causing the issue is now (in this version) showing up as /usr/libexec/nut-driver-enumerator.sh

{I have yet to work through this file to see the logic. The descriptive text is bad enough

)

Posted: **28 Jul 2025, 17:06**

Gremlin wrote: ↑26 Jul 2025, 19:42

1. About the error of /etc/init.d/ups-monitor:
Since the system uses the service management process, the /etc/init.d/ups-monitor script and ups-monitor.service have the same function, so /etc/init.d/ups-monitor is not needed and this error can be ignored.
2. About the error of [email protected]:
Under normal circumstances, when the client connects to the UPS using the TNAS UPS server, [email protected] will be closed and there will be no error message.
However, the testers have found that the [email protected] may be turned on after the client connects to the UPS using the TNAS UPS server and restarts the device. We will fix this problem.
If you have other operations that cause [email protected] to automatically turn on, you can contact us and we will verify and fix it.

Posted: **28 Jul 2025, 19:10**

TMlinda wrote: ↑28 Jul 2025, 17:06

Thank you. I live in hope, but no great expectation.

Posted: **14 Aug 2025, 15:45**

I have the same entries in the log.

And would like to know if the compatibility list for UPSes is actively maintained and new devices added.

My APC UPS is not supported, but seems to be a really standard APC UPS. So why wouldn't it be supported. Competitor Synology has a much longer list.

Posted: **14 Aug 2025, 17:21**

Google "hid ups driver for linux" for some clarity. (perhaps .....)

Posted: **14 Aug 2025, 18:20**

We will continue to test new UPS units and update our compatibility list.

Posted: **14 Aug 2025, 18:27**

It has to be thought that if we had a clean linux install and a clean NUT install that hadn't been messed with by Terra-master, none of this would really be necessary. The NUT compatibility list should be sufficient.

TerraMaster Forum

Network UPS Tools (NUT) Failures continue

Re: Network UPS Tools (NUT) Failures continue

Re: Network UPS Tools (NUT) Failures continue

Re: Network UPS Tools (NUT) Failures continue

Re: Network UPS Tools (NUT) Failures continue

Re: Network UPS Tools (NUT) Failures continue

Re: Network UPS Tools (NUT) Failures continue

Re: Network UPS Tools (NUT) Failures continue