Hi, In my case also, using serctl stop, gave the error pid file cannot be found....blah blah". And killing all running ser forked processes one by one is cumbersome. So the method I m using for the time being till I get a nice solutions is use the command killall /usr/local/sbin/ser , i.e the killall command is followed by the prog name along with the full path or the prog name only, depending upon where in the filesys you are standing right now.
I also found the following commands to be usful when viewing running ser processes -ps -auxmchf | grep ser -pstree -Gpn | grep ser : shows ser heirachy wise, (father and sons)
Regards Ashutosh
________________________________________ From: serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Hemant Patel (IP) Sent: Tuesday, August 09, 2005 8:23 PM To: serusers@lists.iptel.org Subject: [Serusers] starting and stopping ser
Hi List ,
This is my first install and use of ser so please bear with me.
I've installed ser 0.9.3 ( Linux i386 ) binary. Started and stopped ser with the default ser.cfg - fine. Amended ser.cfg to load mysql.so auth and auth_db modules as per standard instructions.
Mysql version is 4.0.18. I used 'mysql_sh' script to create default ser database and ser , serro users in mysql with default password. Checked that 'admin' user also setup on ser database with default password. Have set debug level 7 in ser.cfg to follow what goes on.
Logged in as normal user and then su as root
So here goes..
ser start - this seems to be ok. ser stop - seems to report ser has stopped ser start - connection to 127.0.0.1 already in use message ( ???)
So am I starting and stopping ser incorrectly ? What's the best way to start and stop ser - in a development environment ?
Any pointers gratefully received.
thanks