Hello @aharonya,

From the error message, it does not seem that your instance of LPC is able to connect upstream.

After the connectivity was resolved by your network team, was there a change in the error message, in LPC log, or it remains "

RSSL login failed for user: <USER> Text: Error querying service discovery: Failed to send a request to the token service. Text: </local/jenkins/workspace/RRTLPC/OS/OL7-64/esdk/source/esdk/Cpp-C/Eta/Impl/Reactor/Util/rsslRestClientImpl.c:1594> Error: Failed to perform the request with text: Couldn't resolve host name."

?

You can try enabling, in your lpc.cnf, Trace options:

!!      Tracing information !! *lpc*debugTrace : True *lpc*dumpIncoming : True *lpc*dumpOutgoing : True

Restart LPC and attach the log

Hello @aharonya,

It does not look like your instance of LPC/Refinitiv Realtime Testing Environment is able to connect upstream. Likely, because you are unable to obtain the valid dictionary, as the error message suggests.

I would check what you have configured in lpc.cfg, in sections "Token Retrieval and Service Discovery Parameters" and "Dictionary Parameters".

By default, you should be connecting to the set of endpoints in your geographical region, and the dictionary download should be configured to False, resulting in using the local dictionary that came with the installation.

If your dictionary download is False, I would also verify that the dictionary exists where it's configured to be loaded from, for example:

*lpc*enumFile : ../../etc/enumtype.def
*lpc*fieldDictionary : ../../etc/RDMFieldDictionary

And the files are permissioned for reading, by the user running LPC, for example:

[]# pwd
/opt/refinitiv/SOFTWARE/lpc1.1.0.L1.linux.tis.rrg/linux7_x86_64/bin
[]# ls -l ../../etc/RDMFieldDictionary
-rwxr-xr-x 1 1069 926 1946314 Jul 22  2020 ../../etc/RDMFieldDictionary

I would also verify, with your network admin/group, the availability of the network connectivity, as specified in the configuration as Discovery.

Let us know how this works for you.

lpc_log.txt

@zoya.farberov Thanks for your help. I've found the issue with help of our IT - it was an firewall issue.

But I have now another problem. This is what I'm getting when running the rdmtestClient from the client machine

C:\ThomsonReuters\ezd1.3\win_x86_64\demo>rmdstestClient.exe -h <LPC HOST> -u <USER> -P 14002 -itemList GBP= -S ELEKTRON_DD -d 3 -X
Number of Connection Count = 1
Creating RSSL connection Host: <LPC HOST> Port: 14002
UPA server component version: lpc1.2.0.L1.linux.rrg 64-bit
Setting rmds connection 0000000002E86D60
Connection list count is 1

No service status events received after five seconds.
Service events should be returned immediately.
Data cannot be requested until services are available.
Received login message.
RSSL login failed for user: <USER> Text: Error querying service discovery: Failed to send a request to the token service. Text: </local/jenkins/workspace/RRTLPC/OS/OL7-64/esdk/source/esdk/Cpp-C/Eta/Impl/Reactor/Util/rsslRestClientImpl.c:1594> Error: Failed to perform the request with text: Couldn't resolve host name.

Just note:

1. When I run the

 rmdstestClient.exe -h localhost ... ... 

(within the client machine) it works good.

2. I've tried first to put in the LPC machine the same user_list.txt as I have on the client machine (and works well without the LPC) - but it failed. Then I've tried to create a new user_list.txt via the installation script - but it failed too.

What I did wrong?

Thanks!!

Hello @aharonya,

Let me confirm that we understand exactly what you are seeing.

1. LPC is running now?
2. When you connect rmdstestclient from the same machine via localhost, you can see streaming data?
3. When you connect rmdstestclient from the same machine via ip address you cannot connect?
4. Or when you connect from the same machine by hostname?
5. Or when you connect from a different machine by hostname?
6. Or?