IO Frame error - connector down?

41 views
Skip to first unread message

Ian Ray

unread,
Dec 19, 2011, 12:34:29 PM12/19/11
to google-secure-data-connector
19 Dec 2011 09:34:52,651 [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:
109)
at
com.google.dataconnector.protocol.FrameReceiver.readOneFrame(FrameReceiver.java:
90)
at
com.google.dataconnector.client.SdcConnection.authorize(SdcConnection.java:
247)
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:178)
19 Dec 2011 09:34:52,652
[com.google.dataconnector.protocol.FrameSender] INFO
com.google.dataconnector.protocol.FrameSender - IO error while
sending frame
java.net.SocketException: Broken pipe


Please advise. Was working this weekend, down Monday morning.

Dawen Tan

unread,
Dec 19, 2011, 2:10:02 PM12/19/11
to google-secure-data-connector
it is also down in my place. Google, please help to fix it and don't
let it happening again.

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.

Ian Ray

unread,
Dec 19, 2011, 3:12:09 PM12/19/11
to google-secure-data-connector
Seems to work now.

Ian Ray

unread,
Jan 3, 2012, 2:50:08 PM1/3/12
to googl...@googlegroups.com
Same error again today.

Dawen Tan

unread,
Jan 3, 2012, 4:11:56 PM1/3/12
to google-secure-data-connector
same in my place. google just let it happened again. too bad.

On Jan 3, 11:50 am, Ian Ray <ian...@cypressgrovechevre.com> wrote:
> Same error again today.
Reply all
Reply to author
Forward
0 new messages