-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DISCO test fails (due to timeout?) #24
Comments
This is a problem that can be observed happening with many other "long-duration" tests as well... they fail sometimes because Heroku will decide not to serve them (that's a guess) and respond with a H12 Request Timeout error. These tests usually start working again after a while. We maybe should deploy the protocol inspector in our own servers before v1.0. I ran the buddycloud_disco test against surevine.com a couple times and it managed to succeed everytime here but I know that it fails sometimes, but I think the reason is 100% Heroku related. |
I just observed the DISCO test failing, also my prosody instance seems to be setup properly. In the end I could only get the buddycloud_server_disco passing by adding a PTR record. |
@t3dev - we just had a call about this and, yes you can use a |
I cloned the testing framework and tried to poke into it. Even raising the timeout to 30 seconds the disco discovery fails for me. I can't get any clou from the Exception as it seems to be empty. using xmpp-console in pidgin works nicely with:
Does disco need credentials or require a login to work? |
@guilhermesgb could it be something to do TLS security and the remote domain not having a valid certificate and therefore dropping the s2s connection? Which domain do you test from? https://xmpp.net/result.php?domain=datenbetrieb.de&type=server |
I really don't know. This test used to work as is (the disco, at least)... |
The test connects to the xmpp-servers without SSL and TLS: https://github.com/buddycloud/buddycloud-tests-framework/blob/master/installation/tests/buddycloud_server_disco.py#L146 Maybe this has something to do with it (secure connection is a must)? On Tue, Apr 29, 2014 at 2:29 PM, Guilherme Santos guisgb13@gmail.comwrote:
Guilherme Santos Galvão Baptista |
I've read through the sleekxmpp source - it seems that if an SSL error On Tue, Apr 29, 2014 at 2:55 PM, Guilherme Santos guisgb13@gmail.comwrote:
Guilherme Santos Galvão Baptista |
sleekXMPP ends with IqTimeout. On every attempt I find this in my prosody.log: info incoming s2s stream (unknown host)->buddycloud.org closed: This host does not serve buddycloud.org |
I've just finally fixed this test. Somehow this test used to work a few By the way, @t3dev, I ran the protocol against datenbetrieb.de again and On Wed, Apr 30, 2014 at 6:38 AM, Peter Niederlag
Guilherme Santos Galvão Baptista |
On Wed, Apr 30, 2014 at 9:45 AM, Guilherme Santos guisgb13@gmail.comwrote:
Actually, I've payed more attention to the logs, what is happening when we I don't know what would cause this... @abmargb, any ideas? Cheers, Guilherme Santos Galvão Baptista |
Weird. Will take a look on this as soon as I have time. On Wed, Apr 30, 2014 at 9:57 AM, Guilherme Santos
Abmar Barros |
awesome, thx. It works nicely now! @guilhermesgb I have been frequently debugging/restarting/changing the services and DNS so failures are likely. |
When testing for surevine.com's setup the channel server disco failed potentially due to a timeout (after checking the tests). It would be worth checking out why the test failed. Requests for me respond in 1 second using xmpp-ftw so it may not be the timeout.
The text was updated successfully, but these errors were encountered: