启动OmniEvents时出错 [英] Error When Starting OmniEvents

问题描述

我正在尝试在32位CentOS 6.4的全新安装上安装REDHAWK v1.8.2，但是我无法启动omniNames和omniEvents.

I am attempting to install REDHAWK v1.8.2 on a fresh install of CentOS 6.4 32 bit, but I am unable to get omniNames and omniEvents to start.

sudo /sbin/service omniEvents stop
Stopping CORBA event service: omniEvents

sudo /sbin/service omniNames stop
Stopping omniNames                                         [  OK  ]

sudo /sbin/service omniNames start
Starting omniNames                                         [  OK  ]

sudo /sbin/service omniEvents start

Starting CORBA event service on port 11169: omniEvents: [25848]: Warning - failed to resolve initial reference 'NameService'. Exception: TRANSIENT
omniEvents.

我试图通过调用命名客户端来验证omniNames是否确实在运行，但是出现了错误(请参见下文)，因此似乎omniNames无法成功启动.

I tried to verify if omniNames was really running by calling the naming client, but got an error (see below), so it seems omniNames is not successfully starting.

nameclt list
Caught a TRANSIENT exception when trying to validate the type of the 
NamingContext. Is the naming service running?

作为调试过程的一部分，我试图杀死omniNames进程并以另一种方式启动它(见下文).

As part of the debugging process, I tried to kill the omniNames process and start it a different way (see below).

sudo killall omniNames
omniNames -start

Wed Nov 13 21:08:08 2013:

Starting omniNames for the first time.
Error: cannot create initial log file '/var/omninames/omninames-orion.log': 
No such file or directory

You can set the environment variable OMNINAMES_LOGDIR to specify the
directory where the log files are kept.

我不确定为什么omniNames无法创建日志文件，因为我验证了/var/omninames文件夹确实存在，甚至以root身份启动omniNames都会产生相同的错误.无论如何，我都会将日志目录设置到桌面上以避开该错误(请参见下文).

I'm not sure why omniNames can't create the log file, because I verified that /var/omninames folder actually exists and even starting omniNames as root yields the same error. Regardless, I set the log directory to my desktop to circumvent the error (see below).

export OMNINAMES_LOGDIR=/home/$USER/Desktop/logs
mkdir -p /home/$USER/Desktop/logs
omniNames -start

Wed Nov 13 21:09:17 2013:

Starting omniNames for the first time.
Wrote initial log file.
Read log file successfully.
Root context is IOR:010000002b00000049444c3a6f6d672e6f72672f436f734e616d696e672f4e616d696e67436f6e746578744578743a312e30000001000000000000005c000000010102000a00000031302e322e382e333500f90a0b0000004e616d6553657276696365000200000000000000080000000100000000545441010000001c00000001000000010001000100000001000105090101000100000009010100
Checkpointing Phase 1: Prepare.
Checkpointing Phase 2: Commit.
Checkpointing completed.

即使看起来好像已经成功启动了omniNames，但是当我打开另一个终端窗口并调用命名客户端时，也会遇到与以前相同的错误(见下文).

Even though it looks like omniNames successfully started, when I open another terminal window and call the naming client, I get the same error as before (see below).

nameclt list
Caught a TRANSIENT exception when trying to validate the type of the 
NamingContext. Is the naming service running?

我在/etc/omniORB.cfg文件中所做的唯一修改是为InitRef添加行(见下文).

The only modification I made in the /etc/omniORB.cfg file is to add the lines for InitRef (see below).

InitRef = NameService=corbaname::localhost
InitRef = EventService=corbaloc::localhost:1169/omniEvents

此外，我没有连接到互联网，因此除本手册附录J中推荐的Boost库(

Also, I am not connected to the internet so my version of CentOS has not been updated from the base version, except for the boost libraries as recommended in Appendix J of the manual (http://sourceforge.net/projects/redhawksdr/files/redhawk-doc/1.9.0/REDHAWK_Manual_v1.9.0.pdf/download).

推荐答案

问题似乎出在您的配置中.配置文件中的端口错误.应该是端口11169，但是您已列出端口1169.

Looks like the issue is in your configuration. You've got the wrong port in your configuration file. It should be port 11169 however you've listed port 1169.

请参阅: http://redhawksdr.github.io/Documentation/mainch2. html#x4-120002.6 了解详情.

关于omniOrb的其他一些观察和技巧，以防这不是问题.

A few other observations and tricks regarding omniOrb in case this was not the issue.

• 有时，全名/全名可能会进入错误状态.解决方法是删除由omniNames和omniEvents创建的日志文件，然后重新启动服务.它们位于:

• Sometimes omninames/omnievents can get into a bad state. The fix is to delete the log files created by omniNames and omniEvents and restart the services. They are located:

/var/lib/omniEvents/*

/var/lib/omniEvents/*

/var/omniNames/*

/var/omniNames/*

您需要是root用户才能删除这些文件.我总是忘记了它们的位置，并经常执行"locate omni | grep -i log"来提醒自己，但是由于它们对于标准用户不可见，因此您必须以root用户身份进行操作.

You'll need to be root to delete those files. I always forget where they are located and often do a "locate omni | grep -i log" to remind myself but you must do this as root since they are not visible to standard users.

• 尽管没关系，但我个人发现使用127.0.0.1比本地主机更可靠.出于某种原因，过去在配置文件中的VM中使用localhost导致了我的问题.考虑使用127.0.0.1代替localhost.这也是当前版本的《 Redhawk手册》所推荐的.

• While it should not matter, I've personally found that using 127.0.0.1 is more reliable than localhost. For some reason, using localhost within a VM in the configuration file has caused me problems in the past. Consider using 127.0.0.1 instead of localhost. This is what the current version of the Redhawk Manual recommends as well.

您提到您正在使用Redhawk v1.8.2.作为FYI，1.8系列中的最新REDHAWK版本当前为v1.8.5，最近还发布了1.9.0.

You mentioned you are using Redhawk v1.8.2. As an FYI, the latest REDHAWK version in the 1.8 series is currently v1.8.5 and 1.9.0 was also recently released.

希望这能使您启动并运行！

Hopefully this gets you up and running!

这篇关于启动OmniEvents时出错的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！