ups_mond ups_cond dev file problem

[Doug_3]

Our ups_mond and ems had been turned off for our power trust ups on an hp9000 (rp7400). Upon restart we are seeing this messsage:
/usr/lbin/ups_mond: AC Power
to all recognized, system critical UPS's OK! System will not shutdown.
Oct 17 13:27:17 sd81hp9k /usr/lbin/ups_mond[22628]: /usr/lbin/ups_mond: UPS /dev
/tty1p0 interrupted but read of ups status failed - possible UPS hardware problem

The ups_conf is pointing to tty1p0 and the character file exists with these rights:
crw--w--w- 1 bin bin 1 0x010000 Oct 17 12:18 /dev/tty1p0

Ideas on why the ups_mond can claim the ups is ok but the second msg is claiming it can't read the status of the ups?

[Doug_3]

Ooops, I forgot to report that upon starting ups_mond the syslog msg was:
/usr/lbin/ups_mond[1600]: /usr/lbin/ups_mond: UPS /dev/
tty1p0 write failed: Bad file number; ignoring that UPS

Thanks in advance,
Doug

[jerry1 · Accepted solution]

I ran into something similar with a software
product that uses /dev/lan1. I had to change
the perms to 666. And I had to do that
everytime the system was rebooted.
What owner is ups_mond running as?