[Akonadi] [Bug 397634] Is it possible to define a port for akonadi mariadb database ?
https://bugs.kde.org/show_bug.cgi?id=397634 Nick changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Nick --- Thank you to all who commented on my questions. Also, I apologize for my late response . I am in process of analyzing Daniel's comments/recommendations then deciding how to proceed . I hope that this will help me to alleviate / eliminate those "waiting for update/read/etc" that happens quite often inn Kmail5 . For the time being I will change tje status of this ticket to REPORTED . Thanks again to everybody . Regards, Nick -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 397634] Is it possible to define a port for akonadi mariadb database ?
https://bugs.kde.org/show_bug.cgi?id=397634 Andrew Crouthamel changed: What|Removed |Added Keywords||triaged --- Comment #4 from Andrew Crouthamel --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 397634] Is it possible to define a port for akonadi mariadb database ?
https://bugs.kde.org/show_bug.cgi?id=397634 Christoph Feck changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from Christoph Feck --- If you can provide the information requested in comment #2, please add it. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 397634] Is it possible to define a port for akonadi mariadb database ?
https://bugs.kde.org/show_bug.cgi?id=397634 --- Comment #2 from Christoph Feck --- Nick, did comment #1 help to resolve your issues? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 397634] Is it possible to define a port for akonadi mariadb database ?
https://bugs.kde.org/show_bug.cgi?id=397634 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- Akonadi can only start MariaDB/MySQL in the local socket mode, and I'm quite surprised that tools like adminer cannot connect to a socket as well. However, if you take care of starting the database server yourself (usually as a system-wide service), you can configure Akonadi to connect to that database instead of its custom instance. We currently don't have any GUI to do that, so manually changing ~/.config/akonadiserverrc is needed: [QMYSQL] Name=akonadi Host=localhost User=username Password=youpassword StartServer=false And that should work...:) Regarding your questions: 1) No password, as long as the connecting applications is running under the same user as the database server. No port either, Akonadi is communicating via a local socket 2) There's no difference to Akonadi whether you use "internal" or "external" DB. The only difference is that in case of "external" DB, it's up to you to make sure the database server is started before starting Akonadi 3) Yes, you can just dump everything from the internal DB and import it to your system-wide instance, then you just need to adjust the configuration as described above and make sure the system-wide instance is autostarted 4) It should be OK, some distributions ship Oracle MySQL as default and Akonadi works there as well 5) Indeed, use mysqldump to dump everything from the internal MySQL db and import it into your system-wide database, then adjust the Akonadi configuration in ~/.config/akonadi/akonadiserverrc and you should be good. Make sure that when you are manipulating the database that Akonadi is not running (you can use the "akonadictl" CLI tool to check the status, stop and start Akonadi) - I recommend that for the migration you start the Akonadi's MySQL db manually to make sure Akonadi is not changing the content of the DB while you are migrating it. -- You are receiving this mail because: You are the assignee for the bug.
