This forum has been archived. All content is frozen. Please use KDE Discuss instead.

DB problem after upgrade of akonadi-server

Tags: None
(comma "," separated)
User avatar
Oceanwaves
Registered Member
Posts
64
Karma
0
OS
Hello,

I'm using Gentoo Linux and currently KDE 4.7.4.

Gentoo updated akonadi-server from version 1.6.2 to version 1.7.1.

As a result kmail is not able to access any mail anymore :(. I'm seeing the subjects but can't open any mail.

I'm using a local IMAP server (cyrus-imap) which kmail connects to.

My ~/.config/akonadi/akonadiserverrc looks like this:
Code: Select all
[%General]
Driver=QMYSQL
SizeThreshold=4096
ExternalPayload=false

[QMYSQL]
Name=akonadi
Host=
User=
Password=
Options="UNIX_SOCKET=/home/oliver/.local/share/akonadi/socket-frodo/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true

[Debug]
Tracer=null

When starting akonadi manually (akonadictl start) I'm getting a lot of error messages:
Code: Select all
Starting Akonadi Server...
   done.
         Connecting to deprecated signal
         QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
         search paths:
         ("/etc/java-config-2/current-system-vm/bin",
         "/etc/java-config-2/current-system-vm/bin", "/usr/local/bin", "/usr/bin",
         "/bin", "/opt/bin", "/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.3",
         "/opt/vmware/bin", "/usr/lib64/cyrus", "/home/oliver/bin", "",
         "/home/oliver/bin", "", "/usr/sbin", "/usr/local/sbin",
         "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec",
         "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
         Found mysql_install_db:  "/usr/bin/mysql_install_db"
         Found mysqlcheck:  "/usr/bin/mysqlcheck"
         akonadi.collectionattributetable                   OK
         akonadi.collectionmimetyperelation                 OK
         akonadi.collectionpimitemrelation                  OK
         akonadi.collectiontable                            OK
         akonadi.flagtable                                  OK
         akonadi.mimetypetable                              OK
         akonadi.parttable                                  OK
         akonadi.pimitemflagrelation                        OK
         akonadi.pimitemtable                               OK
         akonadi.resourcetable                              OK
         akonadi.schemaversiontable                         OK
         mysql.columns_priv                                 OK
         mysql.db                                           OK
         mysql.func                                         OK
         mysql.help_category                                OK
         mysql.help_keyword                                 OK
         mysql.help_relation                                OK
         mysql.help_topic                                   OK
         mysql.host                                         OK
         mysql.proc                                         OK
         mysql.procs_priv                                   OK
         mysql.tables_priv                                  OK
         mysql.time_zone                                    OK
         mysql.time_zone_leap_second                        OK
         mysql.time_zone_name                               OK
         mysql.time_zone_transition                         OK
         mysql.time_zone_transition_type                    OK
         mysql.user                                         OK
         Database "akonadi" opened using driver "QMYSQL"
         DbInitializer::run()
         checking table  "SchemaVersionTable"
         checking table  "ResourceTable"
         checking table  "CollectionTable"
         checking table  "MimeTypeTable"
         checking table  "PimItemTable"
         checking table  "FlagTable"
         checking table  "PartTable"
         checking table  "CollectionAttributeTable"
         checking relation  "PimItemFlagRelation"
         checking relation  "CollectionMimeTypeRelation"
         checking relation  "CollectionPimItemRelation"
         DbInitializer::run() done
         skipping update 2
         skipping update 3
         skipping update 4
         skipping update 8
         skipping update 10
         skipping update 12
         skipping update 13
         skipping update 14
         skipping update 15
         skipping update 16
         skipping update 17
         skipping update 18
         skipping update 19
         DbUpdater: update to version: 20  mandatory: false
         DBUpdater: query error: "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL: Unable to execute query" " "
         Query was:  "ALTER TABLE CollectionTable CHANGE queryString queryString
         VARBINARY(1024);"
         Target version was:  20
         Mandatory:  false
         Failed to commit transaction for database update
         Akonadi::NepomukSearchEngine(0x1a88860) QObject(0x0)
         Database "akonadi" opened using driver "QMYSQL"
         Database "akonadi" opened using driver "QMYSQL"
         Database "akonadi" opened using driver "QMYSQL"
         Connecting to deprecated signal
         QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
         DataStore::unhideAllPimItems()
         Error during executing query "DELETE FROM PartTable WHERE ( PartTable.name
         = ( :0 ) )" :  "Binary logging not possible. Message: Transaction level
         'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT' QMYSQL3:
         Unable to execute statement"
         Error during deleting records from table "PartTable" "Binary logging not
         possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe
         for binlog mode 'STATEMENT' QMYSQL3: Unable to execute statement"
         PLUGINS:  "/usr/share/akonadi/agents"
         PLUGINS:  ("akonotesresource.desktop", "birthdaysresource.desktop",
         "calendarsearchagent.desktop", "contactsresource.desktop",
         "davgroupwareresource.desktop", "googlecalendarresource.desktop",
         "googlecontactsresource.desktop", "googletasksresource.desktop",
         "icalresource.desktop", "imapresource.desktop", "invitationsagent.desktop",
         "kabcresource.desktop", "kcalresource.desktop",
         "kdeaccountsresource.desktop", "knutresource.desktop",
         "kolabproxyresource.desktop", "localbookmarksresource.desktop",
         "maildirresource.desktop", "maildispatcheragent.desktop",
         "mboxresource.desktop", "microblog.desktop",
         "mixedmaildirresource.desktop", "mtdummyresource.desktop",
         "nepomukcalendarfeeder.desktop", "nepomukcontactfeeder.desktop",
         "nepomukemailfeeder.desktop", "nepomuktagresource.desktop",
         "nntpresource.desktop", "notesresource.desktop",
         "openxchangeresource.desktop", "pop3resource.desktop",
         "vcarddirresource.desktop", "vcardresource.desktop")
         PLUGINS inserting:  "akonadi_akonotes_resource" 4 ("Resource", "Notes")
         search paths:  ("/etc/java-config-2/current-system-vm/bin",
         "/etc/java-config-2/current-system-vm/bin", "/usr/local/bin", "/usr/bin",
         "/bin", "/opt/bin", "/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.3",
         "/opt/vmware/bin", "/usr/lib64/cyrus", "/home/oliver/bin", "",
         "/home/oliver/bin", "")
         PLUGINS inserting:  "akonadi_birthdays_resource" 0 ("Resource", "Unique")
         PLUGINS inserting:  "akonadi_calendarsearch_agent" 0 ("Unique", "NoConfig")
         PLUGINS inserting:  "akonadi_contacts_resource" 0 ("Resource")
         PLUGINS inserting:  "akonadi_davgroupware_resource" 0 ("Resource")
         PLUGINS inserting:  "akonadi_googlecalendar_resource" 6 ("Resource")
         PLUGINS inserting:  "akonadi_googlecontacts_resource" 0 ("Resource")
         PLUGINS inserting:  "akonadi_googletasks_resource" 1 ("Resource")
         PLUGINS inserting:  "akonadi_ical_resource" 1 ("Resource")
         PLUGINS inserting:  "akonadi_imap_resource" 4 ("Resource")
         PLUGINS inserting:  "akonadi_invitations_agent" 0 ("NoConfig")
         PLUGINS inserting:  "akonadi_kabc_resource" 1 ("Resource")
         PLUGINS inserting:  "akonadi_kcal_resource" 0 ("Resource")
         PLUGINS inserting:  "akonadi_kdeaccounts_resource" 0 ("Resource")
         PLUGINS inserting:  "akonadi_knut_resource" 0 ("Resource")
         PLUGINS inserting:  "akonadi_kolabproxy_resource" 0 ("Resource", "Unique")
         PLUGINS inserting:  "akonadi_localbookmarks_resource" 0 ("Resource")
         PLUGINS inserting:  "akonadi_maildir_resource" 2 ("Resource")
         PLUGINS inserting:  "akonadi_maildispatcher_agent" 0 ("Unique",
         "Autostart")
         PLUGINS inserting:  "akonadi_mbox_resource" 1 ("Resource")
         PLUGINS inserting:  "akonadi_microblog_resource" 0 ("Resource")
         PLUGINS inserting:  "akonadi_mixedmaildir_resource" 1 ("Resource")
         PLUGINS inserting:  "akonadi_mailtransport_dummy_resource" 0 ("Resource",
         "MailTransport")
         PLUGINS inserting:  "akonadi_nepomuk_calendar_feeder" 0 ("Unique",
         "Autostart", "NoConfig")
         PLUGINS inserting:  "akonadi_nepomuk_contact_feeder" 0 ("Unique",
         "Autostart", "NoConfig")
         PLUGINS inserting:  "akonadi_nepomuk_email_feeder" 0 ("Unique", "Search",
         "Autostart")
         PLUGINS inserting:  "akonadi_nepomuktag_resource" 0 ("Resource", "Virtual",
         "Unique", "NoConfig")
         PLUGINS inserting:  "akonadi_nntp_resource" 0 ("Resource")
         PLUGINS inserting:  "akonadi_notes_resource" 0 ("Resource")
         PLUGINS inserting:  "akonadi_openxchange_resource" 0 ("Resource")
         PLUGINS inserting:  "akonadi_pop3_resource" 1 ("Resource")
         PLUGINS inserting:  "akonadi_vcarddir_resource" 0 ("Resource")
         PLUGINS inserting:  "akonadi_vcard_resource" 1 ("Resource")
         search paths:  ("/usr/lib64/kde4/plugins",
         "/home/oliver/.kde4/lib64/kde4/plugins/", "/usr/lib64/kde4/plugins/",
         "/usr/lib64/qt4/plugins", "/usr/bin", "/home/oliver/.kde4/lib64/kde4/",
         "/usr/lib64/kde4/")
         search paths:  ("/usr/lib64/kde4/plugins",
         "/home/oliver/.kde4/lib64/kde4/plugins/", "/usr/lib64/kde4/plugins/",
         "/usr/lib64/qt4/plugins", "/usr/bin", "/home/oliver/.kde4/lib64/kde4/",
         "/usr/lib64/kde4/")
         search paths:  ("/usr/lib64/kde4/plugins",
         "/home/oliver/.kde4/lib64/kde4/plugins/", "/usr/lib64/kde4/plugins/",
         "/usr/lib64/qt4/plugins", "/usr/bin", "/home/oliver/.kde4/lib64/kde4/",
         "/usr/lib64/kde4/")
         AkonadiAgentServer(4973)/libakonadi
         Akonadi::AgentManagerPrivate::createDBusInterface: AgentManager failed to
         get a valid AgentManager DBus interface. Error is: 1
         "org.freedesktop.DBus.Error.NameHasNoOwner" "Could not get owner of name
         'org.freedesktop.Akonadi.Control': no such name"
         Agent instance created in separate process.
         Known subscriber "AkonadiAgentServer" subscribes again
         void Akonadi::NotificationSource::addClientServiceName(const QString&)
         Notification source "AkonadiAgentServer" now serving: (":1.121", ":1.122")
         Known subscriber "AkonadiAgentServer" subscribes again
         void Akonadi::NotificationSource::addClientServiceName(const QString&)
         Notification source "AkonadiAgentServer" now serving: (":1.121", ":1.122",
         ":1.123")
         Database "akonadi" opened using driver "QMYSQL"
         AkonadiAgentServer(4971)/libakonadi
         Akonadi::AgentManagerPrivate::createDBusInterface: AgentManager failed to
         get a valid AgentManager DBus interface. Error is: 1
         "org.freedesktop.DBus.Error.NameHasNoOwner" "Could not get owner of name
         'org.freedesktop.Akonadi.Control': no such name"
         AkonadiAgentServer(4974)/libakonadi
         Akonadi::AgentManagerPrivate::createDBusInterface: AgentManager failed to
         get a valid AgentManager DBus interface. Error is: 1
         "org.freedesktop.DBus.Error.NameHasNoOwner" "Could not get owner of name
         'org.freedesktop.Akonadi.Control': no such name"
         Agent instance created in separate process.
         Agent instance created in separate process.
         Database "akonadi" opened using driver "QMYSQL"
         search paths:  ("/usr/lib64/kde4/plugins",
         "/home/oliver/.kde4/lib64/kde4/plugins/", "/usr/lib64/kde4/plugins/",
         "/usr/lib64/qt4/plugins", "/usr/bin", "/home/oliver/.kde4/lib64/kde4/",
         "/usr/lib64/kde4/")
         Akonadi server is now operational.
         Known subscriber "AkonadiAgentServer" subscribes again
         Known subscriber "AkonadiAgentServer" subscribes again
         void Akonadi::NotificationSource::addClientServiceName(const QString&)
         Notification source "AkonadiAgentServer" now serving: (":1.121", ":1.122",
         ":1.123", ":1.125")
         Database "akonadi" opened using driver "QMYSQL"
         search paths:  ("/usr/lib64/kde4/plugins",
         "/home/oliver/.kde4/lib64/kde4/plugins/", "/usr/lib64/kde4/plugins/",
         "/usr/lib64/qt4/plugins", "/usr/bin", "/home/oliver/.kde4/lib64/kde4/",
         "/usr/lib64/kde4/")
         Known subscriber "AkonadiAgentServer" subscribes again
         void Akonadi::NotificationSource::addClientServiceName(const QString&)
         Notification source "AkonadiAgentServer" now serving: (":1.121", ":1.122",
         ":1.123", ":1.125", ":1.130")
         Database "akonadi" opened using driver "QMYSQL"
         Database "akonadi" opened using driver "QMYSQL"
         Database "akonadi" opened using driver "QMYSQL"
         search paths:  ("/usr/lib64/kde4/plugins",
         "/home/oliver/.kde4/lib64/kde4/plugins/", "/usr/lib64/kde4/plugins/",
         "/usr/lib64/qt4/plugins", "/usr/bin", "/home/oliver/.kde4/lib64/kde4/",
         "/usr/lib64/kde4/")
         Known subscriber "AkonadiAgentServer" subscribes again
         void Akonadi::NotificationSource::addClientServiceName(const QString&)
         Notification source "AkonadiAgentServer" now serving: (":1.121", ":1.122",
         ":1.123", ":1.125", ":1.130", ":1.139")
         Database "akonadi" opened using driver "QMYSQL"
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         Known subscriber "AkonadiAgentServer" subscribes again
         search paths:  ("/usr/lib64/kde4/plugins",
         "/home/oliver/.kde4/lib64/kde4/plugins/", "/usr/lib64/kde4/plugins/",
         "/usr/lib64/qt4/plugins", "/usr/bin", "/home/oliver/.kde4/lib64/kde4/",
         "/usr/lib64/kde4/")
         Known subscriber "AkonadiAgentServer" subscribes again
         void Akonadi::NotificationSource::addClientServiceName(const QString&)
         Notification source "AkonadiAgentServer" now serving: (":1.121", ":1.122",
         ":1.123", ":1.125", ":1.130", ":1.139", ":1.143")
         Known subscriber "AkonadiAgentServer" subscribes again
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         Agent instance created in separate process.
         Database "akonadi" opened using driver "QMYSQL"
         Known subscriber "akonadi_birthdays_resource_0" subscribes again
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         Database "akonadi" opened using driver "QMYSQL"
         Database "akonadi" opened using driver "QMYSQL"
         Agent instance created in separate process.
         Database "akonadi" opened using driver "QMYSQL"
         Database "akonadi" opened using driver "QMYSQL"
         Agent instance created in separate process.
         Known subscriber "akonadi_maildispatcher_agent" subscribes again
         Known subscriber "akonadi_maildispatcher_agent" subscribes again
         Database "akonadi" opened using driver "QMYSQL"
         akonadi_kabc_resource_0(4987)/kio (KDirWatch)
         KDirWatchPrivate::removeEntry: doesn't know
         "/home/oliver/.kde4/share/apps/kabc"
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         Database "akonadi" opened using driver "QMYSQL"
         Database "akonadi" opened using driver "QMYSQL"
         Database "akonadi" opened using driver "QMYSQL"
         Database "akonadi" opened using driver "QMYSQL"
         Database "akonadi" opened using driver "QMYSQL"
         Database "akonadi" opened using driver "QMYSQL"
         Database "akonadi" opened using driver "QMYSQL"
         Agent instance created in separate process.
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         akonadi_nepomuk_email_feeder(4998)/kdecore (KConfigSkeleton)
         KCoreConfigSkeleton::writeConfig:
         Database "akonadi" opened using driver "QMYSQL"
         Database "akonadi" opened using driver "QMYSQL"
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE ( (
         PimItemTable.id = :1 ) )" :  "Binary logging not possible. Message:
         Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode
         'STATEMENT' QMYSQL3: Unable to execute statement"
         Unable to update item access time
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         Database "akonadi" opened using driver "QMYSQL"
         Database "akonadi" opened using driver "QMYSQL"
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         Database "akonadi" opened using driver "QMYSQL"
         Database "akonadi" opened using driver "QMYSQL"
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         Unable to update item access time
         Database "akonadi" opened using driver "QMYSQL"
         Database "akonadi" opened using driver "QMYSQL"
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         akonadi_imap_resource_2(4984)/kdecore (KConfigSkeleton)
         KCoreConfigSkeleton::writeConfig:
         Unable to update item access time
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         akonadi_googlecalendar_resource_0(4976)
         KGoogle::KGoogleAccessManager::nam_replyReceived: Unknown error 0 , Google
         replied ' "" '
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         akonadi_googlecalendar_resource_1(4977)
         KGoogle::KGoogleAccessManager::nam_replyReceived: Unknown error 0 , Google
         replied ' "" '
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         akonadi_googlecalendar_resource_2(4978)
         KGoogle::KGoogleAccessManager::nam_replyReceived: Unknown error 0 , Google
         replied ' "" '
         akonadi_googlecalendar_resource_4(4980)
         KGoogle::KGoogleAccessManager::nam_replyReceived: Unknown error 0 , Google
         replied ' "" '
         akonadi_googlecalendar_resource_5(4981)
         KGoogle::KGoogleAccessManager::nam_replyReceived: Unknown error 0 , Google
         replied ' "" '
         akonadi_googlecalendar_resource_3(4979)
         KGoogle::KGoogleAccessManager::nam_replyReceived: Unknown error 0 , Google
         replied ' "" '
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         akonadi_maildispatcher_agent(4988) OutboxQueue::Private::addIfComplete:
         Item 74050 does not have the required attribute Address.
         akonadi_maildispatcher_agent(4988) OutboxQueue::Private::addIfComplete:
         Item 74049 does not have the required attribute Address.
         akonadi_maildispatcher_agent(4988) OutboxQueue::Private::addIfComplete:
         Item 74048 does not have the required attribute Address.
         akonadi_maildispatcher_agent(4988) OutboxQueue::Private::addIfComplete:
         Item 74047 does not have the required attribute Address.
         akonadi_maildispatcher_agent(4988) OutboxQueue::Private::addIfComplete:
         Item 74046 does not have the required attribute Address.
         akonadi_maildispatcher_agent(4988) OutboxQueue::Private::addIfComplete:
         Item 74045 does not have the required attribute Address.
         akonadi_maildispatcher_agent(4988) OutboxQueue::Private::addIfComplete:
         Item 74044 does not have the required attribute Address.
         akonadi_maildispatcher_agent(4988) OutboxQueue::Private::addIfComplete:
         Item 74043 does not have the required attribute Address.
         akonadi_maildispatcher_agent(4988) OutboxQueue::Private::addIfComplete:
         Item 74042 does not have the required attribute Address.
         akonadi_maildispatcher_agent(4988) OutboxQueue::Private::addIfComplete:
         Item 74041 does not have the required attribute Address.
         akonadi_maildispatcher_agent(4988) OutboxQueue::Private::addIfComplete:
         Item 74040 does not have the required attribute Address.
         akonadi_maildispatcher_agent(4988) OutboxQueue::Private::addIfComplete:
         Item 74039 does not have the required attribute Address.
         akonadi_maildispatcher_agent(4988) OutboxQueue::Private::addIfComplete:
         Item 74038 does not have the required attribute Address.
         akonadi_maildispatcher_agent(4988) OutboxQueue::Private::addIfComplete:
         Item 74037 does not have the required attribute Address.
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time
         Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE (
         collectionId = :1 )" :  "Binary logging not possible. Message: Transaction
         level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
         QMYSQL3: Unable to execute statement"
         Unable to update item access time


I also ran mysql_upgrade but without any success.

When blocking akonadi-server version 1.7.1 and going back to version 1.6.2 everything works fine.

As a workaround I switched to Thunderbird but I would like to go back to KDE-PIM and kmail.

Oliver
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Please try removing ~/.local/share/akonadi/mysql.conf as it seems that InnoDB is running at an insufficient level for some reason for writes to occur to the database, which I suspect is related to an out of date configuration.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
User avatar
Oceanwaves
Registered Member
Posts
64
Karma
0
OS
Thanks for your fast reply, unfortunately it didn't help.

I stopped akonadi (akonadictl stop), moved ~/.local/share/akonadi/mysql.conf to a backup folder, updated akonadi-server to version 1.7.1 and started akonadi again (akonadictl start).

Same error messages, the newly created ~/.local/share/akonadi/mysql.conf is identical to the old version.

The system was set up from scratch in February (new hardware), I only kept my home directory. In addition I switched Linux from 32 to 64 bit, but KDE version didn't change (I was using v4.7.4 32 bit on the old system and now v4.7.4 64 bit). Maybe this is important.

But with akonadi-server version 1.6.2 everything worked fine.

Oliver
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Sorry, you seem to have been hit by http://bugs.mysql.com/bug.php?id=40360

You may need to manually the previously mentioned mysql.conf file to restore the ability of MySQL to be used by Akonadi. I do not know why this has occurred unfortunately.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
User avatar
Oceanwaves
Registered Member
Posts
64
Karma
0
OS
bcooksley wrote:Sorry, you seem to have been hit by http://bugs.mysql.com/bug.php?id=40360

You may need to manually the previously mentioned mysql.conf file to restore the ability of MySQL to be used by Akonadi. I do not know why this has occurred unfortunately.

The bug you mentioned is more than 3 years old. I'm using mysql 5.1.61 and it should be fixed in this version.

However, I don't know MySQL and have no idea what to change in my mysql.conf.
This is my ~/.local/share/akonadi/mysql.conf:
Code: Select all
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
# sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
# sql_mode=strict_trans_tables

# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for production use
# log_queries_not_using_indexes=1
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");

# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)

#expire_logs_days=3

#sync_bin_log=0

# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb

# memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
innodb_additional_mem_pool_size=1M

# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M

# Create a .ibd file for each table (default:0)
innodb_file_per_table=1

# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2

# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M

# Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
innodb_log_file_size=64M

# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err

# print warnings and connection errors (default:1)
log_warnings=2

# Convert table named to lowercase
lower_case_table_names=1

# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M

# Maximum simultaneous connections allowed (default:100)
max_connections=256

# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)

# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0

# Do not cache results (default:1)
query_cache_type=0

# Do not use the privileges mechanisms
skip_grant_tables

# Do not listen for TCP/IP connections at all
skip_networking

# The number of open tables for all threads. (default:64)
table_cache=200

# How many threads the server should cache for reuse (default:0)
thread_cache_size=3

# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000

[client]
default-character-set=utf8
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]
skip_grant_tables
skip_networking

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
#sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
sql_mode=strict_trans_tables

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=latin1
collation_server=latin1_general_ci
table_cache=200
thread_cache_size=3
log_bin=mysql-bin
expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# log all queries, useful for debugging but generates an enormous amount of data
#log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
#log_slow_queries=mysql.slow
#long_query_time=1
# log queries not using indices, debug only, disable for production use
#log_queries_not_using_indexes=1
# maximum blob size
max_allowed_packet=32M
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0

innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
innodb_buffer_pool_size=80M
# size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2


Thanks so far,

Oliver
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Under the [mysql] section, please try adding:
Code: Select all
binlog_format=row


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
User avatar
Oceanwaves
Registered Member
Posts
64
Karma
0
OS
bcooksley wrote:Under the [mysql] section, please try adding:
Code: Select all
binlog_format=row

My ~/.local/share/akonadi/mysql.conf has two [mysqld] sections:
Code: Select all
 ~ $ grep "^\[" ~/.local/share/akonadi/mysql.conf
[mysqld]
[client]
[mysqld]

I added binlog_format=row after the first [mysqld] and... it worked!

No error messages at all after starting akonadi and kmail is able to access all mails. Great!

Thank you very much for your help!

Now I can open a new thread and try to find a solution for my search problem with kmail... ;)

Oliver


Bookmarks



Who is online

Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell