I dont see anything wrong, but then again I may not know wht to look for, 
this is the my.ini file

# Example MySQL config file for small systems.
#
# This is for a system with little memory (<= 64M) where MySQL is only used
# from time to time and it's important that the mysqld daemon
# doesn't use much resources.
#
# You can copy this file to
# C:/xampp/mysql/bin/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is C:/xampp/mysql/data) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
[client]
# password       = removed
port            = 3306
socket          = "C:/xampp/mysql/mysql.sock"

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port= 3306
socket= "C:/xampp/mysql/mysql.sock"
basedir="C:/xampp/mysql"
tmpdir="C:/xampp/tmp"
datadir="C:/xampp/mysql/data"
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



# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
# commented in by lampp security
#skip-networking
skip-federated

# Replication Master Server (default)
# binary logging is required for replication
# log-bin deactivated by default since XAMPP 1.4.11
#log-bin=mysql-bin

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id = 1

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
#    the syntax is:
#
#    CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
#    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
#    where you replace <host>, <user>, <password> by quoted strings and
#    <port> by the master's port number (3306 by default).
#
#    Example:
#
#    CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
#    MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
#    start replication for the first time (even unsuccessfully, for example
#    if you mistyped the password in master-password and the slave fails to
#    connect), the slave will create a master.info file, and any later
#    change in this file to the variables' values below will be ignored and
#    overridden by the content of the master.info file, unless you shutdown
#    the slave server, delete master.info and restart the slaver server.
#    For that reason, you may want to leave the lines below untouched
#    (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id       = 2
#
# The replication master for this slave - required
#master-host     =   <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user     =   <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password =   <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port     =  <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin


# Point the following paths to different dedicated disks
#tmpdir = "C:/xampp/tmp"
#log-update = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000

# Comment the following if you are using InnoDB tables
#skip-innodb
innodb_data_home_dir = "C:/xampp/mysql/"
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = "C:/xampp/mysql/"
#innodb_log_arch_dir = "C:/xampp/mysql/"
## You can set .._buffer_pool_size up to 50 - 80 %
## of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 16M
innodb_additional_mem_pool_size = 2M
## Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 5M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout
[WinMySQLAdmin]
QueryInterval=10

"Carlos Proal" <carlos.pr...@gmail.com> wrote in message 
news:4a58cb7c.4090...@gmail.com...
>
> Take a look on the my.ini to see if there is something wrong (maybe a path 
> pointing to a missing place or memory setting bigger than your actual RAM)
>
> Carlos
>
> On 7/11/2009 12:17 PM, Gary wrote:
>> Not sure if this is it, it was the only .err file that I have.  Also this 
>> seems to be the latest entry that has a date.
>>
>> Thanks for your help.
>>
>> Gary
>>
>> 090617 21:50:45 - mysqld got exception 0xc0000005 ;
>> This could be because you hit a bug. It is also possible that this binary
>> or one of the libraries it was linked against is corrupt, improperly 
>> built,
>> or misconfigured. This error can also be caused by malfunctioning 
>> hardware.
>> We will try our best to scrape up some info that will hopefully help 
>> diagnose
>> the problem, but since we have already crashed, something is definitely 
>> wrong
>> and this may fail.
>>
>> key_buffer_size=16777216
>> read_buffer_size=262144
>> max_used_connections=0
>> max_threads=151
>> threads_connected=0
>> It is possible that mysqld could use up to
>> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 
>> 133305 K
>> bytes of memory
>> Hope that's ok; if not, decrease some variables in the equation.
>>
>> thd: 0x0
>> Attempting backtrace. You can use the following information to find out
>> where mysqld died. If you see no messages after this, something went
>> terribly wrong...
>> 006B8853    mysqld.exe!???
>> The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html 
>> contains
>> information that should help you find out what is causing the crash.
>> 090627  9:35:07 - mysqld got exception 0xc0000005 ;
>> This could be because you hit a bug. It is also possible that this binary
>> or one of the libraries it was linked against is corrupt, improperly 
>> built,
>> or misconfigured. This error can also be caused by malfunctioning 
>> hardware.
>> We will try our best to scrape up some info that will hopefully help 
>> diagnose
>> the problem, but since we have already crashed, something is definitely 
>> wrong
>> and this may fail.
>> "Carlos Proal" <carlos.pr...@gmail.com> wrote in message 
>> news:4a58c79b.2090...@gmail.com...
>>
>>> You have to take a look on the error log, a file named hostname.err 
>>> (hostname=your machine name) and should be located inside
>>> the mysql dir on the xammp dir.
>>> That file will give an insight about the problem, or you can post the 
>>> error here to get help.
>>>
>>> Carlos
>>>
>>>
>>> On 7/11/2009 11:52 AM, Gary wrote:
>>>
>>>> I have an issue that Mysql will not start on my local machine. I 
>>>> noticed a
>>>> few days ago on a restart that I got an error saying that Mysqld had
>>>> encountered a problem and had to close. I did not pay any attention to 
>>>> it
>>>> because I was not working in it for a bit.
>>>>
>>>> I then tried to start it today and got the same error message saying
>>>> mysqld.exe has encountered a problem and had to close.
>>>>
>>>> + Apache 2.2.11
>>>>   + MySQL 5.1.30 (Community Server)
>>>>   + PHP 5.2.8 + PEAR (Support for PHP 4 has been discontinued)
>>>>   + PHP-Switch win32 1.0 (use "php-switch.bat" in the xampp main 
>>>> directory)
>>>>   + XAMPP Control Version 2.5 from www.nat32.com
>>>>   + XAMPP Security 1.0
>>>>   + SQLite 2.8.15
>>>>   + OpenSSL 0.9.8i
>>>>   + phpMyAdmin 3.1.1
>>>>   + ADOdb 4.990
>>>>   + Mercury Mail Transport System v4.52
>>>>   + FileZilla FTP Server 0.9.29
>>>>   + Webalizer 2.01-10
>>>>   + Zend Optimizer 3.3.0
>>>>   + eAccelerator 0.9.5.3 für PHP 5.2.8 (but not activated in the 
>>>> php.ini)
>>>>
>>>> Anyone have an idea to where I should start to look?
>>>>
>>>> Thanks
>>>>
>>>> Gary
>>>>
>>>>
>>>>
>>>>
>>>>
>>
>>
>>
>>
> 



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql?unsub=arch...@jab.org

Reply via email to