similar to: Tripp-Lite AVRX500U issues (objecttothis)

Hi Everyone, I recently bought a Tripp-Lite SMART1500LCD for my Linux Mint 19.3 machine, connected via a USB cable. I installed Nut 2.7.4 from the Mint package repository via sudo apt update && sudo apt install nut. Everything works great: NUT issues low battery warning when it reaches the set low battery point and then issues shutdown commands...computer shuts down..then the UPS shuts

I've built NUT 2.8.0 from source. When the nut-monitor runs: fopen upsmon.pid fails. I'm running as root, upsmon has root:root permissions as well as the other daemons and .conf files. I've tried configuring with and without --prefixpath --prefixaltpath. Is there something I am missing? Please see attached. Dan -------------- next part -------------- An HTML attachment was

I have gone through Two Tripp-Lite AVRX550U units trying to troubleshoot issues. There are two separate (but possibly related issues that I am finding. I’ve created an issue on the Github page, but it’s not clear that anyone looks at those issues (https://github.com/networkupstools/nut/issues/799) 1. According to Tripp-lite, the AVRX550U uses the 2012 protocol, but it’s listed in NUT as

Now that upsstats.cgi works, I've noticed that dummy-ups changes state every 5 minutes between OL and OB (probably when the 300 second timer expires). The UPS state stays online. Also "online" and "onbatt" are broadcast to the console probably via WALL. (The state changes don't seem to be form the ups as upsshed-cmd doesn't run). Upssched-cmd does run when the UPS

hello, i've got a problem with the notifycmd here is a part of my upsmon.conf : NOTIFYCMD /usr/local/ups/bin/nut_notify NOTIFYMSG ONLINE "UPS %s is getting line power" NOTIFYMSG ONBATT "UPS %s is on battery" NOTIFYMSG REPLBATT "The UPS %s battery is bad and needs to be replaced" NOTIFYMSG LOWBATT "UPS %s is being shutdown by the master" NOTIFYMSG FSD

On Tue, 27 Oct 2015, George Anchev wrote: > Yes, that was the power off test. However the upssched-cmd script gave > absolutely no signs of activity. Even it's logger lines don't show up in > journalctl. No any permission error messages - nothing. Only the 2 > messages from upsmon - on battery and then on line power. > > Here is the nut-report: >

I've not been able to connect to my ups using NUT 2.7.4 or NUT 2.8.0. 2.7.4 was installed as a package, 2.8.O was compiled from source. I've messed with permissons, everything is root:root and has the approprate read/execute permissons. I've tried two differnt UPS(es) APC & CyperPower. I'm running PI OS (Raspbian) on a Raspberry Pi3 model B. The port 3493 is open (UFW). I can

Hello guys Yesterday i started do configure my Mustek Powermust650 with nut using the megatec_usb driver. Everything works fine except for the mailing when something happens. My upsmon looks like this: MONITOR powermust650 at localhost 1 local controller master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /root/upsmailer POLLFREQ 10 POLLFREQALERT 5 HOSTSYNC 15

I've setup nas4free (latest version 11.0.0.4, which has NUT 2.7.4) in a VM and configured it via webinterface to my APC UPS and set "shutdown mode" to "UPS goes on battery" with a timer of 30s. Then I started runtime calibration on the UPS and after 30s nas4free has shut down! I think this is not the correct behavior, since the status was "OB CAL". The system

There's supposedly another way with a custom upsmon.conf: NOTIFYMSG type message upsmon comes with a set of stock messages for various events. You can change them if you like. NOTIFYMSG ONLINE "UPS %s is getting line power" NOTIFYMSG ONBATT "Someone pulled the plug on %s" Note that %s is replaced with the identifier of the UPS in question. The message must be one

Charles, This is how I have the upsmon.conf set up. ?The only time I get a message is if the?NUT Monitor gui is running. ?I open LXterminal, pull the wall plug, and I get no messagesin the terminal. ?MONITOR Asium_p700 at localhost 1 upsmon jsamcr master?MINSUPPLIES 1?SHUTDOWNCMD "/sbin/shutdown -h +0"?NOTIFYCMD /sbin/upssched?POLLFREQ 5?POLLFREQALERT 5?HOSTSYNC 15?DEADTIME

Hello, I set up a FreeBSD 8.2 system with nut 2.6.1 and a Powerware 5115 connected by RS-232. I expected this setup to shut down before running out of battery power, but I either missed some important configuration or something else went wrong: The syslog says: Jan 9 05:03:42 b1 upsmon[67752]: UPS upsb1 at localhost on battery Jan 9 05:04:42 b1 upsmon[67752]: UPS upsb1 at localhost on line

Hi, I have problem with upssched on windows. Upssched is not executed. I have 2 scripts, 1 for notification in upsmon and second for scheduling in upssched. Monitoring is working fine, script write to log. I'm using binary windows installer 2.6.5-6 from NUT. Here are my configs: --- nut.conf MODE=netclient --- upsmon.conf MONITOR ups_1000 at 192.168.3.95 1 <user> <password> slave

If there is a next Windows release, perhaps the default NOTIFYFLAG's should be adjusted? NOTIFYFLAG ONLINE SYSLOG NOTIFYFLAG ONBATT SYSLOG NOTIFYFLAG LOWBATT SYSLOG NOTIFYFLAG FSD SYSLOG NOTIFYFLAG COMMOK SYSLOG NOTIFYFLAG COMMBAD SYSLOG NOTIFYFLAG SHUTDOWN SYSLOG NOTIFYFLAG REPLBATT SYSLOG NOTIFYFLAG NOCOMM SYSLOG NOTIFYFLAG NOPARENT SYSLOG The 'wall'

On Feb 25, 2014, at 1:13 AM, Kris Jordan wrote: > If there is a next Windows release, perhaps the default NOTIFYFLAG's should be adjusted? > > NOTIFYFLAG ONLINE SYSLOG > NOTIFYFLAG ONBATT SYSLOG > NOTIFYFLAG LOWBATT SYSLOG > NOTIFYFLAG FSD SYSLOG > NOTIFYFLAG COMMOK SYSLOG > NOTIFYFLAG COMMBAD SYSLOG > NOTIFYFLAG SHUTDOWN SYSLOG > NOTIFYFLAG

Hi All, I'm using a recent post 2.6.1 build provided by Fred (executables have modified date of 9th August) I have configured upsmon.conf with :- NOTIFYCMD C:\NUT\etc\NotifyCmd.bat and :- NOTIFYFLAG ONLINE SYSLOG+EXEC NOTIFYFLAG ONBATT SYSLOG+EXEC NOTIFYFLAG LOWBATT SYSLOG+EXEC NOTIFYFLAG FSD SYSLOG+EXEC NOTIFYFLAG COMMOK SYSLOG+EXEC NOTIFYFLAG COMMBAD SYSLOG+EXEC

Hallo all. I tried to configure the UPS Trust OXXTRON 1300VA but i didn't succeed. i tried the blazer_usb <http://www.networkupstools.org/docs/man/blazer_usb.html> driver and others but i didn't succeed. My lsusb says Bus 002 Device 005: ID 0925:1234 Lakeview Research Bus 004 Device 002: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 004 Device 004: ID 0424:2228 Standard

A couple of different issues with the reporting script. First the password masking is not working as intended: I have three different passwords in my ups.users file and only the last one is masked. Here's the first part of the resulting report where I've replaced the unmasked passwords with <PASSWORD-n>. NUT configuration 2019-07-14 16:58:15 UTC ###########

Dear Chales, Thanks for your quick reply. I have Raspberry with last Kernel [Linux pi1 3.18.6+ #753 PREEMPT Sun Feb 8 14:47:22 GMT 2015 armv6l GNU/Linux] If <upsdrvctl>, <upsd> and <upsmon> are stopped <nutdrv_atcl_usb> Works well without any error as "Device or resource busy". If I run <upsc> command never receive any value from my ups <upsc ups at