WampServer

BigMike Wrote:
-------------------------------------------------------
> ... how can I get
> mysqld.exe (or ensure it is running) when it
> instantly closes due to the error on load.

Try reading the error logs.

Left-click on the WAMP tray icon.

When you run your cursor across Apache, PHP,
or MySQL on the menu that comes up, you will
see a sub-menu that shows you the error logs.

php.ini is also on the PHP sub-menu.

; This file controls many aspects of PHP's behavior. In order for PHP to
; read it, it must be named 'php.ini'. PHP looks for it in the current
; working directory, in the path designated by the environment variable
; PHPRC, and in the path that was defined in compile time (in that order).
; Under Windows, the compile-time path is the Windows directory. The
; path in which the php.ini file is looked for can be overridden using
; the -c argument in command line mode.

I have shot myself in the foot with all of the stuff I was doing yesterday
to try to "fix" the MySQL library/server "problem." I'm probably going
to uninstall everything and then start with a fresh WAMP installation.

I'm convinced that the phpMyAdmin warning is a red herring. My guess
is that the PHP and MySQL developers have just decided not to keep
the client and server in synch. I haven't found any proof of this, but
neither could I find any version of the client that matched the current
server version.

And so it goes.

Marty

MYSQL Error Log:

081209 11:27:41 - 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 [dev.mysql.com] contains
information that should help you find out what is causing the crash.
081209 11:28:55 - 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 [dev.mysql.com] contains
information that should help you find out what is causing the crash.
081209 22:27:27 - 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 [dev.mysql.com] contains
information that should help you find out what is causing the crash.


No reported problems with PHP on start up but here is the error log:

[09-Dec-2008 11:27:39] PHP Notice: Undefined variable: mywampfp in C:\wamp\scripts\refresh.php on line 252
[09-Dec-2008 11:27:39] PHP Notice: Undefined variable: i in C:\wamp\scripts\refresh.php on line 252
[09-Dec-2008 11:27:39] PHP Notice: Undefined variable: mywampini in C:\wamp\scripts\refresh.php on line 252
[09-Dec-2008 11:27:39] PHP Notice: Undefined offset: 1 in C:\wamp\scripts\refresh.php on line 385
[09-Dec-2008 11:27:39] PHP Notice: Undefined offset: 1 in C:\wamp\scripts\refresh.php on line 385
[09-Dec-2008 22:27:26] PHP Notice: Undefined variable: mywampfp in C:\wamp\scripts\refresh.php on line 252
[09-Dec-2008 22:27:26] PHP Notice: Undefined variable: i in C:\wamp\scripts\refresh.php on line 252
[09-Dec-2008 22:27:26] PHP Notice: Undefined variable: mywampini in C:\wamp\scripts\refresh.php on line 252
[09-Dec-2008 22:27:26] PHP Notice: Undefined offset: 1 in C:\wamp\scripts\refresh.php on line 385
[09-Dec-2008 22:27:26] PHP Notice: Undefined offset: 1 in C:\wamp\scripts\refresh.php on line 385


Again the problem I have is that as soon as I start wamp I get an error message from windows saying that there has been a problem with mysqld.exe and it has been closed. The wamp icon remains amber in the system tray.

HELP.

BigMike Wrote:
-------------------------------------------------------
> MYSQL Error Log:

> 081209 11:27:41 - mysqld got exception 0xc0000005

This seems to be a Windows-generated exception.


See this article:

[www.updatexp.com]

> 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.

The remedy for that is to download WAMP again and
reinstall.

> This error can also be caused by
> malfunctioning hardware.

I used BurnInTest to find a problem with some brand-new
RAM last month. It was amazing how long it took me to
become suspicious of the RAM. The system never
blew up the same way twice.

> 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.

I don't know whether these are realistic numbers or
evidence of a runaway loop.

> 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...

The backtrace seems not to have gone anywhere.

> The manual page at
> [dev.mysql.com]
> contains
> information that should help you find out what is
> causing the crash.

It is a very nice page and well worth reading. It may
give you some ideas about things to try.


> No reported problems with PHP on start up but here
> is the error log: ...

There is nothing relevant there. The MySQL error log
is telling you what the big problem is.

Marty

Same issue here.

New install of latest version on my pc (amd athlon64, XP Pro 32bit) results in mysqld crash. Ive tried uninstalling, redownloading and reinstalling but issue remains. same error messages and logs as original poster.

I installed this last night on my laptop (intel core2, vista 64bit) and it works perfectly.

I found my solution for this. After trying all of the above it still would not work, but after going into services.msc (start-->run-->services.msc) I was able to get the mysql service working.
Just click the "Log On" tab on the mysql service's properties and check "Allow service to interact with the desktop." I hope this helps others.

System info: AMD Athlon 64 x2, 4GB ram, Windows XP SP3

This worked for me thanks!


XP Pro SP3

HI,

This worked for me too... a few days.

Today, I get the very same error.

I tried to add a previous release of MySQL (5.0.51b) but it seem to be worse. The service is in a limbo state; I can't do nothing with it even if I stop Wamserver 2.0e.

I also tried to re-download, reboot, reinstall...

Hi,

I was having the same issues. My resolution for this issue was to download the mysql 5.1.30 and install it in the wamp directory. That fixed the issue of the mysql.exe not starting.

I still have to fix "Your PHP MySQL library version 5.0.51a differs from your MySQL server version 5.1.30. This may cause unpredictable behavior."

I tried to reinstall the latest version of php from php.net that didn't help.

Hope this helps someone.

I was and still having the same issue with mysqld.exe crashing on start , but when I manually started mysqld.exe, everything(mysql console, phpmyadmin, etc. ) seems to be working now. Again, I still get the the same error for mysqld.exe, when I first start wamp and wamp icon is still yellow.

Hope this help until the issues are fixed



Edited 1 time(s). Last edit at 12/16/2008 11:55PM by eisagholi.

hello there. i think the problem is something with "mysqld -wampmysqld" command.

i just changed the wampmysqld service's path;

c:\wamp\bin\mysql\mysql5.1.30\bin\mysqld.exe -wampmysqld

to

"C:\wamp\bin\mysql\mysql5.1.30\bin\mysqld" --defaults-file="C:\wamp\bin\mysql\mysql5.1.30\bin\my.ini" MySQL

and it works now.

to do this;
-first check if you have the MySQL service in the services.msc (to check start/run/services.msc then enter)
-if you dont have the service, im not sure that but, MySQLInstanceConfig.exe can create it.
-then start/run/regedit
-search for word "wampmysqld" (without quotes)
-look for values "ImagePath"
-then change the values' data to;

"C:\wamp\bin\mysql\mysql5.1.30\bin\mysqld" --defaults-file="C:\wamp\bin\mysql\mysql5.1.30\bin\my.ini" MySQL

(quotes included)

-i think you have to do it 3 or 4 times. i just cant remember.

sorry guys it looked like a noobs faq.. and i hope you can understand it.

Osman Tataroglu

I just wanted to let everyone know that I just fixed this problem with phpmyadmin displaying the client version error.

1) I first replaced the "libmysql.dll" from the "php/php5.2.7" directory with the one from the "mysql/mysql5.1.30/bin" directory.
2) I then had to rename the "libmysql.dll" from the
apache/apache2.2.10/bin
directory to "libmysql.dll.bak" (as not to delete the file).
3) Then I had to restart my apache server for the changes to take effect.

It seems that php was loading my "libmysql.dll" file from the "apache2.2.10/bin" directory and not using the one in the "php/php5.2.7" directory.

Also note that some people may have other copies of "libmysql.dll" in other folders that are specified in the computers include path such as "c:\Windows\System32".

To BigMike:


I also had the same problem with the MySQL service. Taking some advice from the above posts, I tried changing the Registry:

- make sure wampserver is closed
- go to Start/run/regedit
-search for word "wampmysqld" (without quotes)
-look for values "ImagePath"
-then change the values' data from:

c:\wamp\bin\mysql\mysql5.1.30\bin\mysqld.exe wampmysqld

to:

"c:\wamp\bin\mysql\mysql5.1.30\bin\mysqld" wampmysqld


I think it is the ".exe" on the executable path of the service that causes the crash.

I have found a solution that worked for me. First of all the specs. I am using:

- WampServer2.0f
- Win xp SP3

My installation was working fine until the 7th of jan 2009. then today 8th of jan I started the wamp server and I got the same error message that you guys/girls. So i have tried uninstalling/re-installing, tried the mysql_update.exe in cmd... nothing helped...

then i went to start -> all programs ->accessories -> system tools -> system restore and restored the system 2 days back... And voila the sql started working again.

No idea why that could be. Maybe because i installed matlab 2008r on my machine, but then again i used the wamp server after I installed it. the only thing I didnt do is rebooting my system after the installation of matlab.

Beats me... But it worked... lol

HBK : You are my hero.

Just needed to chime in and say rain34 your solution of excluding the .exe from mysqld.exe in the registry worked for me. Thanks!

Hey, this worked for my on Windows XP. It's a less painful method:

1. Open Control Panel and click "Performance and Maintenance" then "Administrative Tools"(assuming the new style look, not the classic. In the classic version you should go directly to Administrative Tools)
2. Double click "Services" and then double click "wampmysqld"
3. Click the "Log On" tab, and then right underneath "Local System account", check the box for "Allow service
to interact with desktop".
4. Click the "General" tab and click "start" to start the service.

I hope this works for you too.

try uninstalling wamp delete to folder and empty the recycle bin restart your pc then reinstall wamp that should work

Thanks HBK my problem is solved actually i was getting a message that "mysqld.exe has encountered a problem ........" & i was fed up of that tried all the option to solve the problem reinstalled mysql, wamp but still problem was going & finally i saw your solution here i.e through services.msc--> click the "Log On" tab on the mysql service's properties and check "Allow service to interact with the desktop it has really helped me to solve that problem." thanks once again...

Milind Kharwade
Software Engineer
Synergy Technology Solutions Pvt Ltd
PUNE