Secure Enterprise Connector keeps shutting down

[dba...@momnet.com]

Hello, My log file shows the SEC shutting down periodically but then will start back up due to the keep-alive health-checker. However it has been down since last Friday and keeps shutting down. Below is an excerpt from the log file. I'm running the new zicatela version.
Please advise.

21 Jul 2014 05:57:37,947 [main] INFO com.google.dataconnector.util.ShutdownManager - Issuing shutdown for com.google.dataconnector.client.ResourcesFileWatcher
21 Jul 2014 05:57:37,947 [main] INFO com.google.dataconnector.util.ShutdownManager - Issuing shutdown for com.google.dataconnector.client.JsocksStarter
21 Jul 2014 06:02:37,962 [main] INFO com.google.dataconnector.client.Client - Starting agent after 76 unsuccessful attempts. Next connect in 300000 milliseconds.
21 Jul 2014 06:02:37,962 [main] INFO com.google.dataconnector.client.SdcConnection - Connecting to SDC server
21 Jul 2014 06:02:37,962 [main] INFO com.google.dataconnector.util.SSLSocketFactoryInit - Using SSL for client connections.
21 Jul 2014 06:02:37,978 [com.google.dataconnector.client.JsocksStarter] INFO com.google.dataconnector.client.JsocksStarter - Starting JSOCKS listener thread on port 1080
21 Jul 2014 06:02:37,978 [com.google.dataconnector.client.JsocksStarter] INFO net.sourceforge.jsocks.socks.ProxyServer - Starting SOCKS Proxy on:127.0.0.1:1080
21 Jul 2014 06:06:10,942 [main] FATAL com.google.dataconnector.client.Client - Connection failed.
com.google.dataconnector.util.ConnectionException: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
at com.google.dataconnector.client.SdcConnection.verifySubjectInCertificate(SdcConnection.java:282)
at com.google.dataconnector.client.SdcConnection.connect(SdcConnection.java:153)
at com.google.dataconnector.client.Client.parseFlagsValidateAndConnect(Client.java:119)
at com.google.dataconnector.client.Client.main(Client.java:179)
Caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
at sun.security.ssl.SSLSessionImpl.getPeerCertificateChain(SSLSessionImpl.java:446)
at com.google.dataconnector.client.SdcConnection.verifySubjectInCertificate(SdcConnection.java:280)
... 3 more
21 Jul 2014 06:06:10,942 [main] INFO com.google.dataconnector.util.ShutdownManager - Issuing shutdown for com.google.dataconnector.client.ResourcesFileWatcher
21 Jul 2014 06:06:10,942 [main] INFO com.google.dataconnector.util.ShutdownManager - Issuing shutdown for com.google.dataconnector.client.JsocksStarter

[rik...@gmail.com]

SEC down and refusing connections for me as well. Any updates on below? Error below:

C:\SEC\data-connector-agent\bin>java -Djava.net.preferIPv4Stack=true -jar ../lib
/sec-agent-zicatela.jar --localConfigFile ..\config\localConfig.xml --rulesFile
..\config\resourceRules.xml -log4jPropertiesFile ..\config\log4j.properties
Setting iddle timeout to 60000 ms.
Setting accept timeout to 60000 ms.
Setting udp timeout to 600000 ms.
java.net.SocketException: socket closed
at java.net.TwoStacksPlainSocketImpl.socketAccept(Native Method)
at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
at java.net.PlainSocketImpl.accept(Unknown Source)
at java.net.ServerSocket.implAccept(Unknown Source)
at java.net.ServerSocket.accept(Unknown Source)
at net.sourceforge.jsocks.socks.ProxyServer.start(ProxyServer.java:166)
at com.google.dataconnector.client.JsocksStarter.run(JsocksStarter.java:
105)

[Pray Desai]

Hello,

We have already forwarded the problem to the product team and they are working on solving it.

Best regards,

Pray Desai,

Fujitsu RunMyProcess.

[rik...@gmail.com]

Pray,

Any word on when SEC will be up again? It has already been down for over a day.

Rishi

On Monday, July 21, 2014 8:13:14 PM UTC-4, Pray Desai wrote:
> Hello,
>
>
> We have already forwarded the problem to the product team and they are working on solving it.
>
>
>

> Best regards,Pray Desai,

[Bilal Ajaj]

Hello,

Sorry for the late reply. We see no problem from our side concerning the SEC being shut down. Can you please send us more information in order to better investigate the problem ?

The info you sent shows that the socket was closed but nothing more. So can you please send us the agent log to have more info. We are monitoring the SEC constantly and we need to know the exact time when it went down to see if this is an isolated case (some internet connection problem of firewall block) or a general SEC connection problem.

Best regards,

--

Bilal AJAJ

Customer Solutions Engineer

Website: Fujitsu RunMyProcess

3 Rue de Gramont 

75002 Paris - France

     

Fujitsu RunMyProcess user? Please add a review on GoogleApps Marketplace

Afin de contribuer au respect de l'environnement, merci de n'imprimer ce message qu'en cas de nécessité.

Be environmentally friendly: do not print this email unless it is entirely necessary.

[Rishi Kumar]

Hi Bilal,

See error below on launch of SEC connector agent. This type of error has cropped up several times in the last couple of years. In each instance when I emailed RMP support they were able to reset SEC on their end to resolve issue.

C:\SEC\data-connector-agent\bin>java -Djava.net.preferIPv4Stack=true -jar ../lib

/sec-agent-zicatela.jar --localConfigFile ..\config\localConfig.xml --rulesFile

..\config\resourceRules.xml -log4jPropertiesFile ..\config\log4j.properties

Setting iddle timeout to 60000 ms.

Setting accept timeout to 60000 ms.

Setting udp timeout to 600000 ms.

java.net.SocketException: socket closed

        at java.net.TwoStacksPlainSocketImpl.socketAccept(Native Method)

        at java.net.AbstractPlainSocketImpl.accept(Unknown Source)

        at java.net.PlainSocketImpl.accept(Unknown Source)

        at java.net.ServerSocket.implAccept(Unknown Source)

        at java.net.ServerSocket.accept(Unknown Source)

        at net.sourceforge.jsocks.socks.ProxyServer.start(ProxyServer.java:166)

        at com.google.dataconnector.client.JsocksStarter.run(JsocksStarter.java:

105)

--
Fujitsu - RunMyProcess
---
You received this message because you are subscribed to a topic in the Google Groups "RunMyProcess Support Forum" group.
To unsubscribe from this topic, visit https://groups.google.com/a/runmyprocess.com/d/topic/supportforum/Pwf3nYX5HbU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to supportforum...@runmyprocess.com.
To post to this group, send email to suppor...@runmyprocess.com.
Visit this group at http://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/CADRawxVAWNajTXKbVpdfKqdHwZuwHmhA%2ByJQ6mfOv_x6T4yVqQ%40mail.gmail.com.

For more options, visit https://groups.google.com/a/runmyprocess.com/d/optout.

--
r i s h i  k u m a r
ri...@alum.mit.edu
+1 (617) 407 5516

[Bilal Ajaj]

Hello Richi,

What you are sending us is the error. We actually need the logs that will tell us the time the problem occurred and what caused it.

We can see nothing from our side. The SEC was up all the time.

Thanks in advance.

Bilal

[Dave Bandy]

Below is an excerpt from my log file.  The last keep alive request was made on July 18 05:16. After the "Closing SDC connection due to health check failure" message the SDC has not been able to restart so it's been down for 4 days.

Thanks,

Dave

18 Jul 2014 05:16:19,040 [pool-1-thread-50] INFO  com.google.dataconnector.client.fetchrequest.HttpFetchStrategy  - Replying to KeepAlive Request

18 Jul 2014 05:16:19,040 [pool-1-thread-50] INFO  com.google.dataconnector.client.fetchrequest.HttpFetchStrategy  - 59110c19-75c1-47d6-b69f-0075b07fea12: Got response from resource:HTTP/1.1 200 

18 Jul 2014 05:16:19,040 [pool-1-thread-50] INFO  com.google.dataconnector.client.FetchRequestHandler  - 59110c19-75c1-47d6-b69f-0075b07fea12: Sending reply status=200, latency=0

