Re: [Nut-upsuser] Trying to update the official docs for nut on FreeNAS - help needed to ensure it's written correctly

On Fri, 30 Mar 2018, Stilez Stilezy wrote: My own UPS setup is an APC SUA 1500i + AP9630 card, and the default user on the UPS has been changed, so that's what I'll test anything with, to check my understanding and appropriate inputs. Perhaps this question is even more off-topic, but given

Re: [Nut-upsuser] CentOS 7, systemd, nut-monitor, and failing to shut down the UPS

On Thu, 1 Feb 2018, Lee Damon wrote: I've "fixed" this problem by modifying the nutshutdown script: #!/bin/sh # stop nut driver to free up access to the device /sbin/systemctl stop nut-driver # make sure it has time to die sleep 2 # check to see

[Nut-upsuser] Default value for ondelay

On Fri, 2 Feb 2018, nut.user.u...@neverbox.com wrote: I have an older box set up this way for continuous integration, and it needs to see more than a few seconds of power loss for the "always turn on" BIOS setting to work. I forget how many different intervals I tried, but 30

Re: [Nut-upsuser] testing shutdown: pc not restarting; and "ups unavailable" messages

On Thu, 1 Feb 2018, nut.user.u...@neverbox.com wrote: I am installing a UPS with NUT on Ubuntu for the first time. I could follow the instructions up to "testing shutdowns" but on executing the recommended command the computer shuts down and never comes back on, Have you checked the BIOS

Re: [Nut-upsuser] Debian 9.3 nut-client.service reports itself as nut-monitor.service

On Thu, 28 Dec 2017, Charles Lepple wrote: On Dec 28, 2017, at 6:35 AM, Roger Price <ro...@rogerprice.org> wrote: It would be clearer to users if the service unit file was also called /lib/systemd/service/nut-monitor.service From what I can tell, the "nut-client.service"

[Nut-upsuser] Debian 9.3 nut-client.service reports itself as nut-monitor.service

I reported a minor bug in nut 2.7.4 on Debian stretch and got the number 885592 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885592 The systemd service unit /lib/systemd/system/nut-client.service reports itself as nut-monitor.service on command systemctl status nut-client.service. It

Re: [Nut-upsuser] APC SmartUPS 1000 via usb

On Sun, 17 Dec 2017, Hervé Bastet wrote: Bonjour, Je fais suite au message que vous avez posté en 2015 : http://lists.alioth.debian.org/pipermail/nut-upsuser/2015-February/009568.html J'ai le même problème et ne trouve pas la solution. Comment vous en êtes-vous sorti ? D'avance, merci pour

Re: [Nut-upsuser] Debian 9 : Can't open /etc/nut/upsd.users: Permission denied

On Sun, 10 Dec 2017, Jim Klimov wrote: I am not sure the rights offered in that bug are fully ok: generally you wouldn't want the configs to be writable by the service daemon if you can avoid it (so if it's hacked - it can be abused to a lesser extent). I think the only writable bit is the

Re: [Nut-upsuser] Debian 9 : Can't open /etc/nut/upsd.users: Permission denied

On Sun, 10 Dec 2017, Charles Lepple wrote: Either way, the default permissions are under the packager's control, so I would recommend that you file a bug with Debian: https://www.debian.org/Bugs/Reporting (feel free to mention the bug number here) Debian Bug Tracker told me that the URL is

[Nut-upsuser] Debian 9 : Can't open /etc/nut/upsd.users: Permission denied

I installed nut 2.7.4-5 on a fresh Debian 9.2.1 system. I updated the configuration files, started nut in standalone mode, and got the error message Can't open /etc/nut/upsd.users: Permission denied This is because the file has ownership and permissions -rw--- 1 root nut 91

Re: [Nut-upsuser] NUT Restart Issue

On Fri, 8 Dec 2017, Common Granger wrote: I am using Ubuntu 16.04 LTS using NUT 2.7.4 with an APC Back-UPS RS1000G.  The problem is I do test shutdown using  sudo upsmon -c fsd and my computer shuts down ok but no matter how long I wait it never turns back on.  Is there a way to fix this.  I

Re: [Nut-upsuser] Help, please! Driver for APC Back-UPS 390 Watts / 700 VA, 230V, AVR, IEC Sockets

On Mon, 4 Dec 2017, Mikael Imperatori Festa wrote: I had a look on the website, but I can¹t see a detailed list of supported units. Try installing and using apcupsd. Does it work correctly with the BX700UI? Which protocol is it using? Roger___

Re: [Nut-upsuser] Help, please! Driver for APC Back-UPS 390 Watts / 700 VA, 230V, AVR, IEC Sockets

On Mon, 4 Dec 2017, Mikael Imperatori Festa wrote: driver = apcupsd port = auto I meant the « APC UPS Daemon » at http://www.apcupsd.org/ Does this support your UPS unit? If so, what protocol is it using? What is the model number of your unit? BX650CI ?

Re: [Nut-upsuser] Help, please! Driver for APC Back-UPS 390 Watts / 700 VA, 230V, AVR, IEC Sockets

On Fri, 1 Dec 2017, Mikael Imperatori Festa wrote: Hi there, I tried all the driver on the list for this UPS, but they don’t work. Could you help me please? Have you tried with apcupsd? Which protocol does apcupsd use for the Back-UPS 390 ? Roger This e-mail message may contain

Re: [Nut-upsuser] debian 8 "jessie" nut 2.7.2 slaves not shutting down

On Thu, 19 Oct 2017, Drew Plaster wrote: The topology is: UPS TOPAPC, Data link to master, Power supply to master, slave1 and slave2 UPS MIDAPC, Data link to master, Power supply to master, slave1 and slave2 UPS BOTAPC, Data link to master, Power supply to master,

Re: [Nut-upsuser] debian 8 "jessie" nut 2.7.2 slaves not shutting down

On Wed, 18 Oct 2017, Drew Plaster wrote: MASTER SYSTEM nut.conf MODE=netserver ups.conf [TOPAPC] driver = usbhid-ups port = auto pollonly serial = "IS1309002707" desc = "TOPAPC" [MIDAPC] driver = usbhid-ups port = auto

Re: [Nut-upsuser] debian 8 "jessie" nut 2.7.2 slaves not shutting down

On Wed, 18 Oct 2017, Drew Plaster wrote:     there are three APC smart ups connected via usb cables to the master system, the master system shuts down as expected but the slave systems never shutdown eventhough I believe that all the configs are properly set the slaves should

[Nut-upsuser] On getting notify-send to work

The program ``wall´´ used by NUT to put notifications in front of the users is now well past it's best-before date. It has not been internationalized, does not support accented letters or non-latin characters, and is ignored by popular desktop environments such as Gnome and KDE. It's

Re: [Nut-upsuser] How do I configure NUT?

On Thu, 3 Aug 2017, Roger Price wrote: On Thu, 3 Aug 2017, Tomas Larsson wrote: Hi there. I need some advise on how to configure NUT, if it is possible to do it. My UPS, a Compaq R3000 I thought the Compaq R3000 Line was a Series of laptops designed and built by Hewlett-Packard Corporation

Re: [Nut-upsuser] How do I configure NUT?

On Thu, 3 Aug 2017, Tomas Larsson wrote: Hi there. I need some advise on how to configure NUT, if it is possible to do it. My UPS, a Compaq R3000 I thought the Compaq R3000 Line was a Series of laptops designed and built by Hewlett-Packard Corporation, not a UPS? has three individual

Re: [Nut-upsuser] Power Down ESXi before SAN

On Sun, 16 Jul 2017, Mike Schaffner wrote: I have 2 APC UPS systems, one is connected to my ESXi host and the other to my FreeNAS.   The battery for the FreeNAS will run out before the battery for the ESXi, so I need ESXi to shutdown first.   If I wait until BatteryLow on ESXI, it will be too

[Nut-upsuser] Trying to understand sdorder

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

[Nut-upsuser] Three wishes for upsmon

Here are three wishes for the future of upsmon: 1. The NOTIFYMSG texts should allow UTF-8 encoded messages. 2. The flags used in NOTIFYFLAG should be extended to include USER. This flag says that the message is to be sent to the notify daemon, perhaps with the command notify-send -a NUT

[Nut-upsuser] Ubuntu specific configurations

On Tue, 4 Jul 2017, Charles Lepple wrote: Since you are using Ubuntu, upsmon.conf should contain "NOTIFYCMD /sbin/upssched". Similarly, upssched.conf should contain "CMDSCRIPT /usr/local/bin/upssched-script". Thanks. I have updated the Configuration Examples to include these Ubuntu specific

Re: [Nut-upsuser] Help with Elite 800VA usb UPS

On Mon, 3 Jul 2017, Andrea de Lutti wrote: MONITOR dummy@artu 1 user pass master SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /usr/local/bin/upssched-script Hi, As far as I can see, what you are getting in syslog corresponds correctly to what you have specified. You have specified that

