On a quick scan of your output, my first thought would be; The server in question thinks that a critical part of it's filesystem is an NFS-share mount from another system.
Originally Posted by kingston
Dec 7 12:28:29 einbalx0003 automount: failed to mount /efsroots/10/project/build.sh
Dec 7 12:29:30 einbalx0003 automount: lookup(yp): key "build.sh" not found in map.
Dec 7 12:29:30 einbalx0003 automount: failed to mount /efsroots/10/project/build.sh
Dec 7 12:30:01 einbalx0003 automount: lookup(yp): key "opc_op" not found in map.
Dec 7 12:30:01 einbalx0003 automount: failed to mount /home/opc_op
" is a lookup from ypbind to contact and mount an NFS share. Is the server that those filesystems are housed on powered up and available from the network? Also, is the problem-server's /etc/hosts file okay? Ypbind relies on /etc/hosts, as noted here.
Also, I note that RHEL 4.7 is running a 2.6.9-based linux kernel. While I know that you don't want to do it while the server is having an issue, once you have the server stabilized, I'd recommend getting that one updated at your next available opportunity. Current stable linux kernel source for Gentoo right now is 2.6.34-r6, and there have been some kernel-level security issues addressed between 2.6.9 and 2.6.34.
HTH. Let us know.