LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 01-18-2010, 01:59 AM   #1
mcnalu
Member
 
Registered: Dec 2006
Location: Glasgow, UK
Distribution: Slackware current
Posts: 423

Rep: Reputation: 73
mysql restarted problem


A machine running slackware 13 crashed and required a hard reset the other day. I'm not sure why this happened, but I suspect it was KDE4.2.4 or proprietary nvidia driver or X related.

It came back up fine except that these messages kept appearing on tty1:
Code:
Number of processes running now: 0
100118 07:03:50 mysqld restarted

Number of processes running now: 0
100118 07:03:50 mysqld restarted

Number of processes running now: 0
100118 07:03:51 mysqld restarted

Number of processes running now: 0
100118 07:03:51 mysqld restarted
A ps aux | grep mysql showed that mysqld and mysqld_safe were running, the latter presumably being started in this block in rc.mysqld:
Code:
  if [ -x /usr/bin/mysqld_safe ]; then
    # If there is an old PID file (no mysqld running), clean it up:
    if [ -r /var/run/mysql/mysql.pid ]; then
      if ! ps axc | grep mysqld 1> /dev/null 2> /dev/null ; then
        echo "Cleaning up old /var/run/mysql/mysql.pid."
        rm -f /var/run/mysql/mysql.pid
      fi
    fi
    /usr/bin/mysqld_safe --datadir=/var/lib/mysql --pid-file=/var/run/mysql/mysql.pid $SKIP &
  fi
My first guess was that a pid file had been left over after the crash, but I checked /var/run/mysql and it was empty. To stop the messages appearing I switched to another virtual terminal and did kill -9 on the /usr/bin/mysqld_safe process (normal kill didn't work). Running rc.mysqld start again produced the same messages.

I found this thread but I think that's another problem with the same symptom.

Any ideas on how to fix this?
 
Old 01-18-2010, 04:04 AM   #2
mcnalu
Member
 
Registered: Dec 2006
Location: Glasgow, UK
Distribution: Slackware current
Posts: 423

Original Poster
Rep: Reputation: 73
Should've checked the usual suspects. It seems that the root file system had filled up. Now i've cleared some space the problem is gone.

Edit: how do you mark a thread as [SOLVED] - just edit the title?

Last edited by mcnalu; 01-18-2010 at 04:14 AM.
 
Old 01-18-2010, 05:54 AM   #3
mRgOBLIN
Slackware Contributor
 
Registered: Jun 2002
Location: New Zealand
Distribution: Slackware
Posts: 999

Rep: Reputation: 231Reputation: 231Reputation: 231
It's in the thread tools
 
Old 05-27-2012, 08:09 AM   #4
kellogs
Member
 
Registered: Dec 2007
Location: romania
Distribution: mandriva 2010.1
Posts: 30

Rep: Reputation: 0
Smile

heh, I have had the same issue, how about that ?
I have left slow logging on so /var partition eventualy filled up

Thanks
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
No audio until X restarted raysr SUSE / openSUSE 0 03-26-2009 11:23 AM
" mysql restarted" messages on screen Ramonvel Red Hat 3 12-03-2007 05:22 PM
mysql: can't connect from remote since restarted! Shioni Linux - Server 1 12-06-2006 11:26 AM
New help restarted httpd oadvantage Linux - Newbie 2 09-10-2006 12:24 AM
Box restarted Sn7 Linux - Software 5 07-06-2004 01:08 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 09:50 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration