I have a user with an ancient Powerware 9120 that's reportedly working with bcmxcp_usb on NUT 2.8.1, apart from the syslogs getting spammed with the following warnings (?):
Dec 23 11:21:27 FILESERVER bcmxcp_usb[11063]: alarm_set: result was truncated while setting or appending alarm_buf (limited to 256 bytes), with message: OUTGOING_MODEM_CALL_STARTED
Dec 23 11:21:29 FILESERVER bcmxcp_usb[11063]: alarm_set: result was truncated while setting or appending alarm_buf (limited to 256 bytes), with message: STARTUP_FAILURE_CHECK_EPO
Dec 23 11:21:29 FILESERVER bcmxcp_usb[11063]: alarm_set: result was truncated while setting or appending alarm_buf (limited to 256 bytes), with message: OUTGOING_MODEM_CALL_STARTED
Might be related to driver TO-DOs:
- Report UPS alarm status
BCM/XCP supports reporting a wide range of UPS alarm conditions.
- Report UPS statistics information
BCM/XCP supports reporting of UPS statistics data.
But wondering if those unhandled alarm states should be suppressed in the logs, or if the suspected core problem of the exceeded byte size of such alarms needs fixing and then it'd stay quiet anyhow (if unhandled).
Thanks a lot and wishing everyone happy holidays! Sent from mobile, please excuse the bad formatting.
I have a user with an ancient Powerware 9120 that's reportedly working with
bcmxcp_usbon NUT 2.8.1, apart from the syslogs getting spammed with the following warnings (?):Might be related to driver TO-DOs:
But wondering if those unhandled alarm states should be suppressed in the logs, or if the suspected core problem of the exceeded byte size of such alarms needs fixing and then it'd stay quiet anyhow (if unhandled).
Thanks a lot and wishing everyone happy holidays! Sent from mobile, please excuse the bad formatting.