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.

Reply via email to