All,
I recently purchased a Tripp-Lite OmniVS1500XL and am running NUT on a
Centos-based system.
Based on the compatibility list I specified the tripplite_usb driver.
When I query the unit I get:
[root@chryxus ~]# upsc UPS@localhost
battery.voltage.nominal: 24
driver.name: tripplite_usb
driver.version: 2.0.3-pre2
driver.version.internal: 0.6
input.voltage.nominal: 120
ups.debug.0: 20 01 58 58 58 58 0d '..XXXX.'
ups.debug.L: 30 30 45 35 58 58 0d '00E5XX.'
ups.debug.S: 31 30 30 30 00 30 0d '1000.0.'
ups.debug.T: 30 30 30 30 30 31 0d '000001.'
ups.delay.shutdown: 64
ups.firmware: F2211.A
ups.mfr: Tripp Lite
ups.model: UPS
ups.power.nominal: 1500
ups.status: OL
[root@chryxus ~]#
Ever since enabling the driver I have been getting error messages
showing up in the log file every couple of seconds. This is a brief sample:
Oct 12 18:03:44 chryxus tripplite_usb[2115]: Error reading 'D'
value: Unknown error 0
Oct 12 18:03:44 chryxus tripplite_usb[2115]: Error reading 'M'
value: Unknown error 0
Oct 12 18:03:47 chryxus tripplite_usb[2115]: Error reading 'D'
value: Unknown error 0
Oct 12 18:03:47 chryxus tripplite_usb[2115]: Error reading 'M'
value: Unknown error 0
Oct 12 18:03:50 chryxus tripplite_usb[2115]: Error reading 'D'
value: Unknown error 0
Oct 12 18:03:50 chryxus tripplite_usb[2115]: Error reading 'M'
value: Unknown error 0
Oct 12 18:03:53 chryxus tripplite_usb[2115]: Error reading 'D'
value: Unknown error 0
Oct 12 18:03:54 chryxus tripplite_usb[2115]: Error reading 'M'
value: Unknown error 0
The log files are filling up rapidly.
I have two questions.
1) In its current state is this providing any shutdown protection at all?
2) Assuming it is, is there any way I can turn off the generation of
these log messages?
I'm not very technical so probably would not be able to help much with
tracking down the source of the problem.
Thanks for your help.
John
--
John Hobbs
Chryxus Corporation
On 10/13/06, John Hobbs <jhobbs@chryxus.ca> wrote:> 1) In its current state is this providing any shutdown protection at all?It depends on how the value of ups.debug.S changes when the battery goes low. Supposedly, the OmniVS1500XL uses the same protocol as the OmniVS1000, but I am not sure how much of this has been tested. (Note that this is an "empirical" driver, written by observing the USB protocol of an OmniVS1000.)> 2) Assuming it is, is there any way I can turn off the generation of > these log messages?Probably not with CentOS. If you can compile from source, and test a few things, we can cut down on the error messages, but you won't get status on whatever the D and M commands were trying to check. -- - Charles Lepple
On 10/13/2006 09:39 PM, Charles Lepple wrote:> >> 2) Assuming it is, is there any way I can turn off the generation of >> these log messages?actually , depending on how these messages are generated I think that you might configure the syslog daemon to ignore them ( via /etc/syslog.conf ). If you are willing to replace sysklogd with syslog-ng, you can filter out those messages for sure. syslog-ng has builtin filtering abilities but is not included in RHEL (hence neither in Centos). An older version is available ( in rpm format ) in Fedora Extras, I can offer you the rpm (both src.rpm and binary) for the most recent one. Since this is not directly related to nut, , if you want the packages please contact me off list.