Автор Тема: Проблемы с запуском akonadi [решено]  (Прочитано 5678 раз)

Оффлайн Mimas

  • Завсегдатай
  • *
  • Сообщений: 230
  • Mimas
    • Мой Линукс
    • Email
Подозреваю, что при очередном обновлении, что-то случилось с akonadi. Понял это по тому, что kmail стал зависать, а при рестарте ругается: "Инфраструктура управления личной информацией Akonadi не работает". Как починить?
Отчёт:
Спойлер
Akonadi Server Self-Test Report
===============================

Test 1:  ERROR
--------

Database driver not found.
Details: The QtSQL driver 'QSQLITE3' is required by your current Akonadi server configuration.
The following drivers are installed: QSQLITE, QMYSQL3, QMYSQL.
Make sure the required driver is installed.

File content of '/home/strygin/.config/akonadi/akonadiserverrc':
[%General]
Driver=QSQLITE3

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/.private/strygin/akonadi-strygin.PgI15v/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true
User=
Password=

[Debug]
Tracer=null

[QPSQL]
StartServer=true
Name=akonadi
Host=
User=
Password=
Port=5432

[SQLITE]
Name=akonadi

[QSQLITE3]
Name=/home/strygin/.local/share/akonadi/akonadi.db


Test 2:  SUCCESS
--------

Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.

Test 3:  SKIP
--------

MySQL server executable not tested.
Details: The current configuration does not require an internal MySQL server.

Test 4:  SKIP
--------

MySQL server error log not tested.
Details: The current configuration does not require an internal MySQL server.

Test 5:  SKIP
--------

MySQL server configuration not tested.
Details: The current configuration does not require an internal MySQL server.

Test 6:  SUCCESS
--------

akonadictl found and usable
Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
Result:
Akonadi 1.11.0


Test 7:  ERROR
--------

Akonadi control process not registered at D-Bus.
Details: The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 8:  ERROR
--------

Akonadi server process not registered at D-Bus.
Details: The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 9:  SUCCESS
--------

Nepomuk search service registered at D-Bus.
Details: The Nepomuk search service is registered at D-Bus which typically indicates it is operational.

Test 10:  SUCCESS
--------

Nepomuk search service uses an appropriate backend.
Details: The Nepomuk search service uses one of the recommended backends.

Test 11:  SKIP
--------

Protocol version check not possible.
Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements.

Test 12:  SUCCESS
--------

Resource agents found.
Details: At least one resource agent has been found.

Directory listing of '/usr/share/akonadi/agents':
akonadinepomukfeederagent.desktop
akonotesresource.desktop
archivemailagent.desktop
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.desktop
facebookresource.desktop
folderarchiveagent.desktop
googlecalendarresource.desktop
googlecontactsresource.desktop
icaldirresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kabcresource.desktop
kalarmdirresource.desktop
kalarmresource.desktop
kcalresource.desktop
kdeaccountsresource.desktop
knutresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mailfilteragent.desktop
mboxresource.desktop
microblog.desktop
migrationagent.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
nepomuktagresource.desktop
newmailnotifieragent.desktop
nntpresource.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
sendlateragent.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to '/usr/share/kde4:/usr/share'

Test 13:  ERROR
--------

Current Akonadi server error log found.
Details: The Akonadi server reported errors during its current startup. The log can be found in <a href='/home/strygin/.local/share/akonadi/akonadiserver.error'>/home/strygin/.local/share/akonadi/akonadiserver.error</a>.

File content of '/home/strygin/.local/share/akonadi/akonadiserver.error':
Invalid database object during initial database connection
"[
0: akonadiserver(_Z11akBacktracev+0x35) [0x80959a5]
1: akonadiserver() [0x8095cda]
2: linux-gate.so.1(__kernel_sigreturn+0) [0xb7715404]
3: /lib/libc.so.6(gsignal+0x45) [0xb6e5e095]
4: /lib/libc.so.6(abort+0x143) [0xb6e5f883]
5: /usr/lib/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x8e) [0xb74d079e]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xd8) [0x8097a78]
7: /usr/lib/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xe8) [0xb75689e8]
8: /usr/lib/libQtCore.so.4(+0xfe095) [0xb7575095]
9: /usr/lib/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x68) [0xb75751d8]
10: akonadiserver(_ZN7Akonadi13AkonadiServer14createDatabaseEv+0x170) [0x8098910]
11: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0xe1d) [0x809a48d]
12: /usr/lib/libQtCore.so.4(_ZN14QMetaCallEvent13placeMetaCallEP7QObject+0x3a) [0xb75e006a]
13: /usr/lib/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x25b) [0xb75e421b]
14: /usr/lib/libQtCore.so.4(_ZN23QCoreApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x78) [0xb75d02b8]
15: /usr/lib/libQtCore.so.4(_ZN16QCoreApplication6notifyEP7QObjectP6QEvent+0x64) [0xb75d0324]
16: /usr/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8e) [0xb75d00ce]
17: /usr/lib/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x389) [0xb75d32c9]
18: /usr/lib/libQtCore.so.4(_ZN16QCoreApplication16sendPostedEventsEP7QObjecti+0x2c) [0xb75d356c]
19: /usr/lib/libQtCore.so.4(+0x1851ef) [0xb75fc1ef]
20: /lib/libglib-2.0.so.0(g_main_context_dispatch+0x143) [0xb6d11ff3]
21: /lib/libglib-2.0.so.0(+0x4b390) [0xb6d12390]
22: /lib/libglib-2.0.so.0(g_main_context_iteration+0x41) [0xb6d12471]
23: /usr/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x75) [0xb75fc365]
24: /usr/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x4c) [0xb75cec2c]
25: /usr/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x149) [0xb75cef39]
26: /usr/lib/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x9a) [0xb75d361a]
27: akonadiserver(main+0x147) [0x808f9e7]
28: /lib/libc.so.6(__libc_start_main+0xf5) [0xb6e495d5]
29: akonadiserver() [0x8090191]
]
"


Test 14:  SUCCESS
--------

No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.

« Последнее редактирование: 26.12.2015 20:52:43 от Mimas »

Оффлайн Koi

  • alt linux team
  • ***
  • Сообщений: 1 893
  • валар дохаэрис
    • Канал на youtube
Re: Проблемы с запуском akonadi
« Ответ #1 : 25.12.2015 18:34:05 »
Цитировать
Database driver not found.
Details: The QtSQL driver 'QSQLITE3' is required by your current Akonadi server configuration.
The following drivers are installed: QSQLITE, QMYSQL3, QMYSQL.
Make sure the required driver is installed.
В настройках "Параметры kde" есть пункт akonadi. Зайдите в него и на вкладке "настройка сервера" выберите базу данных и запустите сервер.

Если Вы раньше пользовались, то базы должны быть установлены, на всякий случай посмотрите вывод:
$ rpm -qa |grep akonadi-database
Если вы использовали раньше MYSQL, то убедитесь, что загрузка базы прописана в автозагрузке.
Галочка локальный сервер должна быть включена.

Проверить есть ли mysqld в автозагрузке и ее статус:
$ chkconfig --list | grep mysqld
« Последнее редактирование: 25.12.2015 18:39:12 от Koi »

Оффлайн Mimas

  • Завсегдатай
  • *
  • Сообщений: 230
  • Mimas
    • Мой Линукс
    • Email
Re: Проблемы с запуском akonadi
« Ответ #2 : 26.12.2015 15:59:30 »
$ rpm -qa |grep akonadi-database
akonadi-database-8-mysql-1.11.0-alt4.M70P.1
akonadi-database-3-sqlite3-1.11.0-alt4.M70P.1
$ chkconfig --list | grep mysqld

Внимание: в выводе отображены только SysV службы (нативные службы systemd отсутствуют)
      конфигурация SysV  может быть сброшена нативной
      конфигураией systemd.

не удалось открыть каталог /etc/xinetd.d: Отказано в доступе
Предшествующй спойлер был после попытки запустить akonadi с драйвером sqlite, а его, драйвера, не было, пардон, недоглядел. Но дело не в нём. Сейчас всё выглядит так:
Спойлер
Akonadi Server Self-Test Report
===============================

Test 1:  SUCCESS
--------

Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system.

File content of '/home/strygin/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/.private/strygin/akonadi-strygin.MwA2Vu/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true
User=
Password=

[Debug]
Tracer=null

[QPSQL]
StartServer=true
Name=akonadi
Host=
User=
Password=
Port=5432

[SQLITE]
Name=akonadi

[QSQLITE3]
Name=/home/strygin/.local/share/akonadi/akonadi.db


Test 2:  SUCCESS
--------

Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.

Test 3:  SUCCESS
--------

MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server '/usr/sbin/mysqld'.
Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld'; its location varies depending on the distribution.

Test 4:  SUCCESS
--------

MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld  Ver 5.5.34-MariaDB-alt0.M70P.1 for Linux on i686 ((ALT Linux))


Test 5:  ERROR
--------

MySQL server log contains errors.
Details: The MySQL server error log file &apos;<a href='/home/strygin/.local/share/akonadi/db_data/mysql.err'>/home/strygin/.local/share/akonadi/db_data/mysql.err</a>&apos; contains errors.

File content of '/home/strygin/.local/share/akonadi/db_data/mysql.err':
151226 15:38:58 InnoDB: The InnoDB memory heap is disabled
151226 15:38:58 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151226 15:38:58 InnoDB: Compressed tables use zlib 1.2.8
151226 15:38:58 InnoDB: Using Linux native AIO
151226 15:38:58 InnoDB: Initializing buffer pool, size = 128.0M
151226 15:38:58 InnoDB: Completed initialization of buffer pool
151226 15:38:58 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
151226 15:38:58  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
151226 15:38:58  InnoDB: Waiting for the background threads to start
151226 15:38:58  InnoDB: Assertion failure in thread 2768239424 in file trx0purge.c line 848
InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
151226 15:38:58 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 5.5.34-MariaDB-alt0.M70P.1
key_buffer_size=262144
read_buffer_size=131072
max_used_connections=0
max_threads=258
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 564522 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x48000
??:0(??)[0x86fc27d]
??:0(??)[0x830e7e9]
??:0(??)[0xb776a404]
??:0(??)[0xb71be095]
??:0(??)[0xb71bf883]
??:0(??)[0x8498537]
??:0(??)[0x8498ae8]
??:0(??)[0x859d9b0]
??:0(??)[0x8592d67]
??:0(??)[0x8499e6c]
??:0(??)[0x848d4d6]
??:0(??)[0xb7660b4d]
??:0(??)[0xb726c83e]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.


Test 6:  SUCCESS
--------

MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href='/etc/akonadi/mysql-global.conf'>/etc/akonadi/mysql-global.conf</a>.

File content of '/etc/akonadi/mysql-global.conf':
#
# 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)
# Deprecated in MySQL >= 5.6.3
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=8M

# # 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_open_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

# We use InnoDB, so don't let MyISAM eat up memory
key_buffer_size=16K

[client]
default-character-set=utf8


Test 7:  SKIP
--------

MySQL server custom configuration not available.
Details: The custom configuration for the MySQL server was not found but is optional.

Test 8:  SUCCESS
--------

MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href='/home/strygin/.local/share/akonadi/mysql.conf'>/home/strygin/.local/share/akonadi/mysql.conf</a> and is readable.

File content of '/home/strygin/.local/share/akonadi/mysql.conf':
#
# 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)
# Deprecated in MySQL >= 5.6.3
innodb_additional_mem_pool_size=18M

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

# 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=8M

# # 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=16M

# 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_open_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

# We use InnoDB, so don't let MyISAM eat up memory
key_buffer_size=256K

[client]
default-character-set=utf8


Test 9:  SUCCESS
--------

akonadictl found and usable
Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
Result:
Akonadi 1.11.0


Test 10:  ERROR
--------

Akonadi control process not registered at D-Bus.
Details: The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 11:  ERROR
--------

Akonadi server process not registered at D-Bus.
Details: The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 12:  SUCCESS
--------

Nepomuk search service registered at D-Bus.
Details: The Nepomuk search service is registered at D-Bus which typically indicates it is operational.

Test 13:  SUCCESS
--------

Nepomuk search service uses an appropriate backend.
Details: The Nepomuk search service uses one of the recommended backends.

Test 14:  SKIP
--------

Protocol version check not possible.
Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements.

Test 15:  SUCCESS
--------

Resource agents found.
Details: At least one resource agent has been found.

Directory listing of '/usr/share/akonadi/agents':
akonadinepomukfeederagent.desktop
akonotesresource.desktop
archivemailagent.desktop
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.desktop
facebookresource.desktop
folderarchiveagent.desktop
googlecalendarresource.desktop
googlecontactsresource.desktop
icaldirresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kabcresource.desktop
kalarmdirresource.desktop
kalarmresource.desktop
kcalresource.desktop
kdeaccountsresource.desktop
knutresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mailfilteragent.desktop
mboxresource.desktop
microblog.desktop
migrationagent.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
nepomuktagresource.desktop
newmailnotifieragent.desktop
nntpresource.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
sendlateragent.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to '/usr/share/kde4:/usr/share'

Test 16:  ERROR
--------

Current Akonadi server error log found.
Details: The Akonadi server reported errors during its current startup. The log can be found in <a href='/home/strygin/.local/share/akonadi/akonadiserver.error'>/home/strygin/.local/share/akonadi/akonadiserver.error</a>.

