similar to: setting up CYBERPOWER CP1500PFCLCD

I changed IP to NAS IP instead of my PC IP and also used NAS login and pass. Didn't work. When I wanted to launch WinNUT with new settings I got: "Fatal error: insufficient power configured!" (same as before) I got this log: Level INFO 10/26/2016 10:46:17 Detected OS as Windows NT Level NOTICE 10/26/2016 10:46:17 Network UPS Tools upsmon 2.0.0.4 Level INFO

[please use reply-all to include the list - the headers are not mangled] On Oct 25, 2016, at 9:53 AM, Tomasz Przychodzie? wrote: > > Hi, > > Another beginner question. I spend hours trying to find the solution for how to configure winnut properly but I' struggling to make it work. I want my QNAP NAS TS-231 to work as a master and send signal to the PC to shut it down during

This was only the log from the program. I'm sending my upsmon.conf attached (I removed nas ip number, admin login and pass (no spaces in parameters) and also changed back minsupplies to 1), the rest of the settings are the same as I used. Best, Tom 2016-10-26 14:21 GMT+02:00 Charles Lepple <clepple at gmail.com>: > On Oct 26, 2016, at 4:56 AM, Tomasz Przychodzie? wrote: > >

On Oct 26, 2016, at 4:56 AM, Tomasz Przychodzie? wrote: > > Level INFO 10/26/2016 10:46:17 Detected OS as Windows NT > Level NOTICE 10/26/2016 10:46:17 Network UPS Tools upsmon 2.0.0.4 > Level INFO 10/26/2016 10:46:17 Config Load: MINSUPPLIES set to 1 > Level INFO 10/26/2016 10:46:17 Config Load: NOTIFYCMD set to "c:\Program

Hi, I have an Eaton 5SC UPS with only 1 USB communication port, but... I need 3 devices to safely switch off in case of power failure, 2 Synology NAS and 1 PC under Windows 7 (soon 10)! So I've decided to connect the UPS to the main NAS (via the USB cable), enabled the "Network UPS server" on the NAS, entered the other NAS and PC IP addresses to let them receive NUT messages in case

On Oct 26, 2016, at 8:41 AM, Tomasz Przychodzie? wrote: > > This was only the log from the program. I'm sending my upsmon.conf attached (I removed nas ip number, admin login and pass (no spaces in parameters) and also changed back minsupplies to 1), the rest of the settings are the same as I used. > Be sure that the configuration file does not have a "#" before

Hi, Has anyone managed to get a Plexus UPS talking to their NAS. I've followed the excellent instructions here http://forum.qnap.com/viewtopic.php?f=182 <http://forum.qnap.com/viewtopic.php?f=182&t=35970&start=0> &t=35970&start=0 but I'm not there yet. When I manually start upsdrvctl without the UPS plugged in I get [~] # /usr/bin/upsdrvctl start Network UPS

I've searched for quite some time and read the FAQ, but to no avail. I have a UPS connected to a NAS. Unfortunately I have to specify every single client IP (ups slave), because the stupid NAS system (QNAP) does not allow me to set a /16 or /24. Changing the config files manually does not work either, because the service won't come up anymore. (One has to love QNAP at this point.) Thus I

Here are the results from the output of upsc under different conditions from my Debian Test system with NUT 2.7.2 : Normal: ups.status: OL No wall power: ups.status: OB Runtime calibration (started from AP9630 web interface): ups.status: OB CAL So at this stage there is a difference! I then connected to my QNAP and set the UPS settings on the web interface to "Shutdown server if power

Now I have this in /etc/nut/upsmon.conf (my QNAP NAS wants admin and 123456 or not working) RUN_AS_USER root MONITOR qnapups at localhost 1 admin 123456 master MONITOR qnapups at 192.168.222.252 3493 admin 123456 slave MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower NOTIFYFLAG ONLINE SYSLOG+EXEC

I am aware of 2 windows nut clients both interestingly called winnut. One (winnut 2.0.0b) is a service based client based on a port of the but client code (I think). The other is a GUI client based on (I think again) on knutclient . I have corresponded with both authors about a feature request - to allow the shut-down action to be (optionally) a windows hibernate. This seems a very

Hi Roger, Thanks very much for your answer. I appreciate! > The silence says that there is currently very little interest in NUT on > Windows, and to the best of my knowledge no-one is working on it. I would not argue the fact that there's obviously less interest in NUT on Windows than on Linux. But still, some few comments: 1/ There's maybe LESS interest, but there's some

Hi All! This time I'm using Nut 2.2.0, Debian etch and kernel v. 2.6.23.9. My hardware config is quite simple. There are 2 PCs connected to my PowerMust 600VA. One is mensioned above the other is a Windows PC using Winnut 2.0.0b. The Linux PC is connected to the UPS via a serial cable and acts as the server. The problem is that both upsmon and winnut disconnect regularly but in random

On Fri, 7 Sep 2018, Ong, Kevin wrote: > Any comments here? I am not a WinNUT user, but in general NUT clients do not produce their own log files. If you want more detail, you have to set the debug options and then look in your system logs. Upsmon.conf MONITOR ups at pfsense 1 <username> <password> slave ... POWERDOWNFLAG /usr/local/ups/etc/killpower My

Thank You very much !!! Now I see how was entered the master password in the file : "-v "concat(' password = ',//system/password)" -n \" I will test the proposed solution. Two questions - Do I need separate users for each WinNUT client or they can use the same user for monitoring&shutdown client machines ? - This is maybe a newbie question,

Hi Charles, Are there any logs generated by the WinNUT client? I'm trying to configure it for the first time and I cannot make it to work. Here are my settings: Nut.conf MODE=netclient Upsmon.conf MONITOR ups at pfsense 1 <username> <password> slave MINSUPPLIES 1 SHUTDOWNCMD "C:\\WINDOWS\\system32\\shutdown.exe -s -t 0" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME

Hello Having the next problem, manually adding via WinSCP in the upsd.users file the user for remote monitoring, saving the file, WinNUT client connects after "upsd -c reload" in NAS4Free console, but if I restart the NAS4Free system, the slave user disappears from upsd.users and remains only the master user. NAS4Free is version 9.1.0.1 rev 724 and NUT is the version what is included.

Hello All links I can find for winnut are not responding.. Anyone got a working link or maybe can send the package to me privately? /Martin -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20060410/717c77a2/attachment.html

Thanks, the strange is that I could set in this way the master user. At NAS4Free forum cannot get help, I presented the problem there too, but no real help. On Thu, Aug 22, 2013 at 2:19 AM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 21, 2013, at 10:41 AM, Incze Andras wrote: > > > Having the next problem, manually adding via WinSCP in the upsd.users > file the

All, I recently connected my UPS to my NAS. The NAS detected the UPS, and I checked the "Enable network UPS server" option and added relevant IPs to the "Permitted DiskStation devices" option. The NAS is running DSM 5.2-5592 Update 4, with a NUT version of SDS5-2-2015Q1branch-5579-15061. I then attempted to connect my desktop via SNMP. My desktop is running Arch Linux, with a