Help please. Not able to see phMyadmin

[shinokada]

I never had problems until this morning.

All the XAMPP pages are fine, except PHPMyadmin.

When I go to phpMyadmin I get the following error message.

Can anyone help me please?

#2013 - Lost connection to MySQL server at 'reading initial communication packet', system error: 0

Connection for controluser as defined in your configuration failed.

I am using XAMPP for Windows Version 1.7.1 on Vista.

I checked firewall and Apache HTTP server C:\xampp\apache\bin\httpd.exe and C:\xampp\mysql\bin\mysqld.exe have tick in their exceptions.

I am not sure if you need this info. But anyway...

I have the following in ADOdb.

Database
mysql

username
root

Current database on this database server
cdcol

Host of the DB server
17.0.0.1

password

selected table of database
cds

The followings are last two enries of mysql.error.log.
Hope this will tell you something.

+++++++++++++++++++++++++++++++
...
...


key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=4
max_threads=151
threads_connected=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133304 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x3de7650
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...
006AC8BB mysqld.exe!???
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 06004A98=SHOW TABLE STATUS FROM `ci_okadadesign_cecilieokada`
thd->thread_id=6
thd->killed=NOT_KILLED
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.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
100104 10:23:44 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
100104 10:23:45 InnoDB: Started; log sequence number 0 7340085
100104 10:23:45 [Note] Event Scheduler: Loaded 0 events
100104 10:23:45 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.1.33-community' socket: '' port: 3306 MySQL Community Server (GPL)
100104 10:24:46 InnoDB: Error: (1500) Couldn't read the MAX(customer_id) autoinc value from the index (PRIMARY).
100104 10:24:46 InnoDB: Assertion failure in thread 6140 in file .\handler\ha_innodb.cc line 2601
InnoDB: Failing assertion: error == DB_SUCCESS
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/ ... overy.html
InnoDB: about forcing recovery.
100104 10:24:46 - 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=4
max_threads=151
threads_connected=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133304 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x3df8db0
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...
006AC8BB mysqld.exe!???
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 05FE4FF8=SHOW TABLE STATUS FROM `ci_okadadesign_cecilieokada`
thd->thread_id=24
thd->killed=NOT_KILLED
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.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
100104 10:25:03 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
100104 10:25:04 InnoDB: Started; log sequence number 0 7340085
100104 10:25:04 [Note] Event Scheduler: Loaded 0 events
100104 10:25:04 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.1.33-community' socket: '' port: 3306 MySQL Community Server (GPL)
100104 10:25:49 [Note] mysql\bin\mysqld.exe: Normal shutdown

100104 10:25:49 [Note] Event Scheduler: Purging the queue. 0 events
100104 10:25:49 InnoDB: Starting shutdown...
100104 10:25:50 InnoDB: Shutdown completed; log sequence number 0 7340085
100104 10:25:50 [Warning] Forcing shutdown of 1 plugins
100104 10:25:50 [Note] mysql\bin\mysqld.exe: Shutdown complete

100104 10:25:58 InnoDB: Started; log sequence number 0 7340085
100104 10:25:58 [Note] Event Scheduler: Loaded 0 events
100104 10:25:58 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.1.33-community' socket: '' port: 3306 MySQL Community Server (GPL)
100104 10:26:20 [Note] mysql\bin\mysqld.exe: Normal shutdown

100104 10:26:20 [Note] Event Scheduler: Purging the queue. 0 events
100104 10:26:20 InnoDB: Starting shutdown...
100104 10:26:22 InnoDB: Shutdown completed; log sequence number 0 7340085
100104 10:26:22 [Warning] Forcing shutdown of 1 plugins
100104 10:26:22 [Note] mysql\bin\mysqld.exe: Shutdown complete

100104 10:26:34 InnoDB: Started; log sequence number 0 7340085
100104 10:26:34 [Note] Event Scheduler: Loaded 0 events
100104 10:26:34 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.1.33-community' socket: '' port: 3306 MySQL Community Server (GPL)