[Nut-upsuser] Configuration Examples

I have written up a collection of NUT configurations. The chapters are 1. Introduction 2. Simple server with no local users 3. Server with multiple power supplies 4. Workstation with local users 5. Workstations share a UPS 6. Workstation with heartbeat 7. Workstation with timed shutdown

Re: [Nut-upsuser] CentOS rpm package installation

On Thu, 22 Jun 2017, Ambrogio Coletti wrote: Hello I am not a linux expert. The output of uname -r on my system returns: 2.6.32-696.3.1.el6.x86_64 Hi, Linux 2.6.32 was released 3 December, 2009. That's nearly 8 years ago. Linux has now reeched version 4.11. hence I am trying to install

Re: [Nut-upsuser] Apple Mac slave

On Fri, 9 Jun 2017, Robbie van der Walle wrote: ... and also still open is the notification on the Mac. If notify-send is available on the Mac, then perhaps this will work: In upsmon.conf on the Mac you need NOTIFYCMD /usr/sbin/upssched(or wherever this goes on a Mac) NOTIFYFLAG

Re: [Nut-upsuser] Apple Mac slave

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 "message" # # NOTIFYMSG ONLINE "UPS %s on line power" # NOTIFYMSG ONBATT "UPS %s on

Re: [Nut-upsuser] Apple Mac slave

On Thu, 8 Jun 2017, Robbie van der Walle wrote: After the first test and the NAS is restarted I had to change the setting battery.charge.low again to 80  Does the NAS DSM reset battery.charge.low to 10 or is it internal to the UPS? You will have to experiment by disconnecting the UPS

Re: [Nut-upsuser] Apple Mac slave

On Thu, 8 Jun 2017, Robbie van der Walle wrote: The "upsrw" command contacts upsd, so it sounds like you should be able to add a user to upsd.users on the NAS, and then run something like this on the Mac:   upsrw -s battery.charge.low=80 -u upsmaster -s sekret UPS@synology

Re: [Nut-upsuser] Apple Mac slave

On Thu, 8 Jun 2017, Robbie van der Walle wrote: I suppose I have to use -u for user? Which user? and -p  for password?  Sorry, my typo, it should be upsrw -s battery.charge.low=80 -u upsmaster -p sekret UPS@NAS upsmaster is the "user" declared in the NAS file upsd.users in square

Re: [Nut-upsuser] Apple Mac slave

On Wed, 7 Jun 2017, Robbie van der Walle wrote: Out of curiosity, when you shut down the NAS, do you run the command "upsdrvctl shutdown" ?  Do you see or hear anything to suggest that the delayed UPS shutdown has happened? I don’t know where to search to answer this. The

Re: [Nut-upsuser] Apple Mac slave

On Wed, 7 Jun 2017, Robbie van der Walle wrote: I am running NUT on a Synology NAS with attached a USB APC UPS. Do you have upsd and upsmon running as daemons on the Synology DSM? Yes I have them both running on the Synology DSM:  root      7236     1  0 Jun01 ?       

Re: [Nut-upsuser] Apple Mac slave

On Tue, 6 Jun 2017, Robbie van der Walle wrote: I am running NUT on a Synology NAS with attached a USB APC UPS. Do you have upsd and upsmon running as daemons on the Synology DSM? Does the NAS shut down (and restart) correctly when wall power fails? I am trying to connect and shutdown a Mac

Re: [Nut-upsuser] POWERCOM-UPS-USB : UPS Shutdown

On Wed, 17 May 2017, Dinow Hsieh wrote: CC. Does a Ubuntu user with no xterm window open see the message as part of the ==> The root and remote user(ssh-putty) get the broadcasting message all from

Re: [Nut-upsuser] Fw: [Nut-upsdev] POWERCOM-UPS-USB : UPS Shutdown

On Tue, 16 May 2017, Dinow Hsieh wrote: BB. Could you show us the output of command "upsc pcmups"? ==> Yes. Below 2 mode were the outputs of command "upsc pcmups" battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 30 battery.date: 2010/12/20 ... ups.date: 2010/12/20

Re: [Nut-upsuser] Fw: [Nut-upsdev] POWERCOM-UPS-USB : UPS Shutdown

On Mon, 15 May 2017, Dinow Hsieh wrote: ==> I have tried this command "upsdrvctl shutdown" as below results (However the UPS still sustain the power)     Network UPS Tools - UPS driver controller 2.7.1     Network UPS Tools - Generic HID driver 0.38 (2.7.1)     USB communication driver 0.32   

