I can"t start mysql from the windows command line

------=_NextPart_000_0099_01C5FCD9.0645FD00
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,

Mysql is running on Windows 98 SE.

With previous versions of mysql I can start mysql from the command line =
with:
C:\> C:Mysql\bin\mysqld

Now with version 5.0.16 this command don't start mysql and I can't use =
"net start ..." with windows 98.

The command C:\> C:Mysql\bin\mysqld --defaults-file=3D"..." don't start =
mysql.
All commands return : "[Error] Can't find messagefile 'C:\Program =
Files\MySQL\MySQL Server 5.0\share\english\errmsg.sys'"

I checked this file : errmsg.sys exists in C:\Program Files\MySQL\MySQL =
Server 5.0\share\english.

The same thing occurs if I add the MySQL path in Autoexec.bat.

thanks for your help.

NB: Here is my my.ini:

# MySQL Server Instance Configuration File
# ------------------------------------------------------------ ----------
# Generated by the MySQL Server Instance Configuration Wizard
#
#
# Installation Instructions
# ------------------------------------------------------------ ----------
#
# On Linux you can copy this file to /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
# (@localstatedir@ for this installation) or to
# ~/.my.cnf to set user-specific options.
#
# On Windows you should keep this file in the installation directory=20
# of your server (e.g. C:\Program Files\MySQL\MySQL Server 4.1). To
# make sure the server reads the config file use the startup option=20
# "--defaults-file".=20
#
# To run run the server from the command line, execute this in a=20
# command line shell, e.g.
# mysqld --defaults-file=3D"C:\Program Files\MySQL\MySQL Server =
4.1\my.ini"
#
# To install the server as a Windows service manually, execute this in a =

# command line shell, e.g.
# mysqld --install MySQL41 --defaults-file=3D"C:\Program =
Files\MySQL\MySQL Server 4.1\my.ini"
#
# And then execute this in a command line shell to start the server, =
e.g.
# net start MySQL41
#
#
# Guildlines for editing this file
# ------------------------------------------------------------ ----------
#
# In this file, you can use all long options that the program supports.
# If you want to know the options a program supports, start the program
# with the "--help" option.
#
# More detailed information about the individual options can also be
# found in the manual.
#
#
# CLIENT SECTION
# ------------------------------------------------------------ ----------
#
# The following options will be read by MySQL client applications.
# Note that only client applications shipped by MySQL are guaranteed
# to read this section. If you want your own MySQL client program to
# honor these values, you need to specify it as an option during the
# MySQL client library initialization.
#
[client]

port=3D3306

[mysql]

default-character-set=3Dlatin1


# SERVER SECTION
# ------------------------------------------------------------ ----------
#
# The following options will be read by the MySQL Server. Make sure that
# you have installed the server correctly (see above) so it reads this=20
# file.
#
[mysqld]

# The TCP/IP Port the MySQL Server will listen on
port=3D3306


#Path to installation directory. All paths are usually resolved relative =
to this.
basedir=3D"C:/Program Files/MySQL/MySQL Server 5.0/"

#Path to the database root
datadir=3D"C:/Program Files/MySQL/MySQL Server 5.0/Data/"

# The default character set that will be used when a new schema or table =
is
# created and no character set is defined
default-character-set=3Dlatin1

# The default storage engine that will be used when create new tables =
when
default-storage-engine=3DINNODB

# Set the SQL mode to strict
sql-mode=3D"STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGIN E_SUBSTITUTIO=
N"

# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections=3D100

# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# "Qcache_lowmem_prunes" status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.
query_cache_size=3D0

# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]
table_cache=3D256

# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.
tmp_table_size=3D5M


# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before. This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)
thread_cache_size=3D8

#*** MyISAM Specific options

# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).
myisam_max_sort_file_size=3D100G

# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_max_extra_sort_file_size=3D100G

# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_sort_buffer_size=3D8M

# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you're not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.
key_buffer_size=3D8M

# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
read_buffer_size=3D64K
read_rnd_buffer_size=3D256K

# This buffer is allocated when MySQL needs to rebuild the index in
# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
# into an empty table. It is allocated per thread so be careful with
# large settings.
sort_buffer_size=3D212K


#*** INNODB Specific options ***
innodb_data_home_dir=3D"c:/MySQL Datafiles/"

# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.
#skip-innodb

# Additional memory pool that is used by InnoDB to store metadata
# information. If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS. As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.
innodb_additional_mem_pool_size=3D2M

# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.
innodb_flush_log_at_trx_commit=3D1

# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).
innodb_log_buffer_size=3D1M

# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system. Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.
innodb_buffer_pool_size=3D8M

# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.
innodb_log_file_size=3D10M

# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.
innodb_thread_concurrency=3D8


Patrice
------=_NextPart_000_0099_01C5FCD9.0645FD00--

Re: I can"t start mysql from the windows command line

On 12/9/05, Patrice Serrand wrote:
> Hello,
>
> Mysql is running on Windows 98 SE.
>
> With previous versions of mysql I can start mysql from the command line w=
ith:
> C:\> C:Mysql\bin\mysqld
>
> Now with version 5.0.16 this command don't start mysql and I can't use "n=
et start ..." with windows 98.
>
> The command C:\> C:Mysql\bin\mysqld --defaults-file=3D"..." don't start m=
ysql.

The new versions of MySQL install at

%PROGRAMFILES/MySQL/MySQL Server X/

Not at C:\MySQL


> All commands return : "[Error] Can't find messagefile 'C:\Program Files\M=
ySQL\MySQL Server 5.0\share\english\errmsg.sys'"
>

You're probably trying to run an old version that its searching for
libraries and trying to use the new ones (not very good).


> I checked this file : errmsg.sys exists in C:\Program Files\MySQL\MySQL S=
erver 5.0\share\english.
>
> The same thing occurs if I add the MySQL path in Autoexec.bat.
>
> thanks for your help.
>
> NB: Here is my my.ini:
>

no useful info>


>
> Patrice
>

Try running:

"C:\Program Files\MySQL\MySQL Server 5\bin\mysqld.exe"

from command line...

If that fails, backup your data from the old mysql and remove any
traces from mysql on your system, follow the upgrade guide, there are
issues between versions.

If you never used or has no useful data on your mysql, remove it and
follow the install guide at the Manual.

--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org

Re: I can"t start mysql from the windows command line

I completely removed C:\mysql from my hard disk and the my.ini file in
C:\Windows. I used the mysql automated installer then the configuration
wizard.

The command C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld don't start
MySQL on Windows 98 SE.

This commands return : "[Error] Can't find messagefile 'C:\Program
Files\MySQL\MySQL Server 5.0\share\english\errmsg.sys'". (errmsg.sys exists
at that location).

