tovis wrote: > For now I think that my box does not recognize signal about low battery - > I'm only started to read SHUT protocoll of MGE, and do not understand that > is this signal a result of some kind of status request from my box to UPS > or UPS send this signal "unsolicited" - I supose the last idea!
The mge-shut driver will ignore anything sent by the UPS unsolicited. > May be I need higher POLLFREQ on "ONBATTRY" situation - about 1..2 sec?! This is not the problem. Your setup seems to work fine when the load is 120W and only fails to do what you expect at a 300W load. This means that the driver is able to read the status from the UPS and acts accordingly (by shutting down your system). Unfortunately, at the higher load, the time to shutdown the system takes too long for the remaining capacity of the batteries, so the UPS will shutdown itself. You need to verify a couple of things here: 1) Does the shutdown sequence take too long? 2) How old are the batteries? Could it be they are already worn out (you can expect this after 3-5 years and even sooner at temperatures above 25 degrees centigrade. 3) Is the load really 300W? A MGE Pulsar Evolution 800 should have a runtime of about 10 minutes with a load of around 300W, so if it is significantly less you should really checkout item 2 (and maybe 3). Forcing a battery check may be a good idea. You didn't mention which NUT version you're using. If it is anything recent (nut-2.0.5 or higher) you might want to try the 'newmge-shut' driver, which is an improved version. Best regards, Arjen _______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
