[digiKam-users] Can't open DK - DB-Error external DB-Server

[Maik Qualmann]

DigiKam creates a temporary test table (PrivCheck) in the database to see if 
basic operations are possible. I suspect that their database is corrupt, here 
should be further examined, if still access is possible.

Maik

Am Sonntag, 29. Juli 2018, 20:30:55 CEST schrieb cool.chris65 at web.de:
> Hi,
> 
> since today I can't start DK AppImage 6.0.0 (Last build) because it reports
> an error "You have not the permission to alter table" ... (or similar text
> - it is always in german ...
> 
> Here is the console-output:
> -----------------------------------------
> -- digiKam AppImage Bundle
> -- Use 'help' as CLI argument to know all available options for digiKam
> application
> ERROR: ld.so: object '/usr/lib64/libfreetype.so' from LD_PRELOAD cannot be
> preloaded (cannot open shared object file): ignored.
> ERROR: ld.so: object '/usr/lib64/libfreetype.so' from LD_PRELOAD cannot be
> preloaded (cannot open shared object file): ignored.
> Digikam::DXmlGuiWindow::setupIconTheme: Breeze icons resource file found
> Digikam::AlbumWatch::AlbumWatch: AlbumWatch use QFileSystemWatcher
> Digikam::AlbumManager::setDatabase: Database Parameters:
>    Type:                     "QMYSQL"
>    DB Core Name:             "digikam"
>    DB Thumbs Name:           "digikam"
>    DB Face Name:             "digikam"
>    DB Similyritiy Name:      "digikam"
>    Connect Options:          ""
>    Host Name:                "freenas.fritz.box"
>    Host port:                3306
>    Internal Server:          false
>    Internal Server Path:     ""
>    Internal Server Serv Cmd: ""
>    Internal Server Init Cmd: ""
>    Username:                 "christoph"
>    Password:                 "XXXXXXXXX"
> 
> Digikam::DbEngineConfigSettingsLoader::readConfig: Loading SQL code from
> config file
> "/tmp/.mount_digikaY4TbNV/usr/share/digikam/database/dbconfig.xml"
> Digikam::DbEngineConfigSettingsLoader::readConfig: Checking XML version ID
> => expected:  3  found:  3
> Digikam::CoreDbSchemaUpdater::update: Core database: running schema update
> Digikam::BdEngineBackendPrivate::debugOutputFailedQuery: Failure executing
> query:
>  ""
> Error messages: "QMYSQL: Unable to execute query" "Can't DROP 'name'; check
> that column/key exists" 1091 2
> Bound values:  ()
> Digikam::BdEngineBackend::execDBAction: Error while executing DBAction [
> "CheckPriv_ALTER_TABLE" ] Statement [ "\n                    ALTER TABLE
> PrivCheck DROP COLUMN name;\n                " ]
> Digikam::CoreDbPrivilegesChecker::checkPriv: Core database: error while
> creating a trigger. Details:  QSqlError("1091", "QMYSQL: Unable to execute
> query", "Can't DROP 'name'; check that column/key exists")
> Digikam::CoreDbSchemaUpdater::startUpdates: Core database: insufficient
> rights on database.
> Digikam::CoreDbAccess::checkReadyForUse: Core database: cannot process
> schema initialization
> Digikam::KMemoryInfo::update: KMemoryInfo: Platform identified :  "LINUX"
> Digikam::KMemoryInfo::bytes: KMemoryInfo: TotalRam:  16766746624
> Digikam::LoadingCache::setCacheSize: Allowing a cache size of 200 MB
> unknown: QThreadStorage: Thread 0x7f5fae3dcea0 exited after QThreadStorage
> 11 destroyed
> 
> ----------------------------------------------------------------------------
> --------------- the used user has all rights which are needed to operate,
> and there was no change to the user at all
> 
> This problem starts after trouble with dk and killing it from desktop.
> the server is mariadb 10.0 on debian8, dk is running on a kubuntu 18.04-64
> desktop
> 
> Hope you can help
> Thx
> 
> Greetz, Christoph