(In other computer I installed this version (5.0.16) of MySQL on Windows XP.
I can run MySQL as a service. But I can't run it from the command line)


----- Original Message -----
From: "Daniel da Veiga"
To: "MySQL Win32 List"
Sent: Friday, December 09, 2005 4:09 PM
Subject: Re: I can't start mysql from the windows command line


On 12/9/05, Patrice Serrand wrote:
> Hello,
>
> Mysql is running on Windows 98 SE.
>
> With previous versions of mysql I can start mysql from the command line
> with:
> C:\> C:Mysql\bin\mysqld
>
> Now with version 5.0.16 this command don't start mysql and I can't use
> "net start ..." with windows 98.
>
> The command C:\> C:Mysql\bin\mysqld --defaults-file="..." don't start
> mysql.

The new versions of MySQL install at

%PROGRAMFILES/MySQL/MySQL Server X/

Not at C:\MySQL


> All commands return : "[Error] Can't find messagefile 'C:\Program
> Files\MySQL\MySQL Server 5.0\share\english\errmsg.sys'"
>

You're probably trying to run an old version that its searching for
libraries and trying to use the new ones (not very good).


> I checked this file : errmsg.sys exists in C:\Program Files\MySQL\MySQL
> Server 5.0\share\english.
>
> The same thing occurs if I add the MySQL path in Autoexec.bat.
>
> thanks for your help.
>
> NB: Here is my my.ini:
>

no useful info>


>
> Patrice
>

Try running:

"C:\Program Files\MySQL\MySQL Server 5\bin\mysqld.exe"

from command line...

If that fails, backup your data from the old mysql and remove any
traces from mysql on your system, follow the upgrade guide, there are
issues between versions.

If you never used or has no useful data on your mysql, remove it and
follow the install guide at the Manual.

--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe:
http://lists.mysql.com/win32?unsub=Patrice.Serrand@wanadoo.f r

------------------------------------------------------------ ---------------------------
Wanadoo vous informe que cet e-mail a ete controle par l'anti-virus mail.
Aucun virus connu a ce jour par nos services n'a ete detecte.







--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

Re: I can"t start mysql from the windows command line

Get the zipped version and install it by hand (first remove the one
you installed using the wizard). Follow the instructions on the manual
during install, you should have no problems. I really hate those .msi
packages...

On 12/9/05, Patrice Serrand wrote:
> I completely removed C:\mysql from my hard disk and the my.ini file in
> C:\Windows. I used the mysql automated installer then the configuration
> wizard.
>
> The command C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld don't star=
t
> MySQL on Windows 98 SE.
>
> This commands return : "[Error] Can't find messagefile 'C:\Program
> Files\MySQL\MySQL Server 5.0\share\english\errmsg.sys'". (errmsg.sys exis=
ts
> at that location).
>
> (In other computer I installed this version (5.0.16) of MySQL on Windows =
XP.
> I can run MySQL as a service. But I can't run it from the command line)
>
>
> ----- Original Message -----
> From: "Daniel da Veiga"
> To: "MySQL Win32 List"
> Sent: Friday, December 09, 2005 4:09 PM
> Subject: Re: I can't start mysql from the windows command line
>
>
> On 12/9/05, Patrice Serrand wrote:
> > Hello,
> >
> > Mysql is running on Windows 98 SE.
> >
> > With previous versions of mysql I can start mysql from the command line
> > with:
> > C:\> C:Mysql\bin\mysqld
> >
> > Now with version 5.0.16 this command don't start mysql and I can't use
> > "net start ..." with windows 98.
> >
> > The command C:\> C:Mysql\bin\mysqld --defaults-file=3D"..." don't start
> > mysql.
>
> The new versions of MySQL install at
>
> %PROGRAMFILES/MySQL/MySQL Server X/
>
> Not at C:\MySQL
>
>
> > All commands return : "[Error] Can't find messagefile 'C:\Program
> > Files\MySQL\MySQL Server 5.0\share\english\errmsg.sys'"
> >
>
> You're probably trying to run an old version that its searching for
> libraries and trying to use the new ones (not very good).
>
>
> > I checked this file : errmsg.sys exists in C:\Program Files\MySQL\MySQL
> > Server 5.0\share\english.
> >
> > The same thing occurs if I add the MySQL path in Autoexec.bat.
> >
> > thanks for your help.
> >
> > NB: Here is my my.ini:
> >
>
> > no useful info>
>
>
> >
> > Patrice
> >
>
> Try running:
>
> "C:\Program Files\MySQL\MySQL Server 5\bin\mysqld.exe"
>
> from command line...
>
> If that fails, backup your data from the old mysql and remove any
> traces from mysql on your system, follow the upgrade guide, there are
> issues between versions.
>
> If you never used or has no useful data on your mysql, remove it and
> follow the install guide at the Manual.
>
> --
> Daniel da Veiga
> Computer Operator - RS - Brazil
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.1
> GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
> PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
> ------END GEEK CODE BLOCK------
>
> --
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe:
> http://lists.mysql.com/win32?unsub=3DPatrice.Serrand@wanadoo .fr
>
> ------------------------------------------------------------ -------------=
--------------
> Wanadoo vous informe que cet e-mail a ete controle par l'anti-virus mail=
..
> Aucun virus connu a ce jour par nos services n'a ete detecte.
>
>
>
>
>
>
>


--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org

Problems starting from the command line using 5.0.16

------=_NextPart_000_0008_01C5FE7E.A1400930
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Here is a blow-by-blow account....

1. downloaded Essentials package and installed.

selections from Config Wizard were:
Configration Type: Detailed Configuration
Server Type: Developer machine
Usage Type: Multifunctional Database (includes =
Innodb)

Outcome: the server did not start=20
(also tried mysqld-nt from command line and =
found that Innodb=20
had crashed/aborted)

2. uninstalled Mysql 5.0 and deleted mysql50 in Program Files - =
reinstalled

selections from Config Wizard were same except:
Usage Type: Non-Transactional Database (does not =
include Innodb)

Outcome: server starts, but when running mysql/mysqlshow from =
command
line I got message 'ERROR 1045 <28000> =
Access denied=20
for user 'ODBC'@'localhost (using password =
NO)

3. uninstalled Mysql 5.0 and deleted mysql50 in Program Files - =
reinstalled=20

selection from Config Wizard were:
Configration Type: Standard Configuration

Outcome : same as 2 above.
Here is the content of the log for attempt 3:

'InnoDB: The first specified data file .\ibdata1 did not exist:
InnoDB: a new database to be created!
051211 17:18:08 InnoDB: Setting file .\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
051211 17:18:10 InnoDB: Log file .\ib_logfile0 did not exist: new to be =
created
InnoDB: Setting log file .\ib_logfile0 size to 10 MB
InnoDB: Database physically writes the file full: wait...
051211 17:18:12 InnoDB: Log file .\ib_logfile1 did not exist: new to be =
created
InnoDB: Setting log file .\ib_logfile1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
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
051211 17:18:17 InnoDB: Started; log sequence number 0 0
051211 17:18:25 [Note] C:\Program Files\MySQL\MySQL Server =
5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.16-nt' socket: '' port: 3306 Official MySQL binary'

from which it would appear that InnooDB started OK.

What might be the problem?

I am totally stuck, so would appreciate advice.

Best regards
Ken Resander




------=_NextPart_000_0008_01C5FE7E.A1400930--

Re: Problems starting from the command line using 5.0.16

Hello.

It seems that your server is doing fine.
As your log said, your server is good and ready for connections.

When you try to connect to mysql on windows and don´t inform
a user name mysql use the default user ODBC. That´s because
you got the permission denied error on one of your tries.

When you install mysql on windows (and all others OS) a user
named root without a password is configured.

I think you already have a server running on your machine.
Your just need to connect to it.
Open your command line prompt and type 'mysql -u root' (without
apostrofes),
(on mysql bin directory 'C:\Program Files\MySQL\MySQL Server 5.0\bin'
because i think it is not on your path).

Or use your prefered windows client for mysql to connect to server.
Just remember that user is root and the password is empty.

After connected remember to set some password to your root account.

Good luck.


Richard AB.

----- Original Message -----
From: "Ken Resander"
To:
Sent: Sunday, December 11, 2005 7:13 AM
Subject: Problems starting from the command line using 5.0.16


Here is a blow-by-blow account....

1. downloaded Essentials package and installed.

selections from Config Wizard were:
Configration Type: Detailed Configuration
Server Type: Developer machine
Usage Type: Multifunctional Database (includes Innodb)

Outcome: the server did not start
(also tried mysqld-nt from command line and found
that Innodb
had crashed/aborted)

2. uninstalled Mysql 5.0 and deleted mysql50 in Program Files -
reinstalled

selections from Config Wizard were same except:
Usage Type: Non-Transactional Database (does not include
Innodb)

Outcome: server starts, but when running mysql/mysqlshow from
command
line I got message 'ERROR 1045 <28000> Access
denied
for user 'ODBC'@'localhost (using password NO)

3. uninstalled Mysql 5.0 and deleted mysql50 in Program Files -
reinstalled

selection from Config Wizard were:
Configration Type: Standard Configuration

Outcome : same as 2 above.
Here is the content of the log for attempt 3:

'InnoDB: The first specified data file .\ibdata1 did not exist:
InnoDB: a new database to be created!
051211 17:18:08 InnoDB: Setting file .\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
051211 17:18:10 InnoDB: Log file .\ib_logfile0 did not exist: new to be
created
InnoDB: Setting log file .\ib_logfile0 size to 10 MB
InnoDB: Database physically writes the file full: wait...
051211 17:18:12 InnoDB: Log file .\ib_logfile1 did not exist: new to be
created
InnoDB: Setting log file .\ib_logfile1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
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
051211 17:18:17 InnoDB: Started; log sequence number 0 0
051211 17:18:25 [Note] C:\Program Files\MySQL\MySQL Server
5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.16-nt' socket: '' port: 3306 Official MySQL binary'

from which it would appear that InnooDB started OK.

What might be the problem?

I am totally stuck, so would appreciate advice.

Best regards
Ken Resander






------------------------------------------------------------ --------------------


No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.13.12/194 - Release Date: 07/12/2005



--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.13.13/197 - Release Date: 09/12/2005


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

RE: I can"t start mysql from the windows command line

You probably should be running
C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld =
--defaults-file=3D"..."

Do you have two versions of MySQL installed in different places?

You seem to be running some things from C:\MySQL and others from
C:\Program Files\MySQL.

John B.

-----Original Message-----
From: Patrice Serrand [mailto:Patrice.Serrand@wanadoo.fr]=20
Sent: Saturday, 10 December 2005 1:26 AM
To: win32@lists.mysql.com
Subject: I can't start mysql from the windows command line

Hello,

Mysql is running on Windows 98 SE.

With previous versions of mysql I can start mysql from the command line
with:
C:\> C:Mysql\bin\mysqld

Now with version 5.0.16 this command don't start mysql and I can't use
"net start ..." with windows 98.

The command C:\> C:Mysql\bin\mysqld --defaults-file=3D"..." don't start
mysql.
All commands return : "[Error] Can't find messagefile 'C:\Program
Files\MySQL\MySQL Server 5.0\share\english\errmsg.sys'"

I checked this file : errmsg.sys exists in C:\Program Files\MySQL\MySQL
Server 5.0\share\english.

The same thing occurs if I add the MySQL path in Autoexec.bat.

thanks for your help.

NB: Here is my my.ini:

# MySQL Server Instance Configuration File
# ------------------------------------------------------------ ----------
# Generated by the MySQL Server Instance Configuration Wizard
#
#
# Installation Instructions
# ------------------------------------------------------------ ----------
#
# On Linux you can copy this file to /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
# (@localstatedir@ for this installation) or to
# ~/.my.cnf to set user-specific options.
#
# On Windows you should keep this file in the installation directory=20
# of your server (e.g. C:\Program Files\MySQL\MySQL Server 4.1). To
# make sure the server reads the config file use the startup option=20
# "--defaults-file".=20
#
# To run run the server from the command line, execute this in a=20
# command line shell, e.g.
# mysqld --defaults-file=3D"C:\Program Files\MySQL\MySQL Server
4.1\my.ini"
#
# To install the server as a Windows service manually, execute this in a

# command line shell, e.g.
# mysqld --install MySQL41 --defaults-file=3D"C:\Program =
Files\MySQL\MySQL
Server 4.1\my.ini"
#
# And then execute this in a command line shell to start the server,
e.g.
# net start MySQL41
#
#
# Guildlines for editing this file
# ------------------------------------------------------------ ----------
#
# In this file, you can use all long options that the program supports.
# If you want to know the options a program supports, start the program
# with the "--help" option.
#
# More detailed information about the individual options can also be
# found in the manual.
#
#
# CLIENT SECTION
# ------------------------------------------------------------ ----------
#
# The following options will be read by MySQL client applications.
# Note that only client applications shipped by MySQL are guaranteed
# to read this section. If you want your own MySQL client program to
# honor these values, you need to specify it as an option during the
# MySQL client library initialization.
#
[client]

port=3D3306

[mysql]

default-character-set=3Dlatin1


