LPC fail to start on a cloned linux machine
Hi team,
I have successfully installed LPC tool on a linux machine and also able to receive data using the rmdstetsclient tool. Now I cloned the linux machine into a different vm so that I have the same setup that I had in the first machine. But now when I start LPC it fails with error "LPC Error: Initialization failed: : Initialization Failed -Check Program Log-".. After I checked the logs I found error in "retrieving the IP address of the Protocol Converter process".
Can I please get some help to understand the issue and how to resolve it?
Attached are the error logs.Logs.txt
Thank you,
Bansal
Best Answer
-
Hello @bansalshah,
My thoughts are that I would reinstall LPC on the cloned machine, as you would on a new machine.
The installation should be quick, and as you follow Installation Guide, this approach should result in a valid installation on a Refinitiv Real-Time LPC.
0
Answers
-
Hi @zoya faberov,
Thank you for the quick response. I tried reinstalling the LPC as well on the cloned machine, but same error as before.
0 -
Hi @bansalshah,
If you have installed LPC fully according to the Installation Guide and are not able to start LPC, I would look into the health of the machine itself.
I am not a network admin, and thinking that your local network admin may be of more help on this, few things I'd check:
- Does ifconfig look good compared to the other machine, you can see unique IP address assigned to this machine?
- Does hostname yield the hostname you expect?
- Can you ping and telnet to outside machines successfully?
LPC Installation procedure pre-requires that the installation host itself is fully setup and networked. If any issues with this, try contacting your local network admin to verify this?
0 -
Hi @zoya faberov,
Everything you mentioned is resulting in correct output.
1. Both machine have unique IP address.
2. Both machine have the correct hostname as expected.
3. Both machine are on the same network and setup exactly the same.
Can it be anything else that I need to take into account for this?
I will not take much of your time but just good to know what is wrong if machine is properly set up?
0 -
Hi @zoya faberov,
Also under what circumstances is Reuters LPC code going to throw the following error :
"Could not find the retrieve the IP address of the Protocol Converter process"
Thank you
0 -
Hello @bansalshah,
I trust that you are using a different machine ID on the second instance, i.e. not the same machine ID on two LPCs simultaneously.
Just as a sanity check, in the off hours, I would shut down the first LPC, restart the second, connect rmdstestclient and see if that changes the situation.
The error message that you see is not, as you probably have noticed, is listed in the latest "Troubleshooting" section of the Installation Guide among the commonly found troubleshooting issues. I have contacted the product, to see if we can get more insight as to the nature of the possible issue. We appreciate your patience.
0 -
Usually the problem is that the machine hostname is not in the /etc/hosts file or not retrievable by DNS. Check your /etc/hosts file and insert your hostname and IP address of the machine if required.
0 -
Hi @christopher.dugan1,
I checked the first thing when I got the error but that seems to be established correctly as well.
0 -
Hi @zoya faberov,
After working a lot on the cloned machine we removed the use of that machine as you recommended the machine's health was bad.
Now I have a new and different cloned machine from a working LPC machine and it works fine after I re-install the LPC.
Thank you for all the help and Sorry for all the trouble. Closing this ticket atleast. The problem of LPC on a new machine still persists.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 687 Datastream
- 1.4K DSS
- 622 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 254 ETA
- 557 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 276 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 676 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛
