Pages: Previous1234Next
Current Page: 3 of 4
Re: wamp server does not turn GREEN
Posted by: RiggsFolly (---.dynamic.dsl.as9105.com)
Date: August 28, 2014 01:19PM

Thats the Apache error log.

Have a look at the MySQL errror log or if thats empty the Windows Event Viewer

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.1.3 32bit & 64bit)
<Apache 2.4.29/2.2.31> <PHP 7.2/7.1/7.0/5.6/5.5/5.4> <MySQL 5.7.19/5.6.39/5.5.28>
<MariaDB 10.2.14> <phpMyAdmin4.8.1> <MySQL Workbench 6.3.10>

Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your MySQL databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

Options: ReplyQuote
Re: wamp server does not turn GREEN
Posted by: Ritika (117.201.176.---)
Date: August 28, 2014 01:24PM

thats mysql log file


2014-08-28 15:17:30 5016 [Note] Plugin 'FEDERATED' is disabled.
2014-08-28 15:17:30 5016 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-28 15:17:30 5016 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-08-28 15:17:30 5016 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-08-28 15:17:30 5016 [Note] InnoDB: Not using CPU crc32 instructions
2014-08-28 15:17:30 5016 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-08-28 15:17:30 5016 [Note] InnoDB: Completed initialization of buffer pool
2014-08-28 15:17:30 5016 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-28 15:17:30 5016 [Note] InnoDB: 128 rollback segment(s) are active.
2014-08-28 15:17:30 5016 [Note] InnoDB: Waiting for purge to start
2014-08-28 15:17:30 5016 [Note] InnoDB: 5.6.12 started; log sequence number 1625977
2014-08-28 15:17:30 5016 [Note] Recovering after a crash using mysql-bin
2014-08-28 15:17:30 5016 [Note] Starting crash recovery...
2014-08-28 15:17:30 5016 [Note] Crash recovery finished.
2014-08-28 15:17:30 5016 [Note] Server hostname (bind-address): '*'; port: 3306
2014-08-28 15:17:30 5016 [Note] IPv6 is available.
2014-08-28 15:17:30 5016 [Note] - '::' resolves to '::';
2014-08-28 15:17:30 5016 [Note] Server socket created on IP: '::'.
2014-08-28 15:17:30 5016 [Note] Event Scheduler: Loaded 0 events
2014-08-28 15:17:30 5016 [Note] wampmysqld: ready for connections.
Version: '5.6.12-log' socket: '' port: 3306 MySQL Community Server (GPL)
2014-08-28 15:17:51 5016 [Note] wampmysqld: Normal shutdown

2014-08-28 15:17:51 5016 [Note] Giving 0 client threads a chance to die gracefully
2014-08-28 15:17:51 5016 [Note] Event Scheduler: Purging the queue. 0 events
2014-08-28 15:17:51 5016 [Note] Shutting down slave threads
2014-08-28 15:17:51 5016 [Note] Forcefully disconnecting 0 remaining clients
2014-08-28 15:17:51 5016 [Note] Binlog end
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'partition'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_METRICS'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_CMPMEM'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_CMP'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_LOCKS'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'INNODB_TRX'
2014-08-28 15:17:51 5016 [Note] Shutting down plugin 'InnoDB'
2014-08-28 15:17:51 5016 [Note] InnoDB: FTS optimize thread exiting.
2014-08-28 15:17:51 5016 [Note] InnoDB: Starting shutdown...
2014-08-28 15:17:53 5016 [Note] InnoDB: Shutdown completed; log sequence number 1625987
2014-08-28 15:17:53 5016 [Note] Shutting down plugin 'BLACKHOLE'
2014-08-28 15:17:53 5016 [Note] Shutting down plugin 'ARCHIVE'
2014-08-28 15:17:53 5016 [Note] Shutting down plugin 'MRG_MYISAM'
2014-08-28 15:17:53 5016 [Note] Shutting down plugin 'MyISAM'
2014-08-28 15:17:53 5016 [Note] Shutting down plugin 'MEMORY'
2014-08-28 15:17:53 5016 [Note] Shutting down plugin 'CSV'
2014-08-28 15:17:53 5016 [Note] Shutting down plugin 'sha256_password'
2014-08-28 15:17:53 5016 [Note] Shutting down plugin 'mysql_old_password'
2014-08-28 15:17:53 5016 [Note] Shutting down plugin 'mysql_native_password'
2014-08-28 15:17:53 5016 [Note] Shutting down plugin 'binlog'
2014-08-28 15:17:53 5016 [Note] wampmysqld: Shutdown complete

2014-08-28 15:17:54 8088 [Note] Plugin 'FEDERATED' is disabled.
2014-08-28 15:17:54 8088 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-28 15:17:54 8088 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-08-28 15:17:54 8088 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-08-28 15:17:54 8088 [Note] InnoDB: Not using CPU crc32 instructions
2014-08-28 15:17:54 8088 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-08-28 15:17:54 8088 [Note] InnoDB: Completed initialization of buffer pool
2014-08-28 15:17:54 8088 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-28 15:17:54 8088 [Note] InnoDB: 128 rollback segment(s) are active.
2014-08-28 15:17:54 8088 [Note] InnoDB: Waiting for purge to start
2014-08-28 15:17:54 8088 [Note] InnoDB: 5.6.12 started; log sequence number 1625987
2014-08-28 15:17:54 8088 [Note] Server hostname (bind-address): '*'; port: 3306
2014-08-28 15:17:54 8088 [Note] IPv6 is available.
2014-08-28 15:17:54 8088 [Note] - '::' resolves to '::';
2014-08-28 15:17:54 8088 [Note] Server socket created on IP: '::'.
2014-08-28 15:17:55 8088 [Note] Event Scheduler: Loaded 0 events
2014-08-28 15:17:55 8088 [Note] wampmysqld: ready for connections.
Version: '5.6.12-log' socket: '' port: 3306 MySQL Community Server (GPL)
2014-08-28 15:18:41 8088 [Note] wampmysqld: Normal shutdown

2014-08-28 15:18:41 8088 [Note] Giving 0 client threads a chance to die gracefully
2014-08-28 15:18:41 8088 [Note] Event Scheduler: Purging the queue. 0 events
2014-08-28 15:18:41 8088 [Note] Shutting down slave threads
2014-08-28 15:18:41 8088 [Note] Forcefully disconnecting 0 remaining clients
2014-08-28 15:18:41 8088 [Note] Binlog end
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'partition'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_METRICS'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_CMPMEM'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_CMP'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_LOCKS'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'INNODB_TRX'
2014-08-28 15:18:41 8088 [Note] Shutting down plugin 'InnoDB'
2014-08-28 15:18:41 8088 [Note] InnoDB: FTS optimize thread exiting.
2014-08-28 15:18:41 8088 [Note] InnoDB: Starting shutdown...
2014-08-28 15:18:42 8088 [Note] InnoDB: Shutdown completed; log sequence number 1625997
2014-08-28 15:18:42 8088 [Note] Shutting down plugin 'BLACKHOLE'
2014-08-28 15:18:42 8088 [Note] Shutting down plugin 'ARCHIVE'
2014-08-28 15:18:42 8088 [Note] Shutting down plugin 'MRG_MYISAM'
2014-08-28 15:18:42 8088 [Note] Shutting down plugin 'MyISAM'
2014-08-28 15:18:42 8088 [Note] Shutting down plugin 'MEMORY'
2014-08-28 15:18:42 8088 [Note] Shutting down plugin 'CSV'
2014-08-28 15:18:42 8088 [Note] Shutting down plugin 'sha256_password'
2014-08-28 15:18:42 8088 [Note] Shutting down plugin 'mysql_old_password'
2014-08-28 15:18:42 8088 [Note] Shutting down plugin 'mysql_native_password'
2014-08-28 15:18:42 8088 [Note] Shutting down plugin 'binlog'
2014-08-28 15:18:42 8088 [Note] wampmysqld: Shutdown complete

2014-08-28 15:18:50 7004 [Note] Plugin 'FEDERATED' is disabled.
2014-08-28 15:18:50 7004 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-28 15:18:50 7004 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-08-28 15:18:50 7004 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-08-28 15:18:50 7004 [Note] InnoDB: Not using CPU crc32 instructions
2014-08-28 15:18:50 7004 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-08-28 15:18:50 7004 [Note] InnoDB: Completed initialization of buffer pool
2014-08-28 15:18:50 7004 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-28 15:18:50 7004 [Note] InnoDB: 128 rollback segment(s) are active.
2014-08-28 15:18:50 7004 [Note] InnoDB: Waiting for purge to start
2014-08-28 15:18:50 7004 [Note] InnoDB: 5.6.12 started; log sequence number 1625997
2014-08-28 15:18:50 7004 [Note] Server hostname (bind-address): '*'; port: 3306
2014-08-28 15:18:50 7004 [Note] IPv6 is available.
2014-08-28 15:18:50 7004 [Note] - '::' resolves to '::';
2014-08-28 15:18:50 7004 [Note] Server socket created on IP: '::'.
2014-08-28 15:18:50 7004 [Note] Event Scheduler: Loaded 0 events
2014-08-28 15:18:50 7004 [Note] wampmysqld: ready for connections.
Version: '5.6.12-log' socket: '' port: 3306 MySQL Community Server (GPL)
2014-08-28 15:24:00 5452 [Note] Plugin 'FEDERATED' is disabled.
2014-08-28 15:24:00 5452 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-28 15:24:00 5452 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-08-28 15:24:00 5452 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-08-28 15:24:00 5452 [Note] InnoDB: Not using CPU crc32 instructions
2014-08-28 15:24:00 5452 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-08-28 15:24:00 5452 [Note] InnoDB: Completed initialization of buffer pool
2014-08-28 15:24:01 5452 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-28 15:24:01 5452 [Note] InnoDB: The log sequence numbers 1625997 and 1625997 in ibdata files do not match the log sequence number 1626007 in the ib_logfiles!
2014-08-28 15:24:01 5452 [Note] InnoDB: Database was not shutdown normally!
2014-08-28 15:24:01 5452 [Note] InnoDB: Starting crash recovery.
2014-08-28 15:24:01 5452 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-08-28 15:24:03 5452 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bdemo/data uses space ID: 6 at filepath: .\bdemo\data.ibd. Cannot open tablespace gallery1/register which uses space ID: 6 at filepath: .\gallery1\register.ibd
InnoDB: Error: could not open single-table tablespace file .\gallery1\register.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2014-08-28 15:24:19 1564 [Note] Plugin 'FEDERATED' is disabled.
2014-08-28 15:24:19 1564 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-28 15:24:19 1564 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-08-28 15:24:19 1564 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-08-28 15:24:19 1564 [Note] InnoDB: Not using CPU crc32 instructions
2014-08-28 15:24:19 1564 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-08-28 15:24:19 1564 [Note] InnoDB: Completed initialization of buffer pool
2014-08-28 15:24:19 1564 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-28 15:24:19 1564 [Note] InnoDB: The log sequence numbers 1625997 and 1625997 in ibdata files do not match the log sequence number 1626007 in the ib_logfiles!
2014-08-28 15:24:19 1564 [Note] InnoDB: Database was not shutdown normally!
2014-08-28 15:24:19 1564 [Note] InnoDB: Starting crash recovery.
2014-08-28 15:24:19 1564 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-08-28 15:24:19 1564 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bdemo/data uses space ID: 6 at filepath: .\bdemo\data.ibd. Cannot open tablespace gallery1/register which uses space ID: 6 at filepath: .\gallery1\register.ibd
InnoDB: Error: could not open single-table tablespace file .\gallery1\register.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2014-08-28 16:06:05 4588 [Note] Plugin 'FEDERATED' is disabled.
2014-08-28 16:06:05 4588 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-28 16:06:05 4588 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-08-28 16:06:05 4588 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-08-28 16:06:05 4588 [Note] InnoDB: Not using CPU crc32 instructions
2014-08-28 16:06:05 4588 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-08-28 16:06:05 4588 [Note] InnoDB: Completed initialization of buffer pool
2014-08-28 16:06:05 4588 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-28 16:06:05 4588 [Note] InnoDB: The log sequence numbers 1625997 and 1625997 in ibdata files do not match the log sequence number 1626007 in the ib_logfiles!
2014-08-28 16:06:05 4588 [Note] InnoDB: Database was not shutdown normally!
2014-08-28 16:06:05 4588 [Note] InnoDB: Starting crash recovery.
2014-08-28 16:06:05 4588 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-08-28 16:06:06 4588 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bdemo/data uses space ID: 6 at filepath: .\bdemo\data.ibd. Cannot open tablespace gallery1/register which uses space ID: 6 at filepath: .\gallery1\register.ibd
InnoDB: Error: could not open single-table tablespace file .\gallery1\register.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2014-08-28 16:06:12 6632 [Note] Plugin 'FEDERATED' is disabled.
2014-08-28 16:06:12 6632 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-28 16:06:12 6632 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-08-28 16:06:12 6632 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-08-28 16:06:12 6632 [Note] InnoDB: Not using CPU crc32 instructions
2014-08-28 16:06:12 6632 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-08-28 16:06:12 6632 [Note] InnoDB: Completed initialization of buffer pool
2014-08-28 16:06:13 6632 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-28 16:06:13 6632 [Note] InnoDB: The log sequence numbers 1625997 and 1625997 in ibdata files do not match the log sequence number 1626007 in the ib_logfiles!
2014-08-28 16:06:13 6632 [Note] InnoDB: Database was not shutdown normally!
2014-08-28 16:06:13 6632 [Note] InnoDB: Starting crash recovery.
2014-08-28 16:06:13 6632 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-08-28 16:06:13 6632 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bdemo/data uses space ID: 6 at filepath: .\bdemo\data.ibd. Cannot open tablespace gallery1/register which uses space ID: 6 at filepath: .\gallery1\register.ibd
InnoDB: Error: could not open single-table tablespace file .\gallery1\register.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2014-08-28 16:28:09 648 [Note] Plugin 'FEDERATED' is disabled.
2014-08-28 16:28:09 648 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-28 16:28:09 648 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-08-28 16:28:09 648 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-08-28 16:28:09 648 [Note] InnoDB: Not using CPU crc32 instructions
2014-08-28 16:28:09 648 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-08-28 16:28:09 648 [Note] InnoDB: Completed initialization of buffer pool
2014-08-28 16:28:09 648 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-28 16:28:09 648 [Note] InnoDB: The log sequence numbers 1625997 and 1625997 in ibdata files do not match the log sequence number 1626007 in the ib_logfiles!
2014-08-28 16:28:09 648 [Note] InnoDB: Database was not shutdown normally!
2014-08-28 16:28:09 648 [Note] InnoDB: Starting crash recovery.
2014-08-28 16:28:09 648 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-08-28 16:28:09 648 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bdemo/data uses space ID: 6 at filepath: .\bdemo\data.ibd. Cannot open tablespace gallery1/register which uses space ID: 6 at filepath: .\gallery1\register.ibd
InnoDB: Error: could not open single-table tablespace file .\gallery1\register.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2014-08-28 16:28:52 6300 [Note] Plugin 'FEDERATED' is disabled.
2014-08-28 16:28:52 6300 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-28 16:28:52 6300 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-08-28 16:28:52 6300 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-08-28 16:28:52 6300 [Note] InnoDB: Not using CPU crc32 instructions
2014-08-28 16:28:52 6300 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-08-28 16:28:52 6300 [Note] InnoDB: Completed initialization of buffer pool
2014-08-28 16:28:52 6300 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-28 16:28:52 6300 [Note] InnoDB: The log sequence numbers 1625997 and 1625997 in ibdata files do not match the log sequence number 1626007 in the ib_logfiles!
2014-08-28 16:28:52 6300 [Note] InnoDB: Database was not shutdown normally!
2014-08-28 16:28:52 6300 [Note] InnoDB: Starting crash recovery.
2014-08-28 16:28:52 6300 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-08-28 16:28:52 6300 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bdemo/data uses space ID: 6 at filepath: .\bdemo\data.ibd. Cannot open tablespace gallery1/register which uses space ID: 6 at filepath: .\gallery1\register.ibd
InnoDB: Error: could not open single-table tablespace file .\gallery1\register.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2014-08-28 16:38:17 2276 [Note] Plugin 'FEDERATED' is disabled.
2014-08-28 16:38:17 2276 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-28 16:38:17 2276 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-08-28 16:38:17 2276 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-08-28 16:38:17 2276 [Note] InnoDB: Not using CPU crc32 instructions
2014-08-28 16:38:17 2276 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-08-28 16:38:17 2276 [Note] InnoDB: Completed initialization of buffer pool
2014-08-28 16:38:17 2276 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-28 16:38:17 2276 [Note] InnoDB: The log sequence numbers 1625997 and 1625997 in ibdata files do not match the log sequence number 1626007 in the ib_logfiles!
2014-08-28 16:38:17 2276 [Note] InnoDB: Database was not shutdown normally!
2014-08-28 16:38:17 2276 [Note] InnoDB: Starting crash recovery.
2014-08-28 16:38:17 2276 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-08-28 16:38:17 2276 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bdemo/data uses space ID: 6 at filepath: .\bdemo\data.ibd. Cannot open tablespace gallery1/register which uses space ID: 6 at filepath: .\gallery1\register.ibd
InnoDB: Error: could not open single-table tablespace file .\gallery1\register.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2014-08-28 16:38:40 3952 [Note] Plugin 'FEDERATED' is disabled.
2014-08-28 16:38:40 3952 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-28 16:38:40 3952 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-08-28 16:38:40 3952 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-08-28 16:38:40 3952 [Note] InnoDB: Not using CPU crc32 instructions
2014-08-28 16:38:40 3952 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-08-28 16:38:40 3952 [Note] InnoDB: Completed initialization of buffer pool
2014-08-28 16:38:40 3952 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-28 16:38:40 3952 [Note] InnoDB: The log sequence numbers 1625997 and 1625997 in ibdata files do not match the log sequence number 1626007 in the ib_logfiles!
2014-08-28 16:38:40 3952 [Note] InnoDB: Database was not shutdown normally!
2014-08-28 16:38:40 3952 [Note] InnoDB: Starting crash recovery.
2014-08-28 16:38:40 3952 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-08-28 16:38:40 3952 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bdemo/data uses space ID: 6 at filepath: .\bdemo\data.ibd. Cannot open tablespace gallery1/register which uses space ID: 6 at filepath: .\gallery1\register.ibd
InnoDB: Error: could not open single-table tablespace file .\gallery1\register.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2014-08-28 16:38:53 1652 [Note] Plugin 'FEDERATED' is disabled.
2014-08-28 16:38:53 1652 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-28 16:38:53 1652 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-08-28 16:38:53 1652 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-08-28 16:38:53 1652 [Note] InnoDB: Not using CPU crc32 instructions
2014-08-28 16:38:53 1652 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-08-28 16:38:53 1652 [Note] InnoDB: Completed initialization of buffer pool
2014-08-28 16:38:53 1652 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-28 16:38:53 1652 [Note] InnoDB: The log sequence numbers 1625997 and 1625997 in ibdata files do not match the log sequence number 1626007 in the ib_logfiles!
2014-08-28 16:38:53 1652 [Note] InnoDB: Database was not shutdown normally!
2014-08-28 16:38:53 1652 [Note] InnoDB: Starting crash recovery.
2014-08-28 16:38:53 1652 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-08-28 16:38:53 1652 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bdemo/data uses space ID: 6 at filepath: .\bdemo\data.ibd. Cannot open tablespace gallery1/register which uses space ID: 6 at filepath: .\gallery1\register.ibd
InnoDB: Error: could not open single-table tablespace file .\gallery1\register.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2014-08-28 16:38:57 6800 [Note] Plugin 'FEDERATED' is disabled.
2014-08-28 16:38:57 6800 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-28 16:38:57 6800 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-08-28 16:38:57 6800 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-08-28 16:38:57 6800 [Note] InnoDB: Not using CPU crc32 instructions
2014-08-28 16:38:57 6800 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-08-28 16:38:57 6800 [Note] InnoDB: Completed initialization of buffer pool
2014-08-28 16:38:57 6800 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-28 16:38:57 6800 [Note] InnoDB: The log sequence numbers 1625997 and 1625997 in ibdata files do not match the log sequence number 1626007 in the ib_logfiles!
2014-08-28 16:38:57 6800 [Note] InnoDB: Database was not shutdown normally!
2014-08-28 16:38:57 6800 [Note] InnoDB: Starting crash recovery.
2014-08-28 16:38:57 6800 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-08-28 16:38:57 6800 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bdemo/data uses space ID: 6 at filepath: .\bdemo\data.ibd. Cannot open tablespace gallery1/register which uses space ID: 6 at filepath: .\gallery1\register.ibd
InnoDB: Error: could not open single-table tablespace file .\gallery1\register.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2014-08-28 16:47:28 4228 [Note] Plugin 'FEDERATED' is disabled.
2014-08-28 16:47:28 4228 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-28 16:47:28 4228 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-08-28 16:47:28 4228 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-08-28 16:47:28 4228 [Note] InnoDB: Not using CPU crc32 instructions
2014-08-28 16:47:28 4228 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-08-28 16:47:28 4228 [Note] InnoDB: Completed initialization of buffer pool
2014-08-28 16:47:28 4228 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-28 16:47:28 4228 [Note] InnoDB: The log sequence numbers 1625997 and 1625997 in ibdata files do not match the log sequence number 1626007 in the ib_logfiles!
2014-08-28 16:47:28 4228 [Note] InnoDB: Database was not shutdown normally!
2014-08-28 16:47:28 4228 [Note] InnoDB: Starting crash recovery.
2014-08-28 16:47:28 4228 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-08-28 16:47:28 4228 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bdemo/data uses space ID: 6 at filepath: .\bdemo\data.ibd. Cannot open tablespace gallery1/register which uses space ID: 6 at filepath: .\gallery1\register.ibd
InnoDB: Error: could not open single-table tablespace file .\gallery1\register.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2014-08-28 16:48:19 2276 [Note] Plugin 'FEDERATED' is disabled.
2014-08-28 16:48:19 2276 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-28 16:48:19 2276 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-08-28 16:48:19 2276 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-08-28 16:48:19 2276 [Note] InnoDB: Not using CPU crc32 instructions
2014-08-28 16:48:19 2276 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-08-28 16:48:19 2276 [Note] InnoDB: Completed initialization of buffer pool
2014-08-28 16:48:20 2276 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-28 16:48:20 2276 [Note] InnoDB: The log sequence numbers 1625997 and 1625997 in ibdata files do not match the log sequence number 1626007 in the ib_logfiles!
2014-08-28 16:48:20 2276 [Note] InnoDB: Database was not shutdown normally!
2014-08-28 16:48:20 2276 [Note] InnoDB: Starting crash recovery.
2014-08-28 16:48:20 2276 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-08-28 16:48:20 2276 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bdemo/data uses space ID: 6 at filepath: .\bdemo\data.ibd. Cannot open tablespace gallery1/register which uses space ID: 6 at filepath: .\gallery1\register.ibd
InnoDB: Error: could not open single-table tablespace file .\gallery1\register.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.

Options: ReplyQuote
Re: wamp server does not turn GREEN
Posted by: RiggsFolly (---.dynamic.dsl.as9105.com)
Date: August 28, 2014 01:33PM

Yup that says it all.

You have somehow managed to corrupt one of your INNODB databases and it cannot recover the problem.
Maybe you deleted something?

If you dont want the database anymore you can just delete the \bdemo folder and it should come up again.

Otherwise I suggest you restore the last backup for that database or follow the instructions it gives after each attempted recovery fails.

Have a look at the MySQL documentation to get a better idea about how to proceed.


INNODB is a lot more complex that MYISAM and you need to understand what needs to be done to maintain a backup should something like this happen.

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.1.3 32bit & 64bit)
<Apache 2.4.29/2.2.31> <PHP 7.2/7.1/7.0/5.6/5.5/5.4> <MySQL 5.7.19/5.6.39/5.5.28>
<MariaDB 10.2.14> <phpMyAdmin4.8.1> <MySQL Workbench 6.3.10>

Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your MySQL databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

Options: ReplyQuote
Re: wamp server does not turn GREEN
Posted by: Ritika (117.201.176.---)
Date: August 28, 2014 01:55PM

i have got the backup of my db. So shall i uninstall wamp and start the installation again.

Options: ReplyQuote
Re: wamp server does not turn GREEN
Posted by: RiggsFolly (---.dynamic.dsl.as9105.com)
Date: August 28, 2014 02:05PM

No need to uninstall WAMPServer, just restore the database backup

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.1.3 32bit & 64bit)
<Apache 2.4.29/2.2.31> <PHP 7.2/7.1/7.0/5.6/5.5/5.4> <MySQL 5.7.19/5.6.39/5.5.28>
<MariaDB 10.2.14> <phpMyAdmin4.8.1> <MySQL Workbench 6.3.10>

Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your MySQL databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

Options: ReplyQuote
Re: wamp server does not turn GREEN
Posted by: Ritika (117.201.176.---)
Date: August 28, 2014 04:33PM

Its all working now.

Thanx for ur time n guidance riggs. I appreciate ur help.


Cheers.

Options: ReplyQuote
Re: wamp server does not turn GREEN
Posted by: pws (---.cable.teksavvy.com)
Date: August 28, 2014 08:36PM

Thanks in advance for your advice.

Performed Windows 7 - Install of WampServer 2.5 - to e: drive

Had to go to Apache, install service, and then service start
Apache service is running - localhost is up from web browser with wampserver homepage
Test port 80 shows apache running

Went to MySQL, install service, and then service start.
Did not see a command prompt appear during the "install" as occurred during Apache install
MySQL Service does not start
No log file created or available to use.
Verified no stray my.ini files etc. The only copy is located at e:\wamp\bin\mysql\mysql5.6.17\my.ini

Window services show no MySQL services running - wampapache64 is running as expected

If I try to go to phpmyadmin then I get a MySQL #2002 error - No connection could be made because the target machine actively refused it. The server is not responding (or the local server's socket is not correctly configured).

What can you suggest I try?

Again many thanks.
Paul

Options: ReplyQuote
Re: wamp server does not turn GREEN
Posted by: RiggsFolly (---.dynamic.dsl.as9105.com)
Date: August 29, 2014 01:35AM

Hi Paul,

Well for a change it looks like you have done quite a bit of your own research.

If MySQL is not started and there is nothing in the MySQL error log, then have a look at the Windows Event Viewer.

Click the 'Windows Logs' link on the left panel menu and then the Application link below that.

Look for messages from 'MYSQL' there should be a useful error message describing the problem.

If you cannot work out whats wrong, port the error here

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.1.3 32bit & 64bit)
<Apache 2.4.29/2.2.31> <PHP 7.2/7.1/7.0/5.6/5.5/5.4> <MySQL 5.7.19/5.6.39/5.5.28>
<MariaDB 10.2.14> <phpMyAdmin4.8.1> <MySQL Workbench 6.3.10>

Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your MySQL databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

Options: ReplyQuote
Re: wamp server does not turn GREEN
Posted by: pws (---.cable.teksavvy.com)
Date: August 29, 2014 02:08AM

Thanks RiggsFoley,

I've never known of the event viewer in windows before - quite handy!

Yes, I see the same Event ID 100 error with Source MySQL occurred numerous times as I reattempted.

Fatal error: Can't open and lock privilege tables: Can't find file 'user' (errno: 2 - No such file or directory).

I understand that a file user is not in the place in which it is expected... the closest file I can find is user.frm but I don't think that is what is being looked for...

Are you familiar with the user file and where it is expected?
I'm suspecting that this issue might have something to do with the installation not happening on the usual c: partition.

In the my.ini file, all directories appear to be pointing to e: drive locations as one would expect.

The exception is 'socket = /tmp/mysql.sock' which is a bit of an alarm bell because it is critical to the [client] and [wampmysqld] processing. I've done a search for mysql.sock on all my drives and not found it.

What are your thoughts?

I'm tempted to uninstall and reinstall on c: to alleviate that nagging scenario from my head.

Thanks again.

Paul

Options: ReplyQuote
Re: wamp server does not turn GREEN
Posted by: RiggsFolly (---.dynamic.dsl.as9105.com)
Date: August 29, 2014 03:24AM

No need to install on C: I install on D: with no problem.

It sounds like you may have, or, may have had another MySQL installed.

Anyway, search for my.ini and my.cnf files on your C: drive. Sometimes windows builds have a my.ini in the C:\windows folder structure somewhere, which is in the MySQL search path.

Anyway search for these 2 files and if you see any outside the \wamp folder structure, delete them.

Also check you only have a service called wampmysqld or wampmysqld64 and NOT one called MYSQL
Also look for folders that may have contained a MYSQL install.
If another MYSQL is installed, uninstall it, AFTER checking you done want to keep any of its databases.

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.1.3 32bit & 64bit)
<Apache 2.4.29/2.2.31> <PHP 7.2/7.1/7.0/5.6/5.5/5.4> <MySQL 5.7.19/5.6.39/5.5.28>
<MariaDB 10.2.14> <phpMyAdmin4.8.1> <MySQL Workbench 6.3.10>

Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your MySQL databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

Options: ReplyQuote
Re: wamp server does not turn GREEN
Posted by: pws (---.cable.teksavvy.com)
Date: August 29, 2014 08:09AM

Thanks again RiggsFolly,

Absolutely positively no my.ini or my.cnf files anywhere else on my computer. my.cnf does not exist at all only my.ini in the mysql directory.

Checked the services wampapache64 and wampmysqld64 exist - no other services with SQL referenced exist.
Incidentally, I tried to start the wampmysqld64 service from the service console and it produces an "Error 1067: The process terminated unexpectedly."

Checked directories for previous installs, found an entry under windows/program files (x86)/Microsoft SQL server/110/Shared... the only content was a file msasxpress.dll. This folder seems to have been created at the same time as some folders that were part of the MS OFfice install. This folder had the same timestamp as the Microsoft.NET folder. In the MS Office installer I unselected options for MS InfoPath which had .NET Programmability Support therein and then deleted these MS SQL Server and MS.NET folders.

Deleting those folders did not resolve the issue.


I did a string search of SQL on the files of my computer looking for a forgotten other install and could not find anything. SQL anywhere appears to be used by Inuit Turbotax.

From command prompt I went to the mysql5.6.17/bin directory and tried to run the mysql.exe from there and that gave a similar error 2003 "Can't connect to MySQL server on 'localhost' <10061>

I cant find the install or previous install that is conflicting...

:-(

Options: ReplyQuote
Re: wamp server does not turn GREEN
Posted by: RiggsFolly (---.dynamic.dsl.as9105.com)
Date: August 29, 2014 10:08AM

What does Event Viewer say about the MySQL error.

If its still complaining about 'user' then you have done something odd as this file lives in ....mysqlx.y.z/data/mysql and that is the database that mysql uses to manage itself.

So maybe the install has somehow failed or youi have deleted something by mistake.


Maybe we should try a TeamViewer troubleshooting session. If thats ok, install TV and semd me a Private message containing the TV - ID and PASSWORD
I will connect and have a closer look.

I am in GMT +1 timezone, available 09:00 - 16:00 and into the evening most evenings.

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.1.3 32bit & 64bit)
<Apache 2.4.29/2.2.31> <PHP 7.2/7.1/7.0/5.6/5.5/5.4> <MySQL 5.7.19/5.6.39/5.5.28>
<MariaDB 10.2.14> <phpMyAdmin4.8.1> <MySQL Workbench 6.3.10>

Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your MySQL databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

Options: ReplyQuote
Re: wamp server does not turn GREEN
Posted by: pws (---.cable.teksavvy.com)
Date: August 29, 2014 01:59PM

ok thanks,

Same issue in event logger, cant find file user.

I havent really done anything except delete a SQL directory that looked largely empty and from a legacy install, so the error remains.

I am away for a couple of days but will re-install when I get back and let you know.

I am hoping there is some issue during the install.

Regards,
Paul

Options: ReplyQuote
Re: wamp server does not turn GREEN
Posted by: Ritika (117.201.179.---)
Date: August 30, 2014 12:19AM

Hi there, need you help plz.

I m developing a hospital management website demo,

this is my patient registration form->

<?php include("include/header.php"winking smiley;?>
<?php include("include/leftbar.php"winking smiley;?>

<div id="center-column">
<div class="top-bar">
<h1>Patient Registration Form</h1>

</div><br />
<div class="select-bar"> </div>

<form action="insert_p_register.php" method="post" enctype="multipart/form-data">
<table>
<tr>
<td>First Name</td>
<td><input type="text" name="fname" required/> </td>
</tr>


<tr>
<td>Last Name </td>
<td><input type="text" name="lname" required/> </td>
</tr>
<tr>
<script type="text/javascript" src="countries.js"></script>
<td>Country </td>

<td>
<select onchange="print_state('state',this.selectedIndex);" id="country" name ="country" style="width:57%;" required></select>
<br />
</td>
</tr>

<tr>
<td>State</td>
<td>
<select name ="state" id ="state" style="width:57%;" required></select>
<script language="javascript">print_country("country"winking smiley;</script>
</td>
</tr>
<tr>
<td><input type="submit" style="width:60%;color:#000; font-size:large"/> </td>
</tr>
</table>
</form>
</div>

After registration, i have "display_all_patients" detail page, in which i have given a link to edit, hre the page ->

<?php include("include/header.php"winking smiley;?>
<?php include("include/leftbar.php"winking smiley;?>


<div id="center-column">
<div class="top-bar">
<h1>Registered Patients Details</h1>

</div><br />
<div class="select-bar"> </div>

<form>

<?php
include("include/connection.php"winking smiley;
$select= "select * from p_registration";
$query= mysql_query($select);
while($row=mysql_fetch_array($query))
{
@$fnm.='<td>'.$row['fname'].'</td>';
@$lnm.='<td>'.$row['lname'].'</td>';
@$country.='<td>'.$row['country'].'</td>';
@$state.='<td>'.$row['state'].'</td>';
@$edit.='<td>'. '<a href="edit_patient.php?p_id='.$row['id'].'">EDIT</a>'.'</td>';
}

echo '
<table style="font-size:14px; border: 5px solid #FF6600;" cellspacing="11px">
<tbody>
<tr>
<td><b>First Name</td>'.$fnm .'
</tr>
<tr>
<td><b>Last Name</td>'.$lnm .'
</tr>
<tr>
<td><b>Country</td>'.$country .'
</tr>

<tr>
<td><b>State</td>'.$state .'
</tr>
<tr>
<td><b>Edit</td>'.$edit .'
</tr>


</tbody>
</table>';

?>
</form>
</div>

My problem is, when i am clicking on the "Edit link", i am getting all the values to edit accept the "state" dropdown.

here is the "edit_patient_details" page ->

<?php include("include/header.php"winking smiley;?>
<?php include("include/leftbar.php"winking smiley;?>


<div id="center-column">
<script type="text/javascript" src="countries.js"></script>
<script language="javascript">print_country("country"winking smiley;</script>
<div class="top-bar">
<h1>Edit Patients Details</h1>

</div><br />
<div class="select-bar"> </div>
<?php
$p_id= $_GET['p_id'];
include("include/connection.php"winking smiley;
$select= "select * from p_registration where id='$p_id'";
$data= mysql_query($select);
$row= mysql_fetch_array($data);
@$fnm.='<td>'. '<input type="text" name="fname" value="'.$row['fname'].'"/>'.'</td>';
@$lnm.='<td>'.'<input type="text" name="fname" value="'.$row['lname'].'"/>'.'</td>';
@$country.='<td>'.'<select onchange="print_state('."state".',this.selectedIndex);" id="country" name ="country" style="width:57%;" required>

</select>'.'
<br />'.'</td>';



@$state.='<td>'.'<select name ="state" id ="state" style="width:57%;" required></select>'.'<script language="javascript">print_country("country"winking smiley;</script>'.'</td>';

echo '
<table style="font-size:14px; border: 5px solid #FF6600;" cellspacing="11px">
<tbody>
<tr>
<td><b>First Name</td>'.$fnm .'
</tr>
<tr>
<td><b>Last Name</td>'.$lnm .'
</tr>
<tr>
<td><b>Country</td>'.$country .'
</tr>

<tr>
<td><b>State</td>'.$state .'
</tr>
<tr>
<td><b>Update</td>'.$update .'
</tr>


</tbody>
</table>';

?>



</div>


.... Please help....
Thanx
Ritika

Options: ReplyQuote
Re: wamp server does not turn GREEN
Posted by: RiggsFolly (---.dynamic.dsl.as9105.com)
Date: August 31, 2014 02:45PM

This is not a How to code PHP site.

Please try 'StackOverflow.com'

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.1.3 32bit & 64bit)
<Apache 2.4.29/2.2.31> <PHP 7.2/7.1/7.0/5.6/5.5/5.4> <MySQL 5.7.19/5.6.39/5.5.28>
<MariaDB 10.2.14> <phpMyAdmin4.8.1> <MySQL Workbench 6.3.10>

Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your MySQL databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

Options: ReplyQuote
Re: wamp server does not turn GREEN
Posted by: chriscopland (---.range86-182.btcentralplus.com)
Date: September 02, 2014 03:40PM

I just had a look through this thread I had the Not Green problem which was solved by removing three files windows creates

The files are: ib_logfile() ib_logfile1 and ibdata1

They can be found in C:/ wamp/bin/mysql/mysqlx.x.x/data Where (mysqlx.x.x) is your version of wamp.

I copied the files saved them to a new folder as a backup called deleted files then restarted my computer

Low and behold This fixed the problem.

Hope this helps someone.

Options: ReplyQuote
Re: wamp server does not turn GREEN
Posted by: RiggsFolly (---.dynamic.dsl.as9105.com)
Date: September 02, 2014 05:07PM

DONT ATTEMPT WHAT WAS SUGGESTED IN THE PREVIOUS POST AS A SOLUTION UNLESS YOU UNDERSTAND WHAT IT IS YOU ARE ACTUALLY DOING



Hello Chris,

If that solved your problem then you probably had a corrupted INNODB database.

If you look at your MySQL error log, you will probably see some messages informing you of the situation.

By default INNODB databases live in the ibdata1 file and before and after looks are kept in the ib_logfile0 and ib_logfile1 files.

If you delete these files you are actually deleting FOR EVER any/all INNODB databases that you may have created.

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.1.3 32bit & 64bit)
<Apache 2.4.29/2.2.31> <PHP 7.2/7.1/7.0/5.6/5.5/5.4> <MySQL 5.7.19/5.6.39/5.5.28>
<MariaDB 10.2.14> <phpMyAdmin4.8.1> <MySQL Workbench 6.3.10>

Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your MySQL databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

Options: ReplyQuote
Re: wamp server does not turn GREEN
Posted by: rosica (77.28.18.---)
Date: September 12, 2014 05:32PM

Hello , I have installed Wamp server and what I found was that when I ran Apache->Service->Test port 80 i got message: " Your port 80 is actually used by :
Server:Microsoft -IIS7.5

so then i erased IIS microsoft from control panel , actually i uninstalled it and then i tried to activate the wamp server , but i didn't got any results.. and the message for the used port is still there.. so what should i do next.

I'll be very thankful if someone has some idea..
Thanks a lot in advanced.

Options: ReplyQuote
Re: wamp server does not turn GREEN
Posted by: Otomatic (Moderator)
Date: September 12, 2014 06:20PM

Hi,

I don't know the names in English of functions to desactivate (My Windows is French).
- Control Panel
-- Programs & functions (May be other name)
-- Activate or desactivate Windows functions

All items below must be unchecked
-- Microsoft .NET Frameworks 3.5.1
--- Windows Communication Foundation (2 times)
-- Internet Services (IIS)
--- All items must be unchecked
-- Windows Activation Services
--- All items must be unchecked

OK
OK
It will be better to reboot.

------------------------------------------------------------------------------------------------------------
Wampserver 3.1.4 32 bit - Apache 2.4.35 - PHP 7.2.10/7.1.22/7.0.32/5.6.38 - MySQL 5.7.23 - MariaDB 10.3.9
Wampserver 3.1.4 64 bit - Apache 2.4.35 - PHP 7.2.10/7.1.22/7.0.32/5.6.38 - MySQL 5.7.23 - MariaDB 10.3.9
PhPMyadmin 4.8.3 - MysqlDumper 1.24.5
on W10 and W7 Pro 64 bit
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons
« Ce n'est pas parce qu'ils sont nombreux à avoir tort, qu'ils ont forcément raison. Coluche »
« It's not because they are many to be wrong, they are necessarily right. Coluche »

Options: ReplyQuote
Re: wamp server does not turn GREEN
Posted by: vacttox (197.210.54.---)
Date: August 22, 2018 10:04PM

Please my wamp logo is still orange. My apache service is running but my SQL is not. The start/resume button is showing green. When i go to windows services and try to start it, it tells me that it started and stopped and that services start and stop when there is no program to use them. PLEASE WHAT DO I DO NOW?

Options: ReplyQuote
Pages: Previous1234Next
Current Page: 3 of 4


Sorry, only registered users may post in this forum.