[OpenSIPS-Users] ERROR:usrloc:preload_udomain: fetching rows failed on OpenSIPS 1.5.3

[Jonathan Hunter]

Hi Guys,
We are going through a process of getting in a position to start the upgrade path from opensips 1.5.3 to the latest release, however to achieve this, we alsoneed to move from fedora to Centos 6.5.
We are also moving from Mysql 5.1 to Percona 5.6.17.
Now having moved a working configuration from the fedora box, over to Centos 6.5, the following error is reported when starting opensips;


Jun 10 22:44:37 localhost /usr/local/sbin/opensips[25490]: ERROR:core:db_allocate_rows: no memory leftJun 10 22:44:37 localhost /usr/local/sbin/opensips[25490]: ERROR:db_mysql:db_mysql_fetch_result: no memory leftJun 10 22:44:37 localhost /usr/local/sbin/opensips[25490]: ERROR:usrloc:preload_udomain: fetching rows failedJun 10 22:44:37 localhost /usr/local/sbin/opensips[25490]: ERROR:usrloc:child_init: child(1): failed to preload domain 'location'Jun 10 22:44:37 localhost /usr/local/sbin/opensips[25490]: ERROR:core:init_mod_child: failed to initializing module usrloc, rank 1Jun 10 22:44:37 localhost /usr/local/sbin/opensips[25490]: ERROR:core:main_loop: init_child failed for UDP listenerJun 10 22:44:37 localhost /usr/local/sbin/opensips[25503]: CRITICAL:core:receive_fd: EOF on 6


So I have added Fetch_rows entry (which allows opensips to start and work), and I notice that the maximum I can set it to before it crashes is 1550 rows. (was set to the default).
The server has no load, and has no memory issues whatsoever, so we are wondering if there is a buffer issue related to the fetch_rows() in the db connector.
Or is this simply an issue with 1.5.3 and Centos 6.5?
Any comments/thoughts would be appreciated.
As I mentioned we are pushing to make changes so we can start moving the Opensips versions forward, its just doing it in a controlled manner.
Many thanks
Jon
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20140610/b016a1c2/attachment.htm>