Error in installing secure connector:test connector

[cst...@ferreyros.com.pe]

Good morning,
Please have followed the manual for installation of secure connector without success:
The configuration was as follows:

<entity>
<sdcServerHost>sdc.runmyprocess.com</sdcServerHost>
<sdcServerPort>4433</sdcServerPort>
<domain>ferreyros.com.pe</domain>
<user>user</user>
<password>????</password>
<agentId>agent1_example-com</agentId>
<socksServerPort>1080</socksServerPort>
<healthCheckGadgetUsers></healthCheckGadgetUsers>
</entity>

error:

29 jun 2017 22:36:19,789 [main] INFO com.google.dataconnector.client.Client - Starting agent after 5 unsuccessful attempts. Next connect in 32000 milliseconds.
29 jun 2017 22:36:19,799 [main] INFO com.google.dataconnector.client.SdcConnection - Connecting to SDC server
29 jun 2017 22:36:19,799 [main] INFO com.google.dataconnector.util.SSLSocketFactoryInit - Using SSL for client connections.
29 jun 2017 22:36:19,809 [com.google.dataconnector.client.JsocksStarter] INFO com.google.dataconnector.client.JsocksStarter - Starting JSOCKS listener thread on port 1080
29 jun 2017 22:36:19,809 [com.google.dataconnector.client.JsocksStarter] INFO net.sourceforge.jsocks.socks.ProxyServer - Starting SOCKS Proxy on:127.0.0.1:1080
29 jun 2017 22:36:25,011 [main] INFO com.google.dataconnector.client.SdcConnection - Sending initial handshake msg
29 jun 2017 22:36:25,011 [main] INFO com.google.dataconnector.client.SdcConnection - Attemping login
29 jun 2017 22:36:25,564 [main] WARN com.google.dataconnector.client.SdcConnection - Frame error
com.google.dataconnector.protocol.FramingException: Unexpected frame start read
at com.google.dataconnector.protocol.FrameReceiver.readFrame(FrameReceiver.java:108)
at com.google.dataconnector.protocol.FrameReceiver.readOneFrame(FrameReceiver.java:90)
at com.google.dataconnector.client.SdcConnection.authorize(SdcConnection.java:248)
at com.google.dataconnector.client.SdcConnection.connect(SdcConnection.java:169)
at com.google.dataconnector.client.Client.parseFlagsValidateAndConnect(Client.java:119)
at com.google.dataconnector.client.Client.main(Client.java:179)
29 jun 2017 22:36:25,564 [main] FATAL com.google.dataconnector.client.Client - Connection failed.
com.google.dataconnector.util.ConnectionException: Authorization failed
at com.google.dataconnector.client.SdcConnection.connect(SdcConnection.java:170)
at com.google.dataconnector.client.Client.parseFlagsValidateAndConnect(Client.java:119)
at com.google.dataconnector.client.Client.main(Client.java:179)
29 jun 2017 22:36:25,564 [main] INFO com.google.dataconnector.util.ShutdownManager - Issuing shutdown for com.google.dataconnector.client.ResourcesFileWatcher
29 jun 2017 22:36:25,564 [main] INFO com.google.dataconnector.util.ShutdownManager - Issuing shutdown for com.google.dataconnector.client.JsocksStarter
29 jun 2017 22:36:25,564 [main] INFO com.google.dataconnector.util.ShutdownManager - Issuing shutdown for com.google.dataconnector.protocol.FrameSender
29 jun 2017 22:36:25,564 [com.google.dataconnector.protocol.FrameSender] INFO com.google.dataconnector.protocol.FrameSender - Sending frames shutting down
java.lang.InterruptedException
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(Unknown Source)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown Source)
at java.util.concurrent.LinkedBlockingQueue.poll(Unknown Source)
at com.google.dataconnector.protocol.FrameSender.run(FrameSender.java:153)

In the tutorial that I followed it does not speak of the parameters:
<AgentId> agent1_example-com </ agentId>
<SocksServerPort> 1080 </ socksServerPort>
<HealthCheckGadgetUsers> </ healthCheckGadgetUsers>

When pinging
IP address 52.28.206.190 on port 4433 (TCP) was successful

regards

[Prachi Chandak]

Hi,

This issue arises when your network is blocking SEC agent/manager to communicate with RMP server.

Could you please confirm whether you are installing SEC in the Corporate firewall(company network)?

If this is the scenario then your corporate network might be blocking this.

Please make sure following points:

1. Java is properly configured and PATH is set in the Environment variable (JDK version)

2. Need to Open ports for SEC to make successful communication: 8080, 1080 and some ports which are using by JAVA(Please communicate with your IT/Network team for this).

3. Need to open/enable TCP IP address: 

