Re: error message

Addressed to: Beth Clark <elisaclark@earthlink.net> php-db@lists.php.net ** Reply to note from Beth Clark <elisaclark@earthlink.net> Sun, 13 Aug 2000 18:26:42 -0700 > > Hi, Rick - Thanks for your quick response to my post. I'm not really > sure if MySQL is running - > > I get this response from ps ax |grep mysqld > > ps ax | grep mysqld 2083 ? SW 0:00 [safe_mysqld] 24151 ? SWN 0:07 > [mysqld] 21536 ? SW 0:00 [safe_mysqld] 21553 ? SN 0:00 > /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql 21556 ? SN 0:00 > /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql 21557 ? SN 0:00 > /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql 7488 pts/5 S > 0:00 grep mysqld [1]+ Done safe_mysqld > > and a permission denied reply when I try safe_mysql & > > But I guess my biggest concern right now is what would cause MySQL to > stop running in the 1st place? Could it be malicious code or something > like that? If you have any insights, I sure would appreciate it. And > again, thanks for the help you've already extended. The ps tells me it is running. If it was dead you would only see your ps/grep command. (sometimes, but not always) Unless _you_ were messing with php configuration settings, or made changes to the params of your mysql_connect() call, I don't think you will be able to do much about this. You might want to try mysql -u usename -p where usename is the usename you have been given to access your database. This is a command line program to run MySQL queries. It will ask for your user password. If it lets you in try: use databasename; where databasename is the name of your database. You should then be able to type in queries against your database at the command line. Pretty much what you would enter into mysql_query(), only with a ; at the end of each query. Once you know if you can work from the mysql command line, tell your system adminstrator what you found. I don't think you will be able to do anything about this without rights to configure and restart both MySQL and Apache. My first thought is that either the socket has been deleted, or the permissions on the socket or its directory have changed. If not look at MySQL, Apache and PHP configuration. Most important - what was changed when it stopped working. I bet there was something... As far as MySQL reliability, the only thing that has killed my MySQL program so far is power failures. My last uptime was over 120 days, with over 250,000 connections... then someone bumped the power strip the server was plugged into. All I had to do was reboot the machine and restart the server. That was four days ago, and I'm up to 13,861 connections already, with no complaints or problems. Rick Widmer Internet Marketing Specialists www.developersdesk.com