UPS config problem - WARNING: $nut_upsshut is not set properly

Status
Not open for further replies.

Touche

Explorer
Joined
Nov 26, 2016
Messages
55
Upon starting the UPS service, I get the following warning in the console:

root: /usr/local/etc/rc.d/nut: WARNING: $nut_upsshut is not set properly - see rc.conf(5)

I've tried viewing /etc/rc.conf but don't see what I should change:
Code:
#!/bin/sh																	   
																			   
# This file is explicitly in the public domain.  You may do with it			 
# anything you like.														   
																			   
# Fallback settings for FreeNAS.  This file is read in first and is			 
# then overidden by the values in the database.								 
																			   
# XXX need to clean this up													 
																			   
hostname="freenas"															 
openssh_enable="YES"														   
																			   
sendmail_enable="NONE"  # Run the sendmail inbound daemon (YES/NO).			 
																			   
background_fsck="NO"														   
fsck_y_enable="YES"															 
																			   
synchronous_dhclient="YES"	  # Start dhclient directly on configured		 
																			   
ntpd_enable="YES"															   
ntpd_sync_on_start="YES"													   
																			   
# open-vm-tools																 
vmware_guest_vmblock_enable="YES"											   
vmware_guest_vmhgfs_enable="YES"											   
vmware_guest_vmmemctl_enable="YES"											 
vmware_guestd_enable="YES"													 
																			   
devfs_system_ruleset="usbrules"												 
																			   
# System's run from memory disks.											   
clear_tmp_X="NO"															   
																			   
#Do not mark to autodetach otherwise ZFS get very unhappy					   
geli_autodetach="NO"														   
																			   
# get crashdumps															   
dumpdev="AUTO"																 
dumpdir="/data/crash"														   
ix_textdump_enable="YES"													   
																			   
# We run savecore in middleware.  The rc script								 
# just errors out by the time it runs.										 
savecore_enable="NO"														   
																			   
# A set of storage supporting kernel modules, they must be loaded before ix-fsta
b.																			 
early_kld_list="geom_mirror geom_stripe geom_raid3 geom_raid5 geom_gate geom_mul
tipath"																		 
																			   
# A set of kernel modules that can be loaded after mounting local filesystems.  
kld_list="dtraceall ipmi hwpmc t3_tom t4_tom"								   
																			   
dbus_enable="YES"															   
mdnsd_enable="YES"															 
																			   
# Turbo boost																   
performance_cpu_freq="HIGH"													 
																			   
# Add our rc.d scripts to load path											 
local_startup="/etc/ix.rc.d /usr/local/etc/rc.d"							   
																			   
# Make sure ix scripts run early enough										 
early_late_divider="*"														 
																			   
# ZFS																		   
root_rw_mount="YES"															 
																			   
# syslog-ng																	 
syslogd_enable="NO"															 
# Silence syslogd about missing files										   
# syslogd_flags="-s -C"														 
syslog_ng_enable="YES"														 
																			   
nginx_enable="YES"															 
nginx_login_class="nginx"													   
																			   
# Do not log DEVD events below LOG_NOTICE									   
devd_flags="-q"																 
																			   
# /var is a tmpfs, there is no need to clean it every boot					 
cleanvar_enable="NO"														   
																			   
# Skip check against sshd													   
openssh_skipportscheck="YES"												   
																			   
# Enable consul in single node mode by default								 
consul_alerts_enable="YES"													 
consul_alerts_args="--alert-addr=localhost:8542 --watch-events --watch-checks --
log-level=warn"																 
consul_enable="YES"															 
consul_user="root"															 
consul_group="wheel"														   
consul_args="-server -bootstrap-expect=1 -ui -bind=127.0.0.1 -enable-script-chec
ks=true -log-level=warn"													   
																			   
# Enable dnsmasq for forwarding consul service queries						 
dnsmasq_enable="NO"															 
																			   
# Enable iocage jails to autoboot if enabled in the GUI						 
iocage_enable="YES"															 
 
D

dlavigne

Guest
You don't change that file, but you do need to figure out what is causing the error.

Anything in /var/log/messages when the error occurs?

What model of UPS?

What is the FreeNAS build version (from System -> Information)?
 

Touche

Explorer
Joined
Nov 26, 2016
Messages
55
You don't change that file, but you do need to figure out what is causing the error.

Anything in /var/log/messages when the error occurs?

What model of UPS?

What is the FreeNAS build version (from System -> Information)?

This is what is happening when I start/stop the UPS service:
Code:
[root@Free ~]# tail -f /var/log/messages																				
Mar 22 21:07:28 FreeNAS_Dobrinj bcmxcp_usb[41300]: CLOSING																		
Mar 22 21:07:28 FreeNAS_Dobrinj root: /usr/local/etc/rc.d/nut: WARNING: $nut_upsshut is not set properly - see rc.conf(5).		
Mar 22 21:08:56 FreeNAS_Dobrinj upsmon[45862]: upsmon parent: read																
Mar 22 21:08:56 FreeNAS_Dobrinj upsd[45848]: mainloop: Interrupted system call													
Mar 22 21:08:56 FreeNAS_Dobrinj bcmxcp_usb[45846]: CLOSING																		
Mar 22 21:08:56 FreeNAS_Dobrinj root: /usr/local/etc/rc.d/nut: WARNING: $nut_upsshut is not set properly - see rc.conf(5).		
Mar 22 21:09:54 FreeNAS_Dobrinj upsmon[46264]: upsmon parent: read																
Mar 22 21:09:54 FreeNAS_Dobrinj upsd[46250]: mainloop: Interrupted system call													
Mar 22 21:09:54 FreeNAS_Dobrinj root: /usr/local/etc/rc.d/nut: WARNING: $nut_upsshut is not set properly - see rc.conf(5).		
Mar 22 21:09:56 FreeNAS_Dobrinj bcmxcp_usb[46248]: CLOSING	


The UPS is an Eaton Powerware 5110. I'm using the "Eaton ups 5 Powerware 3105 USB (bcmxcp_usb)" driver. The error is the same with both shutdown modes.

Code:
[root@FreeNAS ~]# upsc ups-eaton_5110								   
ambient.temperature.high: 1													 
battery.charge.low: 22														 
battery.charge.restart: 232													 
battery.charger.status: charging											   
battery.packs: 1															   
battery.runtime.low: 1														 
battery.voltage:  26.9														 
battery.voltage.low: 20														 
device.mfr: Eaton															   
device.model: POWERWARE UPS	1000i										   
device.part: 103004263-5591													 
device.type: ups															   
driver.name: bcmxcp_usb														 
driver.parameter.pollinterval: 2											   
driver.parameter.port: /dev/ugen0.2											 
driver.parameter.synchronous: no											   
driver.version: 2.7.4														   
driver.version.internal: 0.31												   
input.frequency:  50.1														 
input.frequency.high: 55													   
input.frequency.low: 45														 
input.frequency.nominal: 50													 
input.quality: 0															   
input.transfer.boost.high: 207												 
input.transfer.high: 275													   
input.transfer.low: 178														 
input.transfer.trim.low: 250												   
input.voltage: 232															 
input.voltage.nominal: 230													 
output.current:   0.0														   
output.current.nominal:   2.6												   
output.frequency:  50.1														 
output.frequency.nominal: 50												   
output.phases: 1															   
output.voltage: 232															 
output.voltage.nominal: 230													 
ups.alarm: LOSS_OF_CHARGER_SYNC INVERTER_LOW_LEVEL_TEST_TIMEOUT CHARGER_ON BYPAS
S_MANUAL_TURN_OFF PARALLEL_DC UPS_IN_PARALLEL OUTPUT_BREAKER_REALY_FAIL CONTROL_
POWER_OFF LEVEL_2_OVERLOAD_PHASE_A LEVEL_2_OVERLOAD_PHASE_B					 
ups.beeper.status: enabled													 
ups.firmware: Cont:00.50 Inve:01.50											 
ups.load: 2																	 
ups.mfr: Eaton																 
ups.model: POWERWARE UPS	1000i											   
ups.power.nominal: 1000														 
ups.status: ALARM OL														   
ups.test.result: Done and passed											   
[root@FreeNAS ~]#			 


