similar to: Link for winnut?

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

My UPS (an APC 620, FWIW) is attached to my Sun workstation, and monitored by NUT. Everything works a treat and I'm delighted with it (in direct contrast to the useless APC software it came with). But ... I'd like to put my wife's XP machine on the UPS, and have the Sun shut it down, when appropriate. I see there is an XP port of NUT, so ... before I start down the path of horror that

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

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

How do you setup the debug options in WinNUT? Correct, it sets the POWERDOWNFLAG when it receives an FSD but only if it acts as a NUT MASTER (since the UPS is connected locally to the NUT MASTER and can issue a killpower). This is the default value and I did not care to change it because it won't be use on my Windows machine anyway as it is working as a NUT SLAVE. Thank you. Regards, Kevin

Hi there, been using NUT for ages and recently upgraded to a new server; while I'm waiting for a USB->Serial adapter for Solaris to arrive, I thought I'd play with the newhidups, as the APC UPS I have has a USB port and the new server doesn't have a serial port.... I've got Solaris 10 & newhidups working with the ugen driver up to a point, and that is a read

Any comments here? Thank you. Regards, Kevin Mychal M. Ong Sr Infrastructure Engineer, Microsoft Technology Services - Messaging Global Infrastructure Operations Ingram Micro Inc. 4F Three World Square, 22 Upper McKinley Hill, Fort Bonifacio Taguig City, Philippines 1634 Direct +1-716-633-3600 ext. 33996 Mobile +63-917-511-0251 *: kevin.ong at ingrammicro.com<mailto:kevin.ong at

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 power outage. I configured QNAP properly (like this: http://geekbeat.tv/qnap-adding-external-devices-qnap), but I don't know what to do next. I work

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

Hello, I got this information from the manufacturer of my ups Kobian/Mercury and were tested wtih powstatd on Linux (Works OK). Now i want to configure it with NUT and i didn't have any luck (it always says OB) Initiliasation for monitoring: RTS = 1 (High) Main power fail: CTS = 0 (Low) Batter low: DCD = 0 (Low) Kill UPS: DTR = 0 (Low) How would the ups.conf look like? Reagards, Lep

Hello, It is 3 or 4 weeks ago since, i want to set communication with my ups a MGE NOVA 1100 AVR. I do it first with manual configuration but after no success, i prefered to install mgeups-psp package to do it directly. But since when i execute psp, the attempt finish with an "No communication with UPS" error. Same is when i type: mge-shut -u root -DDDDDDDDDD /dev/ttyS0 . I unplog

Hi! We have two MGE Evolution 1100 here, and I want to make use of the powershare outlets to force a particular boot sequence on the machines powered by them. However I'm not sure how to set those variables upon NUT starting, without having to change the init scripts to call "upsrw". Is there some place where I can set them, where they can be read automatically on startup? One of

I have an MGE Pulsar Evolution 1100 connected to a Debian box, with nut-2.0.1 (the standard "sarge" packages). I have it connected through USB, and I'm using newhidups. However, about once a day the driver looses contact with the UPS and I have to restart NUT to get it to drop the "data stale" nonsense (it happens more often than this, but most times it recovers without

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

Hope it's not too rude to just drop this here for y'all... Checking device (0764/0501) (001/005) - VendorID: 0764 - ProductID: 0501 - Manufacturer: CPS - Product: UPS AE550 - Serial Number: unknown This one and their 485 don't provide a load measurement -- the Windows drivers kick it onto battery for a timed period and measure the drain to guess the runtime -- apparently all their

Dear nut-upsdev, I writed one small function to test if batteries was really bad (using solis driver). Isn't so acurated but it's what we need. Just wait 100% batteries charge, turn off input, wait some time (10% from previst autonomy) and turn on input again. Looking startAutonomy - stopAutonomy we can know the basic batteries state. To scheduler the tests I have one new parameter on

Hi, I just got at work an MGE UPS Comet EX RT 7 and I can communicate fine with it through mge-shut, it detects correctly when on battery. I am using Nut 2.0.3 on Linux (RHEL 3). I am trying to simulate a low battery condition to test my shutdown procedure by setting lowbatt to 98%: driver.parameter.lowbatt: 98 but the ups reaches this value, goes to 97% and still no LB. I tried to change,

[Please remember to copy the list.] On Oct 15, 2013, at 8:45 AM, eric kreuwels wrote: > Hi Charles > > Thanks for your answer. Good questions/suggestions. I copied both the WinUPSC and the installer project on my GDRIVE and shared it with you: > https://docs.google.com/file/d/0B0mSjYYj84-6ZGM4MWZfMnFxbUU/edit?usp=sharing > > Archiving WinUPSC in the NUT GitHub would be my

fellows, I'm preparing the 2.0.5 release (as always, the Christmas release). I just wanted to be sure: - everybody's in sync (Carlos, IIRC you had some megatec things underway?!) - that the brief NEWS message fits everybody (analyzing the real diff between the Testing+trunk backport and the last trunk backport over Testing was a mess). Since I'm on vacation for a week as of next