Re: [Nut-upsuser] Good Day NUT

On Thu, 11 May 2017, Dinow Hsieh wrote: ==> AA. I confront an issue that can't shutdown the ups    With the nut, I can get the ups status(upsc) and shutdown the linux-ubuntu when power failure occurs(upsmon)  But don't know which configuration I ignore to setup for ups shutdown Hi, Could

Re: [Nut-upsuser] battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error

On Tue, 4 Apr 2017, Arnaud Quette wrote: Hi Jon, Stuart and the list 2017-04-04 1:09 GMT+02:00 Stuart Gathman : Which NOTIFYCMD is run when there is an ALARM? Have you specified that in your upsmon.conf? And that is the question of the hour.  How do you

Re: [Nut-upsuser] how do you test (nagios) that upsmon is connected?

On Mon, 3 Apr 2017, Spike wrote: I'll see if I can implement it some time soon. Hi Spike, I tested the heartbeat proposal on openSUSE 13.1 and 42.2, and made some changes so that it would work. I wrote out some documentation which includes the required changes, which you will find at

Re: [Nut-upsuser] battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error

On Mon, 3 Apr 2017, Jon Bendtsen wrote: On 03/04/17 17.10, Roger Price wrote: On Mon, 3 Apr 2017, Jon Bendtsen wrote: Power seem to be lost immediately. But my APC Smart-UPS 1500 always reported everything OK. battery.charge : 100 ... battery.mfr.date : 2005/08/26 Hi

Re: [Nut-upsuser] battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error

On Mon, 3 Apr 2017, Jon Bendtsen wrote: Power seem to be lost immediately. But my APC Smart-UPS 1500 always reported everything OK. battery.charge : 100 ... battery.mfr.date: 2005/08/26 Hi, Could you confirm that the battery is nearly 12 years old? Roger

[Nut-upsuser] Heartbeat validation of NUT integrity

This note describes a heartbeat technique for validating the integrity of a NUT installation. Introduction A NUT configuration may run for months with little or no output to a system administrator to assure that the combined processes are running correctly. The technique

Re: [Nut-upsuser] how do you test (nagios) that upsmon is connected?

On Sat, 1 Apr 2017, Stuart Gathman wrote: On 04/01/2017 03:14 PM, Dan Craciun wrote: On my Nagios monitoring system I use check_nut_plus (that in turn calls upsc) to monitor the status (ups.status), load (ups.load), battery charge (battery.charge) and runtime (battery.runtime). If these

Re: [Nut-upsuser] Is a timer a file?

Hi Arnaud, On Wed, 22 Mar 2017, Arnaud Quette wrote: The technique is very general and is to send SIGUSR1/SIGUSR2 to the upsd daemon.  SIGUSR1 and SIGUSR2 are events just like ONBATT and ONLINE. The patch runs successfully on my opensuse 13.2 box, and solves my problem. In

Re: [Nut-upsuser] Is a timer a file?

On Tue, 21 Mar 2017, Arnaud Quette wrote: Hi Roger, reviving this discussion, since we have a Github ticket for 2.7.5: https://github.com/networkupstools/nut/issues/293 ... I've made some additions to clarify things on the timer, and complete the script:

Re: [Nut-upsuser] NUT - General Concept Question

On Thu, 2 Mar 2017, Garrett Michael Hayes wrote: I would like to set up a Linux host as a central monitoring system for UPSs throughout our network.  I’d like that system to be able to see the various UPSs basically in one of two ways: 1)  Tapping into a native network interface on the

Re: [Nut-upsuser] NUT configuration complicated by Stonith/Fencing cabling

On Sun, 5 Feb 2017, Tim Richards wrote: Setup: Active/Passive Two Node Cluster. Two UPSes (APC Smart-UPS 1500 C) with USB communication cables cross connected (ie UPS-webserver1 monitored by webserver2, and vice versa) to allow for stonith/fencing OS OpenSuse Leap 42.2 NUT version

Re: [Nut-upsuser] NUT Client shuts down when performing runtime calibration on APC UPS

On Wed, 11 Jan 2017, Merk - Oliver wrote: nas4free: /# more /usr/local/bin/upssched-cmd #!/bin/sh I would strongly recommend specifying which script interpreter is to be used: dash, bash, csh, ksh, ... For example #!/bin/bash There seem to be too many case statements in this script.

Re: [Nut-upsuser] unclear about expected shutdown behavior

On Sat, 24 Dec 2016, Spike wrote: ... from reading the docs it seems the UPS should power off, is that the case? Yes, The UPS should be sent a "delayed shutdown" command, upsdrvctl shutdown, to tell it to shut down _after_ the box. The amount of the delay can be set in ups.conf. The UPS

Re: [Nut-upsuser] NUT Client shuts down when performing runtime calibration on APC UPS

On Tue, 20 Dec 2016, Merk - Oliver wrote: Last week I need to change the battery pack and then I needed to perform a runtime calibration. I used the web interface of the AP9630 card to start the runtime calibration. However, after 2min. of runtime calibration the SAN shut down! This is

Re: [Nut-upsuser] Can't get NUT slave to connect to master

On Fri, 25 Nov 2016, Jonah Naylor wrote: I'm still getting "Connection refused on the client cgi screen as well as in the shell it gives me UPS upsname@ipaddresshere is unavailable... You reported that access works correctly from elsewhere on the master subnetwork. Does access from the

Re: [Nut-upsuser] Can't get NUT slave to connect to master

On Fri, 25 Nov 2016, Jonah Naylor wrote: upsd : ipaddressofclientgoeshere If it were me I would write upsd : ipaddressofclient :\ spawn (/bin/mail -r hosts.allow@localhost\ -s '%s@%h accepted access to %d from %c'\ sysadmin@somedomain) &

Re: [Nut-upsuser] Can't get NUT slave to connect to master

On Fri, 25 Nov 2016, Jonah Naylor wrote: I don't think nut is built with TCP wrappers support, although the package is listed as depending on libwrap... Why would you have such a dependency if nut didn't use TCP Wrappers? I ran this command: ldd /sbin/upsd | grep libwrap.so and it has

Re: [Nut-upsuser] Can't get NUT slave to connect to master

On Thu, 24 Nov 2016, Jonah Naylor wrote: I installed Nut via apt-get, not from source (which I'd rather stick with if possible just for ease of security updates etc) - so I'm not too sure if TCP wrappers are there or available... This could be the problem, am I still able to add the wrappers

Re: [Nut-upsuser] Can't get NUT slave to connect to master

On Thu, 24 Nov 2016, Jonah Naylor wrote: Hi can anyone please help. Although I have two servers in the same cabinet/room and sharing the same UPS - they're on different networks. I've tried everything I can find online, but whatever I do I can't get the slave nut client to connect to the

Re: [Nut-upsuser] Help with failing Nut slave/client connection

On Sat, 15 Oct 2016, Jonah Naylor wrote: HI again, Sorry I didn't mean to cause a security debate. I'd like things to be secure of course, but I've got a dilema that I don't use DHCP and instead have a block of static IPs from my ISP. So my nut server has 68.68.452.02 for example and my two

Re: [Nut-upsuser] UPS Shutdown

On Wed, 5 Oct 2016, Jeff Bowman wrote: I’m trying to better understand OffDelay and OnDelay: http://networkupstools.org/docs/man/usbhid-ups.html#_extra_arguments My server requires ~3½ minutes to shut itself down. Considering this I’m comfortable setting OffDelay to 300 (five minutes). How

Re: [Nut-upsuser] NUT unable to resolve host despite DNS working.

On Sat, 17 Sep 2016, Yevgeniy Kuksenko wrote: Hello all, I have been having a problem with upsmon on Fedora 24 on boot. NUT is configured as a netclient to a Raspbian NUT server. After boot up upsmon repeatedly says "connect failed: No such host". It is not able to connect at all until the

Re: [Nut-upsuser] Help with failing Nut slave/client connection

On Mon, 12 Sep 2016, Jonah Naylor wrote: I have two linux servers both with static IPs not using NAT. My slave can't connect to my host. Whatever I try. I assume that these two machines are on the same LAN, so here are a few suggestions. Can you ping from each one to the other? Can you ssh

Re: [Nut-upsuser] How to get started (Windows)

On Sun, 11 Sep 2016, Jeff Bowman wrote: But first I have to get it working :-) Have you seen https://grafenthal.de/wiki/index.php/Installation_Network_UPS_Tools_%28NUT%29_unter_Windows_Server_2012_USB which shows a working NUT configuration under Windows Server 2012. It's in german, but

Re: [Nut-upsuser] Errors when running on Windows