# SERVER SECTION
# ------------------------------------------------------------ ----------
#
# The following options will be read by the MySQL Server. Make sure that
# you have installed the server correctly (see above) so it reads this=20
# file.
#
[mysqld]

# The TCP/IP Port the MySQL Server will listen on
port=3D3306


#Path to installation directory. All paths are usually resolved relative
to this.
basedir=3D"C:/Program Files/MySQL/MySQL Server 5.0/"

#Path to the database root
datadir=3D"C:/Program Files/MySQL/MySQL Server 5.0/Data/"

# The default character set that will be used when a new schema or table
is
# created and no character set is defined
default-character-set=3Dlatin1

# The default storage engine that will be used when create new tables
when
default-storage-engine=3DINNODB

# Set the SQL mode to strict
sql-mode=3D"STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGIN E_SUBSTITUTIO=
N
"

# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections=3D100

# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# "Qcache_lowmem_prunes" status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.
query_cache_size=3D0

# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]
table_cache=3D256

# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.
tmp_table_size=3D5M


# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before. This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)
thread_cache_size=3D8

#*** MyISAM Specific options

# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).
myisam_max_sort_file_size=3D100G

# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_max_extra_sort_file_size=3D100G

# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_sort_buffer_size=3D8M

# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you're not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.
key_buffer_size=3D8M

# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
read_buffer_size=3D64K
read_rnd_buffer_size=3D256K

# This buffer is allocated when MySQL needs to rebuild the index in
# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
# into an empty table. It is allocated per thread so be careful with
# large settings.
sort_buffer_size=3D212K


#*** INNODB Specific options ***
innodb_data_home_dir=3D"c:/MySQL Datafiles/"

# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.
#skip-innodb

# Additional memory pool that is used by InnoDB to store metadata
# information. If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS. As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.
innodb_additional_mem_pool_size=3D2M

# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.
innodb_flush_log_at_trx_commit=3D1

# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).
innodb_log_buffer_size=3D1M

# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system. Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.
innodb_buffer_pool_size=3D8M

# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.
innodb_log_file_size=3D10M

# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.
innodb_thread_concurrency=3D8


Patrice

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org

Re: I can"t start mysql from the windows command line

Now running Windows 98 SE :

As suggested I got the zipped version of MySQL 5.0.16.

Like Ken Resander:

I completely removed all occurence of MySQL from my hard disk.
Scan the whole disk to find all remaining occurence oh my.ini -
libmySQL.dll - mysql*.* : none found
I removed the registry key : HKEY_LOCAL_MACHINE\SOFTWARE\MySQL AB

I installed mysql 5.0.16 from "mysql-noinstall-5.0.16-win32.zip" in C:\mysql

new ini file my.ini in c:\windows with correct path to myqsl and data

tried mysqld from command line :
The server don't start and this message appear:
"[Error] Can't find messagefile 'C:\mysql\share\english\errmsg.sys'"

I checked this file : errmsg.sys exists in
C:\mysql\share\english\errmsg.sys.

Note: Installation on a computer which never had mysql on the hard disk and
installation at "C:\Program Files\MySQL\MySQL Server 5.0" had the same
outcome : the server did not start from the command line

----- Original Message -----
From:
To: ;
Sent: Sunday, December 11, 2005 10:37 PM
Subject: RE: I can't start mysql from the windows command line


You probably should be running
C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld --defaults-file="..."

Do you have two versions of MySQL installed in different places?

You seem to be running some things from C:\MySQL and others from
C:\Program Files\MySQL.

John B.

-----Original Message-----
From: Patrice Serrand [mailto:Patrice.Serrand@wanadoo.fr]
Sent: Saturday, 10 December 2005 1:26 AM
To: win32@lists.mysql.com
Subject: I can't start mysql from the windows command line

Hello,

Mysql is running on Windows 98 SE.

With previous versions of mysql I can start mysql from the command line
with:
C:\> C:Mysql\bin\mysqld

Now with version 5.0.16 this command don't start mysql and I can't use
"net start ..." with windows 98.

The command C:\> C:Mysql\bin\mysqld --defaults-file="..." don't start
mysql.
All commands return : "[Error] Can't find messagefile 'C:\Program
Files\MySQL\MySQL Server 5.0\share\english\errmsg.sys'"

I checked this file : errmsg.sys exists in C:\Program Files\MySQL\MySQL
Server 5.0\share\english.

The same thing occurs if I add the MySQL path in Autoexec.bat.

thanks for your help.

NB: Here is my my.ini:

# MySQL Server Instance Configuration File
# ------------------------------------------------------------ ----------
# Generated by the MySQL Server Instance Configuration Wizard
#
#
# Installation Instructions
# ------------------------------------------------------------ ----------
#
# On Linux you can copy this file to /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
# (@localstatedir@ for this installation) or to
# ~/.my.cnf to set user-specific options.
#
# On Windows you should keep this file in the installation directory
# of your server (e.g. C:\Program Files\MySQL\MySQL Server 4.1). To
# make sure the server reads the config file use the startup option
# "--defaults-file".
#
# To run run the server from the command line, execute this in a
# command line shell, e.g.
# mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server
4.1\my.ini"
#
# To install the server as a Windows service manually, execute this in a

# command line shell, e.g.
# mysqld --install MySQL41 --defaults-file="C:\Program Files\MySQL\MySQL
Server 4.1\my.ini"
#
# And then execute this in a command line shell to start the server,
e.g.
# net start MySQL41
#
#
# Guildlines for editing this file
# ------------------------------------------------------------ ----------
#
# In this file, you can use all long options that the program supports.
# If you want to know the options a program supports, start the program
# with the "--help" option.
#
# More detailed information about the individual options can also be
# found in the manual.
#
#
# CLIENT SECTION
# ------------------------------------------------------------ ----------
#
# The following options will be read by MySQL client applications.
# Note that only client applications shipped by MySQL are guaranteed
# to read this section. If you want your own MySQL client program to
# honor these values, you need to specify it as an option during the
# MySQL client library initialization.
#
[client]

port=3306

[mysql]

default-character-set=latin1


# SERVER SECTION
# ------------------------------------------------------------ ----------
#
# The following options will be read by the MySQL Server. Make sure that
# you have installed the server correctly (see above) so it reads this
# file.
#
[mysqld]

# The TCP/IP Port the MySQL Server will listen on
port=3306


#Path to installation directory. All paths are usually resolved relative
to this.
basedir="C:/Program Files/MySQL/MySQL Server 5.0/"

#Path to the database root
datadir="C:/Program Files/MySQL/MySQL Server 5.0/Data/"

# The default character set that will be used when a new schema or table
is
# created and no character set is defined
default-character-set=latin1

# The default storage engine that will be used when create new tables
when
default-storage-engine=INNODB

