omn​​iNames服务无法启动，但直接调用可执行文件

Question

由于某种原因，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 x64。此外，/ etc / omniORB.cfg的内容是：

InitRef = NameService=corbaname::127.0.0.1:2809
supportBootstrapAgent = 1
InitRef = EventService=corbaloc::127.0.0.1:11169/omniEvents

知道还有什么可能是错的吗？

Answer 1

除了您引用的上一篇文章中列出的文件外，您可能还需要删除/ var / log / omniORB中的文件。

删除名为：

的文件

/var/log/omniORB/omninames-<computer_name>.bak
/var/log/omniORB/omninames-<computer_name>.log

然后再次尝试启动omniNames并查看它是否正常启动。