[Nut-upsuser] megatec driver floods syslog with "UPS lost/re-established" messages

[Carlos Rodrigues]

On Thu, Jul 3, 2008 at 10:57 PM, Anton Martchukov <anton at martchukov.com> wrote:
> 1) megatac driver is able to load and detect UPS only on
> second or third run. On the first run it typically fails.
> Later if daemon is being stoped and started again it's more
> likely to fail after restart too, but on the second restart
> it will mostly work ok.
>
> When it fails to start it outputs this to syslog:
>
> Jul  2 22:58:53 alcor upsd[5353]: Can't connect to UPS
> [powerman] (megatec-powerman): No such file or directory
>
> 2) When it starts properly it works nice, e.g. output UPS
> parameters, deteact low baterry etc. besides the fact that
> it floods syslog with the following message each polling
> cycle of the driver
>
> Jul  3 23:07:16 alcor megatec[7070]: Communications with UPS re-established
> Jul  3 23:07:24 alcor megatec[7070]: Communications with UPS lost: No status from UPS.
> Jul  3 23:07:31 alcor megatec[7070]: Communications with UPS re-established
> Jul  3 23:07:39 alcor megatec[7070]: Communications with UPS lost: No status from UPS.
> Jul  3 23:07:46 alcor megatec[7070]: Communications with UPS re-established
> Jul  3 23:07:54 alcor megatec[7070]: Communications with UPS lost: No status from UPS.
> Jul  3 23:08:01 alcor megatec[7070]: Communications with UPS re-established
> Jul  3 23:08:07 alcor megatec[7070]: Communications with UPS lost: No status from UPS.
> Jul  3 23:08:14 alcor megatec[7070]: Communications with UPS re-established
> Jul  3 23:08:29 alcor megatec[7070]: Communications with UPS lost: No status from UPS.
>
> I have tried different settings of polling cycle for the
> dirver and believe that it does not affect the presence of
> this message at all.
>
> Any help/directions will be highly appreciated. I know a bit
> of C and willing to try to solve this problem.

Which version of NUT are you using?

-- 
Carlos Rodrigues