Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

A fresh install of MySQL on a 1and1 Windows Server 2008 R2 virtual server cannot start. The log gives:

130304 16:09:59 [Note] Plugin 'FEDERATED' is disabled.
130304 16:09:59  InnoDB: Initializing buffer pool, size = 686.0M
130304 16:10:00  InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file .\ibdata1 did not exist:
InnoDB: a new database to be created!
130304 16:10:00  InnoDB: Setting file .\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
130304 16:10:00  InnoDB: Log file .\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile0 size to 343 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100 200 300
130304 16:10:25  InnoDB: Log file .\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile1 size to 343 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100 200 300
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
130304 16:10:38  InnoDB: Started; log sequence number 0 0

The my.ini is the default one created:

[client]
port=3306
[mysql]
default-character-set=latin1
[mysqld]
port=3306
basedir="C:/Program Files/MySQL/MySQL Server 5.1/"
datadir="C:/ProgramData/MySQL/MySQL Server 5.1/Data/"
character-set-server=latin1
default-storage-engine=INNODB
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
max_connections=100
query_cache_size=0
table_cache=256
tmp_table_size=205M
thread_cache_size=8
myisam_max_sort_file_size=100G
myisam_sort_buffer_size=410M
key_buffer_size=354M
read_buffer_size=64K
read_rnd_buffer_size=256K
sort_buffer_size=256K
innodb_additional_mem_pool_size=15M
innodb_flush_log_at_trx_commit=1
innodb_log_buffer_size=7M
innodb_buffer_pool_size=686M
innodb_log_file_size=343M
innodb_thread_concurrency=10

netstat shows that mysqld is listening on 3306.

This server previously ran MySQL until a node crash killed the virtual server. Everything else appears functional.

Why isn't mysqld able to get itself to the "ready for connections" stage?

share|improve this question
    
Try setting log-warnings=1 in your my.ini, restart the service, and check the logs again. There's a chance that this will give you more information. By the way, which version of MySQL and which flavour? –  Alexander Janssen Mar 13 '13 at 9:26

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.