I was wondering why the active_watchers table includes a field for socket_info. Checks against values stored in this field during startup are causing me problems. I have a pair of OpenSIPS servers arranged for High Availability and using a shared Virtual IP address. Only one of the servers will have the VIP assigned at a given time. If I try to restart the OpenSIPS service on the other server, it will not start because it detects invalid socket information in the Presence module:
2014-01-09 16:18:05 ERROR:presence:restore_db_subs: bad format for stored sockinfo string 2014-01-09 16:18:05 ERROR:presence:mod_init: restoring subscribe info from database 2014-01-09 16:18:05 ERROR:core:init_mod: failed to initialize module presence 2014-01-09 16:18:05 ERROR:core:main: error while initializing modules Is there any way of disabling the check of this value during startup or of making it non-fatal? If I cleared all values in the socket_info field in the database just before restarting, would it allow the restart to complete but maybe break presence? John Quick Smartvox Limited Web: www.smartvox.co.uk _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users