search

hassio-addons / addon-nut

Network UPS Tools - Home Assistant Community Add-ons
https://addons.community
MIT License
188 stars 36 forks source link

Addon Fails to Start: /etc/cont-init.d/nut.sh exited 1 #359

Closed daelsc closed 4 months ago

daelsc commented 5 months ago

NUT-addon fails to start. See copypasta from my logs.

System Details: HAOS x86-64 VM 2x APC Smart-UPS X 3000 via SNMPv1

Add-on: Network UPS Tools Manage battery backup (UPS) devices

Add-on version: 0.13.0 You are running the latest version of this add-on. System: Home Assistant OS 12.3 (amd64 / qemux86-64) Home Assistant Core: 2024.5.3 Home Assistant Supervisor: 2024.05.1

Please, share the above information when looking for help or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service base-addon-banner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service base-addon-timezone: starting s6-rc: info: service base-addon-log-level: starting s6-rc: info: service fix-attrs successfully started [06:36:22] INFO: Configuring timezone (America/Los_Angeles)... s6-rc: info: service base-addon-log-level successfully started s6-rc: info: service base-addon-timezone successfully started s6-rc: info: service legacy-cont-init: starting cont-init: info: running /etc/cont-init.d/nut.sh [06:36:22] INFO: Setting mode to netserver... [06:36:23] INFO: Generating /etc/nut/upsd.users... [06:36:23] INFO: Configuring user: ha [06:36:23] INFO: Password is NOT in the Have I Been Pwned database! Nice! [06:36:23] INFO: Configuring Device named ups... [06:36:23] INFO: Configuring Device named ups2... [06:36:23] INFO: Starting the UPS drivers... Created directory: /var/lib/snmp/cert_indexes No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.27'! Please report it to NUT developers, with an 'upsc' output for your device. Going back to the classic MIB detection method. No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.27'! Please report it to NUT developers, with an 'upsc' output for your device. Going back to the classic MIB detection method. No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.27'! Please report it to NUT developers, with an 'upsc' output for your device. Going back to the classic MIB detection method. Detected Smart-UPS X 3000 on host ups.xxxxxxx.com (mib: apcc 1.6) [ups] Warning: excessive poll failures, limiting error reporting (OID = .1.3.6.1.4.1.318.1.1.1.9.2.3.1.5.1.1.3) [ups] Warning: excessive poll failures, limiting error reporting (OID = .1.3.6.1.4.1.318.1.1.1.9.3.3.1.6.1.1.1) Startup timer elapsed, continuing... Network UPS Tools - UPS driver controller 2.8.0 cont-init: info: /etc/cont-init.d/nut.sh exited 1 cont-init: info: running /etc/cont-init.d/nutclient.sh cont-init: info: /etc/cont-init.d/nutclient.sh exited 0 cont-init: warning: some scripts exited nonzero s6-rc: warning: unable to start service legacy-cont-init: command exited 1 /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. /run/s6/basedir/scripts/rc.init: fatal: stopping the container. s6-rc: info: service fix-attrs: stopping s6-rc: info: service base-addon-timezone: stopping s6-rc: info: service base-addon-log-level: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service base-addon-timezone successfully stopped s6-rc: info: service base-addon-log-level successfully stopped s6-rc: info: service base-addon-banner: stopping s6-rc: info: service base-addon-banner successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped

luke17287 commented 5 months ago

Same Issue here APC Back-UPS 950 via USB HA Core 2024.5.5. OS 12.3.

Config: users:

devices:

log:

Add-on: Network UPS Tools Manage battery backup (UPS) devices

Add-on version: 0.13.0 You are running the latest version of this add-on. System: Home Assistant OS 12.3 (amd64 / qemux86-64) Home Assistant Core: 2024.5.5 Home Assistant Supervisor: 2024.05.1