18 Jul 2014 05:16:49,026 [pool-1-thread-50] INFO  com.google.dataconnector.client.fetchrequest.HttpFetchStrategy  - Replying to KeepAlive Request

18 Jul 2014 05:16:49,026 [pool-1-thread-50] INFO  com.google.dataconnector.client.fetchrequest.HttpFetchStrategy  - 70589e92-f70e-41ad-bc3c-5f66229329fc: Got response from resource:HTTP/1.1 200 

18 Jul 2014 05:16:49,026 [pool-1-thread-50] INFO  com.google.dataconnector.client.FetchRequestHandler  - 70589e92-f70e-41ad-bc3c-5f66229329fc: Sending reply status=200, latency=0

18 Jul 2014 05:16:54,886 [com.google.dataconnector.client.HealthCheckHandler] WARN  com.google.dataconnector.client.HealthCheckHandler  - Health check response not received in 5000022ms.

18 Jul 2014 05:16:54,886 [com.google.dataconnector.client.HealthCheckHandler] ERROR com.google.dataconnector.client.SdcConnection  - Closing SDC connection due to health check failure.

18 Jul 2014 05:16:54,886 [main] FATAL com.google.dataconnector.client.Client  - Connection failed.

com.google.dataconnector.util.ConnectionException: com.google.dataconnector.protocol.FramingException: IO Exception on tunnelsocket

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

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

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

Caused by: com.google.dataconnector.protocol.FramingException: IO Exception on tunnelsocket

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

at com.google.dataconnector.protocol.FrameReceiver.startDispatching(FrameReceiver.java:75)

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

... 2 more

Caused by: java.net.SocketException: Socket closed

at java.net.SocketInputStream.socketRead0(Native Method)

at java.net.SocketInputStream.read(SocketInputStream.java:152)

at java.net.SocketInputStream.read(SocketInputStream.java:122)

at sun.security.ssl.InputRecord.readFully(InputRecord.java:442)

at sun.security.ssl.InputRecord.read(InputRecord.java:480)

at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:927)

at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:884)

at sun.security.ssl.AppInputStream.read(AppInputStream.java:102)

at sun.security.ssl.AppInputStream.read(AppInputStream.java:69)

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

... 4 more

18 Jul 2014 05:16:54,886 [main] INFO  com.google.dataconnector.util.ShutdownManager  - Issuing shutdown for com.google.dataconnector.client.ResourcesFileWatcher

18 Jul 2014 05:16:54,886 [main] INFO  com.google.dataconnector.util.ShutdownManager  - Issuing shutdown for com.google.dataconnector.client.JsocksStarter

18 Jul 2014 05:16:54,886 [com.google.dataconnector.client.ResourcesFileWatcher] INFO  com.google.dataconnector.client.ResourcesFileWatcher  - Shutting down.

java.lang.InterruptedException: sleep interrupted

at java.lang.Thread.sleep(Native Method)

at com.google.dataconnector.util.SystemUtil.sleep(SystemUtil.java:34)

at com.google.dataconnector.client.ResourcesFileWatcher.run(ResourcesFileWatcher.java:171)

18 Jul 2014 05:16:54,886 [com.google.dataconnector.client.ResourcesFileWatcher] INFO  com.google.dataconnector.client.ResourcesFileWatcher  - FileWatcher thread exiting. Any changes in resources file will require restarting agent manually.

18 Jul 2014 05:16:54,886 [main] INFO  com.google.dataconnector.util.ShutdownManager  - Issuing shutdown for com.google.dataconnector.protocol.FrameSender

18 Jul 2014 05:16:54,886 [main] INFO  com.google.dataconnector.util.ShutdownManager  - Issuing shutdown for com.google.dataconnector.client.HealthCheckHandler

18 Jul 2014 05:16:54,886 [main] INFO  com.google.dataconnector.util.ShutdownManager  - Issuing shutdown for com.google.dataconnector.client.SdcConnection

18 Jul 2014 05:16:54,886 [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(AbstractQueuedSynchronizer.java:2017)

at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2095)

at java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)

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

18 Jul 2014 05:17:02,886 [main] INFO  com.google.dataconnector.client.Client  - Starting agent after 3 unsuccessful attempts. Next connect in 8000 milliseconds.

18 Jul 2014 05:17:02,902 [main] INFO  com.google.dataconnector.client.SdcConnection  - Connecting to SDC server

18 Jul 2014 05:17:02,902 [main] INFO  com.google.dataconnector.util.SSLSocketFactoryInit  - Using SSL for client connections.

18 Jul 2014 05:17:02,902 [com.google.dataconnector.client.JsocksStarter] INFO  com.google.dataconnector.client.JsocksStarter  - Starting JSOCKS listener thread on port 1080

18 Jul 2014 05:17:02,902 [com.google.dataconnector.client.JsocksStarter] INFO  net.sourceforge.jsocks.socks.ProxyServer  - Starting SOCKS Proxy on:127.0.0.1:1080

18 Jul 2014 05:32:03,073 [main] FATAL com.google.dataconnector.client.Client  - Connection failed.

com.google.dataconnector.util.ConnectionException: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated

at com.google.dataconnector.client.SdcConnection.verifySubjectInCertificate(SdcConnection.java:282)

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

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

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

Caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated

at sun.security.ssl.SSLSessionImpl.getPeerCertificateChain(SSLSessionImpl.java:446)

at com.google.dataconnector.client.SdcConnection.verifySubjectInCertificate(SdcConnection.java:280)

... 3 more

18 Jul 2014 05:32:03,073 [main] INFO  com.google.dataconnector.util.ShutdownManager  - Issuing shutdown for com.google.dataconnector.client.ResourcesFileWatcher

18 Jul 2014 05:32:03,073 [main] INFO  com.google.dataconnector.util.ShutdownManager  - Issuing shutdown for com.google.dataconnector.client.JsocksStarter

18 Jul 2014 05:32:19,074 [main] INFO  com.google.dataconnector.client.Client  - Starting agent after 4 unsuccessful attempts. Next connect in 16000 milliseconds.

[Dimitri MELCHIOR Pro]

Hi,

SEC's back up now.

Best regards

--

Dimitri MELCHIOR

PreSales Consultant

Contact: dmel...@runmyprocess.com

Tel: +33(0)1 75 77 51 78

Mobile : +33(0)6 52 70 89 82

Website: Fujitsu RunMyProcess

     

Fujitsu RunMyProcess user? Please add a review on GoogleApps Marketplace

Afin de contribuer au respect de l'environnement, merci de n'imprimer ce message qu'en cas de nécessité.
Be environmentally friendly: do not print this email unless it is entirely necessary.

--
Fujitsu - RunMyProcess
---

You received this message because you are subscribed to the Google Groups "RunMyProcess Support Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to supportforum...@runmyprocess.com.

To post to this group, send email to suppor...@runmyprocess.com.
Visit this group at http://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/CAPuJpH0rPxN1Yv-USEnfmfr-xOQrsAoOpGbUB%3DHoTv0Qakhm7A%40mail.gmail.com.

[Dave Bandy]

It came back up today at 12:45 but then shut down at 13:19.  It's back in the loop of trying to start then shutting down every few seconds.

Thanks,

Excerpt from log file:

22 Jul 2014 12:45:47,569 [main] INFO  com.google.dataconnector.client.SdcConnection  - Connecting to SDC server

22 Jul 2014 12:45:47,569 [main] INFO  com.google.dataconnector.util.SSLSocketFactoryInit  - Using SSL for client connections.

22 Jul 2014 12:45:47,569 [com.google.dataconnector.client.JsocksStarter] INFO  com.google.dataconnector.client.JsocksStarter  - Starting JSOCKS listener thread on port 1080

22 Jul 2014 12:45:47,569 [com.google.dataconnector.client.JsocksStarter] INFO  net.sourceforge.jsocks.socks.ProxyServer  - Starting SOCKS Proxy on:127.0.0.1:1080

22 Jul 2014 12:45:48,101 [main] INFO  com.google.dataconnector.client.SdcConnection  - Sending initial handshake msg

22 Jul 2014 12:45:48,101 [main] INFO  com.google.dataconnector.client.SdcConnection  - Attemping login

