Bug #34586 Misleading error message on binlog index not writeable

Submitted:	15 Feb 2008 10:47	Modified:	15 Feb 2008 14:49
Reporter:	Kristian Koehntopp	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S3 (Non-critical)
Version:	5.0.46-enterprise-gpl-log	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
When the binlog.index is not writeable, the error message says "not found", instead of printing the error text from perror():

080215 11:39:23  mysqld started
/usr/local/mysql-enterprise-gpl-5.0.46-linux-i686-glibc23/bin/mysqld: File './linux-bin.index' not found (Errcode: 13)
080215 11:39:23 [ERROR] Aborting

How to repeat:
Change the permissions of the binlog.index file to make it not writeable by the server.
Start the server.
Watch the error message.

It should say 

080215 11:39:23  mysqld started
/usr/local/mysql-enterprise-gpl-5.0.46-linux-i686-glibc23/bin/mysqld: File './linux-bin.index' permission denied (Errcode: 13)

Suggested fix:
Use the perror(3) function in glibc instead of making up wrong text messages yourself.

Verified as described with newest bk tree.

The error should be something like: "permission denied" instead of "file not found".

Page generated in 0.048 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.