[OpenSIPS-Users] Critical Errors on dr_reload

[Kelsey Cummings]

I've had a problem dropped in my lap so please forgive my general
ignorance with regards to opensips.  We've got a pair of 1.5.1 opensips
servers running on centos 5.5 64bit.  After some period of normal
operation, after some number of dr_reloads, we run into the following
problem.  The other person working on this confirmed that it was not the
PUA bug referred to by
http://www.mail-archive.com/users@lists.opensips.org/msg05121.html

It continues to route properly, but on the old config until it is
restarted where it will work for some time (<24hrs) before failing
again.  We've been unable to reproduce the problem by just reloading the
config in a loop so believe there is some other interaction at play -
perhaps it has to do with configurations actually being changed?  The
pair of servers tend to hit the failure at more or less the same time -
the updates are pushed to them automatically by our provisioning
systems.

Aug 24 12:08:52 a /usr/sbin/opensips[21838]: INFO:drouting:dr_reload_cmd: "dr_reload" MI command received! 
Aug 24 12:08:52 a /usr/sbin/opensips[21838]: ERROR:core:db_allocate_rows: no memory left 
Aug 24 12:08:52 a /usr/sbin/opensips[21838]: ERROR:db_mysql:db_mysql_fetch_result: no memory left 
Aug 24 12:08:52 a /usr/sbin/opensips[21838]: ERROR:drouting:dr_load_routing_info: Error fetching rows 
Aug 24 12:08:52 a /usr/sbin/opensips[21838]: CRITICAL:drouting:dr_reload_data: failed to load routing info 
Aug 24 12:08:52 a /usr/sbin/opensips[21838]: CRITICAL:drouting:dr_reload_cmd: failed to load routing data 

Any suggestions?

-- 
Kelsey Cummings - kgc at corp.sonic.net      sonic.net, inc.
System Architect                          2260 Apollo Way
707.522.1000                              Santa Rosa, CA 95407