Hi Waqas,

Thanks for the reply.
I tested out using ip4 and the problem remains. It's probably not a bosh 
issue after all.
Perhaps it is the mod_muc after all. I'll wait until it's in the repo and 
I'll try again.

Thanks,

Peter

On Thursday, May 8, 2014 11:30:23 PM UTC+1, Waqas wrote:
>
> On Thu, May 8, 2014 at 3:57 PM, Peter Villeneuve 
> <pete...@gmail.com<javascript:>
> > wrote:
>
>> Well I decided to remove Prosody and reinstall the 10 nightly debian 
>> package.
>> Bosh doesn't crash now although I'm still having problems with a 
>> previously working setup.
>>
>> Have there been any major changes to mod_bosh or any other core mods in 
>> latest nightly?
>>
>> Here's the error I'm now getting in nginx logs:
>>
>> [error] 7972#0: *69 upstream timed out (110: Connection timed out) while 
>> reading response header from upstream, client: xx.xx.xx.xx, server: 
>> meet.domain.com, request: "POST /http-bind HTTP/1.1", upstream: 
>> "http://[::1]:5280/http-bind";, host: "meet.domain.com", referrer: "
>> https://meet.domain.com/s6xtj6rzq90y66r
>>
>> Any help?
>>
>> Thanks
>>
>>
>> On Wednesday, May 7, 2014 10:50:55 PM UTC+1, Peter Villeneuve wrote:
>>>
>>> Hi,
>>>
>>> I just compiled from latest mercurial on my Debian 7 server and now I 
>>> get the following error.
>>> Any clue as to what's wrong?
>>>
>>> Cheers
>>>
>>>  
>>> May 07 21:46:43 bosh920eddab-981f-4548-9d7f-9405b1c86dbf    debug   
>>> Received[c2s]: <presence 
>>> to='7xtmnmfhsqjs8...@conference.my.domain.com/b9919ff2'>
>>> May 07 21:46:43 mod_muc     debug   
>>> b9919ff2-4b33-422d-931a-806a5a0ca...@my.domain.com/3a02ecfd-903f-4135-8b57-abf69a44cf6c
>>>  joining as 7xtmnmfhsqjs8...@conference.my.domain.com/b9919ff2
>>> May 07 21:46:43 mod_bosh    error   Traceback[bosh]: 
>>> /usr/lib/prosody/modules/muc/muc.lib.lua:172: attempt to call method 
>>> 'get_child' (a nil value)
>>> stack traceback:
>>>     /usr/lib/prosody/modules/muc/muc.lib.lua:172: in function 
>>> 'parse_history'
>>>     /usr/lib/prosody/modules/muc/muc.lib.lua:242: in function 'send_history'
>>>     /usr/lib/prosody/modules/muc/muc.lib.lua:594: in function 
>>> </usr/lib/prosody/modules/muc/muc.lib.lua:550>
>>>     (tail call): ?
>>>
>>>
> Hey, apologies about the issue with trunk.
>
> The error you are seeing is in MUC, not BOSH. We have a new version of 
> mod_muc, which has only partially been merged in trunk due to some issues. 
> The rest of it should make it into the repo shortly.
>
> The nginx error.. can you access "http://[::1]:5280/http-bind"; via cURL? 
> It might be the IPv6 addressing, so give 127.0.0.1 a try as well.
>
> mod_bosh has not seen any significant changes recently, so I don't expect 
> it to be broken in 0.10. Feel free to join our chatroom to discuss this 
> live.
>
> --
> Waqas Hussain
>
>  

-- 
You received this message because you are subscribed to the Google Groups 
"prosody-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to prosody-dev+unsubscr...@googlegroups.com.
To post to this group, send email to prosody-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/prosody-dev.
For more options, visit https://groups.google.com/d/optout.

Reply via email to