Hi Michael , It is not really a hack :) .... i tend to think this number vary from OS to OS, from server to server .....like how slow the write ops take place - on some system is faster, on other is not.....
so nothing to feel bad about :) maybe we should simply increase the default number to cover also the slow cases. Regards, Bogdan opensipsl...@encambio.com wrote: >>> You may try to increase the number of tries to something higher - >>> 3200, just to see if that is the problem: >>> >>> see tls/tls_server.c , line 689 >>> #define MAX_SSL_RETRIES 320 >>> >>> >> This doesn't make sense to me. If 320 retries are attempted with no >> write op success, then trying 3200 can't be the solution. Rather, it >> must be that I have an error in the config script or some permission >> problem no? >> >> > Sadly, the only thing I could do to solve the problem was to > increase 320 as Bogdan suggested. I raised it to 3200, but > surely there is a lower 'cieling' that would work. It leaves > me with a somewhat sick feeling however, because this seems > very hacky and probably only masks the symptom and leaves > the real problem intact (which could surface again in some > other form.) > > Others have reported problems with the same tls_blocking_write > code, but as far as I know the problem has not been looked into. > > Regards, > Michael > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -- Bogdan-Andrei Iancu www.voice-system.ro _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users