# Set the SQL mode to strict
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_ SUBSTITUTION
"

# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections=100

# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# "Qcache_lowmem_prunes" status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.
query_cache_size=0

# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]
table_cache=256

# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.
tmp_table_size=5M


# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before. This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)
thread_cache_size=8

#*** MyISAM Specific options

# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).
myisam_max_sort_file_size=100G

# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_max_extra_sort_file_size=100G

# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_sort_buffer_size=8M

# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you're not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.
key_buffer_size=8M

# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
read_buffer_size=64K
read_rnd_buffer_size=256K

# This buffer is allocated when MySQL needs to rebuild the index in
# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
# into an empty table. It is allocated per thread so be careful with
# large settings.
sort_buffer_size=212K


#*** INNODB Specific options ***
innodb_data_home_dir="c:/MySQL Datafiles/"

# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.
#skip-innodb

# Additional memory pool that is used by InnoDB to store metadata
# information. If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS. As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.
innodb_additional_mem_pool_size=2M

# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.
innodb_flush_log_at_trx_commit=1

# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).
innodb_log_buffer_size=1M

# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system. Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.
innodb_buffer_pool_size=8M

# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.
innodb_log_file_size=10M

# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.
innodb_thread_concurrency=8


Patrice
------------------------------------------------------------ ---------------------------
Wanadoo vous informe que cet e-mail a ete controle par l'anti-virus mail.
Aucun virus connu a ce jour par nos services n'a ete detecte.







--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

Re: I can"t start mysql from the windows command line

On 12/12/05, Patrice Serrand wrote:
> Now running Windows 98 SE :
>
> As suggested I got the zipped version of MySQL 5.0.16.
>
> Like Ken Resander:
>
> I completely removed all occurence of MySQL from my hard disk.
> Scan the whole disk to find all remaining occurence oh my.ini -

Check for C:\my.cnf too. Try starting the server with the option
"--defaults-file=3Dfile_name" and point it to a config file written
following the instructions at:

http://dev.mysql.com/doc/refman/5.0/en/windows-create-option -file.html

And see if it solves your problem.

> libmySQL.dll - mysql*.* : none found
> I removed the registry key : HKEY_LOCAL_MACHINE\SOFTWARE\MySQL AB
>
> I installed mysql 5.0.16 from "mysql-noinstall-5.0.16-win32.zip" in C:\my=
sql
>
> new ini file my.ini in c:\windows with correct path to myqsl and data

Check if ALL the files were extracted correctly, some users reported
bad extraction by using strange decompress software and it caused the
error you're getting.

>
> tried mysqld from command line :
> The server don't start and this message appear:
> "[Error] Can't find messagefile 'C:\mysql\share\english\errmsg.sys'"
>
> I checked this file : errmsg.sys exists in
> C:\mysql\share\english\errmsg.sys.
>

There must be a reason for it. Check this thread:
http://forums.mysql.com/read.php?11,20418,57289#msg-57289

> Note: Installation on a computer which never had mysql on the hard disk a=
nd
> installation at "C:\Program Files\MySQL\MySQL Server 5.0" had the same
> outcome : the server did not start from the command line
>
> ----- Original Message -----
> From:
> To: ;
> Sent: Sunday, December 11, 2005 10:37 PM
> Subject: RE: I can't start mysql from the windows command line
>
>
> You probably should be running
> C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld --defaults-file=3D"...=
"
>
> Do you have two versions of MySQL installed in different places?
>
> You seem to be running some things from C:\MySQL and others from
> C:\Program Files\MySQL.
>
> John B.
>
> -----Original Message-----
> From: Patrice Serrand [mailto:Patrice.Serrand@wanadoo.fr]
> Sent: Saturday, 10 December 2005 1:26 AM
> To: win32@lists.mysql.com
> Subject: I can't start mysql from the windows command line
>
> Hello,
>
> Mysql is running on Windows 98 SE.
>
> With previous versions of mysql I can start mysql from the command line
> with:
> C:\> C:Mysql\bin\mysqld
>
> Now with version 5.0.16 this command don't start mysql and I can't use
> "net start ..." with windows 98.
>
> The command C:\> C:Mysql\bin\mysqld --defaults-file=3D"..." don't start
> mysql.
> All commands return : "[Error] Can't find messagefile 'C:\Program
> Files\MySQL\MySQL Server 5.0\share\english\errmsg.sys'"
>
> I checked this file : errmsg.sys exists in C:\Program Files\MySQL\MySQL
> Server 5.0\share\english.
>
> The same thing occurs if I add the MySQL path in Autoexec.bat.
>
> thanks for your help.
>
> NB: Here is my my.ini:
>
> # MySQL Server Instance Configuration File
> # ------------------------------------------------------------ ----------
> # Generated by the MySQL Server Instance Configuration Wizard
> #
> #
> # Installation Instructions
> # ------------------------------------------------------------ ----------
> #
> # On Linux you can copy this file to /etc/my.cnf to set global options,
> # mysql-data-dir/my.cnf to set server-specific options
> # (@localstatedir@ for this installation) or to
> # ~/.my.cnf to set user-specific options.
> #
> # On Windows you should keep this file in the installation directory
> # of your server (e.g. C:\Program Files\MySQL\MySQL Server 4.1). To
> # make sure the server reads the config file use the startup option
> # "--defaults-file".
> #
> # To run run the server from the command line, execute this in a
> # command line shell, e.g.
> # mysqld --defaults-file=3D"C:\Program Files\MySQL\MySQL Server
> 4.1\my.ini"
> #
> # To install the server as a Windows service manually, execute this in a
>
> # command line shell, e.g.
> # mysqld --install MySQL41 --defaults-file=3D"C:\Program Files\MySQL\MySQ=
L
> Server 4.1\my.ini"
> #
> # And then execute this in a command line shell to start the server,
> e.g.
> # net start MySQL41
> #
> #
> # Guildlines for editing this file
> # ------------------------------------------------------------ ----------
> #
> # In this file, you can use all long options that the program supports.
> # If you want to know the options a program supports, start the program
> # with the "--help" option.
> #
> # More detailed information about the individual options can also be
> # found in the manual.
> #
> #
> # CLIENT SECTION
> # ------------------------------------------------------------ ----------
> #
> # The following options will be read by MySQL client applications.
> # Note that only client applications shipped by MySQL are guaranteed
> # to read this section. If you want your own MySQL client program to
> # honor these values, you need to specify it as an option during the
> # MySQL client library initialization.
> #
> [client]
>
> port=3D3306
>
> [mysql]
>
> default-character-set=3Dlatin1
>
>
> # SERVER SECTION
> # ------------------------------------------------------------ ----------
> #
> # The following options will be read by the MySQL Server. Make sure that
> # you have installed the server correctly (see above) so it reads this
> # file.
> #
> [mysqld]
>
> # The TCP/IP Port the MySQL Server will listen on
> port=3D3306
>
>
> #Path to installation directory. All paths are usually resolved relative
> to this.
> basedir=3D"C:/Program Files/MySQL/MySQL Server 5.0/"
>
> #Path to the database root
> datadir=3D"C:/Program Files/MySQL/MySQL Server 5.0/Data/"
>
> # The default character set that will be used when a new schema or table
> is
> # created and no character set is defined
> default-character-set=3Dlatin1
>
> # The default storage engine that will be used when create new tables
> when
> default-storage-engine=3DINNODB
>
> # Set the SQL mode to strict
> sql-mode=3D"STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGIN E_SUBSTITUTIO=
N
> "
>
> # The maximum amount of concurrent sessions the MySQL server will
> # allow. One of these connections will be reserved for a user with
> # SUPER privileges to allow the administrator to login even if the
> # connection limit has been reached.
> max_connections=3D100
>
> # Query cache is used to cache SELECT results and later return them
> # without actual executing the same query once again. Having the query
> # cache enabled may result in significant speed improvements, if your
> # have a lot of identical queries and rarely changing tables. See the
> # "Qcache_lowmem_prunes" status variable to check if the current value
> # is high enough for your load.
> # Note: In case your tables change very often or if your queries are
> # textually different every time, the query cache may result in a
> # slowdown instead of a performance improvement.
> query_cache_size=3D0
>
> # The number of open tables for all threads. Increasing this value
> # increases the number of file descriptors that mysqld requires.
> # Therefore you have to make sure to set the amount of open files
> # allowed to at least 4096 in the variable "open-files-limit" in
> # section [mysqld_safe]
> table_cache=3D256
>
> # Maximum size for internal (in-memory) temporary tables. If a table
> # grows larger than this value, it is automatically converted to disk
> # based table This limitation is for a single table. There can be many
> # of them.
> tmp_table_size=3D5M
>
>
> # How many threads we should keep in a cache for reuse. When a client
> # disconnects, the client's threads are put in the cache if there aren't
> # more than thread_cache_size threads from before. This greatly reduces
> # the amount of thread creations needed if you have a lot of new
> # connections. (Normally this doesn't give a notable performance
> # improvement if you have a good thread implementation.)
> thread_cache_size=3D8
>
> #*** MyISAM Specific options
>
> # The maximum size of the temporary file MySQL is allowed to use while
> # recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
> # If the file-size would be bigger than this, the index will be created
> # through the key cache (which is slower).
> myisam_max_sort_file_size=3D100G
>
> # If the temporary file used for fast index creation would be bigger
> # than using the key cache by the amount specified here, then prefer the
> # key cache method. This is mainly used to force long character keys in
> # large tables to use the slower key cache method to create the index.
> myisam_max_extra_sort_file_size=3D100G
>
> # If the temporary file used for fast index creation would be bigger
> # than using the key cache by the amount specified here, then prefer the
> # key cache method. This is mainly used to force long character keys in
> # large tables to use the slower key cache method to create the index.
> myisam_sort_buffer_size=3D8M
>
> # Size of the Key Buffer, used to cache index blocks for MyISAM tables.
> # Do not set it larger than 30% of your available memory, as some memory
> # is also required by the OS to cache rows. Even if you're not using
> # MyISAM tables, you should still set it to 8-64M as it will also be
> # used for internal temporary disk tables.
> key_buffer_size=3D8M
>
> # Size of the buffer used for doing full table scans of MyISAM tables.
> # Allocated per thread, if a full scan is needed.
> read_buffer_size=3D64K
> read_rnd_buffer_size=3D256K
>
> # This buffer is allocated when MySQL needs to rebuild the index in
> # REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
> # into an empty table. It is allocated per thread so be careful with
> # large settings.
> sort_buffer_size=3D212K
>
>
> #*** INNODB Specific options ***
> innodb_data_home_dir=3D"c:/MySQL Datafiles/"
>
> # Use this option if you have a MySQL server with InnoDB support enabled
> # but you do not plan to use it. This will save memory and disk space
> # and speed up some things.
> #skip-innodb
>
> # Additional memory pool that is used by InnoDB to store metadata
> # information. If InnoDB requires more memory for this purpose it will
> # start to allocate it from the OS. As this is fast enough on most
> # recent operating systems, you normally do not need to change this
> # value. SHOW INNODB STATUS will display the current amount used.
> innodb_additional_mem_pool_size=3D2M
>
> # If set to 1, InnoDB will flush (fsync) the transaction logs to the
> # disk at each commit, which offers full ACID behavior. If you are
> # willing to compromise this safety, and you are running small
> # transactions, you may set this to 0 or 2 to reduce disk I/O to the
> # logs. Value 0 means that the log is only written to the log file and
> # the log file flushed to disk approximately once per second. Value 2
> # means the log is written to the log file at each commit, but the log
> # file is only flushed to disk approximately once per second.
> innodb_flush_log_at_trx_commit=3D1
>
> # The size of the buffer InnoDB uses for buffering log data. As soon as
> # it is full, InnoDB will have to flush it to disk. As it is flushed
> # once per second anyway, it does not make sense to have it very large
> # (even with long transactions).
> innodb_log_buffer_size=3D1M
>
> # InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
> # row data. The bigger you set this the less disk I/O is needed to
> # access data in tables. On a dedicated database server you may set this
> # parameter up to 80% of the machine physical memory size. Do not set it
> # too large, though, because competition of the physical memory may
> # cause paging in the operating system. Note that on 32bit systems you
> # might be limited to 2-3.5G of user level memory per process, so do not
> # set it too high.
> innodb_buffer_pool_size=3D8M
>
> # Size of each log file in a log group. You should set the combined size
> # of log files to about 25%-100% of your buffer pool size to avoid
> # unneeded buffer pool flush activity on log file overwrite. However,
> # note that a larger logfile size will increase the time needed for the
> # recovery process.
> innodb_log_file_size=3D10M
>
> # Number of threads allowed inside the InnoDB kernel. The optimal value
> # depends highly on the application, hardware as well as the OS
> # scheduler properties. A too high value may lead to thread thrashing.
> innodb_thread_concurrency=3D8
>
>
> Patrice
> ------------------------------------------------------------ -------------=
--------------
> Wanadoo vous informe que cet e-mail a ete controle par l'anti-virus mail=
..
> Aucun virus connu a ce jour par nos services n'a ete detecte.
>
>
>
>
>
>
>
> --
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe: http://lists.mysql.com/win32?unsub=3Ddanieldaveiga@gma=
il.com
>
>

