Re: PQConsumeinput stuck on recv

Hi, On 2018-03-05 17:57:51 -0300, Andre Oliveira Freitas wrote: > Ok, on one hand glad to hear that is an artifact, on the other hand > that means the issue is still out there... > > I'm not a maintainer of Freeswitch, I am an user of it. However I am > trying to supply the maintainers with any

Re: PQConsumeinput stuck on recv

Hi, On 2018-03-01 19:20:04 -0300, Andre Oliveira Freitas wrote: > I was able to capture the backtrace again, now with libpq debugging symbols. > > Thread 15 (Thread 0x7f8cec068700 (LWP 68)): > #0 0x7f8d252a1d9b in __libc_recv (fd=150, buf=0x7f8cf0034410, > n=16384, flags=623517083,

Re: PQConsumeinput stuck on recv

Hi, I was able to capture the backtrace again, now with libpq debugging symbols. Thread 15 (Thread 0x7f8cec068700 (LWP 68)): #0 0x7f8d252a1d9b in __libc_recv (fd=150, buf=0x7f8cf0034410, n=16384, flags=623517083, flags@entry=0) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:33 #1

Re: PQConsumeinput stuck on recv

Hi, On 2018-02-23 15:59:18 -0300, Andre Oliveira Freitas wrote: > I'm using the libpq that comes with debian, however I can install the > library from the official repository to be sure, I assume the one from > the official repo has it enabled. That should be fine. Could you get the backtrace

Re: PQConsumeinput stuck on recv

2018-02-23 14:20 GMT-03:00 Andres Freund : > > Hi, > > On 2018-02-23 13:33:18 -0300, Andre Oliveira Freitas wrote: > > Since it's been happening for a few weeks now, every time it freezes we > > take a gcore dump and check it in gdb... and after a lot of hair pulling > > and

Re: PQConsumeinput stuck on recv

Hi, On 2018-02-23 13:33:18 -0300, Andre Oliveira Freitas wrote: > Since it's been happening for a few weeks now, every time it freezes we > take a gcore dump and check it in gdb... and after a lot of hair pulling > and learning about the innards of the VoIP software we see that most often > the