Skip to main content
1-Visitor
May 25, 2018
Question

Unable to run LSR

  • May 25, 2018
  • 1 reply
  • 3569 views

Hi Team,

I'm getting this error while connecting EMS on Raspberry Pi with ThingWorx server.

[DEBUG] 2018-05-11 19:39:40,950 SDK: twTlsClient_Create: Initializing TLS Client

[ERROR] 2018-05-11 14:09:41,3 UnencryptedClientStream::doopen: Error opening socket. Error: 111

[ERROR] 2018-05-11 14:09:41,4 HttpClient::initialize: Exception while opening connection request to 127.0.0.1. Error: Error opening non-TLS socket [127.0.0.1:8000]

[DEBUG] 2018-05-11 14:09:41,4 TlsStream::doclose: Disconeccting socket

[DEBUG] 2018-05-11 19:39:41,4 SDK: twTlsClient_Close: Disconnecting from server

[DEBUG] 2018-05-11 19:39:41,5 SDK: twTlsClient_Close: Disconnecting from server

[DEBUG] 2018-05-11 14:09:41,4 HttpClient::processReq: Error initializing stream.

[ERROR] 2018-05-11 14:09:41,4 luaBindings::httpPost: Error POSTing to HTTP Server at 127.0.0.1/Thingworx/Things/LocalEms/Services/AddEdgeThing

[INFO ] 2018-05-11 14:09:41,4 PiThing: Error occured while accessing EMS. Checking isConnected.

[DEBUG] 2018-05-11 19:39:41,5 SDK: twTlsClient_Create: Initializing TLS Client

[ERROR] 2018-05-11 14:09:41,6 UnencryptedClientStream::doopen: Error opening socket. Error: 111

[ERROR] 2018-05-11 14:09:41,7 HttpClient::initialize: Exception while opening connection request to 127.0.0.1. Error: Error opening non-TLS socket [127.0.0.1:8000]

[DEBUG] 2018-05-11 14:09:41,7 TlsStream::doclose: Disconeccting socket

[DEBUG] 2018-05-11 19:39:41,7 SDK: twTlsClient_Close: Disconnecting from server

[DEBUG] 2018-05-11 19:39:41,7 SDK: twTlsClient_Close: Disconnecting from server

[DEBUG] 2018-05-11 14:09:41,7 HttpClient::processReq: Error initializing stream.

[ERROR] 2018-05-11 14:09:41,7 luaBindings::httpGet: Error GETing from HTTP server at 127.0.0.1/Thingworx/Things/LocalEms/Properties/isConnected

[INFO ] 2018-05-11 14:09:41,7 PiThing: EMS is available: false, online: false

 

Any help is much appreciated. Also my 30 days free trail period is getting over by today(25th May) for ThingWorx composer server. can the date will be extended as I didn't complete my testing?

1 reply

5-Regular Member
June 7, 2018

When approaching the end of the 30-day hosted trials on the Developer Portal, we recommend exporting all relevant Entities and then importing them into one of our 120-day self-hosted trials.

 

DevPortal downloads page: https://developer.thingworx.com/resources/downloads

 

At the end of the 30-day hosted trial, the entire server is deleted with no way to recover any non-Exported Entities.

 

As for Raspberry Pi connectivity, I'd recommend the DevPortal's Raspberry Pi guide here: https://developer.thingworx.com/resources/guides/thingworx-raspberry-pi-quickstart

 

Thank you,

Jason

pponraj1-VisitorAuthor
1-Visitor
June 11, 2018

I have got the 120 days trail now and downloaded the latest version of EMS.

EMS is getting connected to Thingworx server (isConnected = true).

By going through Composer (TW server), I can Monitor my remote thing 'PiThing'.

While running luaScriptResouce, the execution stops at thingworx.handler: Creating a new handler

And I can't see "EMS is Online: true".

So while trying to manage binding, am always getting "Error browsing properties; be sure remote thing is connected properly and configured".

Please support; I was struggling to move forward....

pponraj1-VisitorAuthor
1-Visitor
June 11, 2018

Moreover, as it is a test application, I disabled SSL completely(Insecure configuration).