Dyntex.net Support Centre: MySQL Reference Manual p.97

<< previous page -- table of contents -- next page >>

Chapter_1

Chapter_2

Chapter_3

Chapter_4

Chapter_5

Return to Table of Contents

Table of Contents
1. General Information
2. MySQL Installation
3. Tutorial Introduction
4. Database Administration
5. MySQL Optimisation
6. MySQL Language Reference
7. MySQL Table Types
8. MySQL APIs
9. Extending MySQL

Chapter 2: MySQL Installation 97 as command-line arguments to mysqld. (These options can be used with safe_mysqld as well.) Normally you should need to tell mysqld only the base directory under which MySQL is installed. You can do this with the --basedir option. You can also use --help to check the eect of changing path options (note that --help must be the nal option of the mysqld command). For example: shell> EXECDIR/mysqld --basedir=/usr/local --help Once you determine the path settings you want, start the server without the --help option. Whichever method you use to start the server, if it fails to start up correctly, check the log le to see if you can nd out why. Log les are located in the data directory (typi- cally `/usr/local/mysql/data' for a binary distribution, `/usr/local/var' for a source distribution, and `\mysql\data\mysql.err' on Windows). Look in the data directory for les with names of the form `host_name.err' and `host_name.log' where host_name is the name of your server host. Then check the last few lines of these les: shell> tail host_name.err shell> tail host_name.log Look for something like the following in the log le: 000729 14:50:10 bdb: Recovery function for LSN 1 27595 failed 000729 14:50:10 bdb: warning: ./test/t1.db: No such file or directory 000729 14:50:10 Can't init databases This means that you didn't start mysqld with --bdb-no-recover and Berkeley DB found something wrong with its log les when it tried to recover your databases. To be able to continue, you should move away the old Berkeley DB log le from the database directory to some other place, where you can later examine it. The log les are named `log.0000000001', where the number will increase over time. If you are running mysqld with BDB table support and mysqld core dumps at start this could be because of some problems with the BDB recover log. In this case you can try starting mysqld with --bdb-no-recover. If this helps, then you should remove all `log.*' les from the data directory and try starting mysqld again. If you get the following error, it means that some other program (or another mysqld server) is already using the TCP/IP port or socket mysqld is trying to use: Can't start server: Bind on TCP/IP port: Address already in use or Can't start server : Bind on unix socket... Use ps to make sure that you don't have another mysqld server running. If you can't nd another server running, you can try to execute the command telnet your-host-name tcp-ip-port-number and press Enter a couple of times. If you don't get an error message like telnet: Unable to connect to remote host: Connection refused, something is us- ing the TCP/IP port mysqld is trying to use. See Section 2.4.1 [mysql install db], page 95 and Section 4.1.4 [Multiple servers], page 190. If mysqld is currently running, you can nd out what path settings it is using by executing this command: shell> mysqladmin variables or

MySQL Reference Manual

Our Partners

SpiritHost - web hosting for spiritual and education sites
SpiritHit.com - Religious and Spiritual Portal

Return to Table of Contents	Back to top

Web Hosting: Manuals & FAQ's

1. Unix-Based Web Hosting
2. Unix Dedicated Servers
3. Windows Dedicated Servers
4. CuteFTP User’s Guide
5. CuteHTML User’s Guide
6. WS_FTP Pro User's Guide
7. Miva Order User's Guide
8. Miva Merchant User's Guide