MySQL Bugs: #44923: purge reached the head of the history list, but its length is still reported as

Bug #44923	purge reached the head of the history list, but its length is still reported as
Submitted:	18 May 2009 1:58	Modified:	9 Jul 2011 17:11
Reporter:	pines li	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S3 (Non-critical)
Version:	5.1.34	OS:	Linux (RHEL 5, kernel 2.6.18-92)
Assigned to:		CPU Architecture:	Any
Tags:	purge

Description:
I upgrade my mysql server from 5.0.22 to 5.1.34 , when mysql start up , this error will occur.
In err file , this warning will be found.
purge reached the head of the history list, but its length is still reported as 69705!

How to repeat:
I only know this error occured, when my database is upgrade from 5.0.22 to 5.1.34. And When i use "reset master", the bin-log can't begin with 0000001.

Thank you for the report.

Have you copied settings you used with server 5.0.22 to new installation? Please also provide full error log file.

This is My log:

090518 14:27:17 [Note] /usr/local/mysql/libexec/mysqld: Normal shutdown

090518 14:27:17 [Note] Event Scheduler: Purging the queue. 0 events
090518 14:27:19  InnoDB: Starting shutdown...
090518 14:27:21  InnoDB: Shutdown completed; log sequence number 1 1903862901
090518 14:27:21 [Warning] Forcing shutdown of 2 plugins
090518 14:27:21 [Note] /usr/local/mysql/libexec/mysqld: Shutdown complete

090518 14:27:21 mysqld_safe mysqld from pid file /usr/local/mysql/var/yfdep.crgs.pid ended
090518 14:27:48 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
090518 14:27:48  InnoDB: Started; log sequence number 1 1903862901
090518 14:27:48 [Note] Event Scheduler: Loaded 0 events
090518 14:27:48 [Note] /usr/local/mysql/libexec/mysqld: ready for connections.
Version: '5.1.34-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
090518 14:27:49  InnoDB: Warning: purge reached the head of the history list,
InnoDB: but its length is still reported as 697077! Make a detailed bug
InnoDB: report, and submit it to http://bugs.mysql.com
090518 14:31:13 [Warning] Stored routine 'sap1'.'parse_device_online_state': invalid value in column mysql.proc.character_set_client.
090518 14:31:13 [Warning] Stored routine 'sap1'.'parse_device_online_state': invalid value in column mysql.proc.collation_connection.
090518 14:31:13 [Warning] Stored routine 'sap1'.'parse_device_online_state': invalid value in column mysql.proc.db_collation.
090518 14:31:13 [Warning] Stored routine 'sap1'.'device_verify': invalid value in column mysql.proc.character_set_client.
090518 14:31:13 [Warning] Stored routine 'sap1'.'device_verify': invalid value in column mysql.proc.collation_connection.
090518 14:31:13 [Warning] Stored routine 'sap1'.'device_verify': invalid value in column mysql.proc.db_collation.
090518 14:31:13 [Warning] Stored routine 'sap1'.'get_device_templetid': invalid value in column mysql.proc.character_set_client.
090518 14:31:13 [Warning] Stored routine 'sap1'.'get_device_templetid': invalid value in column mysql.proc.collation_connection.
090518 14:31:13 [Warning] Stored routine 'sap1'.'get_device_templetid': invalid value in column mysql.proc.db_collation.
090518 14:31:13 [Warning] Stored routine 'sap1'.'get_defined_color4sys': invalid value in column mysql.proc.character_set_client.
090518 14:31:13 [Warning] Stored routine 'sap1'.'get_defined_color4sys': invalid value in column mysql.proc.collation_connection.
090518 14:31:13 [Warning] Stored routine 'sap1'.'get_defined_color4sys': invalid value in column mysql.proc.db_collation.
090518 14:31:13 [Warning] Stored routine 'sap1'.'update_graph_entity': invalid value in column mysql.proc.character_set_client.
090518 14:31:13 [Warning] Stored routine 'sap1'.'update_graph_entity': invalid value in column mysql.proc.collation_connection.
090518 14:31:13 [Warning] Stored routine 'sap1'.'update_graph_entity': invalid value in column mysql.proc.db_collation.
090518 14:31:13 [Warning] Stored routine 'sap1'.'update_graph_device_detail': invalid value in column mysql.proc.character_set_client.
090518 14:31:13 [Warning] Stored routine 'sap1'.'update_graph_device_detail': invalid value in column mysql.proc.collation_connection.
090518 14:31:13 [Warning] Stored routine 'sap1'.'update_graph_device_detail': invalid value in column mysql.proc.db_collation.
090518 14:31:13 [Warning] Stored routine 'sap1'.'device_if_verify': invalid value in column mysql.proc.character_set_client.
090518 14:31:13 [Warning] Stored routine 'sap1'.'device_if_verify': invalid value in column mysql.proc.collation_connection.
090518 14:31:13 [Warning] Stored routine 'sap1'.'device_if_verify': invalid value in column mysql.proc.db_collation.
090518 14:31:13 [Warning] Stored routine 'sap1'.'get_defined_color4if': invalid value in column mysql.proc.character_set_client.
090518 14:31:13 [Warning] Stored routine 'sap1'.'get_defined_color4if': invalid value in column mysql.proc.collation_connection.
090518 14:31:13 [Warning] Stored routine 'sap1'.'get_defined_color4if': invalid value in column mysql.proc.db_collation.

By the way, the new column of myslq.proc is NULL and there is any effect? Thanks for all.

Thank you for the feedback.

Please also provide configuration files for both 5.0.22 and 5.1.34. Have you run mysql_upgrade?

The configuration file is used default , I copy it  from the mysql installation path( /usr/local/mysql/share/mysql/my-large.conf).

And the mysql_upgrade is executed, there is no error.

Thank you for the feedback.

> The configuration file is used default 

I want to be sure if old InnoDB settings (which you used with version 5.0.22), especially log file sizes, are same as new. Please check.

Thanks a lot, 

This is the configuration:

5.1.34

[client]
password	= hello
port		= 3306
socket		= /tmp/mysql.sock
# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port		= 3306
socket		= /tmp/mysql.sock
skip-locking
key_buffer = 256M
max_allowed_packet = 1M
table_cache = 256
sort_buffer_size = 1M
read_buffer_size = 1M
read_rnd_buffer_size = 4M
myisam_sort_buffer_size = 64M
thread_cache_size = 100
query_cache_size= 16M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 8

# Disable Federated by default
skip-federated

log-bin=mysql-bin

# binary logging format - mixed recommended
binlog_format=mixed
#binlog_format=ROW

server-id	= 1

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 128M
sort_buffer_size = 128M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 128M
sort_buffer_size = 128M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

5.0.22

[client]
#password	= your_password
port		= 3306
socket		= /tmp/mysql.sock
default-character-set = gbk
# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port		= 3306
socket		= /tmp/mysql.sock
skip-locking
key_buffer = 256M
max_allowed_packet = 1M
table_cache = 256
sort_buffer_size = 1M
read_buffer_size = 1M
read_rnd_buffer_size = 4M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size= 16M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 8

default-character-set = gbk

# Replication Master Server (default)
# binary logging is required for replication
log-bin=mysql-bin

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id	= 1

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 128M
sort_buffer_size = 128M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 128M
sort_buffer_size = 128M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

See bug: http://bugs.mysql.com/bug.php?id=41165 probably duplicate.

I have read it, but my mysql version is 5.1.34. And I have found no answer from it.

Hi 

I am getting same kind of Error  while  upgrading 5.0.22 to 5.1.34. if any one solved this issue  please let me know.

Thanks

Bug #41165 is set as duplicate of this bug here.

Did you run the script mysql_upgrade?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

hi

sorry for delayed reply . i have treid with mysql_upgrade But no use.

Thank you for the feedback.

This error can show history log is corrupted. Do you still have error log from version 5.0? Was it possible what you experienced crash in 5.0 before upgrade?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

http://bugs.mysql.com/bug.php?id=61567 marked as duplicate of this one.

If not a result of InnoDB files corruption, then let's consider this as a duplicate of Bug #54965.

Related Bug #82213