22 Jul 2014 12:45:48,585 [main] INFO  com.google.dataconnector.client.SdcConnection  - Successful login

22 Jul 2014 12:45:48,601 [main] INFO  com.google.dataconnector.registration.v4.Registration  - Sending resources info

agentId: "all"

socksServerPort: 1080

healthCheckPort: 65535

resourceKey {

  ip: "eaweb.momnet.com"

  port: 80

  key: -5881410056351552669

}

resourcesXml: "<resourceRules>\r\n  <rule repeatable=\"true\">\r\n    <ruleNum>1</ruleNum>\r\n    <agentId>all</agentId>\r\n    <viewerEmail repeatable=\"true\">dba...@momnet.com</viewerEmail>\r\n    <url>http://eaweb.momnet.com/images/dummy.csv</url>\r\n    <urlMatch>URLEXACT</urlMatch>\r\n    <apps>\r\n      <service>Spreadsheets</service>\r\n      <allowAnyAppId>true</allowAnyAppId>\r\n    </apps>\r\n  </rule>\r\n</resourceRules>"

22 Jul 2014 12:45:48,601 [main] INFO  com.google.dataconnector.util.SdcKeysManager  - Adding rule for Pair[eaweb.momnet.com, 80]

22 Jul 2014 12:45:48,616 [main] INFO  com.google.dataconnector.client.SdcConnection  - Starting hearbeat/ health check thread.

22 Jul 2014 12:45:48,616 [com.google.dataconnector.client.HealthCheckHandler] INFO  com.google.dataconnector.client.HealthCheckHandler  - healthcheck config is not yet received from the SDC server. will check again in 5 sec

22 Jul 2014 12:45:48,616 [main] INFO  com.google.dataconnector.client.SdcConnection  - starting a thread to watch resources file

22 Jul 2014 12:45:48,866 [main] INFO  com.google.dataconnector.registration.v4.Registration  - registration successful. Received config info from the SDC server

healthCheckTimeout: 5000

healthCheckWakeUpInterval: 5000

22 Jul 2014 12:45:53,617 [com.google.dataconnector.client.HealthCheckHandler] INFO  com.google.dataconnector.client.HealthCheckHandler  - healthcheck thread is started

22 Jul 2014 12:46:02,680 [pool-1-thread-1] INFO  com.google.dataconnector.client.fetchrequest.HttpFetchStrategy  - Replying to KeepAlive Request

22 Jul 2014 12:46:02,789 [pool-1-thread-1] INFO  com.google.dataconnector.client.fetchrequest.HttpFetchStrategy  - d831286b-43a6-4d8c-9091-e3bfce865cc7: Got response from resource:HTTP/1.1 200 

22 Jul 2014 12:46:02,789 [pool-1-thread-1] INFO  com.google.dataconnector.client.FetchRequestHandler  - d831286b-43a6-4d8c-9091-e3bfce865cc7: Sending reply status=200, latency=156

22 Jul 2014 12:46:32,025 [pool-1-thread-2]

.

.

.

.

22 Jul 2014 13:01:32,915 [pool-1-thread-32] INFO  com.google.dataconnector.client.FetchRequestHandler  - ec77b0b5-de7f-4a5b-91f8-ea0d7e8e31c1: Sending reply status=200, latency=0

22 Jul 2014 13:02:02,994 [pool-1-thread-33] INFO  com.google.dataconnector.client.fetchrequest.HttpFetchStrategy  - Replying to KeepAlive Request

22 Jul 2014 13:02:02,994 [pool-1-thread-33] INFO  com.google.dataconnector.client.fetchrequest.HttpFetchStrategy  - a0c92c4b-fa6c-473f-8480-ecd7977f7914: Got response from resource:HTTP/1.1 200 

22 Jul 2014 13:02:02,994 [pool-1-thread-33] INFO  com.google.dataconnector.client.FetchRequestHandler  - a0c92c4b-fa6c-473f-8480-ecd7977f7914: Sending reply status=200, latency=0

22 Jul 2014 13:02:32,980 [pool-1-thread-34] INFO  com.google.dataconnector.client.fetchrequest.HttpFetchStrategy  - Replying to KeepAlive Request

