Quantcast
Channel: Rockstor Community Forum - Latest topics
Viewing all articles
Browse latest Browse all 1913

Failed to start NUT-UPS service due to a system error

$
0
0

@alexey wrote:

hi.

I have ippon smart power 1400.
Seems blazer_usb support it.

My settings are:
NUT Mode: standalone
NUT Driver : blazer_usb
UPS port: auto
NUT User: monuser
NUT Password: monpassword

After run I've got an error.
Failed to start NUT-UPS service due to a system error. Check the service is configured correctly via it's spanner icon.

Oct 02 11:41:21 server systemd[1]: Reloading.
Oct 02 11:41:21 server systemd[1]: Configuration file /usr/lib/systemd/system/auditd.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Oct 02 11:41:21 server systemd[1]: Configuration file /usr/lib/systemd/system/wpa_supplicant.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Oct 02 11:41:21 server systemd[1]: Starting Network UPS Tools - power device driver controller...
-- Subject: Unit nut-driver.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nut-driver.service has begun starting up.
Oct 02 11:41:21 server systemd-tmpfiles[11692]: Failed to open '/etc/tmpfiles.d/nut-run.conf', ignoring: No such file or directory
Oct 02 11:41:21 server upsdrvctl[11711]: Error: you must specify a port name in ups.conf. Try -h for help.
Oct 02 11:41:21 server upsdrvctl[11711]: Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)
Oct 02 11:41:21 server systemd[1]: nut-driver.service: control process exited, code=exited status=1
Oct 02 11:41:21 server upsdrvctl[11711]: Driver failed to start (exit status=1)
Oct 02 11:41:21 server upsdrvctl[11711]: Network UPS Tools - UPS driver controller 2.7.2
Oct 02 11:41:21 server systemd[1]: Failed to start Network UPS Tools - power device driver controller.
-- Subject: Unit nut-driver.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nut-driver.service has failed.
--
-- The result is failed.
Oct 02 11:41:21 server systemd[1]: Dependency failed for Network UPS Tools - power devices information server.
-- Subject: Unit nut-server.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nut-server.service has failed.
--
-- The result is dependency.
Oct 02 11:41:21 server systemd[1]: Job nut-server.service/start failed with result 'dependency'.
Oct 02 11:41:21 server systemd[1]: Unit nut-driver.service entered failed state.
Oct 02 11:41:21 server systemd[1]: nut-driver.service failed.

How can I fix it?

Error: you must specify a port name in ups.conf.

How to determine which usb port used by UPS?

[root@server ~]# lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 0781:5591 SanDisk Corp.
Bus 003 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 0451:8044 Texas Instruments, Inc.
Bus 002 Device 003: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial
Bus 001 Device 008: ID 0572:141a Conexant Systems (Rockwell), Inc.
Bus 001 Device 010: ID 0bda:58ba Realtek Semiconductor Corp.

Posts: 1

Participants: 1

Read full topic


Viewing all articles
Browse latest Browse all 1913

Trending Articles