You are not logged in.
Latest News at archlinux.org:
It is recommended for all users to upgrade.
To avoid more confusion among those of us who are confused enough, shouldn't that read "all MySQL users"?
Last edited by sonoran (2013-03-28 04:19:53)
Offline
Yes, you can ignore the announcement if you don't use MySQL. You can also ignore the announcement if you use MariaDB.
It's funny, I had no idea this announcement was coming, but I upgraded from MySQL to MariaDB just last month.
Offline
Yes, you can ignore the announcement if you don't use MySQL. You can also ignore the announcement if you use MariaDB.
It's funny, I had no idea this announcement was coming, but I upgraded from MySQL to MariaDB just last month.
I don't explicitely have mysqld running so I did the upgrade by installing the new mariadb packages and accepting the removal of the mysql ones. Then checking the status of the mysqld service:
systemctl status mysqld
mysqld.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mysqld.service; disabled)
Active: inactive (dead)
But I am running KDE as my desktop and it seems that a private instance of mysqld is running:
ps -eaf | egrep mysql
mike 660 657 0 Mar23 ? 00:00:42 /usr/bin/mysqld --defaults-file=/home/mike/.local/share/akonadi/mysql.conf --datadir=/home/mike/.local/share/akonadi/db_data/ --socket=/home/mike/.local/share/akonadi/socket-home1/mysql.socket
mike 9747 761 0 13:39 pts/3 00:00:00 egrep mysql
So the question is whether or not some special upgrade for the KDE instance is needed? If so how does one go about doing it?
Thanks
Mike C
Offline
But I am running KDE as my desktop and it seems that a private instance of mysqld is running:
Akonadi seems to depend now on mariadb, so I'll say kde users should upgrade to mariadb, but I'm not sure.
Offline
But I am running KDE as my desktop and it seems that a private instance of mysqld is running:
Akonadi seems to depend now on mariadb, so I'll say kde users should upgrade to mariadb, but I'm not sure.
Indeed and I have the current version akonadi 1.9.1-2 running when I quoted the results in my initial post.
Mike C
Offline
Akonadi seems to depend now on mariadb, so I'll say kde users should upgrade to mariadb, but I'm not sure.
Ah, I forgot about those use cases! Yes, if you have the "mysql" package installed, then you should* change to the mariadb package.
*and by "should" I mean if you want to. MySQL will still work. But, you know, FREEDOM**!
**and by "freedom" I mean freedom from Oracle.
Last edited by drcouzelis (2013-03-26 15:30:05)
Offline
Can't start mysqld after upgrading, while running kde. Status says:
Process: 26840 ExecStart=/usr/bin/mysqld --pid-file=/run/mysqld/mysqld.pid (code=exited, status=1/FAILURE)
Offline
Can't start mysqld after upgrading, while running kde. Status says:
Process: 26840 ExecStart=/usr/bin/mysqld --pid-file=/run/mysqld/mysqld.pid (code=exited, status=1/FAILURE)
Please consider starting a new thread and including more information.
Offline
It seems that I've a similar problem when I try to start the mysqld.service while akonadi is running.
mysqld.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mysqld.service; disabled)
Active: activating (start-post) (Result: exit-code) since Mi 2013-04-03 09:19:32 CEST; 16s ago
Process: 2590 ExecStart=/usr/bin/mysqld --pid-file=/run/mysqld/mysqld.pid (code=exited, status=1/FAILURE)
Control: 2591 (mysqld-post)
CGroup: name=systemd:/system/mysqld.service
└─control
├─2591 /bin/sh /usr/bin/mysqld-post
└─2731 sleep 1
Apr 03 09:19:32 fruitloop mysqld[2590]: 130403 9:19:32 InnoDB: to what it was, and remove the new ibdata files InnoDB created
Apr 03 09:19:32 fruitloop mysqld[2590]: 130403 9:19:32 InnoDB: in this failed attempt. InnoDB only wrote those files full of
Apr 03 09:19:32 fruitloop mysqld[2590]: 130403 9:19:32 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
Apr 03 09:19:32 fruitloop mysqld[2590]: 130403 9:19:32 InnoDB: remove old data files which contain your precious data!
Apr 03 09:19:32 fruitloop mysqld[2590]: 130403 9:19:32 [ERROR] Plugin 'InnoDB' init function returned error.
Apr 03 09:19:32 fruitloop mysqld[2590]: 130403 9:19:32 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Apr 03 09:19:32 fruitloop mysqld[2590]: 130403 9:19:32 [ERROR] Unknown/unsupported storage engine: InnoDB
Apr 03 09:19:32 fruitloop mysqld[2590]: 130403 9:19:32 [ERROR] Aborting
Apr 03 09:19:32 fruitloop mysqld[2590]: 130403 9:19:32 [Note] /usr/bin/mysqld: Shutdown complete
Apr 03 09:19:32 fruitloop systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE
Offline
Ok. I figured it out. The pre-existing InnoDB file /var/lib/mysql/ibdata1 was zero-sized.
After deleting it I was able to get mysqld.service running. It still had an error due to the recent update. But after running mysql_upgrade it converted correctly and let me restart mysqld.service without issue.
Offline