Displaying 20 results from an estimated 500 matches similar to: "Monitoring slaves via dummy-ups"
2020 Sep 04
1
Monitoring slaves via dummy-ups
On Fri, Sep 4, 2020, at 5:19 PM, Roger Price wrote:
> On Fri, 4 Sep 2020, Dan Langille wrote:
>
> > I wondered how folks monitored slaves.
>
> A NUT solution is to use a "heartbeat" generated in each slave and monitored in
> say the master or elsewhere.
I did find this earlier today: https://alioth-lists.debian.net/pipermail/nut-upsuser/2017-April/010590.html
Is
2020 Sep 04
0
Monitoring slaves via dummy-ups
On Fri, 4 Sep 2020, Dan Langille wrote:
> I wondered how folks monitored slaves.
A NUT solution is to use a "heartbeat" generated in each slave and monitored in
say the master or elsewhere.
> The goal: confirm the slaves have contact with the master.
On your Github site: Goal: allow host to shutdown when needed.
These are not the same goals
In NUT, for the shutdown process,
2020 Sep 11
1
UPS recommendation for NUT and power-on-delay support
On Fri, Sep 11, 2020, at 4:05 PM, Bartosz wrote:
> Dear All,
>
> Could you please recommend me a UPS with 100% support of the ondelay parameter and NUT compatibility?
>
> 850 or 1000 VA
>
> I have the EATON 5E850iUSBDIN UPS and it does not support this parameter so I would like to buy another UPS that for sure will support it.
>
> Thank you,
> Bart
Can you tell
2020 Sep 15
2
loss of communication
rPi3 running current Buster. I get this far:
# upsc networkups
Init SSL without certificate database
battery.charge: 100
battery.charge.warning: 30
battery.runtime: 2891
battery.type: PbAC
device.mfr: Vertiv Co
device.model: Liebert PST5
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid:
2023 Mar 09
1
Question on EATON UPS
Laurent Taieb via Nut-upsuser wrote on 3/9/23 9:25 AM:
>
> Hi NUT Users,
>
> One of my APC UPS is having battery issue and apparently we cannot
> change battery in that UPS. (not super green?)
>
> I have purchased an EATON UPS and added the ref in ups.conf
>
> When restarting the driver, I got this error
>
> >0.030612[D2] Checking device 2 of 10 (0463/FFFF)
2023 Mar 09
1
Question on EATON UPS
On Thursday, March 9th, 2023 at 8:34 AM, Dan Langille via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote:
>> The UPS has been defined in ups.conf as:
>>
>> [myups3]
>>
>> driver : usbhid-ups
>>
>> port = auto
>>
>> vendorid = 0463
>>
>> productid = ffff
>>
>> desc = "5S"
>>
>> bus
2020 Sep 05
9
ups not being started sat reboot
But runs normally if started. On a rpi4 running an uptodate raspbian
buster, how do I set it to auto start at boot time?
Thanks.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
- Louis D.
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 09
1
Question on EATON UPS
Hi NUT Users,
One of my APC UPS is having battery issue and apparently we cannot change battery in that UPS. (not super green?)
I have purchased an EATON UPS and added the ref in ups.conf
When restarting the driver, I got this error
> 0.030612 [D2] Checking device 2 of 10 (0463/FFFF)
> 0.287659 [D2] - VendorID: 0463
> 0.287853 [D2] - ProductID: ffff
>
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)
2007 Nov 25
1
[nut-commits] svn commit r1156 - in trunk: . drivers
On Nov 25, 2007 11:50 AM, Arjen de Korte
<adkorte-guest at alioth.debian.org> wrote:
> Limit detection of UPS to minimum required number of successful attempts. Flush input- and output buffers before sending any command.
Can you explain the reasoning behind these changes please?
The detection phase didn't stop after the minimum number of required
replies to check for models that
2020 Sep 19
0
loss of communication
> On Sep 14, 2020, at 9:12 PM, Joe Reid <jreid at vnet.net> wrote:
>
> rPi3 running current Buster. I get this far:
>
> # upsc networkups
> Init SSL without certificate database
> battery.charge: 100
> battery.charge.warning: 30
> battery.runtime: 2891
> battery.type: PbAC
> device.mfr: Vertiv Co
> device.model: Liebert PST5
> device.type: ups
>
battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
2017 Apr 10
2
battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
On 10/04/17 15.25, Jon Bendtsen wrote:
> On 04/04/17 15.19, Arnaud Quette wrote:
>>
>>
>> 2017-04-04 14:18 GMT+02:00 Jon Bendtsen <jon.bendtsen at jonix.dk
>> <mailto:jon.bendtsen at jonix.dk>>:
[cuuuuut]
> I'd say your change is a success :-)
well, almost, but maybe that is outside NUT's control.
/usr/lib/nagios/plugins/check_ups -H
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,
2009 Jul 26
1
Problems connecting via USB to APC Back-UPS ES 700 (Model BE700-GR)
hi list,
im running debian/testing(act. squeeze) with 2.6.26-2-amd64 kernel. first
tried apcupsd what flawlessly worked but because i run nagios (needs nut
running for 'check_ups'), im trying to run nut.
dmesg and syslog show the device:
Jul 27 00:08:06 kate kernel: [16001.477941] hiddev96hidraw0: USB HID v1.10
Device [APC Back-UPS ES 700 FW:829.D3 .I USB FW:D3 ] on usb-0000:00:1d.1-1
2014 Dec 31
2
Postfix and Dovecot SASL - wiki update
I wanted to mention I updated the Postfix and Dovecot SASL wiki entry yesterday.
http://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL
The entry:
submission inet n - - - - smtpd
was incorrect. It should be:
submission inet n - n - - smtpd
By specifying n for chroot, it ensures that DNS lookups can occur. Otherwise, if you are using reject_unknown_recipient_domain
the following error will
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
2010 Jul 25
4
zpool destroy causes panic
I'm trying to destroy a zfs array which I recently created. It contains
nothing of value.
# zpool status
pool: storage
state: ONLINE
status: One or more devices could not be used because the label is
missing or
invalid. Sufficient replicas exist for the pool to continue
functioning in a degraded state.
action: Replace the device using 'zpool replace'.
2013 Oct 22
2
doveadm: Fatal: open(/dev/tty)
I received this message today, and remembered, you can't do that...
$ doveadm pw -s SHA512-CRYPT
Enter new password: doveadm(dan): Fatal: open(/dev/tty) failed: No such
file or directory
</pre>
It seems if you have no tty, you can't create a password. Surely there
is a better way to do this?
Looking at the code, it's trying to open the tty and turn off echo.
For the
2003 May 18
3
ad0: READ command timeout....
This morning I found a frozen box. On the console was this:
ad0: READ command timeout tag=0 serv=0 - resetting
ata0: resetting devices .. ata0-slave: ATA identify retries exceeded
done
After reboot, those messages were found in /var/log/messages.
I'm running FreeBSD 4.8-RC from Apr 4 10:45:49 EST 2003.
Any ideas?
--
Dan Langille : http://www.langille.org/