Quick follow up: I'm getting the following errors:
20/10/2010 12:43:53 PM org.waveprotocol.box.server.waveserver.WaveServerImpl$3$1 onFailure WARNING: Update failed: eUnknown signer 20/10/2010 12:43:53 PM org.waveprotocol.wave.federation.xmpp.XmppFederationRemote$10 onFailure WARNING: Incoming XMPP waveletUpdate failure: error_code: BAD_REQUEST error_message: "Unknown signer" 20/10/2010 12:43:53 PM org.waveprotocol.box.server.waveserver.RemoteWaveletContainerImpl$1 onFailure WARNING: Signer info prefetch failed: error_code: BAD_REQUEST error_message: "No such wave server eggy.cc: error_code: ITEM_NOT_FOUND\n" 20/10/2010 12:43:53 PM org.waveprotocol.box.server.waveserver.RemoteWaveletContainerImpl internalUpdate INFO: Passed signer info check, now applying all 1 deltas 20/10/2010 12:43:53 PM org.waveprotocol.box.server.waveserver.RemoteWaveletContainerImpl internalUpdate James On Wed, Oct 20, 2010 at 12:47 PM, James Purser <[email protected]> wrote: > Hrmm, let me have a look at the log, what's your account? > > James > > On Wed, Oct 20, 2010 at 12:45 PM, Matt Richards <[email protected]> wrote: >> tried to wave with [email protected] >> >> and I'm getting time outs. >> WARNING: outgoing waveletDeltaUpdate failure: error_code: >> REMOTE_SERVER_TIMEOUT >> >> On Tue, Oct 19, 2010 at 8:42 PM, Matt Richards <[email protected]> wrote: >>> >>> so I'm seeing, whats a better way to test? ;) >>> >>> On Tue, Oct 19, 2010 at 8:39 PM, James Purser <[email protected]> >>> wrote: >>>> >>>> I don't think the ping feature is working at the moment. >>>> >>>> James >>>> >>>> On Wed, Oct 20, 2010 at 12:35 PM, Matt Richards <[email protected]> >>>> wrote: >>>> > eggy.cc is up, with the current tip as well. >>>> > I've got it configured to attempt to ping yours, I thinks. >>>> > >>>> > On Tue, Oct 19, 2010 at 8:30 PM, James Purser <[email protected]> >>>> > wrote: >>>> >> >>>> >> I've got collaborynth up and running with the latest head at the >>>> >> moment. >>>> >> >>>> >> Note that it could be down at random intervals, build times are a bit >>>> >> thick at the moment. >>>> >> >>>> >> James >>>> >> >>>> >> On Wed, Oct 20, 2010 at 12:28 PM, Matt Richards <[email protected]> >>>> >> wrote: >>>> >> > Sounds like my problems, though I've heard you can try disabling >>>> >> > TLS. >>>> >> > But even when I do that, I get timeouts with wavesandbox.com. >>>> >> > If somebody needs a server to test with, I can run mine for a little >>>> >> > bit. >>>> >> > On Tue, Oct 19, 2010 at 8:24 PM, James Purser >>>> >> > <[email protected]> >>>> >> > wrote: >>>> >> >> >>>> >> >> No it's not. >>>> >> >> >>>> >> >> When attempting to federate with the sandbox I get the following >>>> >> >> error >>>> >> >> from my own server: >>>> >> >> >>>> >> >> 20/10/2010 12:22:19 PM >>>> >> >> org.waveprotocol.box.server.waveserver.WaveServerImpl submitDelta >>>> >> >> INFO: Sending update to client listener: >>>> >> >> CoreWaveletDelta([email protected], >>>> >> >> 4:92tZMTtU1/KmwzYxK4BMRNys0/s=, 1 ops: >>>> >> >> [AddParticipant([email protected])]) >>>> >> >> 20/10/2010 12:22:20 PM >>>> >> >> org.waveprotocol.wave.federation.xmpp.RemoteDisco$3 >>>> >> >> retry >>>> >> >> INFO: Sending disco items request for: wavesandbox.com, timeout 15 >>>> >> >> seconds >>>> >> >> 20/10/2010 12:22:21 PM >>>> >> >> org.waveprotocol.wave.federation.xmpp.RemoteDisco$3$1 error >>>> >> >> INFO: Remote server wavesandbox.com failed on disco items: >>>> >> >> UNDEFINED_CONDITION >>>> >> >> 20/10/2010 12:22:21 PM >>>> >> >> org.waveprotocol.wave.federation.xmpp.RemoteDisco requestDiscoInfo >>>> >> >> INFO: Sending disco info request for: wavesandbox.com >>>> >> >> 20/10/2010 12:22:21 PM >>>> >> >> org.waveprotocol.wave.federation.xmpp.RemoteDisco requestDiscoInfo >>>> >> >> INFO: Sending disco info request for: wave.wavesandbox.com >>>> >> >> IDLE s...@27081530 [d=false,io=1,w=true,rb=false,wb=false] >>>> >> >> IDLE s...@33116517 [d=false,io=1,w=true,rb=false,wb=false] >>>> >> >> 20/10/2010 12:22:25 PM >>>> >> >> org.waveprotocol.wave.federation.xmpp.RemoteDisco >>>> >> >> finish >>>> >> >> INFO: Could not discover remote JID: error_code: >>>> >> >> UNDEFINED_CONDITION >>>> >> >> for wavesandbox.com >>>> >> >> 20/10/2010 12:22:25 PM >>>> >> >> org.waveprotocol.box.server.waveserver.WaveServerImpl$5 onFailure >>>> >> >> WARNING: outgoing waveletDeltaUpdate failure: error_code: >>>> >> >> RESOURCE_CONSTRAINT >>>> >> >> error_message: "error_code: UNDEFINED_CONDITION\n" >>>> >> >> >>>> >> >> 20/10/2010 12:22:25 PM >>>> >> >> org.waveprotocol.box.server.waveserver.WaveServerImpl$6 onFailure >>>> >> >> WARNING: outgoing waveletCommitUpdate failure: error_code: >>>> >> >> RESOURCE_CONSTRAINT >>>> >> >> error_message: "error_code: UNDEFINED_CONDITION\n" >>>> >> >> >>>> >> >> Which is better than the continual timeouts I guess :) >>>> >> >> >>>> >> >> James >>>> >> >> >>>> >> >> On Wed, Oct 20, 2010 at 2:26 AM, Vega <[email protected]> wrote: >>>> >> >> > Question: is it currently possible to federate with >>>> >> >> > wavesandbox.com >>>> >> >> > or >>>> >> >> > not? Or put it this way - does anyone is able to federate with >>>> >> >> > wavesandbox? >>>> >> >> > >>>> >> >> > -- >>>> >> >> > You received this message because you are subscribed to the >>>> >> >> > Google >>>> >> >> > Groups "Wave Protocol" group. >>>> >> >> > To post to this group, send email to >>>> >> >> > [email protected]. >>>> >> >> > To unsubscribe from this group, send email to >>>> >> >> > [email protected]. >>>> >> >> > For more options, visit this group at >>>> >> >> > http://groups.google.com/group/wave-protocol?hl=en. >>>> >> >> > >>>> >> >> > >>>> >> >> >>>> >> >> -- >>>> >> >> You received this message because you are subscribed to the Google >>>> >> >> Groups >>>> >> >> "Wave Protocol" group. >>>> >> >> To post to this group, send email to >>>> >> >> [email protected]. >>>> >> >> To unsubscribe from this group, send email to >>>> >> >> [email protected]. >>>> >> >> For more options, visit this group at >>>> >> >> http://groups.google.com/group/wave-protocol?hl=en. >>>> >> >> >>>> >> > >>>> >> > >>>> >> > >>>> >> > -- >>>> >> > --Matt >>>> >> > >>>> >> > -- >>>> >> > You received this message because you are subscribed to the Google >>>> >> > Groups >>>> >> > "Wave Protocol" group. >>>> >> > To post to this group, send email to [email protected]. >>>> >> > To unsubscribe from this group, send email to >>>> >> > [email protected]. >>>> >> > For more options, visit this group at >>>> >> > http://groups.google.com/group/wave-protocol?hl=en. >>>> >> > >>>> >> >>>> >> -- >>>> >> You received this message because you are subscribed to the Google >>>> >> Groups >>>> >> "Wave Protocol" group. >>>> >> To post to this group, send email to [email protected]. >>>> >> To unsubscribe from this group, send email to >>>> >> [email protected]. >>>> >> For more options, visit this group at >>>> >> http://groups.google.com/group/wave-protocol?hl=en. >>>> >> >>>> > >>>> > >>>> > >>>> > -- >>>> > --Matt >>>> > >>>> > -- >>>> > You received this message because you are subscribed to the Google >>>> > Groups >>>> > "Wave Protocol" group. >>>> > To post to this group, send email to [email protected]. >>>> > To unsubscribe from this group, send email to >>>> > [email protected]. >>>> > For more options, visit this group at >>>> > http://groups.google.com/group/wave-protocol?hl=en. >>>> > >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "Wave Protocol" group. >>>> To post to this group, send email to [email protected]. >>>> To unsubscribe from this group, send email to >>>> [email protected]. >>>> For more options, visit this group at >>>> http://groups.google.com/group/wave-protocol?hl=en. >>>> >>> >>> >>> >>> -- >>> --Matt >> >> >> >> -- >> --Matt >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Wave Protocol" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/wave-protocol?hl=en. >> > -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
