List:General Discussion« Previous MessageNext Message »
From:Paul DuBois Date:February 13 2009 7:51pm
Subject:Re: Install problem: log file issue
View as plain text  
On Feb 12, 2009, at 6:28 PM, csegovis@stripped wrote:

> Andy, Michael, and Walter - thank you!
>
> Adding a [mysqld_safe] group to my.cnf gets me further but the start
> still fails.  The good thing is that the failure is no longer due to  
> the
> inability to write the log file.  The [mysqld_safe] section of  
> my.cnf reads:
>
> [mysqld_safe]
> port            = 3306
> socket          = /tmp/mysql.sock
> skip-locking
> key_buffer = 16M
> max_allowed_packet = 1M
> table_cache = 64
> sort_buffer_size = 512K
> net_buffer_length = 8K
> read_buffer_size = 256K
> read_rnd_buffer_size = 512K
> myisam_sort_buffer_size = 8M
> datadir = /app/mysql/data
> #data_file_path = /app/mysql/data
> #log = /app/mysql/log/mysqld.log
> log-bin = /app/mysql/log/mysql-bin.log
> log-output = FILE
> general_log = 1
> general_log_file = /app/mysql/log/msyql_general.log
> socket = /app/mysql/var/mysql.sock
> log-error = /app/mysql/log/error.log
>
> Luckily, I now have an error log which reads:
>
> 090212 18:24:04 mysqld_safe Starting mysqld daemon with databases from
> /app/mysql/data
> InnoDB: Log scan progressed past the checkpoint lsn 0 39548
> 090212 18:24:04  InnoDB: Database was not shut down normally!
> InnoDB: Starting crash recovery.
> InnoDB: Reading tablespace information from the .ibd files...
> InnoDB: Restoring possible half-written data pages from the  
> doublewrite
> InnoDB: buffer...
> InnoDB: Doing recovery: scanned up to log sequence number 0 46409
> 090212 18:24:04  InnoDB: Starting an apply batch of log records to the
> database...
> InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
> 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41  
> 42
> 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65  
> 66
> 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89  
> 90
> 91 92 93 94 95 96 97 98 99
> InnoDB: Apply batch completed
> 090212 18:24:04  InnoDB: Started; log sequence number 0 46409
> 090212 18:24:04 [ERROR] /app/mysql/libexec/mysqld: Can't create/ 
> write to
> file '/var/run/mysqld/mysqld.pid' (Errcode: 2)
> 090212 18:24:04 [ERROR] Can't start server: can't create PID file: No
> such file or directory
> 090212 18:24:04 mysqld_safe mysqld from pid file
> /var/run/mysqld/mysqld.pid ended
>
> Now I need to figure out how to point PID file creation the  
> appropriate
> directory.


Sounds like you want:

pid-file = /app/mysql/log/mysql.pid

http://dev.mysql.com/doc/refman/5.1/en/server-options.html#option_mysqld_pid-file

-- 
Paul DuBois
Sun Microsystems / MySQL Documentation Team
Madison, Wisconsin, USA
www.mysql.com

Thread
Install problem: log file issuecsegovis@gmail.com12 Feb
  • Re: Install problem: log file issuefire912 Feb
    • Re: Install problem: log file issuecsegovis@gmail.com12 Feb
      • Re: Install problem: log file issueAndy Smith12 Feb
        • Re: Install problem: log file issuecsegovis@gmail.com12 Feb
          • Re: Install problem: log file issueWalter Heck12 Feb
            • Re: Install problem: log file issuecsegovis@gmail.com13 Feb
              • Re: Install problem: log file issuePaul DuBois13 Feb