similar to: /var/state not accessible

My understanding is that NUT provides a mechanism to shut down multiple systems protected by multiple UPS's in a given order. For example to shutdown the users before their NFS server. 1. man ups.conf says sdorder Optional. When you have multiple UPSes on your system, you usually need to turn them off in a certain order. upsdrvctl shuts down all the 0s, then the 1s, 2s, and so on. To

Hi, I find the following feature with MGE Pulsar evolution 2200: [root@hat ups]# /usr/sbin/upsd Network UPS Tools upsd 2.0.2 Connected to UPS [hat_PC_ups]: mge-utalk-ttyS0 Synchronizing........ giving up [root@hat ups]# upsc hat_PC_ups@localhost Error: Data stale Is there a way to make the sync part longer? After 5-10 seconds, however, things work fine: [root@hat ups]# upsc

Is anyone besides me using gcc 4.*.*? I noticed that NUT generates an enormous amount of warning noise with that compiler, mostly due to implicit casts between signed/unsigned pointer types. Any volunteers to de-noise the code a bit? The easy way is to insert typecasts; the better way is to actually take care about signedness. -- Peter gcc -I../include -O -Wall -Wsign-compare -c -o everups.o

Hi! On my FreeBSD 12.0-RELEASE-p7 server I was unable to retrieve the correct information from my two UPS. Every time only the first UPS will returned when I entering "upsc apc900" or "upsc apc901". I don't know why (Bug or configuration issue on my side?!). I have downloaded the latest source code and with my "patch" I was able to get the right information

Hi I'm sending this to you as it appears that you are the person who looks after and/or supervises the code for NUT's Belkin drivers. I'm using the address you use for the Nut-upsdev mailing list ( selinger at mathstat.dal.ca ). Anyway... I have a Belkin Universal UPS and, having just upgraded my Fedora Core system from 4 to 5 and had to go back through the system RC files

I'm trying to setup a server controlling 8 ups, 6 APC Smartups 1500 and two 1000. Because of the number of ups, i connected them using usb cables. I'm using Debian Etch AMD64 and nut 2.2.0 from testing (already tried 2.0 from stable, but had problems reading the ups serials and all the following problems of 2.2). This is my ups.conf: [ups2] driver = usbhid-ups port =

Hi Peter Now I can get subdrivers to have ups.conf/command-line options, I've started looking at making the newhidups belkin-hid subdriver have the wait and wait-on-shutdown behaviour in the same was as belkinunv, and having just gone back and gone "yuck!" at my huge comments in my revised belkinunv source, I decided to clear out all the extraneous commentary in my

I recently installed NUT 2.2.1 and set it up with a Belkin F6C100-UNV. I can monitor it via serial (belkinunv) or USB (usbhid-ups) cable, and both do seem to work fine, but I would prefer USB to avoid having to add a PCI serial card to the machine. I had to unplug something else to try it with a serial cable. Using 'belkinunv', there's a "-x wait" option: [ from

Description: Fix warning: variable set but not used [-Wunused-but-set-variable]. bugs.debian.org/633756. Related drivers were not tested. Last-Update: Sat, 13 Aug 2011 14:04:48 +0300 Index: b/drivers/belkinunv.c =================================================================== --- a/drivers/belkinunv.c 2011-05-31 13:36:49.000000000 +0300 +++ b/drivers/belkinunv.c

All, I just bought a Belkin F6C1100-UNV and am trying to get it to work with NUT. I have tried many drivers ( "belkin", "belkinunv", "genericups upstype=4", and "genericups upstype=7", "bestups", "fentonups"). None of them seem to work. Does anyone have any experience with this device? If there is some utility that you all use to

I'm trying to set up a belkin f6c1100-unv UPS to work with nuts. From reading the mailing list, it sounds like the belkinunv serial driver should work and that the USB driver is potentially troublesome. Is this a correct impression? Also I may have missed this but if I do go with the serial (or USB port) is there any simple command line method for verifying basic connectivity? The

Zaid, I have a Belkin F6C800-UNV which has both a serial and USB connector. The serial connection is already working with the Belkinunv driver. I will connect via the USB and then compare both sets of variables. This should allow me to correlate and shed some light on the meaning of many of Belkin's non-standard "Usage" descriptors. With this information, it should be very easy

For the record, I was able to get the following working: Device: Belkin F6C1500-TW-RK Driver: belkin I tried the "belkinunv", which I use for my F6C1100-UNV, but it didn't work. At least there was a driver that worked! :-) Feel free to add it to the list of "tested" configs. Thanks, Dave ---------------------------------------------------------- Are Your Friends

I upgraded from V2.2 to V2.4. I use the "upslog" command to log the values of my belkin ups (belkinunv via serial port). It would occasionally start to record garbage, but it would always go back to normal in V2.2 if I restarted. In V2.4 it would not record the values, and the process would fail after the next interval had passed. I had set if for 300 seconds. I walked through the

While working on the mge-hid subdriver, I wanted to add the 'beeper.mute' command. Unfortunately, the description I intended to use was used already by the 'beeper.off' instcmd: CMDDESC beeper.off "Temporarily mute the UPS beeper" Now of course we could add another instcmd 'beeper.reallyoff', but instead I would prefer to bite the buller and do the following:

I looked through the faq, but couldn't find an answer to this. I'm trying to configure nut-2.0.4-26 on SuSE linux 10.2. In ups.conf, I have [myups] driver = belkinunv port = /dev/undefined desc = "Local UPS" I'm trying to find out what the port should be set to. lsusb shows: Bus 001 Device 005: ID 050d:0980 Belkin Components Device Descriptor: bLength

On Fri, 9 Jun 2017, Robbie van der Walle wrote: > # NOTIFYMSG - change messages sent by upsmon when certain events occur > # > # You can change the default messages to something else if you like. > # > # NOTIFYMSG <notify type> "message" > # > # NOTIFYMSG ONLINE "UPS %s on line power" > # NOTIFYMSG ONBATT "UPS %s on battery" > #

Dear fellow NUT developers, after almost exactly two years as a NUT developer, I have concluded that this would be a good time to retire from active development. The project is in good shape, and the driver I was most involved with (usbhid-ups) is in better condition than ever, due to the excellent recent work of Arjen de Korte. Having already scaled back my activity for the last 6 months, I

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: >

This is the patch to include SVN revision level in version number displays. There should be two enclosures; the patch itself and a new source file. common/upsversion.c. upversion.c defines a single function. upsversion(), that returns a version string for display. Some Makefile trickery ensures that this file will be recompiled whenever the project's SVN revision level has changed since it