tucansam 11 Posted November 15, 2018 Tripp Lite SMART 1500 LCDT Can anyone confirm this works with the plugin? Just got two for a steal, either they talk to unraid or my pi, but I would prefer unraid. Thanks. Quote Share this post Link to post
Dustin 0 Posted November 15, 2018 (edited) I'm new to unRAID. I installed Nut on my server. I'm connected via usb. It works to shutdown my server when it switches to battery mode. However, i have tbe UPS shutdown enabled but the feature isn't working. I stood by my UPS with a stopwatch and let it run for 7 min and it never powered down after the server powered down. Any suggestions? I uninstslled and reinstalled nut. I dide delete the nut folder off of my boot drive before reinstsll and it did not resolve this issue. I have a tripp Lite UPS model su1500rtxlcd2u. Edited November 15, 2018 by Dustin Added UPS model# Quote Share this post Link to post
dmacias 151 Posted November 15, 2018 I'm new to unRAID. I installed Nut on my server. I'm connected via usb. It works to shutdown my server when it switches to battery mode. However, i have tbe UPS shutdown enabled but the feature isn't working. I stood by my UPS with a stopwatch and let it run for 7 min and it never powered down after the server powered down. Any suggestions? I uninstslled and reinstalled nut. I dide delete the nut folder off of my boot drive before reinstsll and it did not resolve this issue. I have a tripp Lite UPS model su1500rtxlcd2u.I assume you have it shutdown based on time on battery. What time did you set it to? If you have a monitor hooked up, watch the console when that time expires and see if it's starting shutdown. Quote Share this post Link to post
Dustin 0 Posted November 15, 2018 (edited) 4 hours ago, dmacias said: 6 hours ago, Dustin said: I'm new to unRAID. I installed Nut on my server. I'm connected via usb. It works to shutdown my server when it switches to battery mode. However, i have tbe UPS shutdown enabled but the feature isn't working. I stood by my UPS with a stopwatch and let it run for 7 min and it never powered down after the server powered down. Any suggestions? I uninstslled and reinstalled nut. I dide delete the nut folder off of my boot drive before reinstsll and it did not resolve this issue. I have a tripp Lite UPS model su1500rtxlcd2u. I assume you have it shutdown based on time on battery. What time did you set it to? If you have a monitor hooked up, watch the console when that time expires and see if it's starting shutdown. I have the shutdown set for 99%, I set it this way for testing. I'm going to set it to 85% once I know it operates correctly. The server appears to be shutting down just fine, it just won't shut the UPS off. I attached the details in NUT on unRAID as well as screen shots from the monitor during shutdown. I'm also running this on unRAID version 6.6.5. NutDetails.pdf ConsoleNutShutdown.pdf Edited November 15, 2018 by Dustin Inform unRAID version. Quote Share this post Link to post
dmacias 151 Posted November 16, 2018 I have the shutdown set for 99%, I set it this way for testing. I'm going to set it to 85% once I know it operates correctly. The server appears to be shutting down just fine, it just won't shut the UPS off. I attached the details in NUT on unRAID as well as screen shots from the monitor during shutdown. I'm also running this on unRAID version 6.6.5.NutDetails.pdfConsoleNutShutdown.pdfI'll look into it. It could just be a nut problem with this ups. Quote Share this post Link to post
rclifton 0 Posted November 26, 2018 Stupid question time, Is there any difference in functionality when using auto vs. manual? In auto mode the NOMINAL POWER and UPS LOAD values are way off from what is reported by the UPS itself. If I use manual mode everything appears to align with what the UPS reports on it's screen except NOMINAL POWER is always reported as the value I entered in the box. RUN TIME and UPS LOAD% are accurate regardless of which one I choose. I'm just wondering if I lose anything by using one over the other? Screenshots below to show what I mean. First one is when in AUTO mode, Second is in MANUAL. Quote Share this post Link to post
dmacias 151 Posted November 26, 2018 Stupid question time, Is there any difference in functionality when using auto vs. manual? In auto mode the NOMINAL POWER and UPS LOAD values are way off from what is reported by the UPS itself. If I use manual mode everything appears to align with what the UPS reports on it's screen except NOMINAL POWER is always reported as the value I entered in the box. RUN TIME and UPS LOAD% are accurate regardless of which one I choose. I'm just wondering if I lose anything by using one over the other? Screenshots below to show what I mean. First one is when in AUTO mode, Second is in MANUAL. What are the variable on the NUT details page in settings? What UPS? Quote Share this post Link to post
rclifton 0 Posted November 26, 2018 29 minutes ago, dmacias said: 1 hour ago, rclifton said: Stupid question time, Is there any difference in functionality when using auto vs. manual? In auto mode the NOMINAL POWER and UPS LOAD values are way off from what is reported by the UPS itself. If I use manual mode everything appears to align with what the UPS reports on it's screen except NOMINAL POWER is always reported as the value I entered in the box. RUN TIME and UPS LOAD% are accurate regardless of which one I choose. I'm just wondering if I lose anything by using one over the other? Screenshots below to show what I mean. First one is when in AUTO mode, Second is in MANUAL. What are the variable on the NUT details page in settings? What UPS? The UPS i'm using is a Cyberpower OR2200PFCRT2Ua. When in manual mode, I just enter the ratings that the manufacturer gives, which are: UPS Output Volt Amp Capacity (VA):2200 UPS Output Watt Capacity (Watts):1320 I notice in the NUT settings the variable ups.realpower.nominal always equals 296 and I think that might be the issue with the differences being displayed.. In manual mode I assume the 1320 I'm entering is overwriting that 296 in it's calculations. Where as in Auto mode its using that 296 and thats why the ups load in watts is way off in Auto. Quote Share this post Link to post
Beta 0 Posted January 8 Hi! I have an Eaton Ellipse PRO 850 that I am using with this plugin on my unRAID-machine. I am having some trouble getting my shutdown settings to work 100%. I have set NUT to intiate shutdown at 10% left on battery, however it intiates shutdown way to early at around 59% from the two times I have tested now. Here is my NUT Settings: Here is the log from the shutdown procedure: Jan 8 23:14:17 unRAID upsmon[23159]: UPS ups@127.0.0.1 on battery Jan 8 23:19:27 unRAID upsmon[23159]: UPS ups@127.0.0.1 battery is low Jan 8 23:19:27 unRAID upsd[23155]: Client monuser@127.0.0.1 set FSD on UPS [ups] Jan 8 23:19:27 unRAID upsmon[23159]: Executing automatic power-fail shutdown Jan 8 23:19:27 unRAID upsmon[23159]: Auto logout and shutdown proceeding Jan 8 23:19:32 unRAID shutdown[12858]: shutting down for system halt Jan 8 23:19:32 unRAID init: Switching to runlevel: 0 Jan 8 23:19:33 unRAID init: Trying to re-exec init Jan 8 23:19:39 unRAID emhttpd: req (5): cmdStop=apply&csrf_token=**************** Jan 8 23:19:39 unRAID kernel: mdcmd (49): nocheck Jan 8 23:19:39 unRAID emhttpd: Spinning up all drives... Jan 8 23:19:39 unRAID kernel: md: nocheck_array: check not active Jan 8 23:19:39 unRAID emhttpd: shcmd (3637): /usr/sbin/hdparm -S0 /dev/sdb Jan 8 23:19:39 unRAID kernel: mdcmd (50): spinup 0 Jan 8 23:19:39 unRAID kernel: mdcmd (51): spinup 1 Jan 8 23:19:39 unRAID kernel: mdcmd (52): spinup 2 Jan 8 23:19:39 unRAID kernel: mdcmd (53): spinup 3 Jan 8 23:19:39 unRAID kernel: mdcmd (54): spinup 4 Jan 8 23:19:39 unRAID kernel: mdcmd (55): spinup 5 Jan 8 23:19:39 unRAID kernel: mdcmd (56): spinup 6 Jan 8 23:19:39 unRAID root: Jan 8 23:19:39 unRAID root: /dev/sdb: Jan 8 23:19:39 unRAID root: setting standby to 0 (off) Jan 8 23:19:39 unRAID emhttpd: shcmd (3638): /usr/sbin/hdparm -S0 /dev/sdc Jan 8 23:19:39 unRAID root: Jan 8 23:19:39 unRAID root: /dev/sdc: Jan 8 23:19:39 unRAID root: setting standby to 0 (off) Jan 8 23:19:47 unRAID emhttpd: Stopping services... Jan 8 23:19:47 unRAID emhttpd: shcmd (3640): /etc/rc.d/rc.libvirt stop Jan 8 23:19:49 unRAID root: Domain e4ccb7aa-8d12-682a-06b3-307208dabd56 is being shutdown Jan 8 23:19:49 unRAID root: Jan 8 23:19:49 unRAID root: Domain 3e293166-fb30-b06a-1c27-1a7d1f74abce is being shutdown Jan 8 23:19:49 unRAID root: Jan 8 23:19:51 unRAID avahi-daemon[10125]: Interface vnet0.IPv6 no longer relevant for mDNS. Jan 8 23:19:51 unRAID avahi-daemon[10125]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fecf:fa47. Jan 8 23:19:51 unRAID kernel: br0: port 2(vnet0) entered disabled state Jan 8 23:19:51 unRAID kernel: device vnet0 left promiscuous mode Jan 8 23:19:51 unRAID kernel: br0: port 2(vnet0) entered disabled state Jan 8 23:19:51 unRAID avahi-daemon[10125]: Withdrawing address record for fe80::fc54:ff:fecf:fa47 on vnet0. Jan 8 23:20:04 unRAID avahi-daemon[10125]: Interface vnet1.IPv6 no longer relevant for mDNS. Jan 8 23:20:04 unRAID avahi-daemon[10125]: Leaving mDNS multicast group on interface vnet1.IPv6 with address fe80::fc54:ff:fe0b:b049. Jan 8 23:20:04 unRAID kernel: br0: port 3(vnet1) entered disabled state Jan 8 23:20:04 unRAID kernel: device vnet1 left promiscuous mode Jan 8 23:20:04 unRAID kernel: br0: port 3(vnet1) entered disabled state Jan 8 23:20:04 unRAID avahi-daemon[10125]: Withdrawing address record for fe80::fc54:ff:fe0b:b049 on vnet1. Jan 8 23:20:04 unRAID root: Waiting on VMs to shutdown............... Jan 8 23:20:04 unRAID root: Stopping libvirtd... Jan 8 23:20:04 unRAID dnsmasq[12878]: exiting on receipt of SIGTERM Jan 8 23:20:04 unRAID kernel: device virbr0-nic left promiscuous mode Jan 8 23:20:04 unRAID kernel: virbr0: port 1(virbr0-nic) entered disabled state Jan 8 23:20:04 unRAID avahi-daemon[10125]: Interface virbr0.IPv4 no longer relevant for mDNS. Jan 8 23:20:04 unRAID avahi-daemon[10125]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Jan 8 23:20:04 unRAID dhcpcd[1675]: virbr0: new hardware address: Jan 8 23:20:04 unRAID avahi-daemon[10125]: Withdrawing address record for 192.168.122.1 on virbr0. Jan 8 23:20:04 unRAID root: Network 7e6a3e65-1f8a-40ba-881f-e3fc72e43adf destroyed Jan 8 23:20:04 unRAID root: Jan 8 23:20:08 unRAID root: Stopping virtlogd... Jan 8 23:20:09 unRAID root: Stopping virtlockd... Jan 8 23:20:10 unRAID emhttpd: shcmd (3641): umount /etc/libvirt Jan 8 23:20:10 unRAID root: Stopping docker_load Jan 8 23:20:10 unRAID emhttpd: shcmd (3643): /etc/rc.d/rc.docker stop Jan 8 23:20:12 unRAID kernel: device br0 left promiscuous mode Jan 8 23:20:12 unRAID kernel: veth5ddce05: renamed from eth0 Jan 8 23:20:13 unRAID root: stopping dockerd ... Jan 8 23:20:14 unRAID root: waiting for docker to die ... Jan 8 23:20:15 unRAID avahi-daemon[10125]: Interface docker0.IPv4 no longer relevant for mDNS. Jan 8 23:20:15 unRAID avahi-daemon[10125]: Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Jan 8 23:20:15 unRAID avahi-daemon[10125]: Withdrawing address record for 172.17.0.1 on docker0. Jan 8 23:20:15 unRAID emhttpd: shcmd (3644): umount /var/lib/docker Jan 8 23:20:15 unRAID cache_dirs: Stopping cache_dirs process 11711 Jan 8 23:20:17 unRAID cache_dirs: cache_dirs service rc.cachedirs: Stopped Jan 8 23:20:17 unRAID unassigned.devices: Unmounting All Devices... Jan 8 23:20:18 unRAID emhttpd: shcmd (3645): /etc/rc.d/rc.samba stop Jan 8 23:20:18 unRAID emhttpd: shcmd (3646): rm -f /etc/avahi/services/smb.service Jan 8 23:20:18 unRAID avahi-daemon[10125]: Files changed, reloading. Jan 8 23:20:18 unRAID avahi-daemon[10125]: Service group file /services/smb.service vanished, removing services. Jan 8 23:20:18 unRAID emhttpd: Stopping mover... Jan 8 23:20:18 unRAID emhttpd: shcmd (3649): /usr/local/sbin/mover stop Jan 8 23:20:18 unRAID root: mover: not running Jan 8 23:20:18 unRAID emhttpd: Sync filesystems... Jan 8 23:20:18 unRAID emhttpd: shcmd (3650): sync Jan 8 23:20:18 unRAID emhttpd: Stopping ProFTPd... Jan 8 23:20:19 unRAID proftpd[2608]: 127.0.0.1 - ProFTPD killed (signal 15) Jan 8 23:20:19 unRAID proftpd[2608]: 127.0.0.1 - ProFTPD 1.3.6 standalone mode SHUTDOWN Jan 8 23:20:20 unRAID emhttpd: ... Stop OK Jan 8 23:20:21 unRAID emhttpd: shcmd (3651): umount /mnt/user0 Jan 8 23:20:21 unRAID emhttpd: shcmd (3652): rmdir /mnt/user0 Jan 8 23:20:21 unRAID emhttpd: shcmd (3653): umount /mnt/user Jan 8 23:20:21 unRAID emhttpd: shcmd (3654): rmdir /mnt/user Jan 8 23:20:21 unRAID emhttpd: shcmd (3655): rm -f /boot/config/plugins/dynamix/mover.cron Jan 8 23:20:21 unRAID emhttpd: shcmd (3656): /usr/local/sbin/update_cron Jan 8 23:20:21 unRAID emhttpd: Unmounting disks... Jan 8 23:20:21 unRAID emhttpd: shcmd (3657): umount /mnt/disk1 Jan 8 23:20:21 unRAID kernel: XFS (md1): Unmounting Filesystem Jan 8 23:20:28 unRAID emhttpd: shcmd (3658): rmdir /mnt/disk1 Jan 8 23:20:28 unRAID emhttpd: shcmd (3659): umount /mnt/disk2 Jan 8 23:20:28 unRAID kernel: XFS (md2): Unmounting Filesystem Jan 8 23:20:28 unRAID emhttpd: shcmd (3660): rmdir /mnt/disk2 Jan 8 23:20:28 unRAID emhttpd: shcmd (3661): umount /mnt/disk3 Jan 8 23:20:28 unRAID kernel: XFS (md3): Unmounting Filesystem Jan 8 23:20:28 unRAID emhttpd: shcmd (3662): rmdir /mnt/disk3 Jan 8 23:20:28 unRAID emhttpd: shcmd (3663): umount /mnt/disk4 Jan 8 23:20:29 unRAID kernel: XFS (md4): Unmounting Filesystem Jan 8 23:20:29 unRAID emhttpd: shcmd (3664): rmdir /mnt/disk4 Jan 8 23:20:29 unRAID emhttpd: shcmd (3665): umount /mnt/disk5 Jan 8 23:20:29 unRAID kernel: XFS (md5): Unmounting Filesystem Jan 8 23:20:29 unRAID emhttpd: shcmd (3666): rmdir /mnt/disk5 Jan 8 23:20:29 unRAID emhttpd: shcmd (3667): umount /mnt/disk6 Jan 8 23:20:29 unRAID kernel: XFS (md6): Unmounting Filesystem Jan 8 23:20:29 unRAID emhttpd: shcmd (3668): rmdir /mnt/disk6 Jan 8 23:20:29 unRAID emhttpd: shcmd (3669): umount /mnt/cache Jan 8 23:20:29 unRAID emhttpd: shcmd (3670): rmdir /mnt/cache Jan 8 23:20:29 unRAID root: Stopping diskload Jan 8 23:20:29 unRAID kernel: mdcmd (57): stop Jan 8 23:20:29 unRAID kernel: md1: stopping Jan 8 23:20:29 unRAID kernel: md2: stopping Jan 8 23:20:29 unRAID kernel: md3: stopping Jan 8 23:20:29 unRAID kernel: md4: stopping Jan 8 23:20:30 unRAID kernel: md5: stopping Jan 8 23:20:30 unRAID kernel: md6: stopping Jan 8 23:20:30 unRAID emhttpd: Starting services... Jan 8 23:20:30 unRAID emhttpd: shcmd (3672): /etc/rc.d/rc.samba start Jan 8 23:20:30 unRAID root: Starting Samba: /usr/sbin/nmbd -D Jan 8 23:20:30 unRAID root: /usr/sbin/smbd -D Jan 8 23:20:30 unRAID root: /usr/sbin/winbindd -D Jan 8 23:20:30 unRAID emhttpd: shcmd (3673): cp /tmp/emhttp/smb.service /etc/avahi/services/smb.service Jan 8 23:20:30 unRAID avahi-daemon[10125]: Files changed, reloading. Jan 8 23:20:30 unRAID avahi-daemon[10125]: Loading service file /services/smb.service. Can anyone help me figure out what is wrong? Thanks! Quote Share this post Link to post
jonathanm 525 Posted January 8 13 minutes ago, Beta said: I have set NUT to intiate shutdown at 10% left on battery, If that UPS is using SLA batteries, you are seriously killing the available life of the batteries by waiting that long. Ideally the server should be shut down completely before you get to 50% capacity. The purpose of a consumer type UPS is to allow for a clean shutdown with enough time to finish critical tasks. If you need extended runtime, you need a different solution. Quote Share this post Link to post
dmacias 151 Posted January 8 Hi! I have an Eaton Ellipse PRO 850 that I am using with this plugin on my unRAID-machine. I am having some trouble getting my shutdown settings to work 100%. I have set NUT to intiate shutdown at 10% left on battery, however it intiates shutdown way to early at around 59% from the two times I have tested now. Can anyone help me figure out what is wrong? Thanks! Where are you reading the 59% from during power test? Maybe check the nut details page and show what it says after the power has been off a few minutes. It could be a problem with the nut driver and what the the ups is reporting. It might not be reporting the battery level right. I always just use a fixed time of 5 or 10 minutes. Quote Share this post Link to post
Beta 0 Posted January 8 14 minutes ago, jonathanm said: If that UPS is using SLA batteries, you are seriously killing the available life of the batteries by waiting that long. Ideally the server should be shut down completely before you get to 50% capacity. The purpose of a consumer type UPS is to allow for a clean shutdown with enough time to finish critical tasks. If you need extended runtime, you need a different solution. Thanks for the heads up! I did not know that. Yes it is using SLA batteries. I'll take this into consideration, however I do not get many power failures. Can't remember I have had any at all since I moved in 4 years ago. 12 minutes ago, dmacias said: Where are you reading the 59% from during power test? Maybe check the nut details page and show what it says after the power has been off a few minutes. It could be a problem with the nut driver and what the the ups is reporting. It might not be reporting the battery level right. I always just use a fixed time of 5 or 10 minutes. From the dashboard in unraid while I was monitoring it when testing the UPS, I was monitoring what NUT reported constantly. The display on the UPS itself was at 2/4 bars battery with about 6-7 minutes left. NUT seems to be reporting about the same as the UPS itself, the battery percentage dropped at an expected rate in NUT. Would it be better to try runtime left or time on battery? I timed the server to need about 1,5m to shutdown properly. Quote Share this post Link to post
Benson 56 Posted January 9 (edited) 1 hour ago, Beta said: Jan 8 23:14:17 unRAID upsmon[23159]: UPS ups@127.0.0.1 on battery Jan 8 23:19:27 unRAID upsmon[23159]: UPS ups@127.0.0.1 battery is low From your log, protection time around 5min. Pls note 850 VA UPS usually equip two general battery. For your case, I would suggest shutdown ASAP if power lost longer then 1 min. Because battery not always guarantee protect 5 min and loading could be change. Any timing tweaking, should have longer runtime first. Edited January 9 by Benson Quote Share this post Link to post
Beta 0 Posted January 9 9 hours ago, dmacias said: Where are you reading the 59% from during power test? Maybe check the nut details page and show what it says after the power has been off a few minutes. It could be a problem with the nut driver and what the the ups is reporting. It might not be reporting the battery level right. I always just use a fixed time of 5 or 10 minutes. I have done some more testing, and whatever setting I choose it automatically intiate shutdown procedures at exactly 5 minutes. My UPS was not listed on the compatibility list so I guess it's as you said som driver issue, and it safely shutdown at some default value instead which is 5 minutes. Makes kinda sense. Well I'm happy at least knowing what causes it and battery time before it shuts down. Quote Share this post Link to post
fireflower 0 Posted January 22 Hello, I am new to unRAID and its plugins and I am trying to setup one of the UPS to work with NUT v2 but I cannot get the charge % or any other data to show up. Am I doing something wrong? Quote Share this post Link to post
dmacias 151 Posted January 23 Hello, I am new to unRAID and its plugins and I am trying to setup one of the UPS to work with NUT v2 but I cannot get the charge % or any other data to show up. Am I doing something wrong? Try using the usbhid driver instead of the tripplite usb. Or run autodetect Quote Share this post Link to post
fireflower 0 Posted January 23 9 minutes ago, dmacias said: Try using the usbhid driver instead of the tripplite usb. Or run autodetect Sadly usbhid driver detects nothing and service won't even start. Quote Share this post Link to post
dmacias 151 Posted January 23 Sadly usbhid driver detects nothing and service won't even start. Did you try running autodetect? And what did it show? Quote Share this post Link to post
fireflower 0 Posted January 23 1 minute ago, dmacias said: 15 minutes ago, fireflower said: Sadly usbhid driver detects nothing and service won't even start. Did you try running autodetect? And what did it show? Auto detect set up tripplite usb, I checked with laptop that windows based poweralert local works and shows all values correctly so I would assume the configuration file in nut is wrong for this? Also don't know does it makes a difference but this is 230V model. Quote Share this post Link to post
dmacias 151 Posted January 23 Auto detect set up tripplite usb, I checked with laptop that windows based poweralert local works and shows all values correctly so I would assume the configuration file in nut is wrong for this? Also don't know does it makes a difference but this is 230V model. It's the tripplite driver. You're missing certain variables. I'll look at compiling nut again. There are fixes for protocol 3005 committed 6 months ago and the branch I used might not have included those. 1 Quote Share this post Link to post
cybrnook 32 Posted January 27 (edited) Thank you sooooo much for this! I was upset this am to find that apcupsd did not work/detect my Cyberpower OL1500RTXL2UN. NUT worked like a charm, I can sleep well tonight. Edited January 27 by cybrnook Quote Share this post Link to post
JoergHH 0 Posted January 31 Excuse the stupid question, but what is the advantage of NUT over the internal Unraid 6.x UPS Settings? Quote Share this post Link to post
dmacias 151 Posted January 31 Excuse the stupid question, but what is the advantage of NUT over the internal Unraid 6.x UPS Settings?Some UPS don't work with apcupsd. I like the server/client aspect. Quote Share this post Link to post
Ambrotos 9 Posted February 2 Is it just my system, or has anyone else noticed that the Settings icon for NUT doesn’t display anymore since the January 24th update to fa font? I initially thought it was just a browser cache thing, but I’ve since tried multiple browsers, multiple computers, etc. The NUT icon in the plugins page loads fine, but I’m assuming that’s because it hasn’t been changed to be “awesome” (Running 6.6.6 if that matters. I haven’t had a chance to try out the 6.7RC yet) -A Quote Share this post Link to post
1activegeek 2 Posted February 2 Yup, I noticed the same thing. It's that evil version (6.6.6) Quote Share this post Link to post
