: 1209600
ups.test.result: NO
Should I be doing something else in order to update battery.date?
Maybe reset the UPS?
Thanks,
Vieri
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut
: AS0836160289
ups.status : OL
ups.temperature : 022.5
ups.test.interval : 1209600
ups.test.result : NO
Thanks,
Vieri
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http
) would I solve this
issue (ie. is it a known issue?)?
Thanks,
Vieri
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
internal resistance that the
voltage reads normal when idle, but it dips too low during a
test.
ups.test.interval : 1209600
1209600 seconds = 14 days, so if it does it again in two
weeks...
Thanks for the explanation.
Vieri
___
Nut-upsuser
suggest changing the battery or is it an overreaction?
Thanks,
Vieri
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
end of it) in order to boot the
ups.
Thoughts greatly appreciated.
Vieri
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
for the hint.
Vieri
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
one soon just to make sure the batteries are ok.
Thanks for all the feedback.
Vieri
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
name and serial numbers
behind the UPS devices)
Anyway, I'll try to get the official serial cables just to rule out wiring
issues.
Thanks for helping.
Vieri
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org
that help?
I'm going to have to move the production servers to another UPS (actually most
servers have dual power supplies each connected to a different UPS but network
switches don't).
I'll try that asap in a few days.
Thanks for pointing that out.
Vieri
As a follow-up I'd like to add that this ended up
being a Gentoo-specific issue which is now solved in
nut-2.0.5-r2.
Need
a vacation? Get great deals
to amazing places on Yahoo! Travel.
Hi,
I am running nut with megatec driver accessing ttyS0
as user nut on standard kernel (gentoo-sources). It
works fine.
However, I just built a hardened kernel on a new
gentoo machine and have no experience with it. NUT
(upsdrv) is failing because it says it doesn't have
permission to access
--- Carlos Rodrigues [EMAIL PROTECTED]
wrote:
On 5/8/07, Vieri [EMAIL PROTECTED] wrote:
However, I just built a hardened kernel on a new
gentoo machine and have no experience with it. NUT
(upsdrv) is failing because it says it doesn't
have
permission to access ttyS0 even though nut
workaround would be to include the nut user in
the uucp group.
I don't know whch solution is best.
Vieri
--- Peter Selinger [EMAIL PROTECTED] wrote:
See the thread USB problem as user by Czuczy
Gergely on the
nut-upsuser list, Apr 20-26.
Czuczy was also running grsecurity, and in his case,
he
I also did:
# ./megatec_usb -D -x vendor=06da -x mfr=OMRON
/dev/usb/hiddev0
Network UPS Tools 2.1.0 - Megatec protocol driver
1.5.2 [megatec_usb]
Carlos Rodrigues (c) 2003-2007
Serial-over-USB transport layer for Megatec protocol
driver [megatec_usb]
debug level is '5'
Checking device
--- Arjen de Korte [EMAIL PROTECTED] wrote:
I also did:
# ./megatec_usb -D -x vendor=06da -x mfr=OMRON
/dev/usb/hiddev0
Please have a look at 'man 8 megatec_usb' again.
You probably need to specify the '-x vendorid' and
'-x productid' options
and most likely, the
16 matches
Mail list logo
