[omniORB] omniORB works in loopback but fails when wirred network added

Meyer, Brad A bradley.meyer at aecom.com
Fri Mar 27 14:26:08 GMT 2015


As a new user, I have stumbled into an omniORB ( version 4.1.6) related problem with RedHawkSDR ( version 10.2R2015013000031) in a python program running under CentOS 6 (2.6.32-504.e16 X86-64).

The program works if there is no network connection except the loopback, but fails if I connect a wired network (listed as System ethO).

At first I assumed omniORB was getting confused about what IP to use, and added an explicit endpoint to the config file, but that did not fix the problem.

It appears I am getting stuck (see below for  details), then timed out when attempting to do

               "omniORB: Scan for idle connections (142707427, 11435000)"


    Details ======================================================

*         I do not specify any IP address in the python program

*         the fire wall is off

*         omniORB.cfg
    traceLevel=40
    InitRef = NameService=corbaname::127.0.0.1:2809
    supportBootstrapAgent = 1
    InitRef = EventService=corbaloc::127.0.0.1:11169/omniEvents
    endPoint = giop:tcp:127.0.0.1:


*         Snippet of log data for case where eth0 is connected
     omniORB: omniORBpy distribution date: Fri Jul  1 14:52:31 BST 2011 dgrisby
     omniORB: Python thread state scavenger start.
     omniORB: Initialising incoming endpoints.
     omniORB: Instantiate endpoint 'giop:tcp:127.0.0.1:'
     omniORB: Explicit bind to host 127.0.0.1.
     omniORB: Bind to address 127.0.0.1 ephemeral port.
     omniORB: Publish specification: 'addr'
     omniORB: Try to publish 'addr' for endpoint giop:tcp:127.0.0.1:46877
     omniORB: Publish endpoint 'giop:tcp:127.0.0.1:46877'
     omniORB: Starting serving incoming endpoints.
     omniORB: AsyncInvoker: thread id = 2 has started. Total threads = 1
     omniORB: giopRendezvouser task execute for giop:tcp:127.0.0.1:46877
     ==>omniORB: SocketCollection idle. Sleeping.
     omniORB: State root<0> (active) -> deactivating

NOTE: WHEN THE NETWORK IS NOT CONNECTED, THE LINE AFTER " ==>" IS
"omniORB: Scan for idle connections (142707427, 11435000)"
which is where it looks like I am getting stuck, then timed out when the network is connected


*         ifconfig shows loopback running
    Link encap:Local Loopback
    inet addr:127.0.0.1  Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING  MTU:65536  Metric:1
    RX packets:302 errors:0 dropped:0 overruns:0 frame:0
    TX packets:302 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:26197 (25.5 KiB)  TX bytes:26197 (25.5 KiB)



*         ping 127.0.0.1 works, so it is possible to access it


*         netstat -tulpn SHOWS OMIN CONNECTED TO SOME PORTS


Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address          Foreign Address  State       PID/Program name
tcp        0      0 127.0.0.1:42451        0.0.0.0:*        LISTEN      2409/omniEvents
tcp        0      0 REDACTED FOR POST      0.0.0.0:*        LISTEN      2617/dnsmasq
tcp        0      0 0.0.0.0:50517          0.0.0.0:*        LISTEN      2067/rpc.statd
tcp        0      0 0.0.0.0:22             0.0.0.0:*        LISTEN      2254/sshd
tcp        0      0 127.0.0.1:631          0.0.0.0:*        LISTEN      2098/cupsd
tcp        0      0 127.0.0.1:25           0.0.0.0:*        LISTEN      2346/master
tcp        0      0 127.0.0.1:42251        0.0.0.0:*        LISTEN      2022/omniNames
tcp        0      0 0.0.0.0:111            0.0.0.0:*        LISTEN      1902/rpcbind
tcp        0      0 :::39409               :::*             LISTEN      2067/rpc.statd
tcp        0      0 :::22                  :::*             LISTEN      2254/sshd
tcp        0      0 ::1:631                :::*             LISTEN      2098/cupsd
tcp        0      0 ::1:25                 :::*             LISTEN      2346/master
tcp        0      0 :::2809                :::*             LISTEN      2022/omniNames
tcp        0      0 :::11169               :::*             LISTEN      2409/omniEvents
tcp        0      0 :::111                 :::*             LISTEN      1902/rpcbind

    Things I've tried ======================================================

*         added and left in place  "endPoint = giop:tcp:127.0.0.1:" to cfg file

After that failed, I tried (as drowning men grab at straws) and removed

*         clientTransportRule = localhost tcp

*         clientTransportRule = "127.0.0.1" tcp

*         clientTransportRule = 127.0.0.1 tcp

*         clientTransportRule = 127.0.0.1/255.255.255.0 tcp

*         serverTransportRule = localhost tcp

*         serverTransportRule = "127.0.0.1" tcp

*         serverTransportRule = 127.0.0.1 tcp

*         serverTransportRule = 127.0.0.1/255.255.255.0 tcp

*         clientCallTimeOutPeriod = 2000

*         oneCallPerConnection = 0

*         maxGIPConnectionPerServer = 10

*         giopTargetAddressMode = 0 1 and 2

*         threadPerConnectionPolicy = 1

*         clientTransportRule = <127.0.0.1> tcp

*         scanGranularity = 0

*         Turning off anything in the OS remotely connected to IP


Any constructive guidance would be appreciated

Best Regards,

Brad Meyer


Brad Meyer
Senior Engineer,  EW Maritime- Crane Operations
D 1-812-863-5092    C 1-317-590-3547
Bradley.Meyer at aecom.com<mailto:Bradley.Meyer at aecom.com>

AECOM
13923 E CAPT WJ Nelson Drive, Odon, Indiana 47562
T 1-812-863-5001     F 1-812-863-5011
www.aecom.com<http://www.aecom.com/>

This electronic communication, which includes any files or attachments thereto, contains proprietary or confidential information and may be privileged and otherwise protected under copyright or other applicable intellectual property laws. All information contained in this electronic communication is solely for the use of the individual(s) or entity to which it was addressed. If you are not the intended recipient(s), you are hereby notified that distributing, copying, or in any way disclosing any of the information in this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately, and destroy the communication and any files or attachments in their entirety, whether in electronic or hard copy format. Since data stored on electronic media can deteriorate, be translated or modified, AECOM, its subsidiaries, and/or affiliates will not be liable for the completeness, correctness or readability of the electronic data. The electronic data should be verified against the hard copy.

Please consider the environment before printing this e-mail.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20150327/fd1b3804/attachment-0001.html>


More information about the omniORB-list mailing list