Salut Marc,
2007/3/14, Marc Rechté [EMAIL PROTECTED]:
Arnaud,
This is the piece of information:
[EMAIL PROTECTED] hylafax]# ldd /bin/newhidups
libusb-0.1.so.4 = /usr/lib64/libusb-0.1.so.4 (0x003d1760)
libc.so.6 = /lib64/tls/libc.so.6 (0x003709d0)
Hello Arjen,
Thanks for your suggestions. I set the pollfreq = 5 and pollinterval = 20 in
ups.conf. It has helped to reduce the frequency of broadcast messages but not
fully. I have attached a log that you can see the frequency.
Many thanks.
Marc
messages
Description: Binary data
Hi Marc,
2007/3/13, [EMAIL PROTECTED] [EMAIL PROTECTED]:
...
Arnaud,
Considering this message I did not try your suggestion.
I can confirm that there is no problem with the UPS and the power line is
stable. I have attached the relevant log file for a run.
I forgot to mention this is a 64-bit
Arnaud,
This is the piece of information:
[EMAIL PROTECTED] hylafax]# ldd /bin/newhidups
libusb-0.1.so.4 = /usr/lib64/libusb-0.1.so.4 (0x003d1760)
libc.so.6 = /lib64/tls/libc.so.6 (0x003709d0)
/lib64/ld-linux-x86-64.so.2 (0x003709b0)
Thanks for the
2007/3/12, Marc Rechté [EMAIL PROTECTED]:
Thanks Arnaud for your prompt answer.
Please find attached the required log (interrupted after a few minutes run).
...
from the UPS (communication layer), you really have power failure / restored.
Search for UPS.PowerSummary.PresentStatus.ACPresent
Does the problem occur frequently? The more details, the better.
from there, 3 possibilities (need more details to audit):
- if the problem occurred only once, then you've seen a battery test,
- else you have some electrical problems upstream,
- else the UPS has some internal problem.
A
2007/3/13, Arjen de Korte [EMAIL PROTECTED]:
Does the problem occur frequently? The more details, the better.
from there, 3 possibilities (need more details to audit):
- if the problem occurred only once, then you've seen a battery test,
- else you have some electrical problems upstream,
Quoting Arnaud Quette [EMAIL PROTECTED]:
2007/3/13, Arjen de Korte [EMAIL PROTECTED]:
Does the problem occur frequently? The more details, the better.
from there, 3 possibilities (need more details to audit):
- if the problem occurred only once, then you've seen a battery test,
[EMAIL PROTECTED] wrote:
I can confirm that there is no problem with the UPS and the power line is
stable. I have attached the relevant log file for a run.
Please try if adding the following lines to 'ups.conf' make any
difference (you'd need to restart the driver in order to make these
ups.conf is:
[EMAIL PROTECTED] rules.d]# cat /etc/ups/ups.conf
# UPS Conf for NUT
[pulsar]
driver=newhidups
port=auto
desc=Pulsar M2200 RT3U
# vendorid=0463
# offdelay = 180 s
offdelay=180
# ondelay = 30 x 10 = 300 s
salut Marc,
2007/3/12, [EMAIL PROTECTED] [EMAIL PROTECTED]:
...
Howerver starting upsmon keeps reporting:
Mar 12 16:19:46 serveur1 upsmon[20453]: UPS [EMAIL PROTECTED] on line power
Mar 12 16:19:46 serveur1 wall[20501]: wall: user ups broadcasted 1 lines (36
chars)
Mar 12 16:19:51 serveur1
Hi Arjen,
Thanks for your prompt answer.
I checked the ups.conf and newhidups man pages and could not locate the
pollfreq parameter. Do you mean pollinterval ?
Best regards.
Marc.
Arjen de Korte a écrit :
ups.conf is:
[EMAIL PROTECTED] rules.d]# cat /etc/ups/ups.conf
# UPS Conf for NUT
Thanks Arnaud for your prompt answer.
Please find attached the required log (interrupted after a few minutes run).
Best regards
Marc.
Arnaud Quette a écrit :
salut Marc,
2007/3/12, [EMAIL PROTECTED] [EMAIL PROTECTED]:
...
Howerver starting upsmon keeps reporting:
Mar 12 16:19:46 serveur1
Marc Rechté wrote:
I checked the ups.conf and newhidups man pages and could not locate the
pollfreq parameter. Do you mean pollinterval ?
I meant just what I said. For 'newhidups' this is an undocumented
feature, while it has been documented for it's successor, 'usbhid-ups'.
Best regards,
14 matches
Mail list logo
