This is usually an indication that there was an error in the ser.cfg file.  If you look in the system messages log (/var/log/messages), it should give you more specific information about which error occurred.

N.


On Tue, 9 May 2006 14:00:49 +0700, Linh Pham wrote
> Hi, I compile SER 0.9.6 from source on a computer running Fedora Core 4.
> I suppose make all, make install all go well as I can't see any warning or error.
> When I start ser, it seems normal but I can't find the pid with ps.

> [root@localhost ~]# serctl start
>
> Starting SER : started pid(18726)
> [root@localhost ~]# ser
> Listening on
>              udp: 127.0.0.1 [127.0.0.1]:5060
>              udp: 192.168.1.4 [192.168.1.4]:5060
>              udp: 192.168.1.17 [192.168.1.17]:5060
>              tcp: 127.0.0.1 [127.0.0.1]:5060
>              tcp: 192.168.1.4 [192.168.1.4]:5060
>              tcp: 192.168.1.17 [192.168.1.17]:5060
> Aliases:
>              tcp: localhost:5060
>              tcp: localhost.localdomain:5060
>              udp: localhost:5060
>              udp: localhost.localdomain:5060
>
> [root@localhost ~]# serctl stop
> Stopping SER : /usr/local/sbin/serctl: line 813: kill: (18726) - No such processstopped
> [root@localhost ~]#
>
> How can I fix this so ser run normally?
> Thank you.
> --
> Best regards,
>
> Linh Pham