0
由於某種原因，omniNames服務不會啓動（再次），但如果調用omniNames可執行文件，它將毫無問題地啓動。這個問題似乎每隔一段時間就會重複出現一次。omniNames服務不會啓動，但直接調用可執行文件
調用omniNames似乎開始罰款...
>> sudo /sbin/service omniNames start
Starting omniNames: [ OK ]
然而，檢查的狀況和上市命名服務對象後，顯而易見的是，omniNames沒有成功啓動：
>> sudo /sbin/service omniNames status
omniNames is stopped
>> nameclt list
Caught a TRANSIENT exception when trying to validate the type of the
NamingContext. Is the naming service running?
如果我嘗試直接調用omniNames可執行文件並要求它在相同的端口上啓動，則一切正常。
>> sudo omniNames -start 2809
Fri Feb 14 18:48:35 2014:
Starting omniNames for the first time.
Wrote initial log file.
Read log file successfully.
Root context is IOR:010000002b00000049444c3a6f6d672e6f72672f436f734e616d696e672f4e616d696e67436f6e746578744578743a312e30000001000000000000006c000000010102000a00000031302e322e382e333500f90a0b0000004e616d6553657276696365000300000000000000080000000100000000545441010000001c00000001000000010001000100000001000105090101000100000009010100035454410800000053abfe5201001037
Checkpointing Phase 1: Prepare.
Checkpointing Phase 2: Commit.
Checkpointing completed.
>> nodeBooter -D
INFO:DomainManager - Starting Domain Manager
WARN:EventChannelSupport - Invalid Criteria for creating event channel REDHAWK_DEV.ODM_Channel
WARN:EventChannelSupport - Invalid Criteria for creating event channel REDHAWK_DEV.IDM_Channel
INFO:DomainManager - Starting ORB!
>> nameclt list
EventChannelFactory
REDHAWK_DEV/
我已經嘗試過刪除日誌，因爲這裏建議：Error When Starting OmniEvents
僅供參考，我運行的Centos 6.4 64位。另外，/etc/omniORB.cfg的內容是：
InitRef = NameService=corbaname::127.0.0.1:2809
supportBootstrapAgent = 1
InitRef = EventService=corbaloc::127.0.0.1:11169/omniEvents
任何想法還有什麼可能是錯的？