Adam Cécile
Adam Cécile
WIP: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986140
Hello, I can confirm this behavior, especially under heavy load. The LDAP server is running on a different machine and there's a Cisco ASA between them. I highly suspect ejabberd...
Another one: http://lists.jabber.ru/pipermail/ejabberd/2006-September/002167.html
According to ejabberd code, I think it now requests for TCP keepalive when establishing LDAP connection: https://github.com/processone/ejabberd/blob/master/src/eldap.erl#L1064 However, we may have a network setup issue here: Default Linux keepalive is...
Problem looks fixed for us with my workaround
uh? Closed? Why? There's obviously something wrong in ejabberd behavior. It cannot expect lifetime connection with no ability to recover from a failure imho. Regards, Adam.
Hi, not yet sure, I just upgraded yesterday, I'll close it myself it's not happening anymore by the end of next week
It happen with the 17.13 release patched from #702 ``` panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x87f1b6] goroutine 15640 [running]:...
For the record, I'm not sure why you say WebRTC does not support h264. It definitely does, we have been running a custom CCTV system for a couple of years,...
For regular camera it is, we have nearly 1000 cams from 10 different brands, all working through Janus and Firefox/Chrome