Re: [naviserver-devel] ns_proxy hang

2017-05-10 Thread David Osborne
Has anyone got any ideas on debugging this issue? Turns out it's causing us many more operational issues that we first thought... Regards, -- David On 18 April 2017 at 15:44, David Osborne wrote: > Hi, > > We're encountering an occasional problem which means calls to ns_proxy > hang forever. >

Re: [naviserver-devel] ns_proxy hang

2017-05-10 Thread Gustaf Neumann
Dear David, i have not been able to look into this yet. However, i've checked our logs on several servers using nsproxy intensively, but did not see any problems. How is the proxy setup (config section and "ns_proxy configure" command) in your environment? -g Am 10.05.17 um 10:50 schrieb Dav

Re: [naviserver-devel] ns_proxy hang

2017-05-10 Thread David Osborne
The manifestation for us in production is quite insidious and difficult to spot the root cause of. Certainly not easy to see via the logs. One place we are experiencing it is in code which generates outgoing emails. Sometimes, when the outgoing email is particularly large, nsproxy times out while

Re: [naviserver-devel] ns_proxy hang

2017-05-10 Thread Gustaf Neumann
We don't see such hangs either. Does increasing the waittimeout solve this issue? ... not as a fix, but to narrow the problem down. -gn Am 10.05.17 um 13:38 schrieb David Osborne: The manifestation for us in production is quite insidious and difficult to spot the root cause of. Certainly not ea

Re: [naviserver-devel] ns_proxy hang

2017-05-10 Thread David Osborne
Increasing waittimeout doesn't seem to have any effect on this problem. I have backtraces of all threads at the point of the hang here: https://gist.github.com/davidqc/ebee38528b0a40a0b8d028981ad933e6 Thread 19 I think is the culprit: Thread 19 (Thread 0x7fffaaffd700 (LWP 17652)): #0 0x7ff

Re: [naviserver-devel] ns_proxy hang

2017-05-10 Thread Gustaf Neumann
I'll look at it at the weekend - unless someone else can fix this before this. -g Am 10.05.17 um 16:00 schrieb David Osborne: Increasing waittimeout doesn't seem to have any effect on this problem. I have backtraces of all threads at the point of the hang here: https://gist.github.com/davidqc