MariaDB couldn't install correctly under fedora 17 with latest updates

Bug #1044938 reported by Mikhail Gavrilov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MariaDB
New
Undecided
Daniel Bartholomew

Bug Description

MariaDB couldn't install correctly under fedora 17 with latest updates

# cat /etc/yum.repos.d/MariaDB.repo
# MariaDB repository list - created 2012-08-20 16:03 UTC
# http://downloads.mariadb.org/mariadb/repositories/
[mariadb]
name = MariaDB
baseurl = http://yum.mariadb.org/5.5/fedora16-x86
gpgcheck=1

# yum install MariaDB-server
Loaded plugins: langpacks, presto, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package MariaDB-server.i686 0:5.5.25-1 will be installed
--> Processing Dependency: MariaDB-common for package: MariaDB-server-5.5.25-1.i686
--> Running transaction check
---> Package MariaDB-common.i686 0:5.5.25-1 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

=========================================================================================================================================================================================
 Package Arch Version Repository Size
=========================================================================================================================================================================================
Installing:
 MariaDB-server i686 5.5.25-1 mariadb 32 M
Installing for dependencies:
 MariaDB-common i686 5.5.25-1 mariadb 23 k

Transaction Summary
=========================================================================================================================================================================================
Install 1 Package (+1 Dependent package)

Total download size: 32 M
Installed size: 129 M
Is this ok [y/N]: y
Downloading Packages:
(1/2): MariaDB-5.5.25-fedora16-i686-common.rpm | 23 kB 00:00
(2/2): MariaDB-5.5.25-fedora16-i686-server.rpm | 32 MB 00:11
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 2.9 MB/s | 32 MB 00:11
Running Transaction Check
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : MariaDB-common-5.5.25-1.i686 1/2
  Installing : MariaDB-server-5.5.25-1.i686 2/2
chown: invalid user: `mysql:mysql'
chown: invalid user: `mysql'
Cannot change ownership of the database directories to the 'mysql'
user. Check that you have the necessary permissions and try again.
chown: invalid user: `mysql:mysql'
  Verifying : MariaDB-server-5.5.25-1.i686 1/2
  Verifying : MariaDB-common-5.5.25-1.i686 2/2

Installed:
  MariaDB-server.i686 0:5.5.25-1

Dependency Installed:
  MariaDB-common.i686 0:5.5.25-1

Complete!

# service mysql restart
MySQL server PID file could not be found! [FAILED]
Starting MySQL.The server quit without updating PID file (/[FAILED]mysql/u3s3.pid).

# ls -la /var/lib/mysql
total 20
drwxr-xr-x. 4 root root 4096 сент. 2 15:08 .
drwxr-xr-x. 42 root root 4096 сент. 2 14:33 ..
drwx--x--x. 2 root root 4096 сент. 2 14:33 mysql
drwxr-xr-x. 2 root root 4096 сент. 2 14:33 test
-rw-rw----. 1 root root 371 сент. 2 15:08 u3s3.err

# cat /var/lib/mysql/u3s3.err
120902 15:08:43 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
120902 15:08:43 [ERROR] Fatal error: Can't change to run as user 'mysql' ; Please check that the user exists!

120902 15:08:43 [ERROR] Aborting

120902 15:08:43 [Note] /usr/sbin/mysqld: Shutdown complete

120902 15:08:43 mysqld_safe mysqld from pid file /var/lib/mysql/u3s3.pid ended

In /etc/passwd and /etc/group mysql is absent!!!

Revision history for this message
Elena Stepanova (elenst) wrote :

I believe we don't have packages for Fedora 17 in the currently available release 5.5.25.
Daniel, could you please take a look -- is the problem caused by trying to install Fedora 16 packages on Fedora 17?

Changed in maria:
assignee: nobody → Daniel Bartholomew (dbart)
milestone: none → 5.5
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.