similar to: Symmetra LX 16000

Hi all, I've been trying to build NUT (latest release source) on a pretty "standard" CentOS (RHEL style) linux box, to monitor an APC Symmetra UPS Unit which powers our server room and broadcasts information via SNMP to appropriate clients. I am having some trouble even encouraging NUT to build with snmp support, which doesn't seem to happen by default. I am curious if anyone

Hello. We've got an APC Symmetra with a network management card. We'd like to run Powerchute Network Shutdown on some of our older Linux servers, but no dice. I'm wondering if anyone has found a way to make NUT work with the network mangement card (it's a TCP connection, not SNMP or cable), or knows of any alternate PCNS clients Also, I was wondering if anyone on the list has

Hello. I need some help. I was running uw-imap on my IMAP server (so I am using mbox email files), but I was having trouble with Outlook 2013, so I decided to move to dovecot. At first things were looking much better, except that most of my folders, other than the Inbox, were not showing up. I started changing both the dovecot configuration and the folder structure of my mail files,

OK, can someone tell me what utterly moronic thing I am doing wrong? I have two roughly identical Linux system running NUT, and one works properly. The other almost does. The second system works well once everything is up, but after booting, the system does not have connectivity to the UPS. I have to manually run `upsdrvctl start backup`, `/etc/init.d/nut start`, and `upsd` to get NUT

Hello all, There is a new Windows package of NUT. It now contains nut-scanner binary. Note that there is a known issue with libupsclient.dll with nut-scanner. The scan of NUT servers using nut-scanner will not work for now. You can find it at : http://www.networkupstools.org/source/2.6/NUT-Installer-2.6.3-1.msi Please send feedback to the list. Regards, Fred -- Team Open Source Eaton -

    I just set up a UPS on a Debian Stretch system for my sister-in-law.  Obviously, I want NUT to properly shut down the unit when the battery gets low.  This means upsmon must be running and healthy.  When I run 'systemctl status nut-monitor`, I see the following in the journal: nut-monitor.service: Supervising process 778 which is not our child. We'll most likely not notice when

On 9/6/2014 12:47 PM, Charles Lepple wrote: > On Sep 6, 2014, at 12:39 PM, Leslie Rhorer <lrhorer at mygrande.net> wrote: > >> I made a number of hardware and software changes, including an upgrade to the latest software versions for that distro (Debian Wheezy), > > Can you be more specific about the changes? Well, I did an automated upgrade (apt-get upgrade), I changed

Hello. I have had NUT working for several years on my servers. Recently I made changes to the main server, where the UPS is local, and now upsd won't properly load there, which essentially disables the entire UPS shutdown system. I made a number of hardware and software changes, including an upgrade to the latest software versions for that distro (Debian Wheezy), although I did not

I just did a fresh installation of Debian Jessie on one of my servers, but NUT won't configure and install. When I try to install, I get the following: Setting up nut-client (2.7.2-1+b2) ... Job for nut-monitor.service failed. See 'systemctl status nut-monitor.service' and 'journalctl -xn' for details. invoke-rc.d: initscript nut-client, action "start" failed.

On Sep 6, 2014, at 12:39 PM, Leslie Rhorer <lrhorer at mygrande.net> wrote: > I made a number of hardware and software changes, including an upgrade to the latest software versions for that distro (Debian Wheezy), Can you be more specific about the changes? Key variables: * USB controller information (old and new hardware) * Kernel versions, for both working and non-working setups

Hi Leslie, 2014-09-29 17:14 GMT+02:00 Leslie Rhorer <lrhorer at mygrande.net>: > > I just did a fresh installation of Debian Jessie on one of my > servers, but NUT won't configure and install. When I try to install, I get > the following: > > Setting up nut-client (2.7.2-1+b2) ... > Job for nut-monitor.service failed. See 'systemctl status >

On Sep 6, 2014, at 4:16 PM, Leslie Rhorer <lrhorer at mygrande.net> wrote: > Oh, hey! That seems to have worked. I'm sure the UPS got plugged into a different port one of the (many) times the server was removed from the relay rack, and it was on a USB 3.0 port. I moved it to a 1.0 port and everything seems to be working just fine. The specifics of the motherboard and its USB

Has someone created a how to or a tutorial for installing/configuring DELL openmanage on centos ? --

Hello everyone. I have NUT up and running on three servers, and I can reach one of the servers from the other two, but two of the servers refuse the connection when I try to get the UPS information remotely. I've looked and looked, but I can't see what I've missed on the other two. From any of the three servers I can issue the command: `upsc <servername>@localhost` This

Leslie, This message is most appropriate for the NUT user list. I kept Rik Faith's and Nicholas Kain's copyright information because the tripplite_usb driver borrows heavily from the tripplite (serial) driver, but they are not responsible for the mess that I made in the USB driver. See below. On Dec 28, 2008, at 5:28 PM, Lelsie Rhorer wrote: > Gentlemen, > >

Hi, Perhaps as you know it Schneider Electric acquired APC, which involves the combination of APC and MGE. http://www.apc-mge.com MGE is an important contributor for NUT with for example Arnaud Quette, it's does not that the MGE strategy for the free software is stopped by Schneider Electric or APC. It is the good moment to make pressure on Schneider Electric, MGE and APC to support the

Hi, I'm trying to install xen+Debian Etch on a Geode LX system. Xen boots fine, but although the package "libc6-xen" is installed I have a large number of such errors: 4gb seg fixup, process syslogd (pid 1878), cs:ip 73:b7f24610 All processes triggers it, and from what I've found on the web it's a sign that libc6-xen is not recognized. Indeed:

Greetings all- I'm currently working with CentOS 5.x (various version 5.0 - 5.5) attempting to run it on a system based on the AMD Geode LX CPU. There are known issues with this CPU running Centos 5, specifically those listed here: http://bugs.centos.org/view.php?id=2552 The kernel and system run fine on the Geode LX, but the installer detects the CPU as i586. Since there is no i586 kernel

I am attempting to use wine to run a windows application called VideoReDo. I'm getting an error when I try to install the program, however, and I don't know how to proceed. The error is: fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT" If I ignore the error, I get a further error: err:seh:setup_exception_record stack overflow 896

I have SAMBA 2.0.7 running on about 20 Solaris 9 servers around the US. One location is experiencing interruptions for Windows XP clients who map to the SAMBA server. There are no known changes to Solaris or SAMBA to explain the change. The problem is very random. I have seen postings that discuss how XP uses ports 139 and 445. Is there a way to block port 445 in SAMBA 2.0.7? The