search for: upsusers

Displaying 20 results from an estimated 4870 matches for "upsusers".

Did you mean: upsuser
2007 Mar 28
1
Re: Nut-upsuser Digest, Vol 21, Issue 29
THANKS, but the 'megatec' driver only works whith windows OS via USB, and i need it for red hat OS with USB-serial connection... Please, anybody can help me.... nut-upsuser-request@lists.alioth.debian.org escribi?: Send Nut-upsuser mailing list submissions to nut-upsuser@lists.alioth.debian.org To subscribe or unsubscribe via the World Wide Web, visit
2024 Mar 06
2
Upssched 100% CPU
Thanks for the tip. I had downloaded a prerelease source version of NUT 2.8.1, built and installed it. Evidently there was an issue with upssched consuming 100% CPU. I downloaded the current release and the issue has been resolved. Updating all 3 systems. Dan ________________________________ From: Nut-upsuser <nut-upsuser-bounces+danpower2023=outlook.com at alioth-lists.debian.net> on
2024 Sep 08
0
Nut-upsuser Digest, Vol 231, Issue 4
This is the first time that i had to use E-mail like forums i'm only hitting reply to mail NOT replay to all mails THIS IS upssched.conf # This file is auto-generated by openmediavault (https://www.openmediavault.org) # WARNING: Do not edit this file, your changes will get lost. CMDSCRIPT /usr/bin/upssched-cmd PIPEFN /run/nut/upssched.pipe LOCKFN /run/nut/upssched.lock AT COMMOK * EXECUTE
2024 Sep 07
2
Nut-upsuser Digest, Vol 231, Issue 2
THIS IS systemctl list-units | grep UPS nut-driver at back-ups.service
2023 Mar 09
1
Question on EATON UPS
Thanks Larry, I tried. Got the following traces and the driver doesn?t start. 1.036797 [D2] - VendorID: 0463 1.036812 [D2] - ProductID: ffff 1.036826 [D2] - Manufacturer: unknown 1.036840 [D2] - Product: unknown 1.036872 [D2] - Serial Number: unknown 1.036912 [D2] - Bus: 002 1.036942 [D2] - Device: unknown 1.036965 [D2] - Device
2023 Mar 23
1
Question on EATON UPS
The "unknown" fields mean the driver did not get that piece of information from libusb. In case of Manufacturer/Product which are unknown in the later post, but known in the first, I suppose you had another driver running, or the kernel still owned it (udev misbehavior, not handing it off after reconnections, etc.) and so exclusive access was not given to the new (currently reporting)
2020 Jan 27
1
Timer doesn't appear to start
Here is the output root at nutpi:/etc/nut# ps -elf | grep -E '[n]ut|ups[dms]' 4 S avahi 246 1 0 80 0 - 1472 poll_s Jan26 ? 00:00:31 avahi-daemon: running [nutpi.local] 1 S nut 451 1 0 80 0 - 678 poll_s Jan26 ? 00:03:41 /lib/nut/upscode2 -a deltec-PRA1500 1 S nut 454 1 0 80 0 - 1173 poll_s Jan26 ? 00:00:28 /lib/nut/upsd 1
2020 Feb 11
1
NOTIFYCMD not running
>I just went through the same issue. Take a look at my thread. >Double check that upsmon.conf:NOTIFYCMD /sbin/upssched is not still commented. Thanks for the response, can you link to it? I'm not finding it in the search. I'm not using /sbin/upssched, I have NOTIFYCMD set up as: NOTIFYCMD /home/pi/Documents/scripts/ups-log.py and it's not commented out. On Tue, Feb 11, 2020
2013 Apr 18
0
Nut-upsuser Digest, Vol 94, Issue 18
?Hello Sabine, this seems as a problem with PATH env. variable; if you issue the command by hand, you do so in an environment with PATH set so that the binaries are found. I guess that the nut user doesn't have so nice PATH, being non-interactive. Try to add full paths to your binaries in the command and see what happens... Regards, vasek -- Vaclav Krpec NUT developer
2020 Feb 12
0
NOTIFYCMD not running
I finally got this working, for the sake of anyone else who comes across this thread with a similar problem: Since NOTIFYCMD was working fine with bash scripts, I had it point to a bash script which I used to call my python script, and I set up the bash script to capture errors and write them to a log file: /etc/nut/ups-log.py > /home/pi/Documents/scripts/mylog 2>&1 I didn't realize
2024 May 16
2
Supporting a DIY UPS with minimal effort butmaximum gain
On 5/16/24 08:59, Jim Klimov via Nut-upsuser wrote: > I agree with earlier posters, such documentation can help future > tinkerers. There is probably more than just one to hold the hand and > walk through the ordeals :) > > Perhaps a new page at https://github.com/networkupstools/nut/wiki > <https://github.com/networkupstools/nut/wiki> can be a good location... >
2024 May 16
1
Supporting a DIY UPS with minimal effort but maximum gain
I agree with earlier posters, such documentation can help future tinkerers. There is probably more than just one to hold the hand and walk through the ordeals :) Perhaps a new page at https://github.com/networkupstools/nut/wiki can be a good location... Jim On Thu, May 16, 2024 at 1:29?PM Bill Gee <bgee at campercaver.net> wrote: > Hi Kelly - > > As an Arduino nerd, I am
2023 Jul 16
1
Powering off the big stuff first
One thing that I think NUT misses is the client side being able to decide to shutdown by itself based on time (this can be done), battery charge (ex if bellow 10%), and estimated runtime left (if available and considered reliable/calibrated). Without having to sort on the LB state from the server. Sent from my iPhone with ? iTypos > On Jul 16, 2023, at 4:34 PM, Willcox David via Nut-upsuser
2024 Sep 06
0
Nut-upsuser Digest, Vol 231, Issue 1
As fast as I know, the standard NUT package will not command your power supply off unless customizations are made. Devices like Synology have an option to command the UPS off. What is acting as your NUT server? Your server PC? On Fri, Sep 6, 2024, 11:10 AM <nut-upsuser-request at alioth-lists.debian.net> wrote: > Send Nut-upsuser mailing list submissions to > nut-upsuser at
2012 Sep 19
1
New intermediate Windows binaries release - 2.6.5-3
?Hello, There is a new intermediate Windows binaries release available at : http://www.networkupstools.org/package/windows/NUT-Installer-2.6.5-3.msi This fixes a regression about stopping the NUT service. Feedback is highly appreciated. Regards, Fred -- Eaton Opensource Team - http://opensource.eaton.com ----------------------------- -----------------------------
2021 Mar 13
1
[EXTERNAL] Re: On retiring some terminology
I didn't go there due to its use by Cisco. On Fri, Mar 12, 2021, 10:03 PM Baker, Lawrence M via Nut-upsuser < nut-upsuser at alioth-lists.debian.net> wrote: > Jim, > > The terminology I recall for that one-to-many relationship is > publisher-subscriber. > > Larry Baker > US Geological Survey > 650-329-5608 > baker at usgs.gov > > > > On Mar 12
2023 Mar 24
1
Question on EATON UPS
Sounds like some other program is holding the port. Have you stopped other NUT drivers for the device (e.g. via auto-resuscitating services) before starting this one? Does udev, ugen or similar facility have the configuration to hand off this device to NUT run-time user? (BTW, if you are now testing a custom build - was it configured to use same accounts as pre-packaged variant)? On Fri, Mar 24,
2023 Jul 16
4
Powering off the big stuff first
Hello, I had an idea last week: why shut everything off (in my basement) when the power goes off (and run time goes below X minutes)? My idea: shutdown the big stuff first (two servers) leaving the little stuff (switches, wireless, gateway) running for a while longer. I might get another 30 minutes of internet that way. Let me watch a bit more streaming?. I?m convinced that idea is achievable
2024 Mar 06
1
Upssched 100% CPU
Am i the only user who has no glue about how to build a new version for my system? I?m running on Raspberry GNU/Linux (bullseye) v 11, which might be similar to your system? Sounds as if it is not a big issue to download the version and build it and install it. Is there anybody out there who might be able to give me a kickoff, how to do that? Have found various built versions here at Binary
2020 Jan 27
3
Nut-upsuser Digest, Vol 175, Issue 32
Here are my permissions and user info. Let me know if there is anything else I should check pi at nutpi:~ $ ls -alt /etc/nut total 56 drwxr-xr-x 87 root root 4096 Jan 26 15:22 .. drwxr-xr-x 2 root nut 4096 Jan 26 13:53 . -rw-r----- 1 root nut 4719 Jan 26 13:15 upssched.conf -rw-r----- 1 root nut 15347 Jan 26 11:25 upsmon.conf -rw-r----- 1 root nut 1543 Jan 26 10:02 nut.conf -rw-r-----