4 Feb
2008
4 Feb
'08
3:38 p.m.
Should have mentioned that I'm running "trunk". Don't know if the
problem is present on 1.3.
The system is lightly used, so it's probably not load related.
Haven't had time to investigate the problem (haven't recompiled with the
extra memory flags).
http://www.openser.org/dokuwiki/doku.php/troubleshooting:memory
For the benefit of the list: The info provided below is just one method
of addressing the symptoms of the problem. It should not be relied on
as a long term solution. That said, it does offer an example of how
someone can get cron, the OpenSER logs, and OpenSER to work together.
Bogdan-Andrei Iancu wrote:
Hi Norm,
have you tried to see if the memory errors are because of a leak or
because of load??
Regards,
Bogdan
Norman Brandinger wrote:
I'm also receiving the out of memory errors.
Created a little shell script and have it executed by cron regularly.
/etc/syslog.conf:
local6.* -/var/log/openser.log
openser.cfg:
log_facility=LOG_LOCAL6
ctontab:
1,15,30,45 * * * * /usr/local/bin/openser_mem_checker
/usr/local/bin/openser_mem_checker:
#!/bin/sh
ERRORCOUNT=`grep 'out of pkg memory' /var/log/openser.log | wc -l`
if [ $ERRORCOUNT -gt 0 ] ; then
echo "OpenSER is having a memory problem. Restarting."
/usr/sbin/logrotate -f /etc/logrotate.d/openser
PID=`cat /var/run/syslogd.pid`
kill -HUP $PID
/etc/init.d/openser restart
fi
</snip>
Regards,
Norm
Iñaki Baz Castillo wrote:
On Monday 04 February 2008 15:37:36 Henning
Westerholt wrote:
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
On Monday 04 February 2008, Iñaki Baz Castillo
wrote:
> Hi, why could this error occur? It has ocurred me now several
> times but
> never seen it before ¿?
>
>
> Feb 4 15:31:31 [27228] ERROR:mysql:db_mysql_convert_row: no private
> memory left
>
Hi Iñaki,
this means that the mysql driver could not allocate memory for its
internal
usage, skipping the query. What version of the server do you use?
I use Debian Sid with mysql-server-5.0 (5.0.51-1).
Do you mean that this is a database bug? or OpenSer mysql driver bug?