Ignite and UPS

[Heath Ramos]

I have 2 HP9000 D class servers both running HP-UX 11.0. One server had a bunch of changes done to it so I decided to create a new ignite tape (all of vg00) and then re-create the new server using that tape. That is how the 2nd server was created in the first place, so I know it should work. When I did it this time, it completed the install but the ups shuts it down every time I get to the logon prompt. The error message is: ups_mond[1229]: /usr/lbin/ups_mond: reboot -halt invoked due to UPS error cited in previous syslog message. /usr/lbin/ups_mond: UPS /dev/tty1p0 could not execute command S120
ked; returned (octal 74).

Any idea what would cause this and how I would get it fixed? It seems that is may not be communicating with the UPS but it was working before and how would I fix it w/o being able to log on at all?

[Steven E. Protter · Accepted solution]

If the UPS was hung off a different Serial port, you may need to adjust the ups_mond.conf file to reflect that.

If its the same, it should have been replicated by Ignite. Our UPS settings and function replicate just fine among three HP-9000 rp5450 servers.

Take a look at /etc/inittab and make sure that got replicated properly, if not make adjustment.

Is it possible the serial device isn't working on the second server.

It would be interesting to see what command you used to create the Ignite archive. make_tape_recovery ...

Just to get out of this horrible loop, try booting the box into single user mode.

With vi disable the ups line of /etc/inittab and /etc/ups_mond.conf

At least the system will boot and you can do further diagnosis.

Hopefully, unless there were other problems with the Ignite transfer.

Any errors in the log when you made the tape?

SEP

[Jim Mallett]

I see this each time I do a DR test offsite and Ignite to a different machine.
It's likely issues with records in your /etc/inittab file.
If you can get the machine into single user mode, edit the ups record in the inittab file by either correcting it or #pounding it out so you can test.
I see this error on modems also because the serial devices are not hooked up to the same port on the new machine.

Jim

[Heath Ramos]

Well...I can boot to single user mode.

How do I edit files from here?

vi isn't a recognized command anymore.

Do I need to be in a particular directory?

[Steven E. Protter]

mouunt /usr

Now you can use vi

SEP

[Heath Ramos]

Thanks for the help.

Once I mounted /usr and exported TERM, vi worked okay.

Of course the # didn't work for some reason but everything is okay now.

I just need to get one of my volume groups back and restore from tape and I am good to go.