If you start ser (via command line) and do a 'ps' is it running? What
does /var/log/messages say? Look in the current directory as well as /
is there a core file?
-Evan
On Thu, 2005-02-03 at 19:28 +0100, info(a)beeplove.com wrote:
See this,
[root@croaker admin]# ser -f /etc/ser/ser.cfg -c -ddd &> ser.log
[root@croaker admin]# vim ser.log
## I have removed few lines from ser.log that seems unimportant.
[root@croaker admin]# cat ser.log
0(26776) read 4076494534 from /dev/random
0(26776) seeding PRNG with 889008826
0(26776) test random number 1332590677
0(26776) shm_mem_init: success
0(26776) DEBUG: register_fifo_cmd: new command (print) registered
0(26776) DEBUG: register_fifo_cmd: new command (uptime) registered
0(26776) DEBUG: register_fifo_cmd: new command (version) registered
0(26776) DEBUG: register_fifo_cmd: new command (pwd) registered
0(26776) DEBUG: register_fifo_cmd: new command (arg) registered
0(26776) DEBUG: register_fifo_cmd: new command (which) registered
0(26776) DEBUG: register_fifo_cmd: new command (ps) registered
0(26776) DEBUG: register_fifo_cmd: new command (kill) registered
0(26776) loading module //lib/ser/modules/mysql.so
0(26776) loading module /lib/ser/modules/sl.so
0(26776) loading module /lib/ser/modules/tm.so
0(26776) loading module /lib/ser/modules/rr.so
0(26776) loading module /lib/ser/modules/maxfwd.so
0(26776) loading module /lib/ser/modules/usrloc.so
0(26776) loading module /lib/ser/modules/registrar.so
0(26776) loading module /lib/ser/modules/auth.so
0(26776) loading module /lib/ser/modules/auth_db.so
0(26776) set_mod_param_regex: usrloc matches module usrloc
0(26776) set_mod_param_regex: found <db_mode> in module usrloc
[/lib/ser/modules/usrloc.so]
0(26776) set_mod_param_regex: auth_db matches module auth_db
0(26776) set_mod_param_regex: found <calculate_ha1> in module auth_db
[/lib/ser/modules/auth_db.so]
0(26776) set_mod_param_regex: auth_db matches module auth_db
0(26776) set_mod_param_regex: found <password_column> in module auth_db
[/lib/ser/modules/auth_db.so]
0(26776) find_export: found <mf_process_maxfwd_header> in module
maxfwd_module [/lib/ser/modules/maxfwd.so]
0(26776) find_export: found <sl_send_reply> in module sl_module
[/lib/ser/modules/sl.so]
0(26776) find_export: found <sl_send_reply> in module sl_module
[/lib/ser/modules/sl.so]
0(26776) find_export: found <record_route> in module rr
[/lib/ser/modules/rr.so]
0(26776) find_export: found <loose_route> in module rr
[/lib/ser/modules/rr.so]
0(26776) find_export: found <t_relay> in module tm
[/lib/ser/modules/tm.so]
0(26776) find_export: found <save> in module registrar
[/lib/ser/modules/registrar.so]
0(26776) find_export: found <lookup> in module registrar
[/lib/ser/modules/registrar.so]
0(26776) find_export: found <sl_send_reply> in module sl_module
[/lib/ser/modules/sl.so]
0(26776) find_export: found <t_relay> in module tm
[/lib/ser/modules/tm.so]
0(26776) find_export: found <sl_reply_error> in module sl_module
[/lib/ser/modules/sl.so]
0(26776) routing table 0:
0(26776) WARNING: could not rev. resolve 192.168.71.3
config file ok, exiting...
0(26776) DEBUG: tm_shutdown : start
0(26776) DEBUG: tm_shutdown : empting hash table
0(26776) DEBUG: tm_shutdown: releasing timers
0(26776) DEBUG: tm_shutdown : removing semaphores
0(26776) DEBUG: tm_shutdown : done
0(26776) shm_mem_destroy
0(26776) destroying the shared memory lock
Listening on
127.0.0.1 [127.0.0.1]:5060
192.168.71.3 [192.168.71.3]:5060
Aliases: localhost:5060 localhost.localdomain:5060 croaker:5060
[root@croaker admin]# cat /etc/ser/ser.cfg
#
# $Id: ser.cfg,v 1.21.4.1 2003/11/10 15:35:15 andrei Exp $
#
# simple quick-start config script
#
# ----------- global configuration parameters ------------------------
#debug=3 # debug level (cmd line: -dddddddddd)
#fork=yes
#log_stderror=no # (cmd line: -E)
/* Uncomment these lines to enter debugging mode
debug=7
fork=no
log_stderror=yes
*/
check_via=no # (cmd. line: -v)
dns=no # (cmd. line: -r)
rev_dns=no # (cmd. line: -R)
#port=5060
#children=4
fifo="/tmp/ser_fifo"
# ------------------ module loading ----------------------------------
# Uncomment this if you want to use SQL database
loadmodule "//lib/ser/modules/mysql.so"
loadmodule "/lib/ser/modules/sl.so"
loadmodule "/lib/ser/modules/tm.so"
loadmodule "/lib/ser/modules/rr.so"
loadmodule "/lib/ser/modules/maxfwd.so"
loadmodule "/lib/ser/modules/usrloc.so"
loadmodule "/lib/ser/modules/registrar.so"
# Uncomment this if you want digest authentication
# mysql.so must be loaded !
loadmodule "/lib/ser/modules/auth.so"
loadmodule "/lib/ser/modules/auth_db.so"
# ----------------- setting module-specific parameters ---------------
# -- usrloc params --
#modparam("usrloc", "db_mode", 0)
# Uncomment this if you want to use SQL database
# for persistent storage and comment the previous line
modparam("usrloc", "db_mode", 2)
# -- auth params --
# Uncomment if you are using auth module
#
modparam("auth_db", "calculate_ha1", yes)
#
# If you set "calculate_ha1" parameter to yes (which true in this
config),
# uncomment also the following parameter)
#
modparam("auth_db", "password_column", "password")
# -- rr params --
# add value to ;lr param to make some broken UAs happy
#modparam("rr", "enable_full_lr", 1)
# ------------------------- request routing logic -------------------
# main routing logic
route{
# initial sanity checks -- messages with
# max_forwards==0, or excessively long requests
if (!mf_process_maxfwd_header("10")) {
sl_send_reply("483","Too Many Hops");
break;
};
if ( msg:len > max_len ) {
sl_send_reply("513", "Message too big");
break;
};
# we record-route all messages -- to make sure that
# subsequent messages will go through our proxy; that's
# particularly good if upstream and downstream entities
# use different transport protocol
record_route();
# loose-route processing
if (loose_route()) {
t_relay();
break;
};
# if the request is for other domain use UsrLoc
# (in case, it does not work, use the following command
# with proper names and addresses in it)
if (uri==myself) {
if (method=="REGISTER") {
# Uncomment this if you want to use digest authentication
# if (!www_authorize("iptel.org",
"subscriber")) {
# www_challenge("iptel.org", "0");
# break;
# };
save("location");
break;
};
# native SIP destinations are handled using our USRLOC
DB
if (!lookup("location")) {
sl_send_reply("404", "Not Found");
break;
};
};
# forward to current uri now; use stateful forwarding; that
# works reliably even if we forward from TCP to UDP
if (!t_relay()) {
sl_reply_error();
};
}
Help .. please
Mohammad
Evan Borgstrom <evan.borgstrom(a)ca.mci.com> wrote on 02/03/2005, 07:08:58
PM:
> This means that ser has crashed... most likely a bad config file.
> Try running: ser -c
>
> That will test your config file, you can also try ser -c -d for more
> debugging info.
>
> -Evan
>
> On Thu, 2005-02-03 at 19:06 +0100, info(a)beeplove.com wrote:
> > Hello List:
> >
> > I have able to to compile ser from source.
> > I also have setup ser database.
> >
> > My problem is:
> >
> > ############################
> > [root@croaker ~]# service ser start
> > [ OK ]
> > [root@croaker ~]# service ser status
> > ser dead but subsys locked
> > ##############################
> >
> > This issue might have discussed before, but I was not able to find
> > *Search* in archive.
> > Would anybody please send me link to search in the archive.
> >
> > Thanks
>
> _______________________________________________
> Serusers mailing list
> serusers(a)lists.iptel.org
>
http://lists.iptel.org/mailman/listinfo/serusers