next up previous contents
Next: 8.3 OWD Component Editor Up: 8 Troubleshooting Previous: 8.1 nodeBooter Throws an   Contents


8.2 nodeBooter Fails to Resolve `TRANSIENT' NameService

When I try to start nodeBooter I get this mess:
 $ nodeBooter -D -d nodes/default_GPP_node/DeviceManager.dcd.xml
 Failed to resolve NameService: TRANSIENT
 terminate called after throwing an instance of 'CORBA::TRANSIENT'
 Aborted
Solution: You need to start the naming service. If you installed omniORB from from RPM (see Section 3.2.2) omniNames will start automatically when you restart your machine. You can manually start the omniNames by creating and running the shell script described in Appendix C.



2008-04-25