Hi;
I've noticed that if I disable contact storage mode ("usrloc",
db_mode", 0), I can start SER just fine. Does anybody have any
thoughts on that? This is a clean install of 0.9.0 with a config that
worked just fine with 0.8.14.
Thanks again,
Dan
On Fri, 4 Mar 2005 11:44:37 -0500, Daniel Poulsen <dpoulsen(a)gmail.com> wrote:
Hi,
I saw another serusers post on this, but didn't find an answer. I
have a vanilla install of 0.9.0 on a freshly built debian box. When I
run ser, I get:
Mar 4 11:34:52 sip-failover ser[5055]: Maxfwd module- initializing
Mar 4 11:34:52 sip-failover ser[5055]: register_udomain(): Invalid
table version (use ser_mysql.sh reinstall)
Mar 4 11:34:52 sip-failover ser[5055]: domain_fixup(): Error while
registering domain
Mar 4 11:34:52 sip-failover ser[5055]: ERROR: fix_expr : fix_actions error
If I run ser_mysql.sh reinstall, I get different errors:
Mar 4 11:36:42 sip-failover ser[5102]: table_version(): Invalid
number of rows received: 2, uri
Mar 4 11:36:42 sip-failover ser[5102]: ERROR: uri_db:mod_init():
Error while querying table version
Mar 4 11:36:42 sip-failover ser[5102]: init_mod(): Error while
initializing module uri_db
As the previous poster defailed, the "invalid number" error occurs
because the ser_mysql.sh script creates duplicate entries in the
version table. The quesion is, what table version sill satisfy
'register_udomain()'?
Currently, I have:
mysql> select * from version;
+-----------------------+---------------+
| table_name | table_version |
+-----------------------+---------------+
| subscriber | 5 |
| reserved | 1 |
| phonebook | 1 |
| pending | 4 |
| missed_calls | 2 |
| location | 6 |
| grp | 2 |
| event | 1 |
| aliases | 6 |
| active_sessions | 1 |
| acc | 2 |
| config | 1 |
| silo | 3 |
| realm | 1 |
| domain | 1 |
| uri | 1 |
| server_monitoring | 1 |
| server_monitoring_agg | 1 |
| trusted | 1 |
| usr_preferences | 1 |
| preferences_types | 1 |
| admin_privileges | 1 |
| calls_forwarding | 1 |
| speed_dial | 1 |
+-----------------------+---------------+
24 rows in set (0.00 sec)
Thank you for your time,
Dan Poulsen