SearchSearch  Log in to check your private messagesLog in to check your private messages  recent posts Recent Posts
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
kajo2000Offline



Joined: Jan 09, 2008
Posts: 1

Status: Offline
Posted: Jan 09, 2008 - 09:23 PM Reply with quote Back to top
Hi, I want ask you for help. I am new in work with OpenSER and I have this problem.
When I try start my SER "/sbin/openserctl start" i have this erorr "ERROR: PID file /var/run/openser.pid does not exist -- OpenSer start faild".
Thank you vary much for help.

This is my openser.cfg:
#
# $Id: openser.cfg 1827 2007-03-12 15:22:53Z bogdan_iancu $
#
# simple quick-start config script
# Please refer to the Core CookBook at http://www.openser.org/dokuwiki/doku.php
# for a explanation of possible statements, functions and parameters.
#

# ----------- global configuration parameters ------------------------

debug=3 # debug level (cmd line: -dddddddddd)
fork=yes
log_stderror=no # (cmd line: -E)
children=4
port=5060

# Uncomment these lines to enter debugging mode
#fork=no
#log_stderror=yes




# uncomment the following lines for TLS support
#disable_tls = 0
#listen = tls:your_IP:5061
#tls_verify_server = 1
#tls_verify_client = 1
#tls_require_client_certificate = 0
#tls_method = TLSv1
#tls_certificate = "/usr/local/ser/etc/openser/tls/user/user-cert.pem"
#tls_private_key = "/usr/local/ser/etc/openser/tls/user/user-privkey.pem"
#tls_ca_list = "/usr/local/ser/etc/openser/tls/user/user-calist.pem"

# ------------------ module loading ----------------------------------

#set module path
mpath="/usr/local/ser/lib/openser/modules/"

# Uncomment this if you want to use SQL database

loadmodule "sl.so"
loadmodule "tm.so"
loadmodule "rr.so"
loadmodule "maxfwd.so"
loadmodule "usrloc.so"
loadmodule "registrar.so"
loadmodule "textops.so"
loadmodule "mi_fifo.so"

# Uncomment this if you want digest authentication
# mysql.so must be loaded !
loadmodule "auth.so"
loadmodule "mysql.so"
loadmodule "auth_db.so"

# ----------------- setting module-specific parameters ---------------

# -- mi_fifo params --

modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo")

# -- 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");
exit;
};

if (msg:len >= 2048 ) {
sl_send_reply("513", "Message too big");
exit;
};

# 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
if (!method=="REGISTER")
record_route();

# subsequent messages withing a dialog should take the
# path determined by record-routing
if (loose_route()) {
# mark routing logic in request
append_hf("P-hint: rr-enforced\r\n");
route(1);
};

if (!uri==myself) {
# mark routing logic in request
append_hf("P-hint: outbound\r\n");
# if you have some interdomain connections via TLS
#if(uri=~"@tls_domain1.net") {
# t_relay("tls:domain1.net");
# exit;
#} else if(uri=~"@tls_domain2.net") {
# t_relay("tls:domain2.net");
# exit;
#}
route(1);
};

# 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("openser.org", "subscriber")) {
# www_challenge("openser.org", "0");
# exit;
#};

save("location");
exit;
};

lookup("aliases");
if (!uri==myself) {
append_hf("P-hint: outbound alias\r\n");
route(1);
};

# native SIP destinations are handled using our USRLOC DB
if (!lookup("location")) {
sl_send_reply("404", "Not Found");
exit;
};
append_hf("P-hint: usrloc applied\r\n");
};

route(1);
}


route[1] {
# send it out now; use stateful forwarding as it works reliably
# even for UDP2TCP
if (!t_relay()) {
sl_reply_error();
};
exit;
}
View user's profile Send private message
x-consoleOffline
Site Admin


Joined: Aug 01, 2006
Posts: 1130
Location: Leeds UK
Status: Offline
Posted: Feb 11, 2008 - 11:13 AM Reply with quote Back to top
does the user you are trying to run openser under have sufficient access to var/run to create the file? do those directories exist? ahve you tried starting openser just using the binary and not the ctl script?
View user's profile Send private message Yahoo Messenger
MocoNOffline



Joined: Nov 07, 2007
Posts: 10

Status: Offline
Posted: Apr 10, 2008 - 03:50 PM Reply with quote Back to top
I would guess that you have an error in your openser.cfg file. I have the same problem now and when I return to a previous working version of the openser configuration file it starts fine.

It would be nice to have a tool to check for errors in the openser.cfg. Anyone who knows if this exists and where to find it? Or other tips on this matter?
View user's profile Send private message
MocoNOffline



Joined: Nov 07, 2007
Posts: 10

Status: Offline
Posted: Apr 10, 2008 - 03:53 PM Reply with quote Back to top
Oh, and by the way, I did not take a look at your cfg file. I just wanted to share my personal experience on this.
View user's profile Send private message
MocoNOffline



Joined: Nov 07, 2007
Posts: 10

Status: Offline
Posted: Apr 10, 2008 - 04:06 PM Reply with quote Back to top
Ok, stupid of me. In the /var/log/messages file the errors are logged of course, with line number etc.

openser: CRITICAL:core:yyerror: parse error in config file, line 386, column 1-10: syntax error
View user's profile Send private message
x-consoleOffline
Site Admin


Joined: Aug 01, 2006
Posts: 1130
Location: Leeds UK
Status: Offline
Posted: Apr 10, 2008 - 04:48 PM Reply with quote Back to top
Quote:

It would be nice to have a tool to check for errors in the openser.cfg. Anyone who knows if this exists and where to find it? Or other tips on this matter?


openser -c -f <your openser.cfg>

this runs your config through the parser to check syntax and a few other things.
View user's profile Send private message Yahoo Messenger
MocoNOffline



Joined: Nov 07, 2007
Posts: 10

Status: Offline
Posted: Apr 11, 2008 - 03:55 PM Reply with quote Back to top
Thanks! This works a bit easier.
View user's profile Send private message


View previous topic Printable version Log in to check your private messages View next topic

Post new topic   Reply to topic
Forum Rules and Guidelines | About VoIP User | Privacy Policy


All logos and trademarks in this site are property of their respective owner.
Comments and posts are property of the poster, all the rest (c) 2003-2006 VoIP User.

No part of this site may be reproduced without our prior consent.