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

[Arjen de Korte]

> Jul  2 22:58:53 alcor upsd[5353]: Can't connect to UPS
> [powerman] (megatec-powerman): No such file or directory

The driver couldn't detect the UPS. The above message is due to a broken
startup script, since the upsd should not be started if drivers failed to
start.

> 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.

Same here. The connection to the UPS is unreliable and the driver is
informing you about this.

> Any help/directions will be highly appreciated. I know a bit
> of C and willing to try to solve this problem.

Well, the only thing I can say is that you should try to find out why the
communication with the UPS is so unreliable. Fixing that would solve both
the startup problems and the flooding of the logs. Running the driver in
debug mode with 'megatec -DDD -a powerman' might help diagnose.

Regards, Arjen
-- 
Eindhoven - The Netherlands
Key fingerprint - 66 4E 03 2C 9D B5 CB 9B  7A FE 7E C1 EE 88 BC 57