works now!
thanks a lot
Thanks for your efforts in debugging this issue. This is what we need in
order to make sure that the code we write is portable, at least for the
platforms we intend to support.
Best regards, Arjen
___
Nut-upsuser mailing
Belkin F6C1200-UNV on Ubuntu 7.04, megatec_usb driver,
Every few minutes I get a beep and a UPS not available message that
seems to be bogus; upsc reports real data, not at complaint that it's
stale.
Is there some timeout I need to lengthen?
Also, shouldn't upsc report the poll time associated
Belkin F6C1200-UNV on Ubuntu 7.04, megatec_usb driver,
Every few minutes I get a beep and a UPS not available message that
seems to be bogus; upsc reports real data, not at complaint that it's
stale.
What's in the logfiles? Is this message generated by the driver, the
server or the client?
On Wed, May 23, 2007 at 01:18:26AM -0300, Peter Selinger wrote:
I'll defer to Alexander Gordeev; he has worked extensively on the
megatec_usb driver, which is solving a somewhat similar problem,
although the protocol is different.
The UPS shutdown 30 seconds after the low battery event might
Eric S. Raymond wrote:
Arjen de Korte [EMAIL PROTECTED]:
What's in the logfiles? Is this message generated by the driver, the
server or the client?
Which log is relevant? /var/log/messages or something else?
The syslog. Where that resides, depends on your local configuration,
although
Eric S. Raymond wrote:
Many repetitions of this message with different timestamps.
May 23 11:25:51 snark upsmon[26084]: Poll UPS [EMAIL PROTECTED] failed -
Write error: Bad file descriptor
May 23 11:25:56 snark upsd[26065]: Rejecting TCP connection from 192.168.1.11
May 23 11:25:56 snark
On 5/23/07, Arjen de Korte [EMAIL PROTECTED] wrote:
Eric S. Raymond wrote:
[...]
Why not? Seems natural to me to want to know the timestamp on the
data sample I'm seeing.
[...]
Regarding the timestamp, when data is stale it is unimportant how stale
it is, it should not be used anymore.
Arjen de Korte [EMAIL PROTECTED]:
This looks a lot like problems with setting the access controls or on
the upsd server. Could you post the contents of 'upsd.conf' and
'upsd.users' here or in a private message? This certainly has nothing to
do with the driver.
-- upsd.conf
Charles Lepple [EMAIL PROTECTED]:
There's a slim possibility that the timestamp could be useful in the
upsc output, especially with drivers that have to cope with buggy
hardware that does not always respond in the same time interval.
That's exactly the case I was thinking about; I'm coping
9 matches
Mail list logo
