| Summary: | Error creating mysql db for internal server (mysql_install_db) | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Tobias Philipp <maillist> |
| Component: | Database-Mysql | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, KDE, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 5.8.0 | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.1.0 | |
| Sentry Crash Report: | |||
| Attachments: |
Error message screenshot
First run dialog with mysql binaries found |
||
|
Description
Tobias Philipp
2018-01-18 21:22:22 UTC
I think it's a problem of the AppImage and finding the right path. Here under openSUSE the AppImage does not find the path to the mysqld and has to be set manually. Set in the dialog the path to mysql_install_db for testing please manually. The syntax for mysql_install_db is correct and works here under a native digiKam version without problems. Here also with a newer MariaDB version. Maik Hi, sorry for the late answer... I deleted the previously generated config files and data directories and started from scratch. The first run dialog shows that he is finding the binaris correct. but i set them nevertheless through the file picker dialog. Nothing changed, same error. How a said in the first comment, if i run the mysql_install_db with the arguments given in the error message from digikam in a console window, i get an error message from mysql_install_db. i think, digikam is getting the same error message... Aattached the screenshot with the mysql binaris found by the first run dialog, bevore i set them. Created attachment 110057 [details]
First run dialog with mysql binaries found
The question is, are my_print_defaults and mysql_install_db not in the same directory? Maik Hi, i checked the location of the files: [philipp@ryzen ~]$ which my_print_defaults /usr/bin/my_print_defaults [philipp@ryzen ~]$ which mysql_install_db /usr/bin/mysql_install_db digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Best Regards Gilles Caulier Hi, i tested the mysql_internal feature with the 7.0 build from Manjaro (Appimage is not working) and i could create and use digikam with internal mysql db without problems. One question: Are the mysql-bin.00000* (Binary Log Files) needed for digikam to function properly? The "digikam" folder in db_data is 6.1GB large, the bin logs add another 8.1GB... (for 196.000 images) digikam 7.0.0-2 Manjaro my_print_defaults Ver 1.7 mariadb 10.4.14-1 Greetings Tobias mysql-bin.00000* (Binary Log Files) are for recovery purpose. See details here: https://stackoverflow.com/questions/29557000/how-to-prevent-mysql-from-createing-mysql-bin-00000x-files Gilles Caulier |