Bug 2739

Summary:	Mysql don't works
Product:	Mageia	Reporter:	Jacques Pronchery <jacques.pronchery>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	mageia
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	MySQL	CVE:
Status comment:

Description Jacques Pronchery 2011-09-13 21:58:19 CEST

Mysqd don't starts
see the report below :

[root@localhost jacques]# mysqld start
mysqld: Table 'mysql.plugin' doesn't exist
110913 17:42:22 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
110913 17:42:22 InnoDB: The InnoDB memory heap is disabled
110913 17:42:22 InnoDB: Mutexes and rw_locks use GCC atomic builtins
110913 17:42:22 InnoDB: Compressed tables use zlib 1.2.5
110913 17:42:22 InnoDB: Using Linux native AIO
110913 17:42:22 InnoDB: Initializing buffer pool, size = 128.0M
110913 17:42:22 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
110913 17:42:22  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
110913 17:42:22  InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
110913 17:42:22  InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
110913 17:42:23  InnoDB: Waiting for the background threads to start
110913 17:42:24 InnoDB: 1.1.7 started; log sequence number 0
mysqld: Too many arguments (first extra is 'start').
Use --verbose --help to get a list of available options
110913 17:42:24 [ERROR] Aborting

110913 17:42:24  InnoDB: Starting shutdown...
110913 17:42:25  InnoDB: Shutdown completed; log sequence number 1595675
110913 17:42:25 [Note] mysqld: Shutdown complete

[root@localhost jacques]# mysql_upgrade
Looking for 'mysql' as: mysql
Looking for 'mysqlcheck' as: mysqlcheck
Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/lib/mysql/mysql.sock' 
mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) when trying to connect
FATAL ERROR: Upgrade failed
[root@localhost jacques]#

Comment 1 Manuel Hiebel 2011-09-14 10:44:53 CEST

is that better with the new version ?

Comment 2 Jacques Pronchery 2011-09-14 13:24:27 CEST

(In reply to comment #1)
> is that better with the new version ?

No there are the same defaults !!!

Comment 3 Jacques Pronchery 2011-09-28 14:45:41 CEST

I install Mageia with LXDE in french and without software
only with configuration and LSB

I install MySQL and it don't start.
I install the driver for NVIDIA
I test MySQL but it don't start
I reboot the system and MySQL started during the reboot
And then MySQL works OK

Comment 4 Sander Lepik 2011-09-28 14:51:10 CEST

For starting the service you should use service mysqld start

And if you use that command then what errors do you get?

CC: (none) => sander.lepik

Comment 5 Jacques Pronchery 2011-09-28 15:50:15 CEST

(In reply to comment #4)
> For starting the service you should use service mysqld start
> 
Yes , I know

> And if you use that command then what errors do you get?

See the description above.

Comment 6 Sander Lepik 2011-09-28 16:18:59 CEST

(In reply to comment #5)
> > And if you use that command then what errors do you get?
> 
> See the description above.

You didn't start it with service command.

Comment 7 Manuel Hiebel 2011-09-28 17:02:49 CEST

(In reply to comment #3)
> I reboot the system and MySQL started during the reboot
> And then MySQL works OK

So yes you must run the command "service mysqld start" or "/etc/init.d/mysqld" and not "mysqld start"

so closing this bug as invalid

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 8 Jacques Pronchery 2011-09-28 17:06:40 CEST

I tryed start MySQL for 2 ways :

In a consol with mysqld start
and with the services of MCC.

It was the same result.

Comment 9 Sander Lepik 2011-09-28 17:14:38 CEST

mysqld start is not the same as service mysqld start. So if you want to report problem then reproduce it with service mysqld start and copy logs or error message that you get. Above error is rather normal for that (bogus) command.

Comment 10 Jacques Pronchery 2011-09-28 22:40:12 CEST

Here is the report of the command :

[root@localhost ~]# service mysqld start
Starting mysqld (via systemctl):  Job failed. See system logs and 'systemctl status' for details.
                                                                                               [ÃCHEC ]
[root@localhost ~]#

Status: RESOLVED => REOPENED
Resolution: INVALID => (none)

Comment 11 Sander Lepik 2011-09-28 23:06:46 CEST

And what are the logs saying? And the satus command?

Comment 12 Jacques Pronchery 2011-09-29 07:44:17 CEST

i don't know what you want,
say me what command i will do.
Thank

Comment 13 Remco Rijnders 2011-10-01 06:03:21 CEST

Jacques, when you get this error, please give the command 'systemctl status' and show the output of that, as well as the contents of /var/log/syslog (only those entries from trying to start the command onwards).

Comment 14 Jacques Pronchery 2011-10-01 11:40:12 CEST

Here is the report :

[root@localhost ~]# systemctl status
Too few arguments.
[root@localhost ~]# systemctl status mysql
Failed to issue method call: Unit name mysql is not valid.
[root@localhost ~]# 

There is no file /var/log/syslog

Comment 15 Jacques Pronchery 2011-10-01 12:08:20 CEST

I make an update and then it's impossible to boot.

I wanted to re-install Cauldron but it's impossible because :
bootloader_utils conflict with libldetect0
Kernel-desktop586  unsatisfied bootloader
libldetect0  unsatisfied libmodprobe.so.0

we will see the probleme later when it will be possible to install Cauldron

Comment 16 Jacques Pronchery 2011-10-06 19:04:55 CEST

If I install Mageia without X, mysql works correctly
and there is a file /var/log/syslog
But if I install Mageia with X (LXDE or Icewm light) mysql don't start.

[root@localhost ~]# systemctl status mysqld.service
mysqld.service - MySQL database server
	  Loaded: loaded (/lib/systemd/system/mysqld.service; enabled)
	  Active: activating (start-post) since Thu, 06 Oct 2011 14:58:13 +0200; 1s ago
	 Process: 1321 ExecStart=/usr/bin/mysqld_safe --nowatch (code=exited, status=0/SUCCESS)
	 Process: 1306 ExecStartPre=/usr/sbin/mysqld-prepare-db-dir (code=exited, status=0/SUCCESS)
	Main PID: 1670 (mysqld); Control: 1671 (mysqld-wait-rea)
	  CGroup: name=systemd:/system/mysqld.service
		  â 1670 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib/mysql/plugin --log-error=/var/lib/mys...
		  â 1671 /bin/sh /usr/sbin/mysqld-wait-ready 1670
		  â 1713 sleep 1
[root@localhost ~]#

and there is not the file /var/log/syslog.

Comment 17 Jacques Pronchery 2011-10-07 19:31:02 CEST

See bug 2962

Comment 18 Jacques Pronchery 2011-10-11 09:52:20 CEST

It seems that there is no problem with MySQL.
The problem is in the X driver nouveau.
But I not founded the link between Mysql and this driver.

I think you can close this bug.

Comment 19 Manuel Hiebel 2011-10-11 11:25:53 CEST

Ok thanks.

(I am also sure that as nothing do to with the video card :))

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED