Re: Starting mysql
On 12/12/2011 06:15 PM, Paul F. Johnson wrote: Hi, 111211 20:48:32 [ERROR] /usr/libexec/mysqld: Can't find file: './mysql/proxies_priv.frm' (errno: 13) 111211 20:48:32 [ERROR] Fatal error: Can't open and lock privilege tables: Can't find file: './mysql/proxies_priv.frm' (errno: 13) I think the nearby suggestions to run mysql_upgrade are probably right, especially if you're trying to upgrade from some pre-5.5 version of mysql. But it occurs to me that there's some chance of SELinux interference; do you see any avc messages in /var/log/messages? If so, restorecon on the /var/lib/mysql tree ought to fix that. Removed the entire mysql* rpms, installed fresh via yum, rm -rf /var/lib/mysql, enabled the service, did the mysql_install_db and all is good. Trying to start the server gives me this though... 111212 07:49:18 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 111212 7:49:18 [Note] Plugin 'FEDERATED' is disabled. 111212 7:49:18 InnoDB: The InnoDB memory heap is disabled 111212 7:49:18 InnoDB: Mutexes and rw_locks use GCC atomic builtins 111212 7:49:18 InnoDB: Compressed tables use zlib 1.2.5 111212 7:49:18 InnoDB: Using Linux native AIO 111212 7:49:18 InnoDB: Initializing buffer pool, size = 128.0M 111212 7:49:18 InnoDB: Completed initialization of buffer pool 111212 7:49:18 InnoDB: highest supported file format is Barracuda. 111212 7:49:19 InnoDB: Waiting for the background threads to start 111212 7:49:20 InnoDB: 1.1.8 started; log sequence number 1589339 111212 7:49:20 [ERROR] /usr/libexec/mysqld: Can't find file: './mysql/proxies_priv.frm' (errno: 13) 111212 7:49:20 [ERROR] Fatal error: Can't open and lock privilege tables: Can't find file: './mysql/proxies_priv.frm' (errno: 13) Where should this proxies_priv.frm reside as it looks to be the same missing file as before? What does 'which mysql_install_db' say? Maybe there is another older version of that script in your path? Also what does 'grep "CREATE TABLE.*proxies_priv" /usr/share/mysql/mysql_system_tables.sql' say? That's what is used by mysql_install_db to create the system tables. Have you actually done an 'ls -l /var/lib/mysql/mysql' to verify that the file is indeed missing? Do the MYD and MYI files for that table exist? Regards, Dennis -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Starting mysql
Date: Mon, 12 Dec 2011 17:15:25 +
> From: "Paul F. Johnson"
>
> Removed the entire mysql* rpms, installed fresh via yum, rm
> -rf /var/lib/mysql, enabled the service, did the mysql_install_db and
> all is good.
>
> Trying to start the server gives me this though...
>
> 111212 07:49:18 mysqld_safe Starting mysqld daemon with databases
> from /var/lib/mysql
>
[...]
> 111212 7:49:20 [ERROR] /usr/libexec/mysqld: Can't find file:
> './mysql/proxies_priv.frm' (errno: 13)
> 111212 7:49:20 [ERROR] Fatal error: Can't open and lock privilege
> tables: Can't find file: './mysql/proxies_priv.frm' (errno: 13)
>
I had that kind of issue, no later than today... on a just migrated Fedora
16 (from a Fedora 14 machine). There were two things:
* I started the mysql service with 'systemctl start mysql.service', instead
of 'systemctl start mysqld.service'
* some directories within /var/lib/mysql were owned by 'root', instead of
by 'mysql' (id=27). http://bugs.mysql.com/bug.php?id=1279 also clearly
states that errno=13 comes from access rights which are not granted.
Well, I stopped all the MySQL services ('systemctl stop
mysql.service', 'systemctl stop mysqld.service'), performed 'chown -R
mysql.mysql /var/lib/mysql', and restarted MySQL ('systemctl stop
mysqld.service'). And it eventually worked.
Hope that it will help...
Regards
Denis
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Starting mysql
Hi, > > 111211 20:48:32 [ERROR] /usr/libexec/mysqld: Can't find file: > > './mysql/proxies_priv.frm' (errno: 13) > > 111211 20:48:32 [ERROR] Fatal error: Can't open and lock privilege > > tables: Can't find file: './mysql/proxies_priv.frm' (errno: 13) > > I think the nearby suggestions to run mysql_upgrade are probably right, > especially if you're trying to upgrade from some pre-5.5 version of > mysql. But it occurs to me that there's some chance of SELinux > interference; do you see any avc messages in /var/log/messages? > If so, restorecon on the /var/lib/mysql tree ought to fix that. Removed the entire mysql* rpms, installed fresh via yum, rm -rf /var/lib/mysql, enabled the service, did the mysql_install_db and all is good. Trying to start the server gives me this though... 111212 07:49:18 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 111212 7:49:18 [Note] Plugin 'FEDERATED' is disabled. 111212 7:49:18 InnoDB: The InnoDB memory heap is disabled 111212 7:49:18 InnoDB: Mutexes and rw_locks use GCC atomic builtins 111212 7:49:18 InnoDB: Compressed tables use zlib 1.2.5 111212 7:49:18 InnoDB: Using Linux native AIO 111212 7:49:18 InnoDB: Initializing buffer pool, size = 128.0M 111212 7:49:18 InnoDB: Completed initialization of buffer pool 111212 7:49:18 InnoDB: highest supported file format is Barracuda. 111212 7:49:19 InnoDB: Waiting for the background threads to start 111212 7:49:20 InnoDB: 1.1.8 started; log sequence number 1589339 111212 7:49:20 [ERROR] /usr/libexec/mysqld: Can't find file: './mysql/proxies_priv.frm' (errno: 13) 111212 7:49:20 [ERROR] Fatal error: Can't open and lock privilege tables: Can't find file: './mysql/proxies_priv.frm' (errno: 13) Where should this proxies_priv.frm reside as it looks to be the same missing file as before? Thanks PFJ -- Vertraue mir, ich weiss, was ich mache... -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Starting mysql
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/12/2011 01:15 AM, Tom Lane wrote: > "Paul F. Johnson" writes: >> /var/log/mysqld.log shows this > >> 111211 20:48:32 [ERROR] /usr/libexec/mysqld: Can't find file: >> './mysql/proxies_priv.frm' (errno: 13) 111211 20:48:32 [ERROR] >> Fatal error: Can't open and lock privilege tables: Can't find >> file: './mysql/proxies_priv.frm' (errno: 13) > > I think the nearby suggestions to run mysql_upgrade are probably > right, especially if you're trying to upgrade from some pre-5.5 > version of mysql. But it occurs to me that there's some chance of > SELinux interference; do you see any avc messages in > /var/log/messages? If so, restorecon on the /var/lib/mysql tree > ought to fix that. > > Alternatively, if you don't have any valuable data in your > database (and I hope you aren't running anything *real* critical on > rawhide ;-)) you could just rm -rf everything under /var/lib/mysql > and let it initialize a brand new database. > > regards, tom lane SELinux error messages could also be in /var/log/audit/audit.log -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7mNTsACgkQrlYvE4MpobOtmACg2roZm6sPjv/ymXn4P8FTn4Cm /VoAoLja7rgIV4bQY5MXgsr+yIf9IuBm =WPb8 -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Starting mysql
"Paul F. Johnson" writes: > /var/log/mysqld.log shows this > 111211 20:48:32 [ERROR] /usr/libexec/mysqld: Can't find file: > './mysql/proxies_priv.frm' (errno: 13) > 111211 20:48:32 [ERROR] Fatal error: Can't open and lock privilege > tables: Can't find file: './mysql/proxies_priv.frm' (errno: 13) I think the nearby suggestions to run mysql_upgrade are probably right, especially if you're trying to upgrade from some pre-5.5 version of mysql. But it occurs to me that there's some chance of SELinux interference; do you see any avc messages in /var/log/messages? If so, restorecon on the /var/lib/mysql tree ought to fix that. Alternatively, if you don't have any valuable data in your database (and I hope you aren't running anything *real* critical on rawhide ;-)) you could just rm -rf everything under /var/lib/mysql and let it initialize a brand new database. regards, tom lane -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Starting mysql
Am 11.12.2011 22:02, schrieb Paul F. Johnson: > Hi, > >> Did you initialize databases as suggested (mysql_install_db) ? > > Yep - gave me this > > [root@PB3 paul]# mysql_install_db > Installing MySQL system tables... > 111211 21:00:37 [ERROR] Incorrect definition of table mysql.proc: > expected column 'comment' at position 15 to have type text, found type > char(64). > ERROR: 1136 Column count doesn't match value count at row 1 > 111211 21:00:38 [ERROR] Aborting > > 111211 21:00:38 [Note] /usr/libexec/mysqld: Shutdown complete sounds like this is not a fresh install people should be advised to call "mysql_upgrade -u root -p" after EACH minor update to avoid such issues over the long use this to start mysqld without permissions-system but make sure it is not reachable for clients as long it is running without priv http://dev.mysql.com/doc/refman/5.1/en/server-options.html#option_mysqld_skip-grant-tables after mysqld si running use "mysql_upgrade -u" (you do not need a password at this point) and after that REMOVE skip-grant from your config and restart the service a last time to active privilege control signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Starting mysql
Uh, if you have existing mysqld root dir, try mysqld_upgrade. Otherwise, try cleaning your /var/lib/mysql (and backing up any interesting MyISAM or InnoDB index/data you want to keep) then initialize again. On Sun, 2011-12-11 at 21:02 +, Paul F. Johnson wrote: > Hi, > > > Did you initialize databases as suggested (mysql_install_db) ? > > Yep - gave me this > > [root@PB3 paul]# mysql_install_db > Installing MySQL system tables... > 111211 21:00:37 [ERROR] Incorrect definition of table mysql.proc: > expected column 'comment' at position 15 to have type text, found type > char(64). > ERROR: 1136 Column count doesn't match value count at row 1 > 111211 21:00:38 [ERROR] Aborting > > 111211 21:00:38 [Note] /usr/libexec/mysqld: Shutdown complete > > > Installation of system tables failed! Examine the logs in > /var/lib/mysql for more information. > > You can try to start the mysqld daemon with: > > shell> /usr/libexec/mysqld --skip-grant & > > and use the command line tool /usr/bin/mysql > to connect to the mysql database and look at the grant tables: > > shell> /usr/bin/mysql -u root mysql > mysql> show tables > > Try 'mysqld --help' if you have problems with paths. Using --log > gives you a log in /var/lib/mysql that may be helpful. > > Please consult the MySQL manual section > 'Problems running mysql_install_db', and the manual section that > describes problems on your OS. Another information source are the > MySQL email archives available at http://lists.mysql.com/. > > Please check all of the above before mailing us! And remember, if > you do mail us, you MUST use the /usr/bin/mysqlbug script! > > Any advice would be appreciated. > > Paul > > -- > Vertraue mir, ich weiss, was ich mache... > -- Pierre Jaury +33(0)1.83.64.80.90 Réalisateur, hébergeur et infogéreur indépendant Internet hosting, outsourcing and development as a freelancer signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Starting mysql
Hi, > Did you initialize databases as suggested (mysql_install_db) ? Yep - gave me this [root@PB3 paul]# mysql_install_db Installing MySQL system tables... 111211 21:00:37 [ERROR] Incorrect definition of table mysql.proc: expected column 'comment' at position 15 to have type text, found type char(64). ERROR: 1136 Column count doesn't match value count at row 1 111211 21:00:38 [ERROR] Aborting 111211 21:00:38 [Note] /usr/libexec/mysqld: Shutdown complete Installation of system tables failed! Examine the logs in /var/lib/mysql for more information. You can try to start the mysqld daemon with: shell> /usr/libexec/mysqld --skip-grant & and use the command line tool /usr/bin/mysql to connect to the mysql database and look at the grant tables: shell> /usr/bin/mysql -u root mysql mysql> show tables Try 'mysqld --help' if you have problems with paths. Using --log gives you a log in /var/lib/mysql that may be helpful. Please consult the MySQL manual section 'Problems running mysql_install_db', and the manual section that describes problems on your OS. Another information source are the MySQL email archives available at http://lists.mysql.com/. Please check all of the above before mailing us! And remember, if you do mail us, you MUST use the /usr/bin/mysqlbug script! Any advice would be appreciated. Paul -- Vertraue mir, ich weiss, was ich mache... -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Starting mysql
Did you initialize databases as suggested (mysql_install_db) ? On Sun, 2011-12-11 at 20:50 +, Paul F. Johnson wrote: > Hi Tom, > > > Ummm ... do you have mysql-server RPM installed? > > Yep. > > > But in any case, > > Fedora's mysql package was converted to systemd some time ago, so you > > might have better luck using the native systemd service management > > commands: > > > > systemctl enable mysqld.service > > systemctl start mysqld.service > > systemctl status mysqld.service > > > > If "start" fails, there might be relevant info in either or both of > > /var/log/messages and /var/log/mysqld.log. > > start fails - it's telling me... > > [root@PB3 paul]# systemctl status mysqld.service > mysqld.service - MySQL database server > Loaded: loaded (/lib/systemd/system/mysqld.service; enabled) > Active: activating (start-post) since Sun, 11 Dec 2011 20:40:36 > +; 801ms ago >Process: 5077 ExecStart=/usr/bin/mysqld_safe --nowatch --basedir=/usr > (code=exited, status=0/SUCCESS) >Process: 5060 ExecStartPre=/usr/libexec/mysqld-prepare-db-dir > (code=exited, status=0/SUCCESS) > Main PID: 5213 (mysqld); Control: 5214 (mysqld-wait-rea) > CGroup: name=systemd:/system/mysqld.service > ├ 5213 /usr/libexec/mysqld --basedir=/usr --datadir=/var/... > ├ 5214 /bin/sh /usr/libexec/mysqld-wait-ready 5213 > └ 5243 sleep 1 > > with this in var/log/messages > > Dec 11 20:47:17 PB3 mysqld_safe[2417]: 111211 20:47:17 mysqld_safe > Starting mysqld daemon with databases from /var/lib/mysql > Dec 11 20:47:18 PB3 systemd[1]: mysqld.service: main process exited, > code=exited, status=1 > Dec 11 20:47:19 PB3 systemd[1]: mysqld.service: control process exited, > code=exited status=1 > Dec 11 20:47:19 PB3 systemd[1]: mysqld.service holdoff time over, > scheduling restart. > Dec 11 20:47:19 PB3 systemd[1]: Job pending for unit, delaying automatic > restart. > Dec 11 20:47:19 PB3 systemd[1]: Unit mysqld.service entered failed > state. > Dec 11 20:47:19 PB3 mysqld_safe[2657]: 111211 20:47:19 mysqld_safe > Logging to '/var/log/mysqld.log'. > Dec 11 20:47:19 PB3 mysqld_safe[2657]: 111211 20:47:19 mysqld_safe > Starting mysqld daemon with databases from /var/lib/mysql > Dec 11 20:47:21 PB3 systemd[1]: mysqld.service: main process exited, > code=exited, status=1 > Dec 11 20:47:22 PB3 systemd[1]: mysqld.service: control process exited, > code=exited status=1 > Dec 11 20:47:22 PB3 systemd[1]: mysqld.service holdoff time over, > scheduling restart. > Dec 11 20:47:22 PB3 systemd[1]: Job pending for unit, delaying automatic > restart. > Dec 11 20:47:22 PB3 systemd[1]: Unit mysqld.service entered failed > state. > Dec 11 20:47:22 PB3 mysqld_safe[2872]: 111211 20:47:22 mysqld_safe > Logging to '/var/log/mysqld.log'. > Dec 11 20:47:22 PB3 mysqld_safe[2872]: 111211 20:47:22 mysqld_safe > Starting mysqld daemon with databases from /var/lib/mysql > Dec 11 20:47:23 PB3 systemd[1]: mysqld.service: main process exited, > code=exited, status=1 > Dec 11 20:47:24 PB3 systemd[1]: mysqld.service: control process exited, > code=exited status=1 > Dec 11 20:47:25 PB3 systemd[1]: mysqld.service holdoff time over, > scheduling restart. > Dec 11 20:47:25 PB3 systemd[1]: Job pending for unit, delaying automatic > restart. > Dec 11 20:47:25 PB3 systemd[1]: Unit mysqld.service entered failed > state. > Dec 11 20:47:25 PB3 mysqld_safe[3079]: 111211 20:47:25 mysqld_safe > Logging to '/var/log/mysqld.log'. > Dec 11 20:47:25 PB3 mysqld_safe[3079]: 111211 20:47:25 mysqld_safe > Starting mysqld daemon with databases from /var/lib/mysql > Dec 11 20:47:26 PB3 systemd[1]: mysqld.service: main process exited, > code=exited, status=1 > Dec 11 20:47:27 PB3 systemd[1]: mysqld.service: control process exited, > code=exited status=1 > Dec 11 20:47:27 PB3 systemd[1]: mysqld.service holdoff time over, > scheduling restart. > Dec 11 20:47:27 PB3 systemd[1]: Job pending for unit, delaying automatic > restart. > Dec 11 20:47:27 PB3 systemd[1]: Unit mysqld.service entered failed > state. > Dec 11 20:47:28 PB3 mysqld_safe[3287]: 111211 20:47:28 mysqld_safe > Logging to '/var/log/mysqld.log'. > Dec 11 20:47:28 PB3 mysqld_safe[3287]: 111211 20:47:28 mysqld_safe > Starting mysqld daemon with databases from /var/lib/mysql > Dec 11 20:47:29 PB3 systemd[1]: mysqld.service: main process exited, > code=exited, status=1 > Dec 11 20:47:30 PB3 systemd[1]: mysqld.service: control process exited, > code=exited status=1 > Dec 11 20:47:30 PB3 systemd[1]: mysqld.service holdoff time over, > scheduling restart. > Dec 11 20:47:30 PB3 systemd[1]: Job pending for unit, delaying automatic > restart. > Dec 11 20:47:30 PB3 systemd[1]: Unit mysqld.service entered failed > state. > Dec 11 20:47:31 PB3 mysqld_safe[3498]: 111211 20:47:31 mysqld_safe > Logging to '/var/log/mysqld.log'. > Dec 11 20:47:31 PB3 mysqld_safe[3498]: 111211 20:47:31 mysqld_safe > Starting mysqld daemon with databases from
Re: Starting mysql
Hi Tom, > Ummm ... do you have mysql-server RPM installed? Yep. > But in any case, > Fedora's mysql package was converted to systemd some time ago, so you > might have better luck using the native systemd service management > commands: > > systemctl enable mysqld.service > systemctl start mysqld.service > systemctl status mysqld.service > > If "start" fails, there might be relevant info in either or both of > /var/log/messages and /var/log/mysqld.log. start fails - it's telling me... [root@PB3 paul]# systemctl status mysqld.service mysqld.service - MySQL database server Loaded: loaded (/lib/systemd/system/mysqld.service; enabled) Active: activating (start-post) since Sun, 11 Dec 2011 20:40:36 +; 801ms ago Process: 5077 ExecStart=/usr/bin/mysqld_safe --nowatch --basedir=/usr (code=exited, status=0/SUCCESS) Process: 5060 ExecStartPre=/usr/libexec/mysqld-prepare-db-dir (code=exited, status=0/SUCCESS) Main PID: 5213 (mysqld); Control: 5214 (mysqld-wait-rea) CGroup: name=systemd:/system/mysqld.service ├ 5213 /usr/libexec/mysqld --basedir=/usr --datadir=/var/... ├ 5214 /bin/sh /usr/libexec/mysqld-wait-ready 5213 └ 5243 sleep 1 with this in var/log/messages Dec 11 20:47:17 PB3 mysqld_safe[2417]: 111211 20:47:17 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql Dec 11 20:47:18 PB3 systemd[1]: mysqld.service: main process exited, code=exited, status=1 Dec 11 20:47:19 PB3 systemd[1]: mysqld.service: control process exited, code=exited status=1 Dec 11 20:47:19 PB3 systemd[1]: mysqld.service holdoff time over, scheduling restart. Dec 11 20:47:19 PB3 systemd[1]: Job pending for unit, delaying automatic restart. Dec 11 20:47:19 PB3 systemd[1]: Unit mysqld.service entered failed state. Dec 11 20:47:19 PB3 mysqld_safe[2657]: 111211 20:47:19 mysqld_safe Logging to '/var/log/mysqld.log'. Dec 11 20:47:19 PB3 mysqld_safe[2657]: 111211 20:47:19 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql Dec 11 20:47:21 PB3 systemd[1]: mysqld.service: main process exited, code=exited, status=1 Dec 11 20:47:22 PB3 systemd[1]: mysqld.service: control process exited, code=exited status=1 Dec 11 20:47:22 PB3 systemd[1]: mysqld.service holdoff time over, scheduling restart. Dec 11 20:47:22 PB3 systemd[1]: Job pending for unit, delaying automatic restart. Dec 11 20:47:22 PB3 systemd[1]: Unit mysqld.service entered failed state. Dec 11 20:47:22 PB3 mysqld_safe[2872]: 111211 20:47:22 mysqld_safe Logging to '/var/log/mysqld.log'. Dec 11 20:47:22 PB3 mysqld_safe[2872]: 111211 20:47:22 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql Dec 11 20:47:23 PB3 systemd[1]: mysqld.service: main process exited, code=exited, status=1 Dec 11 20:47:24 PB3 systemd[1]: mysqld.service: control process exited, code=exited status=1 Dec 11 20:47:25 PB3 systemd[1]: mysqld.service holdoff time over, scheduling restart. Dec 11 20:47:25 PB3 systemd[1]: Job pending for unit, delaying automatic restart. Dec 11 20:47:25 PB3 systemd[1]: Unit mysqld.service entered failed state. Dec 11 20:47:25 PB3 mysqld_safe[3079]: 111211 20:47:25 mysqld_safe Logging to '/var/log/mysqld.log'. Dec 11 20:47:25 PB3 mysqld_safe[3079]: 111211 20:47:25 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql Dec 11 20:47:26 PB3 systemd[1]: mysqld.service: main process exited, code=exited, status=1 Dec 11 20:47:27 PB3 systemd[1]: mysqld.service: control process exited, code=exited status=1 Dec 11 20:47:27 PB3 systemd[1]: mysqld.service holdoff time over, scheduling restart. Dec 11 20:47:27 PB3 systemd[1]: Job pending for unit, delaying automatic restart. Dec 11 20:47:27 PB3 systemd[1]: Unit mysqld.service entered failed state. Dec 11 20:47:28 PB3 mysqld_safe[3287]: 111211 20:47:28 mysqld_safe Logging to '/var/log/mysqld.log'. Dec 11 20:47:28 PB3 mysqld_safe[3287]: 111211 20:47:28 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql Dec 11 20:47:29 PB3 systemd[1]: mysqld.service: main process exited, code=exited, status=1 Dec 11 20:47:30 PB3 systemd[1]: mysqld.service: control process exited, code=exited status=1 Dec 11 20:47:30 PB3 systemd[1]: mysqld.service holdoff time over, scheduling restart. Dec 11 20:47:30 PB3 systemd[1]: Job pending for unit, delaying automatic restart. Dec 11 20:47:30 PB3 systemd[1]: Unit mysqld.service entered failed state. Dec 11 20:47:31 PB3 mysqld_safe[3498]: 111211 20:47:31 mysqld_safe Logging to '/var/log/mysqld.log'. Dec 11 20:47:31 PB3 mysqld_safe[3498]: 111211 20:47:31 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql Dec 11 20:47:32 PB3 systemd[1]: mysqld.service: main process exited, code=exited, status=1 /var/log/mysqld.log shows this 111211 20:48:32 [ERROR] /usr/libexec/mysqld: Can't find file: './mysql/proxies_priv.frm' (errno: 13) 111211 20:48:32 [ERROR] Fatal error: Can't open and lock privilege tables: Ca
Re: Starting mysql
"Paul F. Johnson" writes: > No idea why I can't get mysql running on my rawhide box. When I try to > start it up, I get the infamous > ERROR 2002 (HY000): Can't connect to local MySQL server through socket > '/var/lib/mysql/mysql.sock' (2) > This looks like the daemon isn't running or the service isn't running. Yup, that's what it looks like. > service mysql or service mysqld is giving nothing and I can't find > mysqld anywhere either. Ummm ... do you have mysql-server RPM installed? But in any case, Fedora's mysql package was converted to systemd some time ago, so you might have better luck using the native systemd service management commands: systemctl enable mysqld.service systemctl start mysqld.service systemctl status mysqld.service If "start" fails, there might be relevant info in either or both of /var/log/messages and /var/log/mysqld.log. (One of the prime reasons forcing conversion to systemd was that systemd's handling of SysV init scripts is so utterly user-unfriendly. It surprises me not at all that the emulated "service" commands aren't telling you anything useful. They pretty much suck, so you should learn the new ones ASAP.) regards, tom lane -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Starting mysql
Since recent rawhide changes, default mysql-server installation does not install service bindings (rc.*, checkconfig, etc.) anymore. First initialize mysql databases in /var/lib/mysql using mysql_install_db then run mysqld_safe if you want a quick installation running. Otherwise, unpack old rc.* and checkconfig files from old packages. They still work. On Sun, 2011-12-11 at 17:25 +, Paul F. Johnson wrote: > Hi, > > No idea why I can't get mysql running on my rawhide box. When I try to > start it up, I get the infamous > > ERROR 2002 (HY000): Can't connect to local MySQL server through socket > '/var/lib/mysql/mysql.sock' (2) > > This looks like the daemon isn't running or the service isn't running. > > service mysql or service mysqld is giving nothing and I can't find > mysqld anywhere either. > > There are some mysql-mmm entries in /etc/init.d but nothing else. > > How do I get it running? > > Paul > -- > Vertraue mir, ich weiss, was ich mache... > -- Pierre Jaury +33(0)1.83.64.80.90 Réalisateur, hébergeur et infogéreur indépendant Internet hosting, outsourcing and development as a freelancer signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
