[Nut-upsuser] MGE 800, ttyS0, frequent timeout

[Gaspar Bakos]

Dear all,

I am having trouble with
MGE Pulsar Evolution 800 Tower UPS.

I use this UPS on several computers under RH9.0 O/S -- and the effect
is the same.

Each computer has two UPS connected: one on ttyS0 (MGE) and the other
on ttyS1 (generic). One UPS is MGE, the other one is usually some
inexpensive generic UPS.

The software I am running is nut-2.0.3.

After starting up the UPS utilities (/etc/rc.d/init.d/ups start), this
is a typical message:

Broadcast message from nut (Tue Dec 26 17:38:35 2006):
Communications with UPS hat_PC_ups at localhost lost
Broadcast message from nut (Tue Dec 26 17:38:45 2006):
Communications with UPS hat_PC_ups at localhost established
...
And this goes on forever. Sometimes the connection is lost, sometimes
it is established. After a while (hours, maybe up to a day) the
mge-shut software disappears from the process list.

I guess maybe pollfreq is too small? But that still does not explain
why mge-shut dies away.

When it works, I get the following output:

[root at hat5 root]# upsc hat_PC_ups at localhost
battery.charge: 100
battery.charge.low: 20
battery.runtime: 02175
driver.name: mge-shut
driver.parameter.port: /dev/ttyS0
driver.version: 2.0.3-pre1
driver.version.internal: 0.65
input.frequency: 59
input.voltage: 116
outlet.0.desc: Main Outlet
outlet.0.id: 0
outlet.0.switchable: 0
outlet.1.autoswitch.charge.low: 0
outlet.1.delay.shutdown: -1
outlet.1.delay.start: -1
outlet.1.desc: PowerShare Outlet 1
outlet.1.id: 1
outlet.1.switch: 1
outlet.1.switchable: 1
outlet.2.autoswitch.charge.low: 0
outlet.2.delay.shutdown: -1
outlet.2.delay.start: -1
outlet.2.desc: PowerShare Outlet 2
outlet.2.id: 2
outlet.2.switch: 1
outlet.2.switchable: 1
output.frequency: 59
output.voltage: 116
output.voltage.target.battery: 120
output.voltage.target.line: 120
ups.delay.shutdown: -1
ups.delay.start: -1
ups.load: 20
ups.mfr: MGE UPS SYSTEMS
ups.power.nominal: 800
ups.serial: unknown
ups.status: OL CHRG
ups.test.result: Done and passed

-------------
And here is my config (potentially relevant files):

 =================== ups.conf ==================
maxstartdelay = 60
[hat_PC_ups]
 	driver = mge-shut
	port = /dev/ttyS0
	sdorder = 0

[hat_HAT_ups]
 	driver = genericups
	port = /dev/ttyS1
	sdorder = 1
	upstype = 11

 =================== upsd.conf ==================
ACL all 0.0.0.0/0
ACL localhost 127.0.0.1/32

ACCEPT localhost
REJECT all

MAXAGE 30

 =================== upsd.users ==================
[nut]
	password = ******
	allowfrom = localhost 127.0.0.1
	actions = SET
	instcmds = ALL
	upsmon master

 =================== upsmon.conf ==================
RUN_AS_USER nut
MONITOR hat_PC_ups at localhost 1 nut **** slave
MONITOR hat_HAT_ups at localhost 1 nut **** master
MINSUPPLIES 1

SHUTDOWNCMD "/sbin/shutdown -h now"

# GB: This launches a scheduler
NOTIFYCMD /usr/sbin/upssched

POLLFREQ 10

POLLFREQALERT 5

HOSTSYNC 15

DEADTIME 30

POWERDOWNFLAG /etc/killpower

NOTIFYMSG ONLINE "Power restored on UPS: %s"
NOTIFYMSG ONBATT "Power failure detected on UPS: %s"
NOTIFYMSG LOWBATT "Low battery status reached on UPS: %s"
NOTIFYMSG FSD "Forced shutdown due on UPS: %s"

NOTIFYFLAG ONLINE SYSLOG+EXEC
NOTIFYFLAG ONBATT EXEC+SYSLOG
NOTIFYFLAG LOWBATT SYSLOG+EXEC
NOTIFYFLAG FSD SYSLOG+EXEC
NOTIFYFLAG SHUTDOWN SYSLOG+EXEC

RBWARNTIME 43200

NOCOMMWARNTIME 300

FINALDELAY 5

 =================== upssched.conf ==================
CMDSCRIPT /etc/ups/upssched-cmd
PIPEFN /pervar/state/ups/upssched.pipe
LOCKFN /pervar/state/ups/upssched.lock

AT ONBATT hat_PC_ups at localhost START-TIMER onbattwarn_hat_PC_ups 120

# If PC UPS gets back power, then cancel timer:
#
AT ONLINE hat_PC_ups at localhost CANCEL-TIMER onbattwarn_hat_PC_ups

AT ONBATT hat_HAT_ups at localhost START-TIMER onbattwarn_hat_HAT_ups 150
AT ONLINE hat_HAT_ups at localhost CANCEL-TIMER onbattwarn_hat_HAT_ups