[Kamailio-Devel] [ openser-Bugs-2096506 ] removing openser.pid from /var/run/

[SourceForge.net]

Bugs item #2096506, was opened at 2008-09-06 07:21
Message generated for change (Comment added) made by henningw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=2096506&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: tools
Group: ver 1.3.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Muhammad Akl (m-akl)
Assigned to: Nobody/Anonymous (nobody)
Summary: removing openser.pid from /var/run/

Initial Comment:
bug is found in versions : 1.2.2 , 1.3.3 respectively operationg system is Solaris 10

problem:

when starting openser either version 1.2.2 or 1.3.3 using 
/sbin/openserctl start or stop

 there is no problem and the server starts and stops working normally, but when starting it again it Complains that there is another process is already running although the server PID was killed,therefore it gives the following message : 

INFO:PID file exists (/var/run/openser.pid)! OpenSER already running?

solution :

i have edited the openserctl script , specifically the stop operation section to be like that :

openser_stop() {
	echo
	printf "Stopping OpenSER : "
	if [ -r $PID_FILE ] ; then
		kill `cat $PID_FILE`
		rm -f /var/run/openser.pid
                minfo "stopped"

just added the rm -f /var/run/openser.pid command and now everything starts to work without any problem, by the way i don't know it is the right way to do that but at least it works fine for me 



----------------------------------------------------------------------

>Comment By: Henning Westerholt (henningw)
Date: 2008-09-08 10:22

Message:
Logged In: YES 
user_id=337916
Originator: NO

Hi Muhammad,

thanks for the report. Normally in the cleanup function of the server the
old pid will be removed. If this not happens on Solaris 10 then perhaps the
server crashes on the cleanup? Then you'll get a core dump in the working
directory. Can you check in the log files if there if there goes something
wrong during the shutdown?

The message you get is also not critical, if you decrease the log level
above L_INFO then this will not show up at all in the log files.

Henning

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=2096506&group_id=139143