Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 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/donald/.config/akonadi/akonadiserverrc':
- [%General]
- Driver=QMYSQL
- [QMYSQL]
- Name=akonadi
- Host=
- Options="UNIX_SOCKET=/tmp/akonadi-donald.Ig88K0/mysql.socket"
- ServerPath=/usr/sbin/mysqld
- StartServer=true
- [Debug]
- Tracer=null
- 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: 140329 13:04:34 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
- /usr/sbin/mysqld Ver 5.5.35-0ubuntu0.13.10.2 for debian-linux-gnu on x86_64 ((Ubuntu))
- Test 5: ERROR
- --------
- MySQL server log contains errors.
- Details: The MySQL server error log file '<a href='/home/donald/.local/share/akonadi/db_data/mysql.err'>/home/donald/.local/share/akonadi/db_data/mysql.err</a>' contains errors.
- File content of '/home/donald/.local/share/akonadi/db_data/mysql.err':
- 140329 13:04:02 [Note] Plugin 'FEDERATED' is disabled.
- 140329 13:04:02 InnoDB: The InnoDB memory heap is disabled
- 140329 13:04:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 140329 13:04:02 InnoDB: Compressed tables use zlib 1.2.8
- 140329 13:04:02 InnoDB: Using Linux native AIO
- 140329 13:04:02 InnoDB: Initializing buffer pool, size = 80.0M
- 140329 13:04:02 InnoDB: Completed initialization of buffer pool
- 140329 13:04:02 InnoDB: highest supported file format is Barracuda.
- 140329 13:04:02 InnoDB: Error: page 7 log sequence number 1738788766
- InnoDB: is in the future! Current system log sequence number 1745673.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 140329 13:04:02 InnoDB: Error: page 1 log sequence number 1958104776
- InnoDB: is in the future! Current system log sequence number 1745673.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 140329 13:04:02 InnoDB: Error: page 3 log sequence number 1958104776
- InnoDB: is in the future! Current system log sequence number 1745673.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 140329 13:04:02 InnoDB: Error: page 2 log sequence number 2324137385
- InnoDB: is in the future! Current system log sequence number 1745673.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 140329 13:04:02 InnoDB: Error: page 4 log sequence number 2322616615
- InnoDB: is in the future! Current system log sequence number 1745673.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 140329 13:04:02 InnoDB: Error: page 11 log sequence number 1738851315
- InnoDB: is in the future! Current system log sequence number 1745673.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- 140329 13:04:02 InnoDB: Error: page 6 log sequence number 1973270739
- InnoDB: is in the future! Current system log sequence number 1745673.
- InnoDB: Your database may be corrupt or you may have copied the InnoDB
- InnoDB: tablespace but not the InnoDB log files. See
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
- InnoDB: for more information.
- InnoDB: Error: trying to access page number 378 in space 0,
- InnoDB: space name ./ibdata1,
- InnoDB: which is outside the tablespace bounds.
- InnoDB: Byte offset 0, len 16384, i/o type 10.
- InnoDB: If you get this error at mysqld startup, please check that
- InnoDB: your my.cnf matches the ibdata files that you have in the
- InnoDB: MySQL server.
- 140329 13:04:02 InnoDB: Assertion failure in thread 140354511198016 in file fil0fil.c line 4578
- 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.
- 20:04:02 UTC - 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.
- 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.
- key_buffer_size=8388608
- read_buffer_size=131072
- max_used_connections=0
- max_threads=256
- thread_count=0
- connection_count=0
- It is possible that mysqld could use up to
- key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 568198 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x40000
- /usr/sbin/mysqld(my_print_stacktrace+0x20)[0x7fa6d5196d30]
- /usr/sbin/mysqld(handle_fatal_signal+0x3d5)[0x7fa6d50817b5]
- /lib/x86_64-linux-gnu/libpthread.so.0(+0xfbb0)[0x7fa6d3e13bb0]
- /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7fa6d346af77]
- /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fa6d346e5e8]
- /usr/sbin/mysqld(+0x5e5b5c)[0x7fa6d528db5c]
- /usr/sbin/mysqld(+0x5c1239)[0x7fa6d5269239]
- /usr/sbin/mysqld(+0x5c1bbb)[0x7fa6d5269bbb]
- /usr/sbin/mysqld(+0x5b280f)[0x7fa6d525a80f]
- /usr/sbin/mysqld(+0x58fce4)[0x7fa6d5237ce4]
- /usr/sbin/mysqld(+0x585df6)[0x7fa6d522ddf6]
- /usr/sbin/mysqld(+0x586b43)[0x7fa6d522eb43]
- /usr/sbin/mysqld(+0x588597)[0x7fa6d5230597]
- /usr/sbin/mysqld(+0x5759af)[0x7fa6d521d9af]
- /usr/sbin/mysqld(+0x544ea8)[0x7fa6d51ecea8]
- /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x7fa6d50837f1]
- /usr/sbin/mysqld(+0x301291)[0x7fa6d4fa9291]
- /usr/sbin/mysqld(_Z11plugin_initPiPPci+0x8ea)[0x7fa6d4facfda]
- /usr/sbin/mysqld(+0x28a7cb)[0x7fa6d4f327cb]
- /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x45b)[0x7fa6d4f36f8b]
- /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fa6d3455de5]
- /usr/sbin/mysqld(+0x2866b8)[0x7fa6d4f2e6b8]
- 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=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_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
- [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/donald/.local/share/akonadi/mysql.conf'>/home/donald/.local/share/akonadi/mysql.conf</a> and is readable.
- File content of '/home/donald/.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=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_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
- [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.10.3
- 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: ERROR
- --------
- No resource agents found.
- Details: No resource agents have been found, Akonadi is not usable without at least one. This usually means that no resource agents are installed or that there is a setup problem. The following paths have been searched: '/usr/share/akonadi/agents'. The XDG_DATA_DIRS environment variable is set to '/usr/share:/usr/share/kde-plasma:/usr/local/share/:/usr/share/'; make sure this includes all paths where Akonadi agents are installed.
- Directory listing of '/usr/share/akonadi/agents':
- akonadinepomukfeederagent.desktop
- akonotesresource.desktop
- archivemailagent.desktop
- birthdaysresource.desktop
- contactsresource.desktop
- davgroupwareresource.desktop
- facebookresource.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
- kolabproxyresource.desktop
- localbookmarksresource.desktop
- maildirresource.desktop
- maildispatcheragent.desktop
- mailfilteragent.desktop
- mboxresource.desktop
- microblog.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:/usr/share/kde-plasma:/usr/local/share/:/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/donald/.local/share/akonadi/akonadiserver.error'>/home/donald/.local/share/akonadi/akonadiserver.error</a>.
- File content of '/home/donald/.local/share/akonadi/akonadiserver.error':
- Database process exited unexpectedly during initial connection!
- executable: "/usr/sbin/mysqld"
- arguments: ("--defaults-file=/home/donald/.local/share/akonadi/mysql.conf", "--datadir=/home/donald/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-donald.Ig88K0/mysql.socket")
- stdout: ""
- stderr: ""
- exit code: 1
- process error: "Unknown error"
- "[
- 0: akonadiserver() [0x419828]
- 1: akonadiserver() [0x419ab2]
- 2: /lib/x86_64-linux-gnu/libc.so.6(+0x36ff0) [0x7f5676151ff0]
- 3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7f5676151f77]
- 4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f56761555e8]
- 5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x102) [0x7f5677c34912]
- 6: akonadiserver() [0x41ba8d]
- 7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f5677ccf020]
- 8: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1183ad) [0x7f5677cdc3ad]
- 9: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7f5677ce4f93]
- 10: akonadiserver() [0x48a1b0]
- 11: akonadiserver() [0x41c737]
- 12: akonadiserver() [0x41e54a]
- 13: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7f5677d56dce]
- 14: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f5677d3e8bd]
- 15: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ef) [0x7f5677d41e1f]
- 16: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1a8073) [0x7f5677d6c073]
- 17: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x146) [0x7f56758283b6]
- 18: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x48708) [0x7f5675828708]
- 19: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f56758287ac]
- 20: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x7f5677d6ba55]
- 21: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7f5677d3d5ef]
- 22: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7f5677d3d8e5]
- 23: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x8b) [0x7f5677d42e5b]
- 24: akonadiserver() [0x41278a]
- 25: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f567613cde5]
- 26: akonadiserver() [0x412ff8]
- ]
- "
- Test 17: ERROR
- --------
- Previous Akonadi server error log found.
- Details: The Akonadi server reported errors during its previous startup. The log can be found in <a href='/home/donald/.local/share/akonadi/akonadiserver.error.old'>/home/donald/.local/share/akonadi/akonadiserver.error.old</a>.
- File content of '/home/donald/.local/share/akonadi/akonadiserver.error.old':
- Database process exited unexpectedly during initial connection!
- executable: "/usr/sbin/mysqld"
- arguments: ("--defaults-file=/home/donald/.local/share/akonadi/mysql.conf", "--datadir=/home/donald/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-donald.Ig88K0/mysql.socket")
- stdout: ""
- stderr: ""
- exit code: 1
- process error: "Unknown error"
- "[
- 0: akonadiserver() [0x419828]
- 1: akonadiserver() [0x419ab2]
- 2: /lib/x86_64-linux-gnu/libc.so.6(+0x36ff0) [0x7f39ccc26ff0]
- 3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7f39ccc26f77]
- 4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f39ccc2a5e8]
- 5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x102) [0x7f39ce709912]
- 6: akonadiserver() [0x41ba8d]
- 7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f39ce7a4020]
- 8: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1183ad) [0x7f39ce7b13ad]
- 9: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7f39ce7b9f93]
- 10: akonadiserver() [0x48a1b0]
- 11: akonadiserver() [0x41c737]
- 12: akonadiserver() [0x41e54a]
- 13: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7f39ce82bdce]
- 14: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f39ce8138bd]
- 15: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ef) [0x7f39ce816e1f]
- 16: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1a8073) [0x7f39ce841073]
- 17: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x146) [0x7f39cc2fd3b6]
- 18: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x48708) [0x7f39cc2fd708]
- 19: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f39cc2fd7ac]
- 20: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x7f39ce840a55]
- 21: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7f39ce8125ef]
- 22: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7f39ce8128e5]
- 23: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x8b) [0x7f39ce817e5b]
- 24: akonadiserver() [0x41278a]
- 25: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f39ccc11de5]
- 26: akonadiserver() [0x412ff8]
- ]
- "
- Test 18: SUCCESS
- --------
- No current Akonadi control error log found.
- Details: The Akonadi control process did not report any errors during its current startup.
- Test 19: SUCCESS
- --------
- No previous Akonadi control error log found.
- Details: The Akonadi control process did not report any errors during its previous startup.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement