WampServer

Hi there,
After many days of combing the threads here and finding no solution I figured I'd post and see what I'm doing wrong. Currently, I can't connect to MySQL, the error is the subject of the post. I can't connect to it using phpmyadmin, nor using the dos mysql tool. In fact, when I use phpmyadmin I don't even get an error, just a blank white screen, probably from firefox timing out. So, the usual questions:

-the wamp icon is white
-i have made the my.ini value change: default-storage-engine=MyISAM
-and taken the comment away from skip skip-innodb
-i have turned off windows firewall entirely
-i have verified that the mysqld-nt process is running as well as httpd
-[localhost] works just fine, it parses php perfectly
-heres a copy of my mysql error log:
InnoDB: The first specified data file .\ibdata1 did not exist:
InnoDB: a new database to be created!
081112 23:01:28 InnoDB: Setting file .\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
081112 23:01:29 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...
081112 23:01:31 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
081112 23:01:32 InnoDB: Started; log sequence number 0 0
081112 23:01:34 [Note] wampmysqld: ready for connections.
Version: '5.0.45-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
081112 23:02:14 [Note] wampmysqld: Normal shutdown

081112 23:02:14 InnoDB: Starting shutdown...
081112 23:02:16 InnoDB: Shutdown completed; log sequence number 0 43655
081112 23:02:16 [Note] wampmysqld: Shutdown complete

081113 17:27:29 [Note] wampmysqld: ready for connections.
Version: '5.0.45-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
081113 17:29:15 [Note] wampmysqld: Normal shutdown

081113 17:29:15 [Note] wampmysqld: Shutdown complete

081113 17:29:46 [Note] wampmysqld: ready for connections.
Version: '5.0.45-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
081113 17:32:59 [Note] wampmysqld: Normal shutdown

081113 17:32:59 [Note] wampmysqld: Shutdown complete

081113 17:33:00 [Note] wampmysqld: ready for connections.
Version: '5.0.45-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)

-here is my.ini file:
# 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


# 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.
#
[wampmysqld]

# 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:/wamp/bin/mysql/mysql5.0.45

#log file
log-error=c:/wamp/logs/mysql.log

#Path to the database root
datadir=c:/wamp/bin/mysql/mysql5.0.45/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=MyISAM

# 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=255

# 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=8M

# 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=510

# 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=13M


# 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=12

#*** 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=9M

# 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=203K


#*** INNODB Specific options ***


# 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=15M

# 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



[mysqld]
port=3306


-i've overwritten my user files with the ones supplied on the forum in different places, but that doesn't fix anything
-when i use dos to connect, typing: mysql -h 127.0.0.1 -u root -p (and hitting enter for blank pword) it just hangs until it gives me the error above.
-ive also tried a clean install of wamp 2.0a and c, clean install of phpeasy, and clean install of just mysql downloaded from their site but none of them allow me to connect to mysql in any way. and clean install means i've cleaned the registry as well.
-ive added wamp/bin/mysql/mysql5.0..../bin/ to the Environment Path variable

So i'm all out of ideas. It seems to me that mysql and wamp are giving me all the signals that this should work, but then it doesnt. Its almost as if the connection between mysql and mysqld-nt isn't happening. Is there another windows service that might block the connection? Oh ya, i've tried connecting with the internet on and off. Does anyone have any clue? I'd really appreciate it!

Quote

i've overwritten my user files with the ones supplied on the forum in different place

Quote

ive also tried a clean install of wamp 2.0a and c, clean install of phpeasy

you've tried way too many things and now not quite sure which might be the cause, so try to search and rename/remove any my.ini file outside wamp folder, restart wamp and try again

Have fun,

FREE One A Day
FREE Photo
FREE Games
FREE Websites
FREE Portable GPS
FREE WAMP Guides

Hello,

I Have the same problem.
First install went ok.
But after playing around i had to uninstall and reinstall.
Then the trouble started.
(working on Vista)
Even with a system restore on vista to the situation before the first install did not help...




But, found this work-around :

just add : index.php to the URL for phpmyadmin.


so : [localhost]
works fine.
[localhost] gives the famous error


btw : [localhost] works without the (index.php) added.

Anybody knows a permanent solution.

yfastud Wrote:
-------------------------------------------------------
> > i've overwritten my user files with the ones
> supplied on the forum in different place
>
>
> ive also tried a clean install of wamp 2.0a and c,
> clean install of phpeasy
>
> you've tried way too many things and now not quite
> sure which might be the cause, so try to search
> and rename/remove any my.ini file outside wamp
> folder, restart wamp and try again


sorry i didn't mention that i had made sure there were no other my.ini files anywhere. still aren't, but thats not working either. i also tried localhost/phpmyadmin/index.php but that didnt work either. it seems, since mysql is the one thing that hasn't worked despite my attempts with wampserver, easyphp and just mysql with no attachments, that there the problem is more inherent with a setting in windows, perhaps? does anoyne have any thoughts about this?

also, it might be interesting to note that if i turn off mysqld and try to connect to phpmyadmin, the same thing happens as if i had mysqld turned on - that is, i get a blank white screen with no error.

also, after everything says that mysqld is turned on (the logs/white icon/etc), if i try to telnet to localhost 3306, the connection times out (doesn't connect) as it should. I've been looking here: [dev.mysql.com] for solutions and either i have some really low level connection block from windows, or the mysqld server isn't starting properly but not telling me about it.

ok, found the solution - this might help some people out there!!!

the problem was comodo firewall. the interesting thing was that it wasn't on, nor was the service running, but it still managed to block my connection. On a whim (after disabling and screwing with windows firewall), I decided to turn on Comodo, add mysqld-nt as a trusted application, voila, i could connect. So, don't ask me how as a disabled service and not running on my computer, comodo managed to block connections, but it did. Hopefully this will be a lesson for all those out there who are doing what I was doing.

Good luck!

Hey men you saved my life! and COMODO Firewall was destryoing me...

Thanks to your suggestion, I didn't remeber that I had COMODO installed because it wasn't running BUT (afterall it was).

How can a firewall be disabled AND blocking connections? Sounds like a new functionality under the form of a BUG - it could be called the Firewall that watch for our lives....

Latest release includes the fix :
"FIXED! Firewall blocks fragmented packets even if it is disabled "

so I just would want to know if our "old" versions will remove this feature after uninstall the firewall.




Regards,

Duarte

Awesome! I'm glad I could help. I remember how infuriating the whole thing was for me, and to think I saved you hours of that same frustration makes me happy

Anyway, to be honest after I figured out the issue I made the changes and didn't research it further, but you are right - it either sounds like a "bug" or an intentional feature by COMODO to keep an eye on us. Kinda makes you wonder what the "disabled" feature even does... But to answer your question I believe uninstalling the firewall will remove any issues regarding blocking packets, etc. If you aren't using COMODO anyway its probably the smart idea. And who knows, if it doesn't work then just reinstall COMODO and add WAMPSERVER as a trusted application to the firewall and everything should work fine. Hope that helps.

Yes pelkin I've read that uninstalling wont cause more problems. It was because of the "zombie" cmdagent.exe process...

Thanks!