On Fri, 9 Sep 2016, Jeff Bowman wrote: All of this leads me to the conclusion that NUT isn't working on my system. Here is my configuration: What command(s) do you use to start NUT? Do usbhid-ups, upsd and upsmon start up? Roger ___ Nut-upsuser

Re: [Nut-upsuser] How to get started (Windows)

On Thu, 8 Sep 2016, Jeff Bowman wrote: That said, is there a way to manually poll the driver for UPS/power line status? I ask because I can foresee a scenario such as this: ... So I'd like to be able to remote in and check the status to make sure everything is OK. If not, then I can manually

Re: [Nut-upsuser] How to get started (Windows)

On Thu, 8 Sep 2016, Jeff Bowman wrote: I’ve been able to get the latest Windows port installed on my Hyper-V 2012 R2 instance and start the service. But as I’m an absolute beginner I’m not sure how to proceed further. I’ve browsed the archives, but discussions here tend to assume at least an

Re: [Nut-upsuser] Any good SNMP tutorial?

On Wed, 17 Aug 2016, Brian Hilmers wrote: Hello, I am looking for good instructions on how to configure NUT to receive SNMP Trap signals and how to shutdown a server. My setup is: NUT: version 2.7.1-1ubuntu1, from package OS: Ubuntu 14.04.5 LTS UPS: Tripp Lite SMART3000RM2U The only thing I

Re: [Nut-upsuser] Best practice to shutdown hosts which has not NUT via upssched

On Thu, 14 Jul 2016, Dmitri Stepanov wrote: Some of those hosts haven't NUT including upsmon (and other software which is not included by suppliers of the hosts) for a number of reasons. I don't need to inform not-NUT hosts about any UPS events, etc... but only shutdown all the hosts after

Re: [Nut-upsuser] Best practice to shutdown hosts which has not NUT via upssched

On Wed, 13 Jul 2016, Dmitri Stepanov wrote:    shutdown-all-hosts.sh contains: # Linux hosts HOSTLIST="sim iogate br" for host in $HOSTLIST do ... ssh $host halt -p ... done    shutdown-all-hosts.sh works fine if it runned manually.    But it does not work even if I insert sleep 30 sec

Re: [Nut-upsuser] Best practice to shutdown hosts which has not NUT via upssched

