[arch-general] Question about mariadb replacing mysql
With the move to mariadb I have the following situation: I am not explicitely running mysqld so checking the status with systemctl shows it is inactive. However I am running KDE as my desktop. After doing the suggested install after ensuring that mysqld is stopped: pacman -S mariadb libmariadbclient mariadb-clients and accepting the install of these packages with removal of mysql equivalents, I then find that there is a private instance of mysql running by the KDE desktop: 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 does any expert know whether a mysql_upgrade is necessary for KDE and if so how does one go about doing that upgrade? Thanks. -- mike c
On Tuesday 26 Mar 2013 13:50:13 Mike Cloaked wrote:
So does any expert know whether a mysql_upgrade is necessary for KDE and if so how does one go about doing that upgrade?
I also use KDE. I went ahead with the switch. I stopped akonadi first, though: # akonadictl stop <install mariadb> # akonadictl start And all seemed to go well. I haven't done anything special for KDE when upgrading mysql before, so I don't think anything is required now. I haven't noticed any issues. Paul
On Tue, Mar 26, 2013 at 3:07 PM, Paul Gideon Dann <pdgiddie@gmail.com>wrote:
I also use KDE. I went ahead with the switch. I stopped akonadi first, though:
# akonadictl stop <install mariadb> # akonadictl start
And all seemed to go well. I haven't done anything special for KDE when upgrading mysql before, so I don't think anything is required now. I haven't noticed any issues.
Thank you - I had already done the mariadb install with akonadi running - however I have just stopped and restarted it, and then checked with: $ akonadictl status there seemed not to be any problem so I guess restarting KDE or rebooting would also be fine. -- mike c
On Tue, Mar 26, 2013 at 8:50 PM, Mike Cloaked <mike.cloaked@gmail.com> wrote:
With the move to mariadb I have the following situation:
I am not explicitely running mysqld so checking the status with systemctl shows it is inactive.
However I am running KDE as my desktop.
After doing the suggested install after ensuring that mysqld is stopped: pacman -S mariadb libmariadbclient mariadb-clients
and accepting the install of these packages with removal of mysql equivalents, I then find that there is a private instance of mysql running by the KDE desktop:
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 does any expert know whether a mysql_upgrade is necessary for KDE and if so how does one go about doing that upgrade?
Akonadi is using MySQL. You can disable Akonadi (personally I found it useless). $ nano .config/akonadi/akonadiserverrc StartServer=false Regards. An.
Thanks.
-- mike c
-- Nguyễn Châu An || An NGUYEN Linux Technician & FOSS Advocate ------- OpenPGP KeyID 2048R/8F77A48C Key Fingerprint 7652 B403 749F F173 227D 4865 FB71 EC95 8F77 A48C
On Wednesday 27 Mar 2013 11:05:12 An Nguyen wrote:
Akonadi is using MySQL. You can disable Akonadi (personally I found it useless).
$ nano .config/akonadi/akonadiserverrc StartServer=false
Bear in mind that all things PIM rely on Akonadi; specifically, most of Kontact. Paul
On Wed, Mar 27, 2013 at 9:45 AM, Paul Gideon Dann <pdgiddie@gmail.com>wrote:
On Wednesday 27 Mar 2013 11:05:12 An Nguyen wrote:
Akonadi is using MySQL. You can disable Akonadi (personally I found it useless).
$ nano .config/akonadi/akonadiserverrc StartServer=false
Bear in mind that all things PIM rely on Akonadi; specifically, most of Kontact.
The question remains as to whether any action is necessary after moving from mysql to mariadb for any user who is using Kontact and other KDE components that rely on mariadb after the change? Presumably there will be some people who know whether it will continue to work or not without taking any specific action once mariadb is installed? -- mike c
On Wednesday 27 March 2013 11:21:45 Mike Cloaked wrote:
The question remains as to whether any action is necessary after moving from mysql to mariadb for any user who is using Kontact and other KDE components that rely on mariadb after the change?
Presumably there will be some people who know whether it will continue to work or not without taking any specific action once mariadb is installed?
I logged out of KDE (so that Akonadi was stopped) and installed mariadb as suggested by Arch developers in their announcement. Everything is still working fine, so you should not worry about anything. Also notice that after the upgrade /usr/bin/mysqld is provided by mariadb. Bests, Stefano
On Wednesday 27 Mar 2013 11:21:45 Mike Cloaked wrote:
The question remains as to whether any action is necessary after moving from mysql to mariadb for any user who is using Kontact and other KDE components that rely on mariadb after the change?
Presumably there will be some people who know whether it will continue to work or not without taking any specific action once mariadb is installed?
Maybe you missed my reply to the original post? I have this setup, and there is no issue after upgrade. Make sure you restart Akonadi (preferably stop it before upgrade), and you should be fine. Paul
On Wed, Mar 27, 2013 at 12:13 PM, Paul Gideon Dann <pdgiddie@gmail.com>wrote:
On Wednesday 27 Mar 2013 11:21:45 Mike Cloaked wrote:
The question remains as to whether any action is necessary after moving from mysql to mariadb for any user who is using Kontact and other KDE components that rely on mariadb after the change?
Presumably there will be some people who know whether it will continue to work or not without taking any specific action once mariadb is installed?
Maybe you missed my reply to the original post? I have this setup, and there is no issue after upgrade. Make sure you restart Akonadi (preferably stop it before upgrade), and you should be fine.
Thanks - my experience was that although I had ensured that the mysqld service was stopped at the time of installing mariadb, it was also the case that since there was no mention of KDE that I could see in the original announcement I simply left akonadi running whilst installing mariadb. I have not personally had any obvious issues arising after the change, and only realised after the event that akonadi uses it even though "systemctl status mysqld" shows it is inactive. That was the reason for my original post in case some surprise related to Pim in KDE may later appear for KDE users despite the process of change being executed correctly according to the announcement. On other machines I manage I ensured that the mysqld service was stopped as well as executing aknodictl stop before installing mariadb. Since the feedback seems to indicate that there is no onward problem relating to KDE and mariadb once installed, even if that install was done with KDE and akonadi running at the time, I guess this thread can be closed. I appreciate the replies. Many thanks. -- mike c
On Wednesday 27 Mar 2013 12:22:51 Mike Cloaked wrote:
Thanks - my experience was that although I had ensured that the mysqld service was stopped at the time of installing mariadb, it was also the case that since there was no mention of KDE that I could see in the original announcement I simply left akonadi running whilst installing mariadb. I have not personally had any obvious issues arising after the change, and only realised after the event that akonadi uses it even though "systemctl status mysqld" shows it is inactive. That was the reason for my original post in case some surprise related to Pim in KDE may later appear for KDE users despite the process of change being executed correctly according to the announcement. On other machines I manage I ensured that the mysqld service was stopped as well as executing aknodictl stop before installing mariadb.
Since the feedback seems to indicate that there is no onward problem relating to KDE and mariadb once installed, even if that install was done with KDE and akonadi running at the time, I guess this thread can be closed. I appreciate the replies.
If you're curious as to why Akonadi seems to be running mysqld without systemd knowing about it, it's because Akonadi is using an embedded mysql database (like sqlite, but slightly heavier-duty and with more advanced features). It's not a "normal" mysql instance, and won't accept normal mysql client connections, for instance. I suspect that because Akonadi knows that nothing else can use the database, it takes care of any necessary upgrade migration automatically when it starts. Paul
participants (4)
-
An Nguyen
-
Mike Cloaked
-
Paul Gideon Dann
-
Stefano Avallone