MySQL Bugs: #4262: mysqld does not load with my.ini

Bug #4262	mysqld does not load with my.ini
Submitted:	23 Jun 2004 18:46	Modified:	23 Jun 2004 21:12
Reporter:	ali mahani	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	4.0.20a	OS:	Windows (Windows XP)
Assigned to:		CPU Architecture:	Any

Description:
I hope that I am not asking a redundant question, I searched the bug database but could not fix my problem (btw I'm a novice):

I installed mysql recently as a service using mysqld-max-nt --install.
The server loaded automatically w/o any problems.

I added a my.ini file (@ c:\windows\) and then mysqld-max-nt does not load anymore. Neither the service at start-up nor if I install it as a standalone and try to run it manually.

Here are the contents of the my.ini:
[mysqld]
# binary logging, slow query logging
log-bin
log-slow-queries

#config for holding data and indexes
innodb_data_file_path = ibdata1:10M:autoextend

#buffer-pool size to 50-80% of memory
set-variable = innodb_buffer_pool_size=70M
set-variable = innodb_additional_mem_pool_size=10M

#log file size 25% of buffer pool size
set-variable = innodb_log_file_size=20M
set-variable = innodb_log_buffer_size=8M

#Set flush log at trx to 0 if you can afford it
innodb_flush_log_at_trx_commit=1

I tried to use the my.cnf at c:\ but a windows program uses this extension so I have to stick with the .ini file
I appreciate any help
Thanks, 
a.a.

How to repeat:
Install mysql as a service and then create manually a my.ini file in the windows directory, copy and paste the contents from the description and then restart the machine and (in my case) you'll see that mysqld-max-nt.exe is not loaded nor does it load through the cmd prompt or through services in the control panel

Suggested fix:
I don't know, I worked around it by removing my my.ini file.

Please try in prompt screen:

mysqld-nt --standalone --console

and verify for possible message error output.

I ran it and here's the output:

c:\mysql\bin>mysqld-nt --standalone --console
InnoDB: Error: log file .\ib_logfile0 is of different size 0 5242880 bytes
InnoDB: than specified in the .cnf file 0 20971520 bytes!
040623 10:29:46  Can't init databases
040623 10:29:46  Aborting

040623 10:29:46  InnoDB: Warning: shutting down a not properly started
                 InnoDB: or created database!
040623 10:29:46  mysqld-nt: Shutdown Complete

That means that when you did the first start, InnoDB created the default
size file and when you created the my.ini file you defined different
size.
The workaround is to delete all the current InnoDB's files and start
the server for InnoDB to create new ones according my.ini values.

This isn't a bug, just lack of knowledge on my part:
I tried to delete InnoDB as described in the ref-man.
I typed "mysqldump InnoDB -uroot -p***".
It gave me the following message:
mysqldump: Got error: 1049: Unknown database 'innodb' when selecting the databas
e

:) mysqldump tool isn't for to delete the InnodDB tablespace files.

When I said you for to delete these files is to use the Windows del
command see below:

C:\mysql\data>dir ib*
 O volume na unidade C não tem nome.
 O número de série do volume é 3C2A-26E8

 Pasta de C:\mysql\data

23/06/2004  14:24        10.485.760 ibdata1
23/06/2004  14:24        20.971.520 ib_logfile0
23/06/2004  14:19        20.971.520 ib_logfile1
               3 arquivo(s)     52.428.800 bytes
               0 pasta(s) 15.761.719.296 bytes disponíveis

C:\mysql\data>del ib*

C:\mysql\data>dir ib*
 O volume na unidade C não tem nome.
 O número de série do volume é 3C2A-26E8

 Pasta de C:\mysql\data

Arquivo não encontrado

Anyway this forum is for to report bugs, so I ask you for to read
the Manual, our online search, to subscribe in our Mail list:
http://dev.mysql.com/doc/mysql/en/Mailing-list.html which is
the appropriate forum for that kind of issue.

Thanks

Thank You So Much, I've been trying to solve this for a while. I will do as you told me and direct my questions to the mailing list. I just wanted to thank you:
Thanks
a.m.