castellano | contact
 
    >VoIP Protocols   >Telephones   >QoS   >Codecs   >Forum   >Dictionary   >Future
 
Main Menu
SER (SIP Express Router)
    >Introduction   >SER vs Asterisk   >Linux Installation   >FreeBSD Installation   >Installation + MySQL   >Errors + Solutions    
  VoIP Protocols
  Telephones
  QoS
  Codecs
  SER (SIP Express Router)
  Introduction
  SER vs Asterisk
  Linux Installation
  FreeBSD Installation
  Installation + MySQL
  Errors + solutions
  Asterisk
  Forum
  Dictionary
  Future
     
 

SER (Sip Express Router) - Errors + solutions

SER (SIP Express Router) is sometimes a bit problematic. There are some methods to detect the problems.

1. If the SER server does not start correctly we can look at the following file to look for errors

/var/log/messages

In this file appears information about errors and warning when the SER server starts or tries to start

Another way is to start the SER server with "#/usr/local/sbin/ser -c" instead of "# /usr/local/serctl start" . This way we could see the messages at the screen or command line.


2. If the SER server starts but we want to monitor it we can execute the command

/usr/local/sbin/serctl moni

3. If the ser_mysql.sh script does not work verify that the mysql client is installed in a proper way.

Some common errors and the possible solution:

Problem Solution
Starting SER : PID file /var/run/ser.pid does not exist -- SER start failed

When starting the server with /usr/local/sbin/serctl start
Look at /var/log/messages because is a common failed error
ser: ERROR: load_module: could not open module </usr/local/lib/ser/modules/mysql.so>: libmysqlclient.so.15: cannot open shared object file: No such file or directory

At the file /var/log/messages

It is a bit strange but it can be solve. I solve it this way (perhaps is not the better one). A library is missing but perhaps we have a superior or inferior one: Find it at /usr/lib and then we can do for example

# ln -s libmysqlclient.so.14 libmysqlclient.so.15
new connection(): Can´t connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)

At the file /var/log/messages
Happens when mysql.sock is not at that folder It can be at /tmp/ You can solve it doing a virtual link

# ln -s /tmp/mysql.sock /var/lib/mysql/mysql.sock

submit_query(): Unknown column 'table version' in field list'

At the file /var/log/messages
Incompatibiitly between 0.8.X and 0.9.x. A table field has been changed We are executing 0.9.x version with 0.8.x database version

Solution: re-execute ser_mysql.sh script of 0.9.x version

ALERT: Backup the database previously.
/usr/local/sbin/ser_mysql.sh: line 160: gen_ha1: command not found HA1 calculation failed

When executing /usr/local/sbin/ser_mysql.sh create

Appear when we are not root. Sudo is not enough. We must be logged as root. If we do that the problem disappears.
* Warning: no fifo_db_url given - fifo DB commands disabled

At the file /var/log/messages

It is just a warning. We can do nothing. Or doing the following:

Add the following line to ser.cfg

fifo_db_url="mysql://mysqluser:mysqlpassword@dbhost/dbname"

If you have had a different problem you can send me an email and I will add it here for everybody. Or perhaps I can help you if I have time enough.




 
   
VoIP Foro©2006