[Serusers] serctl start|stop|restart

[Hernando Maisano]

Hello pardon that m puts in convesacion, to my happens to me the same, but 
single when I add in ser.cfg to I modulate "acc". Soon I raise with serctl 
start, says OK to me, but the port does not raise it and in logs I do not 
see anything. Somebody can help me?
 Excuse my Ingles, but I do not speak it well
 Thanks

Nando

----- Original Message ----- 
From: "seehoe yee" <seehoe at time.net.my>
To: "Marc Khayat" <marc at globalcarrier.net>
Cc: <serusers at lists.iptel.org>
Sent: Tuesday, August 09, 2005 11:40 AM
Subject: Re: [Serusers] serctl start|stop|restart


> ----- Original Message -----
> From: "Marc Khayat" <marc at globalcarrier.net>
> Date: Tuesday, August 9, 2005 9:00 pm
> Subject: [Serusers] serctl start|stop|restart
>
>> Hi all,
>> The first few times I do START STOP or RESTART, everything works fine.
>> But after that, it gives the following:
>> [root at linux ~]# serctl stop
>> Stopping SER : /usr/local/sbin/serctl: line 614: kill: (8771) - No
>> suchprocess
>> stopped
>> [root at linux ~]#
>> [root at linux ~]# serctl start
>>
>> Starting SER : PID file exists! (/var/run/ser.pid) already running?
>> [root at linux ~]#
>> [root at linux ~]# serctl restart
>> Stopping SER : /usr/local/sbin/serctl: line 627: kill: (8771) - No
>> suchprocess
>> stopped
>> Starting SER : PID file exists! (/var/run/ser.pid) already running?
>>
>
>> How can I solve it?
>>
>
> I've encounter this issue before, my previous encounter was caused by
> misconfiguration in 'ser.cfg'. I can't remember what was my configuration.
>
> If you have made any changes recently to ser.cfg. It could be the cause.
>
> To stop ser, kill /var/run/ser.pid then start again.
>
> seehoe
>
>
>
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers