Darren,
thank you for the report. Which SER version are you using?
What we need you to do is to recompile SER from sources in debug mode, set memlog<debug and resend the memory report. (In debug mode, the report identifies the fragments which is what we need to see.)
Thank you,
-jiri
At 08:27 PM 1/14/2004, Darren Nay wrote:
Hey All,
Since we have ramped up usage from about 2 SIP phones to 30 SIP phones on our SER boxes to start some testing we are now getting a LOT of "Out of memory" errors in the syslog.
We were originally running on a Sun Ultra60 with Solaris 9 but changed to an Intel box running Redhat 9 since we thought that there might be some memory leaks on Solaris. Unfortunately the problem exists regardless of the OS. When we start SER, it usually works fine for about 5 mins and then it starts giving the errors.
We have plenty of memory on both servers that we have tested this on. Over a gig on each. Also, when I run top to check system resources it tells me that there is still over 800 meg of physical memory and over a gig of swap free even while SER is spitting out these errors.
The errors that we are seeing the logs are as follows:
Jan 14 13:32:45 jupiter /usr/sbin/ser[27179]: ERROR: build_req_buf_from_sip_req: out of memory Jan 14 13:32:45 jupiter /usr/sbin/ser[27179]: ERROR: print_uac_request: no pkg_mem Jan 14 13:32:45 jupiter /usr/sbin/ser[27179]: ERROR: t_forward_nonack: failure to add branches We get these over and over again in the syslog.
Anyone know the reason that we are getting these errors? Is this a bug with SER? or misconfiguration somehow on our part? If so, how do we fix it?
I have included our ser.cfg file as an attachment to this email, and I have also included debug output from SER as a seperate attachment.
Any help would be very much appreciated! Thanks,
Darren Nay - mailto:dnay@libertyisp.comdnay@libertyisp.com
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/