Hello, Thanks for your answer. For a holidays issue, I will not be able to try this solution until January; but as soon as I can test it, I will answer with the result. Again, thanks. Regards, Rebeca Martinez -----Mensaje original----- De: Sabatella, Michael [mailto:Michael.Sabatella@ipc.com] Enviado el: mié 23/12/2009 14:46 Para: Martínez García, Rebeca; serusers(a)lists.iptel.org CC: Huertas García, Victor Asunto: RE: problems when starting ser This may help you: You need to create the fifo something like this I believe in the /tmp directory. mkfifo ser_fifo; chmod 777 rfifo From: serusers-bounces(a)lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of "Martínez García, Rebeca" Sent: Wednesday, December 23, 2009 7:06 AM To: serusers(a)lists.iptel.org Cc: "Huertas García, Victor" Subject: [Serusers] problems when starting ser Hello all, I have installed ser in Ubuntu Karmic by means of Synaptic without any problems or errors during the installation. 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"): cng@cng:/etc/ser$ ser D E Listening on udp: 127.0.0.1 [127.0.0.1]:5060 udp: 10.1.3.207 [10.1.3.207]:5060 udp: 192.168.50.10 [192.168.50.10]:5060 tcp: 127.0.0.1 [127.0.0.1]:5060 tcp: 10.1.3.207 [10.1.3.207]:5060 tcp: 192.168.50.10 [192.168.50.10]:5060 Aliases: tcp: cng.local:5060 tcp: cng:5060 tcp: localhost:5060 udp: cng.local:5060 udp: cng:5060 udp: localhost:5060 0(2956) init_tcp: using epoll_lt as the io watch method (auto detected) cng@cng:/etc/ser$ 0(2958) Maxfwd module- initializing 0(2958) ERROR: fifo_server.c:857: Can't create FIFO: No such file or directory (mode=384) 0(2958) ERROR: ctl: mod_init: init ctrl. sockets failed 0(2958) init_mod(): Error while initializing module ctl ERROR: error while initializing modules It seems that it starts ok but suddenly finds an error and stops. However if I run: cng@cng:/etc/ser$ sudo /etc/init.d/ser start Starting ser: serListening on udp: 127.0.0.1 [127.0.0.1]:5060 udp: 10.1.3.207 [10.1.3.207]:5060 udp: 192.168.50.10 [192.168.50.10]:5060 tcp: 127.0.0.1 [127.0.0.1]:5060 tcp: 10.1.3.207 [10.1.3.207]:5060 tcp: 192.168.50.10 [192.168.50.10]:5060 Aliases: tcp: cng.local:5060 tcp: cng:5060 tcp: localhost:5060 udp: cng.local:5060 udp: cng:5060 udp: localhost:5060 0(3016) init_tcp: using epoll_lt as the io watch method (auto detected) . 0(3018) unable to create pid file /var/run/ser/ser.pid: No such file or directory It only complains about the ser.pid file. I am a little bit confused. Where is the problem? Thanks in advance, Rebeca Martinez ________________________________ DISCLAIMER: This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail.E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered with without the knowledge of the sender or the intended recipient. If you are not comfortable with the risks associated with e-mail messages, you may decide not to use e-mail to communicate with IPC. IPC reserves the right, to the extent and under circumstances permitted by applicable law, to retain, monitor and intercept e-mail messages to and from its systems.

Hi all, First of all, answering to Andrei, yes the version I am using is 2.0. And, in fact, all the problems I have with SER are related to /var/run/ser. 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... I know that one possibility is to create it directly when calling SER, however I would like to make it survive the reboot. I though to make it immutable but I am not sure if it is the correct solution. Is there any other way? Thanks in advance, Rebeca Martinez -----Mensaje original----- De: Andrei Pelinescu-Onciul [mailto:andrei@iptel.org] Enviado el: mié 23/12/2009 21:32 Para: Martínez García, Rebeca CC: serusers(a)lists.iptel.org; Huertas García, Victor Asunto: Re: [Serusers] problems when starting ser On Dec 23, 2009 at 13:06, "Mart?nez Garc?a, Rebeca" <remartinez(a)indra.es> wrote: I don't know which version and what config are included with the Ubuntu package, but it looks at least a 2.0 version. You probably don't need the fifo at all. You only need it if you have some scripts for an older ser version. Just comment it out of the .cfg and use sercmd to send runtime commands to ser. There is probably a problem with the fifo path in the .cfg. Probably you don't have /var/run/ser (maybe it was not created by the package) or there is some kind of permission problem. Either mkdir /var/run/ser or start ser with -P /var/run/ser.pid. Andrei