This forum is no longer active. Please post your questions to our new community site

Forums Joomla!

Εrror 2003 Can't connect to mySql in localhost .

Subscribe to Εrror 2003 Can't connect to mySql in localhost . 6 post(s), 5 voice(s)

 
Avatar Stelios 1 post

Dear Sirs,

I was installing Joomla, all was fine until a little before the end when i i got this error message: Εrror 2003 Can’t connect to mySql in localhost .

Please advice

 
Avatar antonio 621 post(s)

We would need more info to help:

- On what operating system have yo tried to install the stack?
- Are you using a firewall or proxy?

Also, you can find mysqld.log in mysql/data folder, that could be useful to trace the problem.

Cheers!

 
Avatar Lallo 1 post

I’m getting the same error.
-I’m running Vista Home Premium
-No firewall besides the default Windows one
I’ll try to get the mysqld.log later when at home.

Thanks!

 
Avatar RichardR 2 post(s)

I’m getting the same error. I’m not sure whether or not it is anything to do with the fact that I’d already successfully installed the Drupal stack a few days ago? I’m using Windows XP Home with SP3 installed. The sequence of events is as follows:

1. Successfully installed Drupal BitNami stack 5 days ago and happily able to use it.
2. Tried to install Joomla stack this morning but this came up with an error [think it was MySQL related but can’t be sure] I therefore abandoned the the install and the install process started to uninstall. On completion there were a few files left in the install location folder AND the 2 services were still running [joomlaAppache & joomlaMySQL.
3. Started to re-install [asked me to use a new file location – but I just deleted the remaining files/folders left over from the previous un-install, and that worked OK].
4. Got the following warning message “Warning

Problem running post-install step. Installation may not complete correctly
 Error running N:/Program Files/BitNami Joomla 1.5.10-0 Stack/mysql/bin/mysql -u root -pN7AfYKXod1nHesXHWYgw -D "bitnami_joomla" -e "SOURCE
N:\Program Files\BitNami Joomla 1.5.10-0 Stack/apps/joomla/htdocs/installation/sql/mysql/joomla.sql" : ERROR 2003 (HY000): Can't connect to MySQL 
server on 'localhost' (10061)" this was followed by a mysqld.exe error message.  This created 4 error files 2 of which were sent to MS.  The file names are: "mysqld.exe.mdmp", "appcompat.txt", "manifest.txt" & "mysqld.exe.hdmp"

4. The “appcompat.txt” file contents are below:

<?xml version=”1.0” encoding=”UTF-16”?>
<database>
<exe name="mysqld.exe" filter="GRABMI_FILTER_PRIVACY"> <matching_file linker_version="0x0" name="bug25714.exe" link_date="11/15/2008 04:45:09" size="2150400" module_type="WIN32" upto_link_date="11/15/2008 04:45:09" checksum="0x4818C35E" pe_checksum="0x0" /> <matching_file linker_version="0x0" name="comp_err.exe" link_date="11/15/2008 04:38:05" size="1646592" module_type="WIN32" upto_link_date="11/15/2008 04:38:05" checksum="0x24B9DA11" pe_checksum="0x0" /> <matching_file linker_version="0x0" name="echo.exe" link_date="11/15/2008 04:37:54" size="156288" module_type="WIN32" upto_link_date="11/15/2008 04:37:54" checksum="0xF6CE9F52" pe_checksum="0x2E367" /> <matching_file linker_version="0x0" name="libmysql.dll" link_date="11/15/2008 04:45:49" size="2260992" module_type="WIN32" upto_link_date="11/15/2008 04:45:49" checksum="0x16C4E6C0" pe_checksum="0x0" /> <matching_file linker_version="0x0" name="myisamchk.exe" link_date="11/15/2008 04:41:12" size="1999488" module_type="WIN32" upto_link_date="11/15/2008 04:41:12" checksum="0x54EC3D3A" pe_checksum="0x1EDB88" /> <matching_file linker_version="0x0" name="myisamlog.exe" link_date="11/15/2008 04:41:08" size="1888896" module_type="WIN32" upto_link_date="11/15/2008 04:41:08" checksum="0xBE72C1DB" pe_checksum="0x1CE7FA" /> <matching_file linker_version="0x0" name="myisampack.exe" link_date="11/15/2008 04:41:06" size="1917568" module_type="WIN32" upto_link_date="11/15/2008 04:41:06" checksum="0x3B52CFBC" pe_checksum="0x1E0ED3" /> <matching_file linker_version="0x0" name="myisam_ftdump.exe" link_date="11/15/2008 04:41:14" size="1876608" module_type="WIN32" upto_link_date="11/15/2008 04:41:14" checksum="0x91ED75EB" pe_checksum="0x1D19B4" /> <matching_file linker_version="0x0" name="mysql.exe" link_date="11/15/2008 04:40:56" size="2253440" module_type="WIN32" upto_link_date="11/15/2008 04:40:56" checksum="0x9C799FDC" pe_checksum="0x2322EA" /> <matching_file linker_version="0x0" name="mysqladmin.exe" link_date="11/15/2008 04:41:18" size="2192000" module_type="WIN32" upto_link_date="11/15/2008 04:41:18" checksum="0xE175FED3" pe_checksum="0x21E10D" /> <matching_file linker_version="0x0" name="mysqlbinlog.exe" link_date="11/15/2008 04:41:02" size="2278016" module_type="WIN32" upto_link_date="11/15/2008 04:41:02" checksum="0x5902E8E3" pe_checksum="0x231954" /> <matching_file linker_version="0x0" name="mysqlcheck.exe" link_date="11/15/2008 04:40:47" size="2187904" module_type="WIN32" upto_link_date="11/15/2008 04:40:47" checksum="0x9CBCE8D2" pe_checksum="0x22278E" /> <matching_file linker_version="0x0" name="mysqld-debug.exe" link_date="11/15/2008 04:52:08" size="10576512" module_type="WIN32" upto_link_date="11/15/2008 04:52:08" checksum="0x67700F06" pe_checksum="0xA1A165" /> <matching_file linker_version="0x0" name="mysqld.exe" link_date="11/15/2008 04:44:45" size="6447744" module_type="WIN32" upto_link_date="11/15/2008 04:44:45" checksum="0x85E85C9" pe_checksum="0x636222" /> <matching_file linker_version="0x0" name="mysqldump.exe" link_date="11/15/2008 04:40:44" size="2241152" module_type="WIN32" upto_link_date="11/15/2008 04:40:44" checksum="0x651A698" pe_checksum="0x230712" /> <matching_file linker_version="0x0" name="mysqlimport.exe" link_date="11/15/2008 04:40:40" size="2179712" module_type="WIN32" upto_link_date="11/15/2008 04:40:40" checksum="0x950FC05C" pe_checksum="0x21BF2A" /> <matching_file linker_version="0x0" name="mysqlmanager.exe" link_date="11/15/2008 04:45:02" size="2228864" module_type="WIN32" upto_link_date="11/15/2008 04:45:02" checksum="0x9AC7E6CC" pe_checksum="0x227AC2" /> <matching_file linker_version="0x0" name="mysqlshow.exe" link_date="11/15/2008 04:40:36" size="2183808" module_type="WIN32" upto_link_date="11/15/2008 04:40:36" checksum="0x6AEC745F" pe_checksum="0x224AE5" /> <matching_file linker_version="0x0" name="mysqlslap.exe" link_date="11/15/2008 04:41:20" size="2191360" module_type="WIN32" upto_link_date="11/15/2008 04:41:20" checksum="0x1CC8B95" pe_checksum="0x0" /> <matching_file linker_version="0x0" name="mysqltest.exe" link_date="11/15/2008 04:40:51" size="2318976" module_type="WIN32" upto_link_date="11/15/2008 04:40:51" checksum="0x3DE9008E" pe_checksum="0x2362F3" /> <matching_file linker_version="0x0" name="mysql_client_test.exe" link_date="11/15/2008 04:45:07" size="2514944" module_type="WIN32" upto_link_date="11/15/2008 04:45:07" checksum="0xD5A92114" pe_checksum="0x0" /> <matching_file linker_version="0x0" name="mysql_upgrade.exe" link_date="11/15/2008 04:45:20" size="1708672" module_type="WIN32" upto_link_date="11/15/2008 04:45:20" checksum="0x419AEC15" pe_checksum="0x1A50CE" /> <matching_file linker_version="0x0" name="my_print_defaults.exe" link_date="11/15/2008 04:41:24" size="1634304" module_type="WIN32" upto_link_date="11/15/2008 04:41:24" checksum="0xEE36565B" pe_checksum="0x0" /> <matching_file linker_version="0x0" name="perror.exe" link_date="11/15/2008 04:41:23" size="1617920" module_type="WIN32" upto_link_date="11/15/2008 04:41:23" checksum="0xFBAA199F" pe_checksum="0x0" /> <matching_file linker_version="0x0" name="replace.exe" link_date="11/15/2008 04:38:06" size="1630208" module_type="WIN32" upto_link_date="11/15/2008 04:38:06" checksum="0x4E89DF2" pe_checksum="0x0" /> <matching_file linker_version="0x0" name="resolveip.exe" link_date="11/15/2008 04:41:22" size="1613824" module_type="WIN32" upto_link_date="11/15/2008 04:41:22" checksum="0xD86BA23C" pe_checksum="0x0" />
</exe>
<exe name="kernel32.dll" filter="GRABMI_FILTER_THISFILEONLY"> <matching_file upto_bin_file_version="5.1.2600.5781" linker_version="0x50001" name="kernel32.dll" link_date="03/21/2009 14:06:58" original_filename="kernel32" file_version="5.1.2600.5781 (xpsp_sp3_gdr.090321-1317)" size="989696" module_type="WIN32" company_name="Microsoft Corporation" bin_file_version="5.1.2600.5781" upto_link_date="03/21/2009 14:06:58" legal_copyright="© Microsoft Corporation. All rights reserved." verfiletype="0x2" verfileos="0x40004" verfiledatehi="0x0" checksum="0x2D998938" pe_checksum="0xFE572" internal_name="kernel32" verfiledatelo="0x0" product_name="Microsoft® Windows® Operating System" file_description="Windows NT BASE API Client DLL" ver_language="English (United States) [0x409]" upto_bin_product_version="5.1.2600.5781" bin_product_version="5.1.2600.5781" product_version="5.1.2600.5781" />
</exe>
</database>

5. Also here is the contents of the error log:

InnoDB: The first specified data file .\ibdata1 did not exist:
InnoDB: a new database to be created!
090530 7:31:44 InnoDB: Setting file .\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait…
090530 7:31:44 InnoDB: Log file .\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait…
090530 7:31:45 InnoDB: Log file .\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile1 size to 5 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
090530 7:31:46 InnoDB: Started; log sequence number 0 0
090530 7:31:46 [Note] Event Scheduler: Loaded 0 events
090530 7:31:46 [Note] N:\PROGRA1\BITNAM1.10-\mysql\bin\mysqld.exe: ready for connections.
Version: ‘5.1.30-community-log’ socket: ’’ port: 3306 MySQL Community Server (GPL)
090530 7:32:21 [Note] N:\PROGRA1\BITNAM1.10-\mysql\bin\mysqld.exe: Normal shutdown

090530 7:32:21 [Note] Event Scheduler: Purging the queue. 0 events
090530 7:32:21 InnoDB: Starting shutdown…
090530 7:32:22 InnoDB: Shutdown completed; log sequence number 0 46409
090530 7:32:22 [Note] N:\PROGRA1\BITNAM1.10-\mysql\bin\mysqld.exe: Shutdown complete

090530 7:32:51 – 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: 0×0
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.
090530 13:15:51 – 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: 0×0
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.
090530 13:15:58 – 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: 0×0
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.
090530 13:25:44 – 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: 0×0
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.

6. Your advice would be appreciated.

 
Avatar RichardR 2 post(s)

Well I’ve just had another go at installing the BitNami Joomla stack – and success! Here is what I did.

1. Downloaded a fresh version of the BitNami Joomla stack [note I did a file comparison using Beyond Compare V2 and these files are exactly the same!]
2. Created a new target folder without any period [full stops] in the name.
3. Used the new download
4. called the super admin user “admin_user” previous failed attempt was “adminuser”
5. Chose an 8 character password [previous was 20 characters – I use Keepass to generate passwords]
6. Gave the site a name with out any spaces in it [used underscore instead of a space] Previous install have a space in the site name.
7. Chose port 81

That was it – and the install worked OK

Hope this helps others who may have problems

 
Avatar Beltrán Rueda Administrator 3,714 post(s)

Hi,

It is a strange error and it seems a MySQL bug. We can not reproduce on our side but thanks for reporting your solution.

Cheers.

Forums Joomla!