SDC service is out again today

18 views

Skip to first unread message

Dawen Tan

unread,

Dec 8, 2011, 2:10:29 PM12/8/11

to google-secure-data-connector

it started this morning from 6:30 am.

it attempped to login but failted.

error message:
08 Dec 2011 07:00:06,537 [main] INFO
com.google.dataconnector.util.HealthCheckRequestHandler - healthcheck
service started on port 58129
08 Dec 2011 07:00:06,543 [main] INFO
com.google.dataconnector.client.SdcConnection - Connecting to SDC
server
08 Dec 2011 07:00:06,543 [main] INFO
com.google.dataconnector.util.SSLSocketFactoryInit - Using SSL for
client connections.
Setting iddle timeout to 60000 ms.
Setting accept timeout to 60000 ms.
Setting udp timeout to 600000 ms.
08 Dec 2011 07:00:06,592
[com.google.dataconnector.client.JsocksStarter] INFO
com.google.dataconnector.client.JsocksStarter - Starting JSOCKS
listener thread on port 1080
08 Dec 2011 07:00:06,592
[com.google.dataconnector.client.JsocksStarter] INFO
net.sourceforge.jsocks.socks.ProxyServer - Starting SOCKS Proxy on:
127.0.0.1:1080
08 Dec 2011 07:00:07,863 [main] INFO
com.google.dataconnector.client.SdcConnection - Sending initial
handshake msg
08 Dec 2011 07:00:07,864 [main] INFO
com.google.dataconnector.client.SdcConnection - Attemping login

it seems it is really not stable, why?
NOTICE: This e-mail and any files transmitted with it may contain confidential information,
and are intended solely for the use of the individual or entity to whom they are addressed.
Any retransmission, dissemination or other use of the information by persons other than
the intended recipient or entity is prohibited. If you receive this e-mail in error please
contact the sender by return e-mail and delete the material from your system. Thank you.

Eric Pollmann

unread,

Dec 8, 2011, 4:49:33 PM12/8/11

to enterprise-data-questions, Dawen Tan, google-secure-data-connector

Hello Dawen,

Thank you letting us know about this problem.

We spent some time debugging it just now and were able to fix it. It
looks like your agent has reconnected successfully since the fix.
Please let us know if you are still experiencing problems. The issue
was a problem early in the agent connection process and was not
detected by our existing monitoring. A small subset of users were
affected. We discussed ways of improving the monitoring to catch
problems like this sooner in the future and have a plan on how to do
so.

In the long run, we are working hard on writing the next version of
SDC, which should be significantly more stable, better supported, and
will likely also be somewhat lower latency. Thanks for bearing with
us as we work on the new system!