Mysql problem on fresh 1.7.7 install. log seq does not match

Problems with the Windows version of XAMPP, questions, comments, and anything related.

Mysql problem on fresh 1.7.7 install. log seq does not match

Postby sadp » 04. December 2011 14:30

Hi,

i installed xampp-win32-1.7.7-VC9-installer.exe on a windowsxp sp3. An older 1.7.1 is working perfectly on it but it was time to update.

Problem: even without making any modification to *any* configuration file, if i start/stop mysql from the ControlPanel, i get this in the mysql_error log:


111204 14:58:20 [Note] Plugin 'FEDERATED' is disabled.
111204 14:58:20 InnoDB: The InnoDB memory heap is disabled
111204 14:58:20 InnoDB: Mutexes and rw_locks use Windows interlocked functions
111204 14:58:20 InnoDB: Compressed tables use zlib 1.2.3
111204 14:58:20 InnoDB: Initializing buffer pool, size = 16.0M
111204 14:58:20 InnoDB: Completed initialization of buffer pool
111204 14:58:20 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
111204 14:58:20 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...
111204 14:58:21 InnoDB: Waiting for the background threads to start
111204 14:58:22 InnoDB: 1.1.8 started; log sequence number 1595675
111204 14:58:22 [Note] Event Scheduler: Loaded 0 events
111204 14:58:22 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.16' socket: '' port: 3306 MySQL Community Server (GPL)


And this happens on *every* start/stop from the control panel. This is surely not normal. bin-log is not enabled in my.ini.

This is a fresh install (I uninstalled and reinstalled just to be sure it was not my fault).

The first entry was this (if it matters):
Code: Select all
111204 14:57:22 [Note] Plugin 'FEDERATED' is disabled.
111204 14:57:22 InnoDB: The InnoDB memory heap is disabled
111204 14:57:22 InnoDB: Mutexes and rw_locks use Windows interlocked functions
111204 14:57:22 InnoDB: Compressed tables use zlib 1.2.3
111204 14:57:22 InnoDB: Initializing buffer pool, size = 16.0M
111204 14:57:22 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file D:\xampp1.7.7\mysql\data\ibdata1 did not exist:
InnoDB: a new database to be created!
111204 14:57:22  InnoDB: Setting file D:\xampp1.7.7\mysql\data\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
111204 14:57:23  InnoDB: Log file D:\xampp1.7.7\mysql\data\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file D:\xampp1.7.7\mysql\data\ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
111204 14:57:23  InnoDB: Log file D:\xampp1.7.7\mysql\data\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file D:\xampp1.7.7\mysql\data\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: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
111204 14:57:25  InnoDB: Waiting for the background threads to start
111204 14:57:26 InnoDB: 1.1.8 started; log sequence number 0
111204 14:57:26 [Note] Event Scheduler: Loaded 0 events
111204 14:57:26 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.16'  socket: ''  port: 3306  MySQL Community Server (GPL)


PS: on old 1.7.1 in the mysql_error log, when stopping the server it said:

111204 13:13:44 [Note] Event Scheduler: Purging the queue. 0 events
111204 13:13:44 InnoDB: Starting shutdown...
111204 13:13:46 InnoDB: Shutdown completed; log sequence number 0 301151805
111204 13:13:46 [Warning] Forcing shutdown of 1 plugins
111204 13:13:46 [Note] mysql\bin\mysqld.exe: Shutdown complete

PS2: mysql is not installed as a service !
sadp
 
Posts: 3
Joined: 04. December 2011 14:14
Operating System: XP SP3

Re: Mysql problem on fresh 1.7.7 install. log seq does not m

Postby hackattack142 » 04. December 2011 16:43

okay, so the issue i am assuming is the "not shut down properly, crash recovery" thing.

That is normal for the way we are using mysql. There is no fully automated way to cleanly shutdown a mysql server if it is not running as a service so we end up just killing the process. The "normal" way would be to use the mysqladmin application and issue a shutdown but that requires a user to login with an account that has the necessary permissions.

If this bothers you, you can run it as a service, as is the "normal" way it would be used, and you should not have that issue.
XAMPP Control Panel Developer
Latest CP: viewtopic.php?f=16&t=48932
hackattack142
 
Posts: 703
Joined: 20. May 2011 23:29
Operating System: Windows 7 Ultimate SP1 64-Bit

Re: Mysql problem on fresh 1.7.7 install. log seq does not m

Postby sadp » 04. December 2011 16:50

I am running as administrator, i dont see a problem about having permissions. Yes, i know there is the option to install as service, but i dont understand what is so complicated about running as a regular program. In 1.7.1 this was working fine. I am not an expert, but running as a normal program sounds more simple than installing a service.
sadp
 
Posts: 3
Joined: 04. December 2011 14:14
Operating System: XP SP3

Re: Mysql problem on fresh 1.7.7 install. log seq does not m

Postby hackattack142 » 04. December 2011 17:53

When i say you need to login, i mean you need to login to the mysql server to do the shutdown, it does not matter what you are logged in as if you are not running as a service. I do not have the source code for the 1.7.1 version of the old control panel so I cannot speak with certainty but it appears from the 1.7.4 Control Panel version 2.5 Source Code the developers used to hardcode a root login to the to the mysqladmin console application to do the shutdown but they commented it out and switched to killing the process when not using a service. The mysqladmin method would require either leaving the root login to have an empty password (not a great idea) or changing the password and requiring the user to type in a password each time they want to stop the mysql server. All the command line administration commands for the mysqld application only apply if it is running as a service. Like i said, it was meant to be run as a service but it has a special command line option to be run standalone. The ideal situation is to not have to type in a password each time you wish to stop it or to hardcode in a empty password root login. In the newer 2.5 versions of the official control panels, they also stopped using that method and switched to killing the process if it is not a service. Installing the service is as easy as checking a box and selecting 'yes' to the install. The control commands are adjusted accordingly and the service control commands can are used avoiding this unclean shutdown or having to use special logins and privileges. There is also a newer control panel included with 1.7.7 called 'xampp-control-3-beta.exe' in the xampp root folder that has more functionality than the older control panel.
XAMPP Control Panel Developer
Latest CP: viewtopic.php?f=16&t=48932
hackattack142
 
Posts: 703
Joined: 20. May 2011 23:29
Operating System: Windows 7 Ultimate SP1 64-Bit

Re: Mysql problem on fresh 1.7.7 install. log seq does not m

Postby Sharley » 04. December 2011 19:09

@sadp
In earlier control panel versions lots of the returned messages where hard coded and often did not reflect the actual issues or avoided using unnecessary messages, now we have an active developer present in this thread who devotes many hours of his spare time for free to developing the newer and much more feature rich version3 CP - worth using instead of the older panels.

To find out how MySQL is stopped in 1.7.7 or indeed in any XAMPP version read the mysql_stop.bat file located in the xampp folder for the actual command used.

In some earlier XAMPP versions this stopping of MySQL used a different method namely
Code: Select all
xampp_cli.exe stop mysql
xampp_cli.exe was a closed source copyright protected file that was developed and included in the free and open source XAMPP suit by what has been described as a rogue member of the XAMPP development team and who is obviously no longer a member of that team.

It was introduced in 1.7.1 for the first time and dropped in 1.7.4 and later versions and there is no way of telling if xampp_cli.exe used the pv.exe method also but used different messages for the error log file (closed source).

This is the error log file entries created with the CP3 to start 1.7.7 MySQL and I used the xampp_cli.exe and the mysql_stop.bat file copied to the 1.7.7 xampp folder from the 1.7.1 xampp folder and as you can see the shutdown has a different message but similar to your posted error log message.
Code: Select all
111205  3:46:29 [Note] Plugin 'FEDERATED' is disabled.
111205  3:46:29 InnoDB: The InnoDB memory heap is disabled
111205  3:46:29 InnoDB: Mutexes and rw_locks use Windows interlocked functions
111205  3:46:29 InnoDB: Compressed tables use zlib 1.2.3
111205  3:46:29 InnoDB: Initializing buffer pool, size = 16.0M
111205  3:46:29 InnoDB: Completed initialization of buffer pool
111205  3:46:29 InnoDB: highest supported file format is Barracuda.
111205  3:46:29  InnoDB: Waiting for the background threads to start
111205  3:46:30 InnoDB: 1.1.8 started; log sequence number 1595675
111205  3:46:30 [Note] Event Scheduler: Loaded 0 events
111205  3:46:30 [Note] g:\xampp177\mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.16'  socket: ''  port: 3306  MySQL Community Server (GPL)
111205  3:46:44 [Note] g:\xampp177\mysql\bin\mysqld.exe: Normal shutdown

111205  3:46:44 [Note] Event Scheduler: Purging the queue. 0 events
111205  3:46:44  InnoDB: Starting shutdown...
111205  3:46:45  InnoDB: Shutdown completed; log sequence number 1595675
111205  3:46:45 [Note] g:\xampp177\mysql\bin\mysqld.exe: Shutdown complete
The end result is the same using both methods, the mysql process has been stopped.


So an alternate method used prior to the introduction of the xampp_cli.exe has been reintroduced to kill the mysql process using the mysql_stop.bat file namely pv.exe which has many other uses depending on what switch is added to the command line.

Your MySQL instance in XAMPP appears to be running normally and stopping normally even though the error.log file gives an indication that it did not stop normally but that behaviour has been adequately explained in this thread - millions of XAMPP users have exactly the same log file entries as you including me.

There is no need to run MySQL as a Windows service if you prefer, many developers do not start Apache or MySQL as a service.

If there is no more discussion about this issue then it will be closed in due course.

Best wishes. :)
User avatar
Sharley
AF Moderator
 
Posts: 3316
Joined: 03. October 2008 05:10
Location: Yeppoon, Australia Time Zone: GMT/UTC+10
Operating System: Win 7 Pro 32bit/XP Pro SP3

Re: Mysql problem on fresh 1.7.7 install. log seq does not m

Postby sadp » 05. December 2011 10:56

Thanks hackattack142 and Sharley for the full story! Maybe others will find search and find this thread informative.
sadp
 
Posts: 3
Joined: 04. December 2011 14:14
Operating System: XP SP3

Re: Mysql problem on fresh 1.7.7 install. log seq does not m

Postby Sharley » 05. December 2011 11:17

Thanks for the feedback. 8)

I will close this now as it seems to have been finalised.

Best wishes. :)
User avatar
Sharley
AF Moderator
 
Posts: 3316
Joined: 03. October 2008 05:10
Location: Yeppoon, Australia Time Zone: GMT/UTC+10
Operating System: Win 7 Pro 32bit/XP Pro SP3


Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 51 guests