Good luck.

--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org

Re: I can"t start mysql from the windows command line

I checked for C:\my.cnf too. No my.cnf in my hard disk

Starting the server with the option "--defaults-file=file_name" doesn't
solve my problem.

----- Original Message -----
From: "Daniel da Veiga"
To: "MySQL Win32 List"
Sent: Monday, December 12, 2005 4:08 PM
Subject: Re: I can't start mysql from the windows command line


On 12/12/05, Patrice Serrand wrote:
> Now running Windows 98 SE :
>
> As suggested I got the zipped version of MySQL 5.0.16.
>
> Like Ken Resander:
>
> I completely removed all occurence of MySQL from my hard disk.
> Scan the whole disk to find all remaining occurence oh my.ini -

Check for C:\my.cnf too. Try starting the server with the option
"--defaults-file=file_name" and point it to a config file written
following the instructions at:

http://dev.mysql.com/doc/refman/5.0/en/windows-create-option -file.html

And see if it solves your problem.

> libmySQL.dll - mysql*.* : none found
> I removed the registry key : HKEY_LOCAL_MACHINE\SOFTWARE\MySQL AB
>
> I installed mysql 5.0.16 from "mysql-noinstall-5.0.16-win32.zip" in
> C:\mysql
>
> new ini file my.ini in c:\windows with correct path to myqsl and data

Check if ALL the files were extracted correctly, some users reported
bad extraction by using strange decompress software and it caused the
error you're getting.

>
> tried mysqld from command line :
> The server don't start and this message appear:
> "[Error] Can't find messagefile 'C:\mysql\share\english\errmsg.sys'"
>
> I checked this file : errmsg.sys exists in
> C:\mysql\share\english\errmsg.sys.
>

There must be a reason for it. Check this thread:
http://forums.mysql.com/read.php?11,20418,57289#msg-57289

> Note: Installation on a computer which never had mysql on the hard disk
> and
> installation at "C:\Program Files\MySQL\MySQL Server 5.0" had the same
> outcome : the server did not start from the command line
>
> ----- Original Message -----
> From:
> To: ;
> Sent: Sunday, December 11, 2005 10:37 PM
> Subject: RE: I can't start mysql from the windows command line
>
>
> You probably should be running
> C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld --defaults-file="..."
>
> Do you have two versions of MySQL installed in different places?
>
> You seem to be running some things from C:\MySQL and others from
> C:\Program Files\MySQL.
>
> John B.
>
> -----Original Message-----
> From: Patrice Serrand [mailto:Patrice.Serrand@wanadoo.fr]
> Sent: Saturday, 10 December 2005 1:26 AM
> To: win32@lists.mysql.com
> Subject: I can't start mysql from the windows command line
>
> Hello,
>
> Mysql is running on Windows 98 SE.
>
> With previous versions of mysql I can start mysql from the command line
> with:
> C:\> C:Mysql\bin\mysqld
>
> Now with version 5.0.16 this command don't start mysql and I can't use
> "net start ..." with windows 98.
>
> The command C:\> C:Mysql\bin\mysqld --defaults-file="..." don't start
> mysql.
> All commands return : "[Error] Can't find messagefile 'C:\Program
> Files\MySQL\MySQL Server 5.0\share\english\errmsg.sys'"
>
> I checked this file : errmsg.sys exists in C:\Program Files\MySQL\MySQL
> Server 5.0\share\english.
>
> The same thing occurs if I add the MySQL path in Autoexec.bat.
>
> thanks for your help.
>
> NB: Here is my my.ini:
>
> # MySQL Server Instance Configuration File
> # ------------------------------------------------------------ ----------
> # Generated by the MySQL Server Instance Configuration Wizard
> #
> #
> # Installation Instructions
> # ------------------------------------------------------------ ----------
> #
> # On Linux you can copy this file to /etc/my.cnf to set global options,
> # mysql-data-dir/my.cnf to set server-specific options
> # (@localstatedir@ for this installation) or to
> # ~/.my.cnf to set user-specific options.
> #
> # On Windows you should keep this file in the installation directory
> # of your server (e.g. C:\Program Files\MySQL\MySQL Server 4.1). To
> # make sure the server reads the config file use the startup option
> # "--defaults-file".
> #
> # To run run the server from the command line, execute this in a
> # command line shell, e.g.
> # mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server
> 4.1\my.ini"
> #
> # To install the server as a Windows service manually, execute this in a
>
> # command line shell, e.g.
> # mysqld --install MySQL41 --defaults-file="C:\Program Files\MySQL\MySQL
> Server 4.1\my.ini"
> #
> # And then execute this in a command line shell to start the server,
> e.g.
> # net start MySQL41
> #
> #
> # Guildlines for editing this file
> # ------------------------------------------------------------ ----------
> #
> # In this file, you can use all long options that the program supports.
> # If you want to know the options a program supports, start the program
> # with the "--help" option.
> #
> # More detailed information about the individual options can also be
> # found in the manual.
> #
> #
> # CLIENT SECTION
> # ------------------------------------------------------------ ----------
> #
> # The following options will be read by MySQL client applications.
> # Note that only client applications shipped by MySQL are guaranteed
> # to read this section. If you want your own MySQL client program to
> # honor these values, you need to specify it as an option during the
> # MySQL client library initialization.
> #
> [client]
>
> port=3306
>
> [mysql]
>
> default-character-set=latin1
>
>
> # SERVER SECTION
> # ------------------------------------------------------------ ----------
> #
> # The following options will be read by the MySQL Server. Make sure that
> # you have installed the server correctly (see above) so it reads this
> # file.
> #
> [mysqld]
>
> # The TCP/IP Port the MySQL Server will listen on
> port=3306
>
>
> #Path to installation directory. All paths are usually resolved relative
> to this.
> basedir="C:/Program Files/MySQL/MySQL Server 5.0/"
>
> #Path to the database root
> datadir="C:/Program Files/MySQL/MySQL Server 5.0/Data/"
>
> # The default character set that will be used when a new schema or table
> is
> # created and no character set is defined
> default-character-set=latin1
>
> # The default storage engine that will be used when create new tables
> when
> default-storage-engine=INNODB
>
> # Set the SQL mode to strict
> sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_ SUBSTITUTION
> "
>
> # The maximum amount of concurrent sessions the MySQL server will
> # allow. One of these connections will be reserved for a user with
> # SUPER privileges to allow the administrator to login even if the
> # connection limit has been reached.
> max_connections=100
>
> # Query cache is used to cache SELECT results and later return them
> # without actual executing the same query once again. Having the query
> # cache enabled may result in significant speed improvements, if your
> # have a lot of identical queries and rarely changing tables. See the
> # "Qcache_lowmem_prunes" status variable to check if the current value
> # is high enough for your load.
> # Note: In case your tables change very often or if your queries are
> # textually different every time, the query cache may result in a
> # slowdown instead of a performance improvement.
> query_cache_size=0
>
> # The number of open tables for all threads. Increasing this value
> # increases the number of file descriptors that mysqld requires.
> # Therefore you have to make sure to set the amount of open files
> # allowed to at least 4096 in the variable "open-files-limit" in
> # section [mysqld_safe]
> table_cache=256
>
> # Maximum size for internal (in-memory) temporary tables. If a table
> # grows larger than this value, it is automatically converted to disk
> # based table This limitation is for a single table. There can be many
> # of them.
> tmp_table_size=5M
>
>
> # How many threads we should keep in a cache for reuse. When a client
> # disconnects, the client's threads are put in the cache if there aren't
> # more than thread_cache_size threads from before. This greatly reduces
> # the amount of thread creations needed if you have a lot of new
> # connections. (Normally this doesn't give a notable performance
> # improvement if you have a good thread implementation.)
> thread_cache_size=8
>
> #*** MyISAM Specific options
>
> # The maximum size of the temporary file MySQL is allowed to use while
> # recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
> # If the file-size would be bigger than this, the index will be created
> # through the key cache (which is slower).
> myisam_max_sort_file_size=100G
>
> # If the temporary file used for fast index creation would be bigger
> # than using the key cache by the amount specified here, then prefer the
> # key cache method. This is mainly used to force long character keys in
> # large tables to use the slower key cache method to create the index.
> myisam_max_extra_sort_file_size=100G
>
> # If the temporary file used for fast index creation would be bigger
> # than using the key cache by the amount specified here, then prefer the
> # key cache method. This is mainly used to force long character keys in
> # large tables to use the slower key cache method to create the index.
> myisam_sort_buffer_size=8M
>
> # Size of the Key Buffer, used to cache index blocks for MyISAM tables.
> # Do not set it larger than 30% of your available memory, as some memory
> # is also required by the OS to cache rows. Even if you're not using
> # MyISAM tables, you should still set it to 8-64M as it will also be
> # used for internal temporary disk tables.
> key_buffer_size=8M
>
> # Size of the buffer used for doing full table scans of MyISAM tables.
> # Allocated per thread, if a full scan is needed.
> read_buffer_size=64K
> read_rnd_buffer_size=256K
>
> # This buffer is allocated when MySQL needs to rebuild the index in
> # REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
> # into an empty table. It is allocated per thread so be careful with
> # large settings.
> sort_buffer_size=212K
>
>
> #*** INNODB Specific options ***
> innodb_data_home_dir="c:/MySQL Datafiles/"
>
> # Use this option if you have a MySQL server with InnoDB support enabled
> # but you do not plan to use it. This will save memory and disk space
> # and speed up some things.
> #skip-innodb
>
> # Additional memory pool that is used by InnoDB to store metadata
> # information. If InnoDB requires more memory for this purpose it will
> # start to allocate it from the OS. As this is fast enough on most
> # recent operating systems, you normally do not need to change this
> # value. SHOW INNODB STATUS will display the current amount used.
> innodb_additional_mem_pool_size=2M
>
> # If set to 1, InnoDB will flush (fsync) the transaction logs to the
> # disk at each commit, which offers full ACID behavior. If you are
> # willing to compromise this safety, and you are running small
> # transactions, you may set this to 0 or 2 to reduce disk I/O to the
> # logs. Value 0 means that the log is only written to the log file and
> # the log file flushed to disk approximately once per second. Value 2
> # means the log is written to the log file at each commit, but the log
> # file is only flushed to disk approximately once per second.
> innodb_flush_log_at_trx_commit=1
>
> # The size of the buffer InnoDB uses for buffering log data. As soon as
> # it is full, InnoDB will have to flush it to disk. As it is flushed
> # once per second anyway, it does not make sense to have it very large
> # (even with long transactions).
> innodb_log_buffer_size=1M
>
> # InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
> # row data. The bigger you set this the less disk I/O is needed to
> # access data in tables. On a dedicated database server you may set this
> # parameter up to 80% of the machine physical memory size. Do not set it
> # too large, though, because competition of the physical memory may
> # cause paging in the operating system. Note that on 32bit systems you
> # might be limited to 2-3.5G of user level memory per process, so do not
> # set it too high.
> innodb_buffer_pool_size=8M
>
> # Size of each log file in a log group. You should set the combined size
> # of log files to about 25%-100% of your buffer pool size to avoid
> # unneeded buffer pool flush activity on log file overwrite. However,
> # note that a larger logfile size will increase the time needed for the
> # recovery process.
> innodb_log_file_size=10M
>
> # Number of threads allowed inside the InnoDB kernel. The optimal value
> # depends highly on the application, hardware as well as the OS
> # scheduler properties. A too high value may lead to thread thrashing.
> innodb_thread_concurrency=8
>
>
> Patrice
> ------------------------------------------------------------ ---------------------------
> Wanadoo vous informe que cet e-mail a ete controle par l'anti-virus mail.
> Aucun virus connu a ce jour par nos services n'a ete detecte.
>
>
>
>
>
>
>
> --
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe:
> http://lists.mysql.com/win32?unsub=danieldaveiga@gmail.com
>
>

Good luck.

--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe:
http://lists.mysql.com/win32?unsub=Patrice.Serrand@wanadoo.f r

------------------------------------------------------------ ---------------------------
Wanadoo vous informe que cet e-mail a ete controle par l'anti-virus mail.
Aucun virus connu a ce jour par nos services n'a ete detecte.







--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

Re: I can"t start mysql from the windows command line

------=_Part_29708_19742213.1135005879641
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

I=B4m having the same exactly problem over here. Tried all the tips posted =
but
got nothing so far.

Does anyone were able to start MySQL 5.0 from the command line? Or it just
doesn't work with Win 98 SE?

------=_Part_29708_19742213.1135005879641--

Re: I can"t start mysql from the windows command line

See Bug #15209

----- Original Message -----
From: "Marcelo Carnaval"
To:
Sent: Monday, December 19, 2005 4:24 PM
Subject: Re: I can't start mysql from the windows command line


Hi,

I´m having the same exactly problem over here. Tried all the tips posted but
got nothing so far.

Does anyone were able to start MySQL 5.0 from the command line? Or it just
doesn't work with Win 98 SE?

------------------------------------------------------------ ---------------------------
Wanadoo vous informe que cet e-mail a ete controle par l'anti-virus mail.
Aucun virus connu a ce jour par nos services n'a ete detecte.





--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org