Please, share the above information when looking for help or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service base-addon-banner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service base-addon-timezone: starting s6-rc: info: service base-addon-log-level: starting s6-rc: info: service fix-attrs successfully started [21:37:23] INFO: Configuring timezone (Europe/Berlin)... s6-rc: info: service base-addon-log-level successfully started s6-rc: info: service base-addon-timezone successfully started s6-rc: info: service legacy-cont-init: starting cont-init: info: running /etc/cont-init.d/nut.sh [21:37:24] INFO: Setting mode to netserver... [21:37:24] INFO: Connected USB devices: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub [21:37:24] INFO: Generating /etc/nut/upsd.users... [21:37:24] INFO: Configuring user: usv [21:37:24] INFO: Password is NOT in the Have I Been Pwned database! Nice! [21:37:24] INFO: Configuring Device named myups... [21:37:24] INFO: Starting the UPS drivers... Network UPS Tools - UPS driver controller 2.8.0 Can't start /lib/nut/usbhid-usb: No such file or directory cont-init: info: /etc/cont-init.d/nut.sh exited 1 cont-init: info: running /etc/cont-init.d/nutclient.sh cont-init: info: /etc/cont-init.d/nutclient.sh exited 0 cont-init: warning: some scripts exited nonzero s6-rc: warning: unable to start service legacy-cont-init: command exited 1 /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. /run/s6/basedir/scripts/rc.init: fatal: stopping the container. s6-rc: info: service fix-attrs: stopping s6-rc: info: service base-addon-timezone: stopping s6-rc: info: service base-addon-log-level: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service base-addon-timezone successfully stopped s6-rc: info: service base-addon-log-level successfully stopped s6-rc: info: service base-addon-banner: stopping s6-rc: info: service base-addon-banner successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped

johntdyer commented 5 months ago

same issue, even at trace logging there is no more information

dcgrove commented 5 months ago

Same for me. Using a leibert UPS.

users:

Add-on: Network UPS Tools Manage battery backup (UPS) devices

Add-on version: 0.13.0 You are running the latest version of this add-on. System: Home Assistant OS 12.3 (amd64 / qemux86-64) Home Assistant Core: 2024.5.5 Home Assistant Supervisor: 2024.05.1

Please, share the above information when looking for help or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service base-addon-banner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service base-addon-timezone: starting s6-rc: info: service base-addon-log-level: starting s6-rc: info: service fix-attrs successfully started [21:31:38] INFO: Configuring timezone (America/Los_Angeles)... s6-rc: info: service base-addon-log-level successfully started s6-rc: info: service base-addon-timezone successfully started s6-rc: info: service legacy-cont-init: starting cont-init: info: running /etc/cont-init.d/nut.sh [21:31:38] INFO: Setting mode to netserver... [21:31:38] INFO: Connected USB devices: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 006: ID 10af:0002 Liebert Corp. PowerSure PST UPS Bus 002 Device 005: ID 0409:55aa NEC Corp. Hub Bus 002 Device 004: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T Bus 002 Device 003: ID 1a86:55d4 QinHeng Electronics 800 Z-Wave Stick Bus 002 Device 002: ID 1a86:55d4 QinHeng Electronics SONOFF Zigbee 3.0 USB Dongle Plus V2 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub [21:31:38] INFO: Generating /etc/nut/upsd.users... [21:31:39] INFO: Configuring user: cnut [21:31:39] INFO: Password is NOT in the Have I Been Pwned database! Nice! [21:31:39] INFO: Configuring Device named Leibert UPS... [21:31:39] INFO: Starting the UPS drivers... Error: no UPS definitions found in ups.conf Network UPS Tools - UPS driver controller 2.8.0 cont-init: info: /etc/cont-init.d/nut.sh exited 1 cont-init: info: running /etc/cont-init.d/nutclient.sh cont-init: info: /etc/cont-init.d/nutclient.sh exited 0 cont-init: warning: some scripts exited nonzero s6-rc: warning: unable to start service legacy-cont-init: command exited 1 /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. /run/s6/basedir/scripts/rc.init: fatal: stopping the container. s6-rc: info: service fix-attrs: stopping s6-rc: info: service base-addon-timezone: stopping s6-rc: info: service base-addon-log-level: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service base-addon-log-level successfully stopped s6-rc: info: service base-addon-timezone successfully stopped s6-rc: info: service base-addon-banner: stopping s6-rc: info: service base-addon-banner successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped

github-actions[bot] commented 4 months ago

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

daelsc commented 4 months ago

I am still experiencing this same issue, with the latest and greatest of everything.

sinclairpaul commented 4 months ago

The addon wraps NUT, I would suggest looking at https://github.com/networkupstools/nut as per the logged message No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.27'!

There really isn't much we can do here.

I've hidden the other comments as they are all related to USB devices, not SNMP.