On Wed, 13 Jul 2016, Dmitri Stepanov wrote: Hi    I need to shutdown a number of hosts which has not NUT from one which has it.    I tried to do it from upssched script (after upssched's timer) like this: case $1 in     earlyshutdown)     logger -t upssched-cmd "Early

Re: [Nut-upsuser] Driver Inform Sinus SS 230

Sorry if this is a duplicated message. On Tue, 12 Jul 2016, Barbieri, Matteo wrote: ... a new model "Inform Sinus SS 230". Obviously I already saw on the official NUT website that the model is not supported, but I was wondering if there are some compatible drivers or maybe someone who are

Re: [Nut-upsuser] UPS is not turned off in slave-only configuration?

On Wed, 22 Jun 2016, André Hänsel wrote: Now, what I see is that when the UPS feeding server-1 goes LB, server-1 is indeed shut down, but it seems that the UPS is never switched off. This is a problem because when power is restored after shutdown, but before the battery runs out (with no load,

Re: [Nut-upsuser] Besoin d’aide pour upssched

On Tue, 14 Jun 2016, Philippe Le Mesle wrote: I finally received a delayed SMS saying power was back. I'm guessing that your test action is to disconnect the building power from the UPS for a certain time and then re-connect. How long do you wait? Even when all the gear is permanently

Re: [Nut-upsuser] Besoin d’aide pour upssched

On Tue, 14 Jun 2016, Philippe Le Mesle wrote: Roger? Can your read me? I receive a single e-mail from you via the list. Remember that the mailing list very probably removes duplicates. If you do not receive a copy of your own messages to the list, check your options on the list

Re: [Nut-upsuser] Besoin d’aide pour upssched

On Tue, 14 Jun 2016, Philippe Le Mesle wrote: "essayer la commande /usr/bin/upssched-cmd upssms manuellement sans passer par NUT." Là je ne comprends pas (je débute en Linux). Comment puis-je exécuter cette commande , PS: préférez-vous que cet échange soit en anglais ? It is better to

Re: [Nut-upsuser] Besoin d’aide pour upssched

On Tue, 14 Jun 2016, Philippe Le Mesle wrote: Voici ma configuration : ** 3/ le script /usr/bin/upssched-cmd #!/bin/bash case $1 in upssms) logger -t upssched-cmd "The UPS has been gone for 30 secs. Warn by sms..." /bin/echo "Power

Re: [Nut-upsuser] Is a timer a file?

On Sat, 4 Jun 2016, Charles Lepple wrote: On Jun 3, 2016, at 6:48 AM, Roger Price <ro...@rogerprice.org> wrote: ... the timer. I don't see it in /var/lib/ups where the locate tool finds upsd.pid, and I don't see it in /run or /var/run where I see upsmon.pid. ... it seems that the

[Nut-upsuser] Is a timer a file?

Hi, I'm trying to get a better understanding of what a timer is, so I added the following line to upssched.conf # Debug - turn on long-running timer to find out where upssched puts it AT ONBATT * START-TIMER where-am-I 1000 I can then start this timer by pulling the power cord from the wall

Re: [Nut-upsuser] Low Battery event not occurring

On Fri, 13 May 2016, Kamran Khan wrote: I have a TrippLite SMART2200RM2UN UPS.  I have installed and configured NUT as instructed on the website, and am able to monitor the status of the UPS without much problem.  The only problem I am seeing is that I cannot get the machine to actually send

Re: [Nut-upsuser] cyberpower ups need to manully turn on the switch

On Sun, 8 May 2016, Min Wang wrote: Hi centos 6.3 uses traditional SysV script ( not systemctl) here is the /etc/init.d/ups ( script) assuming it similar to nutshutdown File /etc/init.d/ups is an administrative script which is used to set up the nut daemon - I was looking for a run-time

Re: [Nut-upsuser] cyberpower ups need to manully turn on the switch

On Sat, 7 May 2016, Min Wang wrote: I am using centos 6.3, and nut-2.6.5-2.el6.x86_64. could you explain why not sending "a delayed command to the UPS to turn it off" may cause that issue?   You need to stop the UPS from beeping. Only then can you get a clear restart when power returns.

Re: [Nut-upsuser] cyberpower ups need to manully turn on the switch

On Sat, 7 May 2016, Min Wang wrote: Hi  I have CP825AVR-G UPS.  sometimes the UPS is shutdown due to whatever reason.  But the annoying thing is even if the electrical power is back, that UPS will continue to beep, and I have to manually turn on the switch button in order for it to supply

[Nut-upsuser] KDE loses NUT wall notifications

On Wed, 28 Oct 2015, George Anchev wrote: > However there was no any notification on desktop at I'm guessing you use KDE and this may be a problem in the default way KDE treats the output of the "wall" program. I don't have a KDE setup to test with, Hi George, I finally have a 42.1 Leap

Re: [Nut-upsuser] Cannot access Patriot Pro II from new system

On Wed, 2 Dec 2015, Olav Seyfarth wrote: I'd ideally set it to "shut down when only 20% battery left" (which should give at least five minutes power left, shutdown takes far less than one minute). BUT: # upsc eaton@localhost battery.charge: 89 *battery.charge.low: 20* ... ... but mine does

Re: [Nut-upsuser] The system doesn't shutdown

On Wed, 2 Dec 2015, George Anchev wrote: Did find a solution regarding the wall notifications? Hello George, I'm still struggling to install openSUSE 42.1 with KDE. When I have this (almost) working, I will have a look at the effect of wall on KDE. Roger

Re: [Nut-upsuser] The system doesn't shutdown

On Wed, 28 Oct 2015, George Anchev wrote: P.S. There is a typo in your nut-delayed-ups-shutdown.service. Line: ExecStart=/usr/bin/logger -t upsdrvctl "nut-delayed-ups-shudown.service calling upsdrvctl to shut down UPS unit" shudown is missing a 't'. It is in the log message but might still be

Re: [Nut-upsuser] The system doesn't shutdown

On Thu, 29 Oct 2015, George Anchev wrote: Today I experienced something weird. As I was working, the system started a shutdown and did shut down, then the UPS got powered off and then back on - an expected behavior for a power fail situation. However there was no power failure! ... Oct 29

Re: [Nut-upsuser] The system doesn't shutdown

On Wed, 28 Oct 2015, George Anchev wrote:  ${sbinPath}upsmon -c fsd In 'upsmon --help' I read: "- fsd: shutdown all master UPSes (use with caution)". What exactly does this line do? My understanding is that it calls upsmon running as root to execute the command specified by SHUTDOWNCMD in

Re: [Nut-upsuser] The system doesn't shutdown

On Wed, 28 Oct 2015, George Anchev wrote: Beautiful! The shutdown succeeded. Did you see a line in the journal similar to this ? Oct 06 22:49:54 pinta nut-delayed-ups-shutdown[1854]: nut-delayed-ups-shudown.service calling upsdrvctl to shut down UPS unit

Re: [Nut-upsuser] The system doesn't shutdown

On Tue, 27 Oct 2015, George Anchev wrote: Oct 26 21:02:56 i7 upsd[2227]: Startup successful ... Oct 26 21:02:56 i7 upsmon[2229]: Startup successful ... Oct 26 21:04:51 i7 upsmon[2230]: UPS myups@localhost on battery Oct 26 21:05:11 i7 upsmon[2230]: UPS myups@localhost on line power Power

Re: [Nut-upsuser] The system doesn't shutdown

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

Re: [Nut-upsuser] The system doesn't shutdown

On Mon, 26 Oct 2015, George Anchev wrote: Hello, I have been following the details in this article to configure my UPS: http://rogerprice.org/NUT.html However the system won't shutdown although file permissions look ok: ls -alF /usr/sbin/ups* -rwxr--r-- 1 upsd daemon 64984 Oct 15  2014

Re: [Nut-upsuser] NUT configuration problem

On Mon, 26 Oct 2015, George Anchev wrote: > The best way to shut down becomes a power disconnection. Hm. Not quite convenient for a dual boot system. Actually that contradicts the very idea of being the power being non-interrupted. Isn't there any way to reporgram the service to distinguish

Re: [Nut-upsuser] No power cycle after shutdown on Atlantis Land OnePower A03-S1001

On Wed, 14 Oct 2015, Davide Baldini wrote: Is there any command in the list provided by "upscmd -l myups" which is accepted by this UPS? None of the command sin the list successfully completes, not even beeper.toggle. It looks as if the problem is more general than turning off the UPS. The

Re: [Nut-upsuser] No power cycle after shutdown on Atlantis Land OnePower A03-S1001

On Wed, 14 Oct 2015, Davide Baldini wrote: the full output of upsc ${myups} is at https://pastebin.mozilla.org/8849188 ; in particular: ups.delay.shutdown: 30 ups.delay.start: 180 However, the UPS does not shut down, not immediately nor well after the timeout of the command:

Re: [Nut-upsuser] No power cycle after shutdown on Atlantis Land OnePower A03-S1001

On Wed, 14 Oct 2015, Davide Baldini wrote: upsdrvctl shutdown ... instcmd(shutdown.return, [NULL]) instcmd: FAILED Shutdown failed! Driver failed to start (exit status=1) This time /var/log/syslog doesn't register anything about the UPS after issuing the command above. Instead, It logged

[Nut-upsuser] NUT with openSUSE 13.2

I have been looking closely at using NUT with openSUSE 13.2. Here is a quick summary. 1. Like the alien plant in the Quatermass Experiment, systemd is reaching into every corner of the distribution. New systemd service units exist in /usr/lib/systemd/system: Power devices information server,

Re: [Nut-upsuser] UPS/NUT with openSUSE 13.1

On Tue, 8 Sep 2015, Rob Groner wrote: I executed lsusb to verify the USB device is there, and it is. I tried the shutdown command again with debug enabled, but it didn't seem to reveal much more: ---

Re: [Nut-upsuser] UPS/NUT with openSUSE 13.1

On Tue, 8 Sep 2015, Rob Groner wrote: Roger, rtd@linux-5048> sudo /usr/local/ups/bin/usbhid-ups -a rtdups -k -DDD Network UPS Tools - Generic HID driver 0.39 (2.7.2.6_RTD) USB communication driver 0.32 0.00 debug level is '3' 0.000405 upsdrv_initups... ... 0.004555

Re: [Nut-upsuser] UPS/NUT with openSUSE 13.1

On Fri, 4 Sep 2015, Rob Groner wrote: Well, I tried the same script method with openSUSE 13.2, and it still did not execute. So I tried the system method, and it worked 1 time out of 3 attempts. I captured the last failure: 2015-09-04T11:43:38.825317-04:00 linux-5048 upsdrvctl[1887]: Can't

Re: [Nut-upsuser] UPS/NUT with openSUSE 13.1

Hello Bob, I had preferred the shutdown script method because it was a little more straight-forward, and possibly more portable. This guide is meant to help people get the UPS up and running, whatever their Linux distro. I don't know how common the systemd implementation is across various

  1   2   >