1 Jul
2005
1 Jul
'05
6:34 a.m.
Finally, I know why I am having problems with SER + MySQL: I think
is that because I trying to run SER and MySQL in different machines. Per the
installation instructions that I found in www.iptel.org, I have installed
SER on other machine in the same subnet, and I was able to create and
initialize the DB with the "ser_mysql create" command. I do that modifying
the ser_mysql.sh and serctl.sh scripts setting DBHOST=<MySQL IP Address> on
both files. I thought that those changes would allow to ser application to
start using the remote MySQL server, but analyzing the ser debug messages, I
understand that the application is trying to locate the DB on the local
machine.
So, there is somebody that there is implemented SER + Remote MySQL
Server?... can you tell me what I need to do to tell to SER that the DB is
located on a remote machine?...
Thanxs in advance!
Zeva
----- Original Message -----
From: "Sebastian Kigelman" <sebastian(a)kigelman.com.ar>
To: <serusers(a)lists.iptel.org>
Sent: Wednesday, June 29, 2005 11:34 AM
Subject: [Serusers] 2nd try: SER does not start with MySQL
Hi there!!!... Iam newy in SER mailing list, and I
have a problem with my
SER installation that I saw that other members have before, but I can't
find
a solution to the issue.
I have installed the SER (v0.8.14), all works fine until I add MySQL
support
to get persistent users. after that, when I run "serctl start" I get this
error:
----------------------------------------------------------------
Starting SER : cat: /var/run/ser.pid: No such file or directory
started pid()
----------------------------------------------------------------
I have made some test to troubleshot this issue, for exsaplme: remplacing
DIR=... with the full path to SER executable in "serctl"... and also I
increase the debug level in "ser.cfg" to 7, and I get this output:
----------------------------------------------------------------
MyHost:/etc/ser# ser -c
0(2577) loading module /usr/lib/ser/modules/mysql.so
0(2577) loading module /usr/lib/ser/modules/sl.so
0(2577) loading module /usr/lib/ser/modules/tm.so
0(2577) loading module /usr/lib/ser/modules/rr.so
0(2577) loading module /usr/lib/ser/modules/maxfwd.so
0(2577) loading module /usr/lib/ser/modules/usrloc.so
0(2577) loading module /usr/lib/ser/modules/registrar.so
0(2577) loading module /usr/lib/ser/modules/auth.so
0(2577) loading module /usr/lib/ser/modules/auth_db.so
0(2577) set_mod_param_regex: usrloc matches module usrloc
0(2577) set_mod_param_regex: found <db_mode> in module usrloc
[/usr/lib/ser/modules/usrloc.so]
0(2577) set_mod_param_regex: auth_db matches module auth_db
0(2577) set_mod_param_regex: found <calculate_ha1> in module auth_db
[/usr/lib/ser/modules/auth_db.so]
0(2577) set_mod_param_regex: auth_db matches module auth_db
0(2577) set_mod_param_regex: found <password_column> in module auth_db
[/usr/lib/ser/modules/auth_db.so]
0(2577) set_mod_param_regex: rr matches module rr
0(2577) set_mod_param_regex: found <enable_full_lr> in module rr
[/usr/lib/ser/modules/rr.so]
0(2577) find_export: found <mf_process_maxfwd_header> in module
maxfwd_module [/usr/lib/ser/modules/maxfwd.so]
0(2577) find_export: found <sl_send_reply> in module sl_module
[/usr/lib/ser/modules/sl.so]
0(2577) find_export: found <sl_send_reply> in module sl_module
[/usr/lib/ser/modules/sl.so]
0(2577) find_export: found <record_route> in module rr
[/usr/lib/ser/modules/rr.so]
0(2577) find_export: found <loose_route> in module rr
[/usr/lib/ser/modules/rr.so]
0(2577) find_export: found <t_relay> in module tm
[/usr/lib/ser/modules/tm.so]
0(2577) find_export: found <www_authorize> in module auth_db
[/usr/lib/ser/modules/auth_db.so]
0(2577) find_export: found <www_challenge> in module auth
[/usr/lib/ser/modules/auth.so]
0(2577) find_export: found <save> in module registrar
[/usr/lib/ser/modules/registrar.so]
0(2577) find_export: found <lookup> in module registrar
[/usr/lib/ser/modules/registrar.so]
0(2577) find_export: found <sl_send_reply> in module sl_module
[/usr/lib/ser/modules/sl.so]
0(2577) find_export: found <t_relay> in module tm
[/usr/lib/ser/modules/tm.so]
0(2577) find_export: found <sl_reply_error> in module sl_module
[/usr/lib/ser/modules/sl.so]
0(2577) routing table 0:
...blah
...blah
...blah
...blah
WARNING: could not rev. resolve 192.168.0.4
Listening on
127.0.0.1 [127.0.0.1]:5060
192.168.0.4 [192.168.0.4]:5060
Aliases: MyHost:5060 localhost:5060 localhost.localdomain:5060
config file ok, exiting...
0(2577) DEBUG: tm_shutdown : start
0(2577) DEBUG: tm_shutdown : empting hash table
0(2577) DEBUG: tm_shutdown: releasing timers
0(2577) DEBUG: tm_shutdown : removing semaphores
0(2577) DEBUG: tm_shutdown : done
0(2577) shm_mem_destroy
0(2577) destroying the shared memory lock
----------------------------------------------------------------
I couldn't find what is wrong in my configuration...
BTW, I can add, remove and edit users in MySQL Database using "serctl"
subscribers commands (that means that my SER machine is talking with MySQL
server as in expected)
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers