View Single Post
  #1   (View Single Post)  
Old 14th October 2008
disappearedng disappearedng is offline
Shell Scout
 
Join Date: May 2008
Posts: 128
Default MYSQL can't start "UNABLE TO LOCK

Hi everyone.
I can't start my mysqld for some reason. I am running mysql 5.16 on FreeBSD 7.0

this is the output of $cat /var/db/mysql/www.miuky.com.err
where www.miuky.com is my hostname

Code:
[root@www /var/db/mysql]# cat miuky.err 
081013 22:03:56 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
081013 22:03:56  InnoDB: Retrying to lock the first data file
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 35
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
081013 22:05:36  InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
081013 22:05:36  InnoDB: Operating system error number 35 in a file operation.
InnoDB: Error number 35 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data files, and it failed here,
InnoDB: you should now edit innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB only wrote those files full of
InnoDB: zeros, but did not yet use them in any way. But be careful: do not
InnoDB: remove old data files which contain your precious data!
081013 22:05:36 [ERROR] Plugin 'InnoDB' init function returned error.
081013 22:05:36 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
081013 22:05:36 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
081013 22:05:36 [ERROR] Do you already have another mysqld server running on port: 3306 ?
081013 22:05:36 [ERROR] Aborting

081013 22:05:36 [Note] /usr/local/libexec/mysqld: Shutdown complete

081013 22:05:36 mysqld_safe mysqld from pid file /var/db/mysql/miuky.pid ended
However, when I do a ps x | grep mysql, nothing shows up
infact, this is my ps -x
Code:
    0  ??  WLs    0:00.00 [swapper]
    1  ??  ILs    0:00.01 /sbin/init --
    2  ??  DL     0:00.41 [g_event]
    3  ??  DL     0:11.55 [g_up]
    4  ??  DL     0:12.58 [g_down]
    5  ??  DL     0:00.00 [kqueue taskq]
    6  ??  DL     0:00.00 [thread taskq]
    7  ??  DL     0:00.00 [mskc0 taskq]
    8  ??  DL     0:00.00 [sctp_iterator]
    9  ??  DL     0:00.77 [pagedaemon]
   10  ??  DL     0:00.00 [audit]
   11  ??  RL   230:17.85 [idle: cpu0]
   12  ??  WL     0:10.21 [swi4: clock]
   13  ??  WL     0:00.00 [swi3: vm]
   14  ??  WL     0:00.01 [swi1: net]
   15  ??  DL     0:01.99 [yarrow]
   16  ??  WL     0:00.00 [swi5: +]
   17  ??  WL     0:00.00 [swi6: Giant taskq]
   18  ??  WL     0:00.00 [swi6: task queue]
   19  ??  WL     0:21.52 [irq21: sis0]
   20  ??  WL     0:00.00 [irq16: pcm0 drm0]
   21  ??  WL     0:00.00 [irq14: ata0]
   22  ??  WL     0:00.00 [irq15: ata1]
   23  ??  WL     0:14.61 [irq17: atapci1]
   24  ??  WL     0:00.44 [irq1: atkbd0]
   25  ??  WL     0:11.52 [irq12: psm0]
   26  ??  DL     0:00.00 [vmdaemon]
   27  ??  DL     0:00.00 [pagezero]
   28  ??  DL     0:01.69 [bufdaemon]
   29  ??  DL     0:01.49 [vnlru]
   30  ??  DL     0:06.31 [syncer]
   31  ??  DL     0:01.55 [softdepflush]
   32  ??  DL     0:00.83 [schedcpu]
  176  ??  Is     0:00.00 adjkerntz -i
  508  ??  Is     0:00.00 /sbin/devd
  574  ??  Ss     0:00.03 /usr/sbin/syslogd -s
  594  ??  Ss     0:00.01 /usr/sbin/rpcbind
  639  ??  Is     0:00.00 /usr/sbin/mountd -r
  641  ??  Is     0:00.03 nfsd: master (nfsd)
  643  ??  S      0:23.82 nfsd: server (nfsd)
  644  ??  I      0:00.03 nfsd: server (nfsd)
  645  ??  I      0:00.00 nfsd: server (nfsd)
  646  ??  I      0:00.00 nfsd: server (nfsd)
  742  ??  Ss     0:16.69 /usr/sbin/moused -3 -p /dev/psm0 -t auto
  831  ??  Is     0:00.00 /usr/sbin/sshd
  837  ??  Ss     0:00.19 sendmail: accepting connections (sendmail)
  847  ??  Is     0:00.03 /usr/sbin/cron -s
  892  v0  Is     0:00.02 login [pam] (login)
 2182  v0  R      2:41.34 X :0 -auth /home/disappearedng/.serverauth.2163 (Xorg)
 2270  v0  I      0:00.03 gnome-pty-helper
  893  v1  Is+    0:00.00 /usr/libexec/getty Pc ttyv1
  894  v2  Is+    0:00.00 /usr/libexec/getty Pc ttyv2
  895  v3  Is+    0:00.00 /usr/libexec/getty Pc ttyv3
  896  v4  Is+    0:00.00 /usr/libexec/getty Pc ttyv4
  897  v5  Is+    0:00.00 /usr/libexec/getty Pc ttyv5
  898  v6  Is+    0:00.00 /usr/libexec/getty Pc ttyv6
  899  v7  Is+    0:00.00 /usr/libexec/getty Pc ttyv7
  343 con- I+     0:00.00 dhclient: sis0 [priv] (dhclient)
10327  p0  I      0:00.01 su
10328  p0  S      0:00.02 su (bash)
10598  p0  R+     0:00.00 ps x
What gives?

Last edited by disappearedng; 14th October 2008 at 02:07 AM.
Reply With Quote