a. 52.28.206.190:4433

b. Open TCP port 4433 to sdc.runmyprocess.com (174.129.212.17)

c. If using DNS/proxy server need to enable to communicate with SEC and RMP.  

3. These ports are not assigned or access by the others applications.

Also could you please check the following command in cmd whether your network is allowing SEC to establish connection with RMP

telnet 52.28.206.190 4433

Let us know if you still face any issue or further information required.

Thanks & Regards,

Prachi Chandak

Fujitsu RunMyProcess Support

--
Fujitsu - RunMyProcess
---
You received this message because you are subscribed to the Google Groups "Fujitsu RunMyProcess Developer Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to supportforum+unsubscribe@runmyprocess.com.
To post to this group, send email to suppor...@runmyprocess.com.
Visit this group at https://groups.google.com/a/runmyprocess.com/group/supportforum/.
To view this discussion on the web visit https://groups.google.com/a/runmyprocess.com/d/msgid/supportforum/0f243886-2f39-40fd-87b4-fb6285c5a033%40runmyprocess.com.
For more options, visit https://groups.google.com/a/runmyprocess.com/d/optout.

[Cstirmp Outsourcing]

It was tested with telnet and was correct

telnet 52.28.206.190 4433

connection sec manager correcto

error sec agent

30 jun 2017 15:05:45,366 [main] INFO  com.google.dataconnector.util.ShutdownManager  - Issuing shutdown for com.google.dataconnector.client.ResourcesFileWatcher

30 jun 2017 15:05:45,366 [main] INFO  com.google.dataconnector.util.ShutdownManager  - Issuing shutdown for com.google.dataconnector.client.JsocksStarter

30 jun 2017 15:05:45,366 [main] INFO  com.google.dataconnector.util.ShutdownManager  - Issuing shutdown for com.google.dataconnector.protocol.FrameSender

30 jun 2017 15:05:45,367 [com.google.dataconnector.protocol.FrameSender] INFO  com.google.dataconnector.protocol.FrameSender  - Sending frames shutting down

java.lang.InterruptedException

at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(Unknown Source)

at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown Source)

at java.util.concurrent.LinkedBlockingQueue.poll(Unknown Source)

at com.google.dataconnector.protocol.FrameSender.run(FrameSender.java:153)

30 jun 2017 15:05:47,367 [main] INFO  com.google.dataconnector.client.Client  - Starting agent after 1 unsuccessful attempts. Next connect in 2000 milliseconds.

30 jun 2017 15:05:47,389 [main] INFO  com.google.dataconnector.client.SdcConnection  - Connecting to SDC server

30 jun 2017 15:05:47,389 [main] INFO  com.google.dataconnector.util.SSLSocketFactoryInit  - Using SSL for client connections.

30 jun 2017 15:05:47,424 [com.google.dataconnector.client.JsocksStarter] INFO  com.google.dataconnector.client.JsocksStarter  - Starting JSOCKS listener thread on port 1080

30 jun 2017 15:05:47,425 [com.google.dataconnector.client.JsocksStarter] INFO  net.sourceforge.jsocks.socks.ProxyServer  - Starting SOCKS Proxy on:127.0.0.1:1080

30 jun 2017 15:10:48,314 [main] INFO  com.google.dataconnector.client.SdcConnection  - Connecting to SDC server

30 jun 2017 15:10:48,316 [main] INFO  com.google.dataconnector.util.SSLSocketFactoryInit  - Using SSL for client connections.

30 jun 2017 15:10:48,321 [com.google.dataconnector.client.JsocksStarter] INFO  com.google.dataconnector.client.JsocksStarter  - Starting JSOCKS listener thread on port 1080

30 jun 2017 15:10:48,326 [com.google.dataconnector.client.JsocksStarter] INFO  net.sourceforge.jsocks.socks.ProxyServer  - Starting SOCKS Proxy on:127.0.0.1:1080

30 jun 2017 15:10:50,424 [main] INFO  com.google.dataconnector.client.SdcConnection  - Sending initial handshake msg

30 jun 2017 15:10:50,425 [main] INFO  com.google.dataconnector.client.SdcConnection  - Attemping login

30 jun 2017 15:10:50,960 [main] WARN  com.google.dataconnector.client.SdcConnection  - Frame error

com.google.dataconnector.protocol.FramingException: Unexpected frame start read

at com.google.dataconnector.protocol.FrameReceiver.readFrame(FrameReceiver.java:108)

at com.google.dataconnector.protocol.FrameReceiver.readOneFrame(FrameReceiver.java:90)

at com.google.dataconnector.client.SdcConnection.authorize(SdcConnection.java:248)

at com.google.dataconnector.client.SdcConnection.connect(SdcConnection.java:169)

at com.google.dataconnector.client.Client.parseFlagsValidateAndConnect(Client.java:119)

at com.google.dataconnector.client.Client.main(Client.java:179)

30 jun 2017 15:10:50,963 [main] FATAL com.google.dataconnector.client.Client  - Connection failed.

com.google.dataconnector.util.ConnectionException: Authorization failed

at com.google.dataconnector.client.SdcConnection.connect(SdcConnection.java:170)

at com.google.dataconnector.client.Client.parseFlagsValidateAndConnect(Client.java:119)

at com.google.dataconnector.client.Client.main(Client.java:179)

[Ghanshyam Mule]

Hello Sir,

Generally, a framing error is the result of starting to read a sequence of data at the wrong point.

While executing  SEC agent, it might be passing wrong sequence data(Domain username & password) due to this getting authorization failed (connection failed) error message.

We are checking your issue with RnD team & will keep you updated soon.

Regards,

Ghanshyam Mule

Fujitsu RunMyProcess Support

To view this discussion on the web visit https://groups.google.com/a/runmyprocess.com/d/msgid/supportforum/CAEK60XMgcWu264C-UiUP95YU%3DemCpy8pfR9bked-dJZyPMiQ4w%40mail.gmail.com.

[Cstirmp Outsourcing]

good morning, When I telnet with sdc.runmyprocess.com 174.129.212.17 is successful; However if I use the ip directly 174.129.212.17 4433 fails.

[Richard Manga]

Good morning Sir,

Please use  sdc.runmyprocess.com in your configuration. In fact, based on the configuration of your proxy, sometimes it is necessary to use url instead of IP address.

Could you tell us which kind of server you are also using?

And the procedure you are following to get this error?

Best Regards,

[Cstirmp Outsourcing]

I'm doing a test from my personal computer. The procedure followed is the one presented in your tutorial

http://docs.runmyprocess.com/Integration_Guide/SEC/Installation_Guide

<entity>

  <sdcServerHost>sdc.runmyprocess.com</sdcServerHost>

  <sdcServerPort>4433</sdcServerPort>

  <domain>ferreyros.com.pe</domain>

  <user>user</user>

  <password>xxxx</password>

  <agentId>agent1_example-com</agentId>

  <socksServerPort>1080</socksServerPort>

  <healthCheckGadgetUsers></healthCheckGadgetUsers>

</entity>

The agentId what should it be? The socksServerPort cul should be? For the test I'm leaving the configuration like this or you have to make a change

<resourceRules> <!-- $Id: resourceRules.xml-dist 444 2009-08-07 18:10:03Z matt.proud $ --> <rule repeatable="true"> <ruleNum>1</ruleNum> <agentId>agent1_example-com</agentId> <viewerEmail repeatable="true">joh...@example.com</viewerEmail> <viewerEmail repeatable="true">ad...@example.com</viewerEmail> <apps repeatable="true"> <service>Gadgets</service> <allowAnyAppId>true</allowAnyAppId> </apps> <apps repeatable="true"> <service>Spreadsheets</service> <allowAnyAppId>true</allowAnyAppId> </apps> <url>http://internal.corp.example.com</url> <urlMatch>HOSTPORT</urlMatch> </rule> <rule repeatable="true"> <ruleNum>2</ruleNum> <agentId>all</agentId> <viewerEmail repeatable="true">joh...@example.com</viewerEmail> <viewerEmail repeatable="true">ad...@example.com</viewerEmail> <apps repeatable="true"> <service>Spreadsheets</service> <allowAnyAppId>true</allowAnyAppId> </apps> <apps repeatable="true"> <service>Gadgets</service> <appId>http://feedserver-enterprise.googleusercontent.com/a/example.com/g/PrivateGadgetSpec/gadget.xml</appId> </apps> <apps repeatable="true"> <service>AppEngine</service> <appId>hellosdc</appId> </apps> <url>http://feed.example.com/userlookup?user=johndoe</url> <urlMatch>URLEXACT</urlMatch> </rule> <rule repeatable="true"> <ruleNum>3</ruleNum> <agentId>all</agentId> <allowDomainViewers>true</allowDomainViewers> <apps repeatable="true"> <service>Gadgets</service> <allowAnyAppId>true</allowAnyAppId> </apps> <apps repeatable="true"> <service>Spreadsheets</service> <allowAnyAppId>true</allowAnyAppId> </apps> <apps repeatable="true"> <service>AppEngine</service> <allowAnyAppId>true</allowAnyAppId> </apps> <url>socket://0.0.0.0:22</url> <urlMatch>HOSTPORT</urlMatch> </rule> </resourceRules>

regards