root user password not set implicitly in PS 5.6

Bug #1236369 reported by Muhammad Irfan
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.1
Invalid
Undecided
Unassigned
5.5
Invalid
Undecided
Unassigned
5.6
Triaged
Medium
Unassigned
5.7
New
Medium
Unassigned

Bug Description

I tired Percona Server 5.6.13/5.6.14 on CentOS 5/CentOS 6 and found that root password is not set implicitly. As per MySQL manual from MySQL 5.6.8, new RPM install operations invoke mysql_install_db with the --random-passwords option that provides for more secure MySQL installation. That is not the case here, Check below output for detail.

[root@centos63 download]# rpm -ivh Percona-Server-56-debuginfo-5.6.13-rc60.6.427.rhel6.x86_64.rpm Percona-Server-client-56-5.6.13-rc60.6.427.rhel6.x86_64.rpm Percona-Server-devel-56-5.6.13-rc60.6.427.rhel6.x86_64.rpm Percona-Server-server-56-5.6.13-rc60.6.427.rhel6.x86_64.rpm Percona-Server-shared-56-5.6.13-rc60.6.427.rhel6.x86_64.rpm Percona-Server-test-56-5.6.13-rc60.6.427.rhel6.x86_64.rpm
Preparing... ########################################### [100%]
   1:Percona-Server-shared-5########################################### [ 17%]
   2:Percona-Server-client-5########################################### [ 33%]
ls: cannot access /var/lib/mysql/*.err: No such file or directory
ls: cannot access /var/lib/mysql/*.err: No such file or directory
   3:Percona-Server-server-5########################################### [ 50%]
2013-10-07 02:27:50 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:

  /usr/bin/mysqladmin -u root password 'new-password'
  /usr/bin/mysqladmin -u root -h centos63 password 'new-password'

Alternatively you can run:

  /usr/bin/mysql_secure_installation

which will also give you the option of removing the test
databases and anonymous user created by default. This is
strongly recommended for production servers.

Tags: pkg
tags: added: pkg
Revision history for this message
Valerii Kravchuk (valerii-kravchuk) wrote :
Download full text (6.0 KiB)

Confirmed with PS 5.6 GA:

...
Percona-Server-server-56-5.6.13-rel61.0.461.rhel6.x86_64 | 18 MB 00:33
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : Percona-Server-server-56-5.6.13-rel61.0.461.rhel6.x86_64 1/1
2013-10-10 11:35:07 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2013-10-10 11:35:07 18881 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-10 11:35:07 18881 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2013-10-10 11:35:07 18881 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-10 11:35:07 18881 [Note] InnoDB: Using Linux native AIO
2013-10-10 11:35:07 18881 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-10 11:35:07 18881 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-10-10 11:35:07 18881 [Note] InnoDB: Completed initialization of buffer pool
2013-10-10 11:35:07 18881 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2013-10-10 11:35:07 18881 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2013-10-10 11:35:07 18881 [Note] InnoDB: Database physically writes the file full: wait...
2013-10-10 11:35:08 18881 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2013-10-10 11:35:09 18881 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2013-10-10 11:35:11 18881 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2013-10-10 11:35:11 18881 [Warning] InnoDB: New log files created, LSN=45781
2013-10-10 11:35:11 18881 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-10-10 11:35:11 18881 [Note] InnoDB: Doublewrite buffer created
2013-10-10 11:35:11 18881 [Note] InnoDB: 128 rollback segment(s) are active.
2013-10-10 11:35:11 18881 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-10-10 11:35:11 18881 [Note] InnoDB: Foreign key constraint system tables created
2013-10-10 11:35:11 18881 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-10-10 11:35:11 18881 [Note] InnoDB: Tablespace and datafile system tables created.
2013-10-10 11:35:11 18881 [Note] InnoDB: Waiting for purge to start
2013-10-10 11:35:11 18881 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.13-rel61.0 started; log sequence number 0
2013-10-10 11:35:11 18881 [Note] RSA private key file not found: /var/lib/mysql//private_key.pem. Some authentication plugins will not work.
2013-10-10 11:35:11 18881 [Note] RSA public key file not found: /var/lib/mysql//public_key.pem. Some authentication plugins will not work.
2013-10-10 11:35:13 18881 [Note] Binlog end
2013-10-10 11:35:13 18881 [Note] InnoDB: FTS optimize thread exiting.
2013-10-10 11:35:13 18881 [Note] InnoDB: Starting shutdown...
2013-10-10 11:35:15 18881 [Note] InnoDB: Shutdown completed; log sequence number 1625977

2013-10-10 11:35:15 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2013-10-10 11:35:15 18905 [Note] InnoDB: The InnoDB m...

Read more...

Revision history for this message
Roel Van de Paar (roel11) wrote :

Yes, AlexeyB also confirmed.

As a sidenote, MySQL 5.1 from Centos distribution is installed without password also. But this may be due to 5.5/5.6 change in MS since then.

Revision history for this message
Roel Van de Paar (roel11) wrote :

May make sense to check 5.5 behavior also.

Revision history for this message
Alexey Kopytov (akopytov) wrote :

mysql_install_db --random-passwords is a new feature in 5.6, thus Invalid for 5.1/5.5.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1434

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.