Re: [arch-general] [arch-dev-public] MySQL 5.5
On Wednesday 22 of December 2010 10:29:43 Andrea Scarpino wrote:
[root@beruska ~]# mysql_upgrade Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck Running 'mysqlcheck' with connection arguments: '--port=3306' '-- socket=/var/run/mysqld/mysqld.sock' '--port=3306' '-- socket=/var/run/mysqld/mysqld.sock' mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) when trying to connect FATAL ERROR: Upgrade failed
Any ideas?
Is mysql running? It is not, mysqld doesn't know some option '--skip-locking' . Here's my debugging :
[root@beruska ~]# ps aux | grep mysql marek 27468 1.1 1.2 235992 24788 ? Sl 11:19 0:03 /usr/bin/mysqld --defaults-file=/home/marek/.local/share/akonadi//mysql.conf --datadir /home/marek/.local/share/akonadi/db_data/ -- socket=/home/marek/.local/share/akonadi/db_misc/mysql.socket root 27829 0.0 0.0 4284 828 pts/2 S+ 11:23 0:00 grep mysql [root@beruska ~]# /etc/rc.d/mysqld restart :: Stopping MySQL Server [FAIL] :: Starting MySQL Server [FAIL] [root@beruska ~]# vim /etc/rc.d/mysqld I tried the commands manually to see output [root@beruska ~]# pgrep -u mysql mysqld [root@beruska ~]# /usr/bin/mysqld_safe --user=mysql 101222 11:26:35 mysqld_safe Logging to '/var/lib/mysql/beruska.err'. 101222 11:26:35 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 101222 11:26:37 mysqld_safe mysqld from pid file /var/lib/mysql/beruska.pid ended [root@beruska ~]# /usr/bin/mysqladmin -uUNKNOWN_USER ping /usr/bin/mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)' Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists! [root@beruska ~]# ls -l /var/run/mysqld/mysqld.sock ls: cannot access /var/run/mysqld/mysqld.sock: No such file or directory [root@beruska ~]# tail -10 /var/lib/mysql/beruska.err 101222 11:26:36 InnoDB: highest supported file format is Barracuda. 101222 11:26:36 InnoDB: 1.1.4 started; log sequence number 1591525 101222 11:26:36 [ERROR] /usr/bin/mysqld: unknown option '--skip-locking' 101222 11:26:36 [ERROR] Aborting 101222 11:26:36 InnoDB: Starting shutdown... 101222 11:26:37 InnoDB: Shutdown completed; log sequence number 1591525 101222 11:26:37 [Note] /usr/bin/mysqld: Shutdown complete 101222 11:26:37 mysqld_safe mysqld from pid file /var/lib/mysql/beruska.pid ended Thanks, Marek -- Marek Otahal :o)
On Wed, Dec 22, 2010 at 5:33 AM, Marek Otahal <markotahal@gmail.com> wrote:
On Wednesday 22 of December 2010 10:29:43 Andrea Scarpino wrote:
Is mysql running? It is not, mysqld doesn't know some option '--skip-locking' . Here's my debugging :
It's now called skip-external-locking. You should add any configuration customizations you have to /etc/mysql/my.cnf.pacnew and then move it into the place of /etc/mysql/my.cnf, overwriting the latter. Andrea, the new MySQL packages work fine here. Good job. :)
On Wednesday 22 of December 2010 11:47:34 Evangelos Foutras wrote:
On Wed, Dec 22, 2010 at 5:33 AM, Marek Otahal <markotahal@gmail.com> wrote:
On Wednesday 22 of December 2010 10:29:43 Andrea Scarpino wrote:
Is mysql running?
It is not, mysqld doesn't know some option '--skip-locking' . Here's my
debugging : It's now called skip-external-locking. You should add any configuration customizations you have to /etc/mysql/my.cnf.pacnew and then move it into the place of /etc/mysql/my.cnf, overwriting the latter.
Andrea, the new MySQL packages work fine here. Good job. :) I didn't do any customizations to mysql. Attaching my.cnf , the skip-external- locking is there, but some program still complains about --skip-locking.
mysql.err: 101222 12:28:18 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 101222 12:28:18 [Note] Plugin 'FEDERATED' is disabled. InnoDB: The InnoDB memory heap is disabled InnoDB: Mutexes and rw_locks use GCC atomic builtins InnoDB: Compressed tables use zlib 1.2.5 101222 12:28:18 InnoDB: Initializing buffer pool, size = 128.0M 101222 12:28:18 InnoDB: Completed initialization of buffer pool 101222 12:28:18 InnoDB: highest supported file format is Barracuda. 101222 12:28:18 InnoDB: 1.1.4 started; log sequence number 1591525 101222 12:28:18 [ERROR] /usr/bin/mysqld: unknown option '--skip-locking' 101222 12:28:18 [ERROR] Aborting 101222 12:28:18 InnoDB: Starting shutdown... 101222 12:28:20 InnoDB: Shutdown completed; log sequence number 1591525 101222 12:28:20 [Note] /usr/bin/mysqld: Shutdown complete 101222 12:28:20 mysqld_safe mysqld from pid file /var/lib/mysql/beruska.pid ended # mysql_upgrade Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck Running 'mysqlcheck' with connection arguments: '--port=3306' '-- socket=/var/run/mysqld/mysqld.sock' '--port=3306' '-- socket=/var/run/mysqld/mysqld.sock' mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) when trying to connect FATAL ERROR: Upgrade failed Thanks a lot! -- Marek Otahal :o)
participants (2)
-
Evangelos Foutras
-
Marek Otahal