<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: [Serusers] problems when starting ser</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>Hi all,<BR>
<BR>
First of all, answering to Andrei, yes the version I am using is 2.0.<BR>
And, in fact, all the problems I have with SER are related to /var/run/ser.<BR>
This morning I checked and it was not there, so I created the directory, which solved the problem. However, after rebooting the directory was gone again; so I decided to uninstall completely SER and start again with the process, which showed me that /var/run/ser was created correctly during the installation. But, I do not know why, it does not survive after rebooting...<BR>
<BR>
I know that one possibility is to create it directly when calling SER, however I would like to make it survive the reboot.<BR>
I though to make it immutable but I am not sure if it is the correct solution. Is there any other way?<BR>
<BR>
Thanks in advance,<BR>
Rebeca Martinez<BR>
<BR>
<BR>
-----Mensaje original-----<BR>
De: Andrei Pelinescu-Onciul [<A HREF="mailto:andrei@iptel.org">mailto:andrei@iptel.org</A>]<BR>
Enviado el: mié 23/12/2009 21:32<BR>
Para: Martínez García, Rebeca<BR>
CC: serusers@lists.iptel.org; Huertas García, Victor<BR>
Asunto: Re: [Serusers] problems when starting ser<BR>
<BR>
On Dec 23, 2009 at 13:06, "Mart?nez Garc?a, Rebeca" <remartinez@indra.es> wrote:<BR>
><BR>
> Hello all,<BR>
><BR>
> I have installed ser in Ubuntu Karmic by means of Synaptic without any problems or errors during the installation.<BR>
> But before starting to configure the ser.cfg, I decided firstly to try the configuration by default and I got this error (I only uncommented the "log_stderror=yes"):<BR>
<BR>
><BR>
> cng@cng:/etc/ser$ ser D E<BR>
> Listening on<BR>
> udp: 127.0.0.1 [127.0.0.1]:5060<BR>
> udp: 10.1.3.207 [10.1.3.207]:5060<BR>
> udp: 192.168.50.10 [192.168.50.10]:5060<BR>
> tcp: 127.0.0.1 [127.0.0.1]:5060<BR>
> tcp: 10.1.3.207 [10.1.3.207]:5060<BR>
> tcp: 192.168.50.10 [192.168.50.10]:5060<BR>
> Aliases:<BR>
> tcp: cng.local:5060<BR>
> tcp: cng:5060<BR>
> tcp: localhost:5060<BR>
> udp: cng.local:5060<BR>
> udp: cng:5060<BR>
> udp: localhost:5060<BR>
><BR>
> 0(2956) init_tcp: using epoll_lt as the io watch method (auto detected)<BR>
> cng@cng:/etc/ser$ 0(2958) Maxfwd module- initializing<BR>
> 0(2958) ERROR: fifo_server.c:857: Can't create FIFO: No such file or directory (mode=384)<BR>
> 0(2958) ERROR: ctl: mod_init: init ctrl. sockets failed<BR>
> 0(2958) init_mod(): Error while initializing module ctl<BR>
> ERROR: error while initializing modules<BR>
<BR>
I don't know which version and what config are included with the Ubuntu<BR>
package, but it looks at least a 2.0 version.<BR>
You probably don't need the fifo at all. You only need it if you have<BR>
some scripts for an older ser version. Just comment it out of the .cfg<BR>
and use sercmd to send runtime commands to ser.<BR>
<BR>
><BR>
> It seems that it starts ok but suddenly finds an error and stops.<BR>
<BR>
There is probably a problem with the fifo path in the .cfg.<BR>
<BR>
> However if I run:<BR>
><BR>
> cng@cng:/etc/ser$ sudo /etc/init.d/ser start<BR>
> Starting ser: serListening on<BR>
> udp: 127.0.0.1 [127.0.0.1]:5060<BR>
> udp: 10.1.3.207 [10.1.3.207]:5060<BR>
> udp: 192.168.50.10 [192.168.50.10]:5060<BR>
> tcp: 127.0.0.1 [127.0.0.1]:5060<BR>
> tcp: 10.1.3.207 [10.1.3.207]:5060<BR>
> tcp: 192.168.50.10 [192.168.50.10]:5060<BR>
> Aliases:<BR>
> tcp: cng.local:5060<BR>
> tcp: cng:5060<BR>
> tcp: localhost:5060<BR>
> udp: cng.local:5060<BR>
> udp: cng:5060<BR>
> udp: localhost:5060<BR>
><BR>
> 0(3016) init_tcp: using epoll_lt as the io watch method (auto detected)<BR>
> .<BR>
> 0(3018) unable to create pid file /var/run/ser/ser.pid: No such file or directory<BR>
><BR>
> It only complains about the ser.pid file.<BR>
><BR>
> I am a little bit confused. Where is the problem?<BR>
<BR>
Probably you don't have /var/run/ser (maybe it was not created<BR>
by the package) or there is some kind of permission problem.<BR>
Either mkdir /var/run/ser or start ser with -P /var/run/ser.pid.<BR>
<BR>
Andrei<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>