FreeNAS-11.1-U2
i3-6100
16 GB ECC
Supermicro X11SSL-CF
 
D

dlavigne

Guest
Did you make any progress with this? If not, does updating to U4 resolve it?

Also, do you know if bcmxcp_usb is the correct driver for this device? Have you checked the cable? It is most likely either a driver or a hardware issue.
 

Touche

Explorer
Joined
Nov 26, 2016
Messages
55
Did you make any progress with this? If not, does updating to U4 resolve it?

Also, do you know if bcmxcp_usb is the correct driver for this device? Have you checked the cable? It is most likely either a driver or a hardware issue.
I still have the problem. bcmxcp_usb should be the correct driver as most of the other listed Powerware models use it and I was able to change UPS parameters with it, read its state and automatic shutdown worked. I've since changed to another Eaton model (Ellipse ECO) that is directly listed and uses usbhid-ups. Also upgraded to U4. I still get the same error. The USB cable is the same, though. Could it be the cause if upsc/upscmd are working and FreeNAS reacts to power state changes?
 

Deranged

Cadet
Joined
Dec 9, 2016
Messages
2
Were you able to make any headway on this? I have an APC Back UPS Pro and have set different drivers but am getting the same error you are. I only noticed this yesterday when the power went out and FreeNAS did not shutdown properly, it just completely shutoff when the battery died. Luckily there were no corruptions but I don't want this to happen again. I have checked the rc.conf and there is nothing showing the nut_upsshut in there. I have also ran upsc UPS@localhost and my stats and model number come up so it is communicating.
 

Touche

Explorer
Joined
Nov 26, 2016
Messages
55
No, still get the same error. So far, different UPS models using different drivers and different USB cables show the same error. Tried on 11.1-U3 and 11.1-U4.
 

Deranged

Cadet
Joined
Dec 9, 2016
Messages
2
Well hopefully someone else has seen this and has been able to get it fixed. I too was on 11.1-U3 and upgraded to 11.1-U4 after power was restored but still get the same issue as well
 

CarlB

Dabbler
Joined
Jan 30, 2018
Messages
40
I'm also having the same error on 11.1-U4. This worked a few builds back, U1 or maybe U2.
 

keithg

Explorer
Joined
May 15, 2013
Messages
92
I'm having the same problem with 11.1-U6. I am not yet interested in going to 11.2 due to the need to update my jails. U6 is working fine except this UPS problem. Is there a fix I can do to U6? I keep getting a low battery message with the upshut not set properly. This is with a 'new from USB iso' install with my config imported.

Looks like the battery is fully charged but that the OS does not recognize it. If I unplug it, It shuts down immediately and no longer sends me the online/offline message.

Code:
Oct 15 14:11:08 NAS upsmon[2210]: UPS ups battery is low
Oct 15 19:44:45 NAS upsmon[2209]: upsmon parent: read
Oct 15 19:44:45 NAS upsd[2203]: mainloop: Interrupted system call
Oct 15 19:44:45 NAS root: /usr/local/etc/rc.d/nut: WARNING: $nut_upsshut is not set properly - see rc.conf(5).
Oct 15 19:44:54 NAS upsmon[87884]: UPS ups battery is low



Code:
~ $ upsc ups@localhost
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 20
battery.mfr.date: CPS
battery.runtime: 330
battery.runtime.low: 300
battery.type: PbAcid
battery.voltage: 14.3
battery.voltage.nominal: 12
device.mfr: CPS
device.model: CP625HGa
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ugen0.2
driver.parameter.synchronous: no
driver.version: 2.7.4
driver.version.data: CyberPower HID 0.4
driver.version.internal: 0.41
input.transfer.high: 0
input.transfer.low: 0
input.voltage: 121.0
input.voltage.nominal: 120
output.voltage: 121.0
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.load: 55
ups.mfr: CPS
ups.model: CP625HGa
ups.productid: 0501
ups.realpower.nominal: 375
ups.status: OL LB
ups.test.result: No test initiated
ups.timer.shutdown: -60
ups.timer.start: 0
 
Status
Not open for further replies.
Top