22 Jul 2014 13:02:32,980 [pool-1-thread-34] INFO  com.google.dataconnector.client.fetchrequest.HttpFetchStrategy  - c94c2de0-2985-4831-996d-913ef94607fc: Got response from resource:HTTP/1.1 200 

22 Jul 2014 13:02:32,980 [pool-1-thread-34] INFO  com.google.dataconnector.client.FetchRequestHandler  - c94c2de0-2985-4831-996d-913ef94607fc: Sending reply status=200, latency=0

22 Jul 2014 13:04:17,908 [main] INFO  com.google.dataconnector.client.SdcConnection  - Connecting to SDC server

22 Jul 2014 13:04:17,908 [main] INFO  com.google.dataconnector.util.SSLSocketFactoryInit  - Using SSL for client connections.

22 Jul 2014 13:04:17,939 [com.google.dataconnector.client.JsocksStarter] INFO  com.google.dataconnector.client.JsocksStarter  - Starting JSOCKS listener thread on port 1080

22 Jul 2014 13:04:17,970 [com.google.dataconnector.client.JsocksStarter] INFO  net.sourceforge.jsocks.socks.ProxyServer  - Starting SOCKS Proxy on:127.0.0.1:1080

22 Jul 2014 13:19:21,048 [main] FATAL com.google.dataconnector.client.Client  - Connection failed.

com.google.dataconnector.util.ConnectionException: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated

at com.google.dataconnector.client.SdcConnection.verifySubjectInCertificate(SdcConnection.java:282)

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

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

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

Caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated

at sun.security.ssl.SSLSessionImpl.getPeerCertificateChain(SSLSessionImpl.java:446)

at com.google.dataconnector.client.SdcConnection.verifySubjectInCertificate(SdcConnection.java:280)

... 3 more

22 Jul 2014 13:19:21,048 [main] INFO  com.google.dataconnector.util.ShutdownManager  - Issuing shutdown for com.google.dataconnector.client.ResourcesFileWatcher

22 Jul 2014 13:19:21,048 [main] INFO  com.google.dataconnector.util.ShutdownManager  - Issuing shutdown for com.google.dataconnector.client.JsocksStarter

22 Jul 2014 13:19:23,048 [main] INFO  com.google.dataconnector.client.Client  - Starting agent after 1 unsuccessful attempts. Next connect in 2000 milliseconds.

Fujitsu - RunMyProcess
---
You received this message because you are subscribed to a topic in the Google Groups "RunMyProcess Support Forum" group.
To unsubscribe from this topic, visit https://groups.google.com/a/runmyprocess.com/d/topic/supportforum/Pwf3nYX5HbU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to supportforum...@runmyprocess.com.

To post to this group, send email to suppor...@runmyprocess.com.
Visit this group at http://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/CAED7vk0pOdbhqLHQ%2B4Sp7W%3DYNqQ32YHr47ZFkY7iy9vCtpdLow%40mail.gmail.com.

[Pray Desai]

Hi Dave,

 We updated our SEC server and it should fix issues now. Can you test your SEC again ?

Log file should get updated with SEC connection and health check successful.

After launching protocol manager and SEC agent, just test a connector call to check protocol manager status with GET request from RMP to your local host via your SEC domain. If it shows the same result as seen on browser, then your SEC tunnel is working.

 Let us know if still there are issues.

 

Regards,

Pray Desai,

Fujitsu RunMyProcess.

------------------

On Monday, July 21, 2014 3:23:53 AM UTC-7, dba...@momnet.com wrote:

[Dave Bandy]

It's working again. Thank you.

--

Fujitsu - RunMyProcess
---
You received this message because you are subscribed to a topic in the Google Groups "RunMyProcess Support Forum" group.
To unsubscribe from this topic, visit https://groups.google.com/a/runmyprocess.com/d/topic/supportforum/Pwf3nYX5HbU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to supportforum...@runmyprocess.com.
To post to this group, send email to suppor...@runmyprocess.com.
Visit this group at http://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/be7e3348-4f6f-4eb5-b770-2ac4dd3389d1%40runmyprocess.com.