Getting "COMMENDSrReaderService_assertRemoteWriter:!create reachable destination" when I run

4 posts / 0 new
Log in or register to post comments
Last post
Tue, 12/17/2013 - 15:49
#1
mwkozak
Offline
Last seen: 10 years 11 months ago
Joined: 11/05/2013
Posts: 2
Getting "COMMENDSrReaderService_assertRemoteWriter:!create reachable destination" when I run

I'm seeing a strange error outputting in the console when I run my software. The error disappeared for a while without making any changes, and then reappeared and has continued to appear even after a system restart. I didn't see anything for it in the knowledge base, documents, or the forums. Any idea what's causing it?

 

The full error:

COMMENDSrReaderService_assertRemoteWriter:!create reachable destination
can't reach:
   locator:
      transport: 2
      address: 0002:0403:0200:0000:0000:0000:0000:0000
      port: 7662
      encapsulation:
   transport_priority: 0
   aliasList: ""
COMMENDSrWriterService_assertRemoteReader:!create reachable destination
COMMENDSrWriterService_assertRemoteReader:!create reachable destination
COMMENDSrWriterService_assertRemoteReader:!create reachable destination
COMMENDSrReaderService_assertRemoteWriter:!create reachable destination
can't reach:
   locator:
      transport: 2
      address: 0002:0403:0200:0000:0000:0000:0000:0000
      port: 7662
      encapsulation:
   transport_priority: 0
   aliasList: ""
COMMENDSrReaderService_assertRemoteWriter:!create reachable destination
can't reach:
   locator:
      transport: 2
      address: 0002:0403:0200:0000:0000:0000:0000:0000
      port: 7662
      encapsulation:
   transport_priority: 0
   aliasList: ""
 

Organization:
Top
Mon, 12/30/2013 - 07:15
michelledo
Offline
Last seen: 10 years 8 months ago
Joined: 12/19/2013
Posts: 5

Hi,

I am having the same problem.  My DDS message works fine using UDP transport.  Now that I have a requirement to run this processes in a standalone machine, I switched to use shared memory and started to get this message.  None of my apps are able to communicate to each other anymore when  I switch to shared.  They all display this error at discovery phase:

COMMENDSrReaderService_assertRemoteWriter:!create reachable destination
can't reach:
   locator:
      transport: 2

 

Please help!

Thanks,

Michelle

 

Top
Thu, 01/02/2014 - 11:03
rose
rose's picture
Offline
Last seen: 3 years 5 months ago
Joined: 08/22/2011
Posts: 148

Hello Michelle and mwkozak,

That message is stating that the application is trying to contact a shared memory region and failing.  ("transport: 2" is shared memory).

Here are a couple of things to check:

  1. Have you changed your initial peers?  Maybe you have a peer that is pointing to an invalid shared memory address.  Make sure that "shmem://" is one of your initial peers.
  2. What OS are you running?  It might be possible that the applications do not have permission to access the shared memory regions created by other applications.
  3. Are all applications configured with the same transport settings?

Thank you!

Rose

Top
Fri, 01/03/2014 - 22:15
michelledo
Offline
Last seen: 10 years 8 months ago
Joined: 12/19/2013
Posts: 5

Thank you for you response Rose. 

I changed it back to use UDPv4 with unicast and that works for my standalone environment. 

To answer your question:

1.  I did not set any initial peers.  Could this be the cause?

2.  OS is CentOS.  all apps are running as same user, so don't think they have permission problem

3. All apps are using the same QOS_USER_PROFILES.xml, so they all have same setting.

 

THanks,

Michelle

Top