How come I am getting these error messages on system console?

[Zhang Zhao gui]

After a AC power failure at 3:45am, I was called to sit down before the system
console at 9:30am, I saw the server hang with the following messages appeared
on the system console,
INIT: command is responding too rapidly.
will try again in 5 minutes
check for possible errors
id: a0 "/usr/lbin/uucp/uugetty -r -t 60 -h ttyd0p7 9600"
...
id:vue "/usr/vue/bin/vuerc
will try again in 5 minutes
id:cons "/usr/sbin/getty console console
will try again in 5 minutes
id:ems4 "/etc/opt/resmon/lbin/p_client".

I found the above commands are all inside /etc/inittab.
But how come I was getting these messages and never get
"console login" prompt? Is the system shutting down or booting up when I saw
these messages?
Is there anybody encountered this problem before?

[Randy Mather]

boot in single user modeand see if your device files are there. Can you login
to the system ?
The device files may be missing.

[Frank Piccolino]

One reason you are seeing these errors is that the /etc/inittab file may be
corrupt or contain an incorrect entry. There is a default inittab file in
/usr/newconfig/etc

[Zhang Zhao gui]

I don't think /etc/inittab is corrupted. Because when the system hang, I do a
"TOC" to reboot the system and
it can still boot up properly. In addition, I check
against the same file on another server and they have same contents As for
the message in my previous post, I found it just kept cycling a retrying cycle
of 5 minutes. I can't even get "login:" prompt and also cannot issue any
commands or go to single user mode unless go to service mode and did a "TOC".

As for the device files, I don't know what you mean. All the devices files
including those for disks,tapes,
terminals,etc.

[Randy Mather]

device files for tty and pty.
also check a files called dld.sl in /usr/lib
it is needed for most commands.

[Alan Riggs_1]

Are you using NIS for host or user administration? I have seen init spawn out
of control if no NIS master is available when a client boots.

[Zhang Zhao gui]

Sorry to reply you so late. I just returned from a long leave.

Reply to Alan's question:
No, I don't use NIS for host or user administration.
I checked /etc/rc.log.old and found that the system
does not have enough time to shutdown all processes gracefully and in the end
just killed whatever is left.
At the end of this file, it shows as below,
Output from "/sbin/rc1.d/K900swagentd stop":
----------------------------
The swagentd daemon is stopped.

Stop syncer daemon
Output from "/sbin/rc0.d/K480syncer stop":
----------------------------
Syncer stopped

Killing user processes
Output from "/sbin/rc0.d/K800killall stop":
----------------------------

Unmount file systems
Output from "/sbin/rc0.d/K900localmount stop":
----------------------------
umountall: umount : has failed.
umountall: diagnostics from umount
umount: cannot unmount /usr : Device busy
umountall: umount : has failed.
umountall: diagnostics from umount
umount: cannot unmount /var : Device busy

Do you think in this case it will cause system hang
when it tried to boot up next time and generated those
error messages on the system console as I mentioned
before?