File content of '/home/strygin/.local/share/akonadi/akonadiserver.error':
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/home/strygin/.local/share/akonadi/mysql.conf", "--datadir=/home/strygin/.local/share/akonadi/db_data/", "--socket=/tmp/.private/strygin/akonadi-strygin.MwA2Vu/mysql.socket")
stdout: ""
stderr: ""
exit code: 1
process error: "Process operation timed out"
"[
0: akonadiserver(_Z11akBacktracev+0x35) [0x80959a5]
1: akonadiserver() [0x8095cda]
2: linux-gate.so.1(__kernel_sigreturn+0) [0xb772c404]
3: /lib/libc.so.6(gsignal+0x45) [0xb6e75095]
4: /lib/libc.so.6(abort+0x143) [0xb6e76883]
5: /usr/lib/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x8e) [0xb74e779e]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xd8) [0x8097a78]
7: /usr/lib/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xe8) [0xb757f9e8]
8: /usr/lib/libQtCore.so.4(+0xfe095) [0xb758c095]
9: /usr/lib/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x68) [0xb758c1d8]
10: akonadiserver(_ZN13DbConfigMysql19startInternalServerEv+0x1b36) [0x8116a26]
11: akonadiserver(_ZN7Akonadi13AkonadiServer20startDatabaseProcessEv+0xe1) [0x8098751]
12: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0xa3) [0x8099713]
13: /usr/lib/libQtCore.so.4(_ZN14QMetaCallEvent13placeMetaCallEP7QObject+0x3a) [0xb75f706a]
14: /usr/lib/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x25b) [0xb75fb21b]
15: /usr/lib/libQtCore.so.4(_ZN23QCoreApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x78) [0xb75e72b8]
16: /usr/lib/libQtCore.so.4(_ZN16QCoreApplication6notifyEP7QObjectP6QEvent+0x64) [0xb75e7324]
17: /usr/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8e) [0xb75e70ce]
18: /usr/lib/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x389) [0xb75ea2c9]
19: /usr/lib/libQtCore.so.4(_ZN16QCoreApplication16sendPostedEventsEP7QObjecti+0x2c) [0xb75ea56c]
20: /usr/lib/libQtCore.so.4(+0x1851ef) [0xb76131ef]
21: /lib/libglib-2.0.so.0(g_main_context_dispatch+0x143) [0xb6d28ff3]
22: /lib/libglib-2.0.so.0(+0x4b390) [0xb6d29390]
23: /lib/libglib-2.0.so.0(g_main_context_iteration+0x41) [0xb6d29471]
24: /usr/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x75) [0xb7613365]
25: /usr/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x4c) [0xb75e5c2c]
26: /usr/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x149) [0xb75e5f39]
27: /usr/lib/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x9a) [0xb75ea61a]
28: akonadiserver(main+0x147) [0x808f9e7]
29: /lib/libc.so.6(__libc_start_main+0xf5) [0xb6e605d5]
30: akonadiserver() [0x8090191]
]
"


Test 17:  SUCCESS
--------

No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.

Баз не было. Но, как я понял, kmail не будет работать без akonadi, возможно, он и письма хранит по принципу баз данных? Есть подозрения, что всё это настало после того как рубанули свет (я без UPS-а  :-() И мои поиски в Интернете по моей ошибке приводят меня к темам, где пытаются спасти базу данных. Собственно, меня бы устроил вариант переноса (спасения) писем и полного перезапуска/перезагрузки akonadi. Есть ли более-менее простые решения?
« Последнее редактирование: 26.12.2015 16:01:29 от Mimas »

Инфлэйм

  • Гость
Re: Проблемы с запуском akonadi
« Ответ #3 : 26.12.2015 16:51:23 »
что-то случилось с akonadi. Понял это по тому, что kmail стал зависать, а при рестарте ругается: "Инфраструктура управления личной информацией Akonadi не работает". Как починить?
Попробуйте отодвинуть в сторону файл
~/.local/share/akonadi/mysql.confИ перезапустите
akonadictl restart

Оффлайн Mimas

  • Завсегдатай
  • *
  • Сообщений: 230
  • Mimas
    • Мой Линукс
    • Email
Re: Проблемы с запуском akonadi
« Ответ #4 : 26.12.2015 17:32:55 »
Переместил конфиг и пытался перезапустить.
$ akonadictl restart
Akonadi is not running.
В логах примерно то же, но хуже, в спойлер не помещается.
« Последнее редактирование: 26.12.2015 17:41:01 от Mimas »

Оффлайн Mimas

  • Завсегдатай
  • *
  • Сообщений: 230
  • Mimas
    • Мой Линукс
    • Email
Re: Проблемы с запуском akonadi
« Ответ #5 : 26.12.2015 20:50:52 »
Удалил папку ~/.local/share/akonadi (скопировав на всякий случай почту в надёжное место). И акоНадя запустилась!  :-)
Потом запустил kmail, с письмами, вроде бы порядок, если не считать, что некоторые уже прочитанные письма были отмечены как непрочитанные.
Спасибо всем, кто пытался мне помочь!