Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14

Thread: Problem with MySQL after Fedora LAMP Install

  1. #11
    Join Date
    Mar 2009
    Posts
    9

    Default

    Hey guys,
    I seem to have more or less the same problem as Nate but pablasso's fix, running mysql(d) start (from etc/inet.d), gives me the following:

    [root@tuneburg init.d]# ./mysqld start
    Starting MySQL: [ OK ]
    touch: cannot touch `/var/lock/subsys/mysqld': No such file or directory

    I did as Andrew suggested and set up the levels with chkconfig and have mysqld on for levels 3 4 and 5.

    Any advice would be appreciated as I'm dead in the water without mySQL.

  2. #12
    Join Date
    Jun 2008
    Posts
    232

    Default

    Quote Originally Posted by faltschuler View Post
    [root@tuneburg init.d]# ./mysqld start
    Starting MySQL: [ OK ]
    touch: cannot touch `/var/lock/subsys/mysqld': No such file or directory
    I'd hazard a guess that the directory /var/lock/subsys doesn't exist.

    What does ls -ld /var/lock/subsys/ give you:
    Code:
    [bill@bell ~]$ ls -ld /var/lock/subsys/
    drwxr-xr-x 2 root root 4096 Mar 30 19:35 /var/lock/subsys/
    I admit it would be quite odd if it didn't exist, as that seems to be where all processes started from init record their running state.

  3. #13
    Join Date
    Apr 2009
    Posts
    1

    Default

    Quote Originally Posted by chriss View Post
    I'd hazard a guess that the directory /var/lock/subsys doesn't exist.

    What does ls -ld /var/lock/subsys/ give you:
    Code:
    [bill@bell ~]$ ls -ld /var/lock/subsys/
    drwxr-xr-x 2 root root 4096 Mar 30 19:35 /var/lock/subsys/
    I admit it would be quite odd if it didn't exist, as that seems to be where all processes started from init record their running state.
    Hello, I have the same "touch" problem with MySQL, I'm also running a Fedora LAMP installation, mysql seems to work fine, but I still get that touch error, not sure if it will cause me problems in the future:
    Code:
    [root@mepho mysql]# service mysqld restart
    Stopping MySQL:                                            [  OK  ]
    Starting MySQL:                                            [  OK  ]
    touch: cannot touch `/var/lock/subsys/mysqld': No such file or directory
    You mentioned it would be quite odd if that dir didn't exist.. well, here it's the output on my terminal:

    Code:
    [root@mepho mysql]# chkconfig --list|grep mysql
    mysqld          0:off 1:off    2:on  3:on       4:on    5:on    6:off
    [root@mepho mysql]# ls -ld /var/lock
    ls: cannot access /var/lock: No such file or directory
    [root@mepho mysql]# ls -ld /var/lock/subsys/
    ls: cannot access /var/lock/subsys/: No such file or directory
    Any ideas on why that dir doesn't exist in my box? (I honestly don't know what it is for.. but you made it sound important, so now I'm worried )

  4. #14
    Join Date
    Jun 2008
    Posts
    232

    Default

    Quote Originally Posted by Mephisto View Post
    Any ideas on why that dir doesn't exist in my box? (I honestly don't know what it is for.. but you made it sound important, so now I'm worried )
    I have no idea as to why it wouldn't exist, but it should be easy enough to create it and see if the error goes away.

    [edit]
    Here's a link I found through a quick google search that discusses the directory and its purpose http://www.redhat.com/magazine/008ju...s/tips_tricks/. Refer to the paragraph entitled Why do init scripts require lock files?.
    Last edited by chriss; 04-10-2009 at 11:51 AM. Reason: Add link to explanation of purpose of /var/lock/subsys/

Page 2 of 2 FirstFirst 12

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •