MySQL Bugs: #42780: ERROR 1105 (HY000): Unknown error when execute show function status;

Bug #42780	ERROR 1105 (HY000): Unknown error when execute show function status;
Submitted:	12 Feb 2009 6:10	Modified:	12 Mar 2009 10:29
Reporter:	rajesh goswami	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Stored Routines	Severity:	S1 (Critical)
Version:	5.0.27-log	OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	show errors when execute show function status;

Description:
When I am going to execute show function status OR show procedure status command on Mysql prompt. It shows error like 'ERROR 1105 (HY000): Unknown error'
If idea... then please suggest me how to fix.

How to repeat:
It may be the shows same error on Mysql version 5.0.27-log

Thank you for the report.

But version 5.0.27 is old. Please try current version 5.0.75 (or 5.0.67 binaries we provide for) and inform us if problem till exists.

Thanks for the prompt reply. But I am facing this problem on My Production server, So Mysql version can not upgrade easily. If the solution is available in Existing versin then Please give me immediatly... Thanks

Thank you for the feedback.

But bugs system is for handling bugs in MySQL code only. Also we don't backport bug fixes.

Regarding to this problem we need to know circumstances problem is repeatable with to create test case. Please start with following questions:

1. Do you get error for every database?
2. Which exact output of SHOW FUNCTION STATUS in your case?
3. Is problem repeatable if do local copy, then upload dump of the database used in production?

1. Do you get error for every database? Yes
2. Which exact output of SHOW FUNCTION STATUS in your case? ERROR 1105 (HY000): Unknown error
3. Is problem repeatable if do local copy, then upload dump of the database used in production? No idea!

Thank you for the feedback.

Please send us your configuration file and full error log file.

The configuration file as under.
[net4nuts@u15285668 /]$ cat /etc/my.cnf 
[mysqld]
server-id=2
set-variable=local-infile=0
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1
#skip-networking
log-bin
log-slow-queries
long_query_time=0
log-long-format 
[mysql.server]
user=mysql
basedir=/var/lib
log_bin_trust_function_creators=1
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
#log-bin=/var/log/mysqlBinLogs
#log_slow_queries=/var/log/slowSELECT.log
#long_query_time=0
#log-long-format

But I cannot send full log files bcoze its size too large.
Inside I shown error "mysqld restarted" when I execute SHOW FUNCTION STATUS command on mysql prompt.

log files details as under :

thd->query at 0x1c84670 = select getSeq()
thd->thread_id=12
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0
090212 12:06:08  mysqld restarted
090212 12:06:08 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=u15285668-bin' to avoid this problem.
090212 12:06:08  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...
090212 12:06:08  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 3 772611315.
InnoDB: Doing recovery: scanned up to log sequence number 3 772620462
090212 12:06:08  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 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
InnoDB: Last MySQL binlog file position 0 41725, file name ./u15285668-bin.000069
090212 12:06:08  InnoDB: Started; log sequence number 3 772620462
090212 12:06:08 [Note] Recovering after a crash using u15285668-bin
090212 12:06:08 [Note] Starting crash recovery...
090212 12:06:08 [Note] Crash recovery finished.
090212 12:06:08 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.27-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
mysqld got signal 11;
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.

Thank you for the feedback.

Part of the error log file which you provided shows server crashes when you invoke a custom function. Many crashing bugs were fixed since 5.0.27, so it would be good to check with new version. You can do it in test environment. For example:

1. Install second instance of MySQL 5.0.27 in separate directory (or another machine). Lets call it LOCAL COPY, start it.
2. Dump one of databases you experience problem with from production server (mysqldump -R dbname >dump.sql) For example, database where function getSeq was defined.
3. Restore this database in LOCAL COPY (mysql dbname <dump.sql)
4. Run SHOW FUNCTION STATUS and be sure you get same error like in production server. Try also SELECT getSeq() to be sure server crashes with partial data too.
5. If error happens repeat steps 1-4, but with version 5.0.67 or 5.0.75.
6. If new version fails too please send us dump problem repeatable with. Instructions how to upload large files are under "Files" tab in the bug report interface.

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".