WampServer

The wampmysqld service keeps on terminating unexpectedly. There isn't much information logged in mysql.log. Here's whats in it:


2021-10-25 16:42:57 4668 [Note] Plugin 'FEDERATED' is disabled.
2021-10-25 16:42:57 4668 [Note] InnoDB: Using atomics to ref count buffer pool pages
2021-10-25 16:42:57 4668 [Note] InnoDB: The InnoDB memory heap is disabled
2021-10-25 16:42:57 4668 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2021-10-25 16:42:57 4668 [Note] InnoDB: Compressed tables use zlib 1.2.3
2021-10-25 16:42:57 4668 [Note] InnoDB: Not using CPU crc32 instructions
2021-10-25 16:42:57 4668 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2021-10-25 16:42:57 4668 [Note] InnoDB: Completed initialization of buffer pool
2021-10-25 16:42:57 4668 [Note] InnoDB: Highest supported file format is Barracuda.
2021-10-25 16:42:57 4668 [Note] InnoDB: Log scan progressed past the checkpoint lsn 88774913000
2021-10-25 16:42:57 4668 [Note] InnoDB: Database was not shutdown normally!
2021-10-25 16:42:57 4668 [Note] InnoDB: Starting crash recovery.
2021-10-25 16:42:57 4668 [Note] InnoDB: Reading tablespace information from the .ibd files...
2021-10-25 16:42:57 4668 [Note] InnoDB: Restoring possible half-written data pages
2021-10-25 16:42:57 4668 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 88774913504
2021-10-25 16:42:58 4668 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
2021-10-25 16:42:59 4668 [Note] InnoDB: 128 rollback segment(s) are active.
2021-10-25 16:42:59 4668 [Note] InnoDB: Waiting for purge to start
2021-10-25 16:42:59 4668 [Note] InnoDB: 5.6.17 started; log sequence number 88774913504
2021-10-25 16:42:59 4668 [Note] Server hostname (bind-address): '*'; port: 3306
2021-10-25 16:42:59 4668 [Note] IPv6 is available.
2021-10-25 16:42:59 4668 [Note] - '::' resolves to '::';
2021-10-25 16:42:59 4668 [Note] Server socket created on IP: '::'.
2021-10-25 16:42:59 4668 [Note] Event Scheduler: Loaded 0 events
2021-10-25 16:42:59 4668 [Note] wampmysqld: ready for connections.
Version: '5.6.17' socket: '' port: 3306 MySQL Community Server (GPL)

I have tried forcing recover (innodb_force_recovery = 1) and even took mysqldump of all databases and restored.

Wampserver ver 2.5
Mysql ver 5.6.17

Hi,

> Wampserver ver 2.5
> Mysql ver 5.6.17
Very old versions no longer supported.

> 2021-10-25 16:42:59 4668 [Note] wampmysqld: ready for connections.
> Version: '5.6.17' socket: '' port: 3306 MySQL Community Server (GPL)
MySQL is ready. What is the problem ?

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons

Otomatic Wrote:
-------------------------------------------------------
> Hi,
>
> > Wampserver ver 2.5
> > Mysql ver 5.6.17
> Very old versions no longer supported.

Yes, I understand. Can I just upgrade to the latest without loosing any configuration and application settings?

>
> > 2021-10-25 16:42:59 4668 [Note] wampmysqld:
> ready for connections.
> > Version: '5.6.17' socket: '' port: 3306 MySQL
> Community Server (GPL)
> MySQL is ready. What is the problem ?


Yes, the logs says MySQL is ready. But the wampmysqld service stops pretty randomly, sometimes in minutes, sometimes in hours. The log doesn't reflect any of that issue, it just says MySQL is ready for connection. However, Wamp icon turns orange and in the event viewer I can see following:

Faulting application name: mysqld.exe, version: 5.6.17.0, time stamp: 0x532358d8
Faulting module name: mysqld.exe, version: 5.6.17.0, time stamp: 0x532358d8
Exception code: 0xc0000005
Fault offset: 0x0001aca6
Faulting process id: 0xe18
Faulting application start time: 0x01d7c962f77be782
Faulting application path: c:\wamp\bin\mysql\mysql5.6.17\bin\mysqld.exe
Faulting module path: c:\wamp\bin\mysql\mysql5.6.17\bin\mysqld.exe
Report Id: 4c8f2b51-3556-11ec-80cf-109836a65a0c
Faulting package full name:
Faulting package-relative application ID:



Edited 1 time(s). Last edit at 10/26/2021 12:27AM by ashishs.

Hi,

> Can I just upgrade to the latest without loosing any configuration and application settings?
You back up your local sites and export your databases in SQL files.
This is exactly the same procedure as the transfer between local and a hosting company.

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons

Hi Otomatic,

I wampmysqld service terminated this morning at around 3AM. So it happened about 22 hours after last crash. I had set the service on auto-recovery, so it did start and is running at the moment. Any clue why this might be happening? Like I said, the error log says nothing.

>This is exactly the same procedure as the transfer between local and a hosting company.
I'm more concerned about PHP and plugins. I'm afraid current WAMPSERVER version 2.5 is too old, should I step upgrade or can directly upgrade to the latest?

Thanks

Hi,

See item 12 of Wampserver 3 - Some explanations

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons