similar to: Systemd sequencing problem in Fedora 16,17

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: > The opposite opinion is that programs should be quiet until asked to > squeak (e.g. by restarting with higher debug verbosity... "that would help > troubleshooting why the rack went down last week, right!" says the sysadmin > me). That's a fair summary but my opinion is: daemon-type

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: > The opposite opinion is that programs should be quiet until asked to > squeak (e.g. by restarting with higher debug verbosity... "that would help > troubleshooting why the rack went down last week, right!" says the sysadmin > me). That's a fair summary but my opinion is: daemon-type

I just hooked up an old Best Fortress (with new batteries). Those things are built like a tank, and it works out of the box in Fedora 14 (nut-2.6.2) thanks to the bestfortress driver still in the project. It had disappeared for 2.0, but I sent it in for 2.2, and you guys kept it going. -- Stuart D. Gathman <stuart at bmsi.com> Business Management Systems Inc. Phone: 703

Hi, I looked into this some time back... My reading was that: * The PIDPATH (for root-owned daemons) could be desired in a secured location where only root may write (so unprivileged processes running as `nut`, e.g. random scripts called from upsmon, can not compromise important stuff - say, replace `upsmon.pid` with a content of `1` so the next `upsmon -c command` might signal `init` and bring

I'm following up on a request from a pkgsrc user to improve the package, and that's leading me to thinking part of the issues are in nut, vs the package. Setting aside daemons that run as root vs not, there are two kinds of directories, using the BSD hier(7) scheme: /var/db/nut: - state files intended to persist across reboots /var/run/nut: - pidfiles - (probably)

I bought this UPS to use with NUT. I've used Belkin, APC, CyberPower, Best, Powerware upses with NUT on dozens of servers beginning with RHEL3. http://www.amazon.com/Tripp-Lite-Display-Protection-SMART1500LCDT/dp/B009TZTGWK Since this was advertised as USB HID, I didn't expect any problems. Bad idea (should have gotten the Cyberware with somewhat less runtime). Initially, it seems to

Cheers, I don't think there is any particular strategy, at least not one I'd know of either :) So it is mostly ad-hoc, to keep smaller verbosity numbers reasonably quiet, and sufficient info to see the logic progression at a given debug level (e.g. if major milestones of a routine are logged at level N, further traces like "I saw value X here" would be N+1 or more). De-facto

I could not make the bestfortress driver 0.02 work for my Best Fortress LI675VA, so I have made a patch for the driver. The reason was, that all responses are preceded and terminated by CR LF, but the driver would discard everything after the first CR LF. The following patch discards everything up to the first LF. It also adds a debugging feature of displaying the accepted data (level 5 i.e. -D

Hello list, I have explored https://github.com/networkupstools/nut repository and found that Riello UPS added into list of supported UPS. But current package for most distribution it's nut-2.6.5 which doesn't have Riello's models. Do we need to wait next upcoming nut release to get start with Riello? I tried to install from source but stuck: # git clone

On Tue, Jan 27, 2015 at 5:53 AM, Charles Lepple <clepple at gmail.com> wrote: > On Jan 24, 2015, at 12:45 AM, Ryan Sizemore <ryan.sizemore at gmail.com> > wrote: > > Hello, > > I am trying to get nut running on a Windows 2012 R2 server (x64). I am > using the MSI release of 2.6.5-3. > > > I am not sure why they are not listed on the main download page,

On Jan 24, 2015, at 12:45 AM, Ryan Sizemore <ryan.sizemore at gmail.com> wrote: > Hello, > > I am trying to get nut running on a Windows 2012 R2 server (x64). I am using the MSI release of 2.6.5-3. I am not sure why they are not listed on the main download page, but there are actually three Windows MSI releases after that: http://www.networkupstools.org/package/windows/ I

Hi- I just upgraded R to 3.0.0 from 2.15.1 (which worked fine). When I started trying to install updated versions of the libraries, I saw the following error: > install.packages("lme4") Installing package into 'c:/Docume~1/melissa/R/win-library/3.0' (as 'lib' is unspecified) Warning in install.packages :

Hello, I am trying to get nut running on a Windows 2012 R2 server (x64). I am using the MSI release of 2.6.5-3. The attached UPS is an APC xs1500 (model bx1500g). The connection is an RJ45 to USB cable. Here is my ups.conf: [xs1500] driver = usbhid-ups port = auto desc = "APC Back-UPS xs1500" The problem I am encountering is upsd crashing with an 'Out of memory' error. I can

# reboot Connection to 192.168.5.81 closed by remote host. Connection to 192.168.5.81 closed. ppo at admin:/tmp$ ssh root at 192.168.5.81 root at 192.168.5.81's password: Last login: Tue Jul 30 14:10:49 2013 from pc-ppo.kh.ektos OpenBSD 5.3 (GENERIC.MP) #58: Tue Mar 12 18:43:53 MDT 2013 # ps -aux | grep ups root 2254 0.0 0.0 324 700 p0 S+ 5:29PM 0:00.00 grep ups # ps -aux

My apologies, I don't know why my brain is stuck on NTPD, I meant UPSD. Regards Ge-org Brohammer -----Original Message----- From: Nut-upsuser [mailto:nut-upsuser-bounces+ge-org=kingbro.co.za at lists.alioth.debian.org] On Behalf Of Ge-org Brohammer Sent: 28 June 2013 01:06 PM To: nut-upsuser at lists.alioth.debian.org Subject: [Nut-upsuser] Server 2012 - 64bit NTPD Crash Good day I?m

I am looking at bestfortress and trying to figure out and fix some things, which is causing me to try to improve logging first. A few questions: 0) The developer guide doesn't seem to address any of this, or did I miss it? 1) It seems upsdebugx prints to stdout instead of syslog if in foreground. That's great but I didn't figure it out from docs. 2) I didn't find a plan for

Description: Replace many usleep and some sleep calls with nanosleep. usleep is stated in its manual page as removed by POSIX. Contrary to its predecessors, nanosleep semantics is well defined. The replacement, which is mostly in drivers, is untested. Supplements http://bugs.debian.org/633791. Last-Update: Sat, 13 Aug 2011 14:04:48 +0300 Index:

Good day I?m trying to get NUT working on Server 2012 64-bit. I can start the ntpd but as soon as I connect with upsc, the NTPD process exits with the following debug output: c:\Program Files (x86)\NUT\sbin>upsd -DDDD Network UPS Tools upsd 2.6.5-3780M 0.000000 listen_add: added 127.0.0.1:3493 0.000000 listen_add: added ::1:3493 0.015599 setuptcp: try to bind to ::1 port

On Jul 30, 2013, at 3:28 AM, Pavel Potcheptsov (EKTOS) wrote: > another attempt: > # upsd > Network UPS Tools upsd 2.6.5 > fopen /var/db/nut/upsd.pid: No such file or directory > listening on 127.0.0.1 port 3493 > listening on ::1 port 3493 > Can't connect to UPS [senpro] (riello_ser-senpro): No such file or directory We need to determine whether upsd and the driver are

Best fortress support was understandably dropped, but we still use them, and someone else may want the driver I ported to nut-2.0. We also often attach the serial cable from a UPS to a network terminal server, since servers these days don't come with very many serial ports. (They call them "legacy" ports.) I submitted a patch to support these for nut-1.x, and it was rejected