| View previous topic :: View next topic |
| Author |
Message |
Xywa
Veteran
Joined: 23 Jul 2005
Posts: 1631
Location: /mnt/Gentoo/Europe
|
 Posted: Fri Aug 01, 2014 11:16 am Post subject: Akonadi server can't connect to mysql |
 |
|
Hi,
I cannot start akonadi server after Yesterday update (emerge -uDN world).
Maybe this is a problem - *mysql-5.6.19 (29 Jul 2014)
| Code: | 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/ryszard/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/akonadi-ryszard.8sXCg7/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: /usr/sbin/mysqld Ver 5.6.19 for Linux on x86_64 (Source distribution)
Test 5: ERROR
--------
MySQL server log contains errors.
Details: The MySQL server error log file '<a href='/home/ryszard/.local/share/akonadi/db_data/mysql.err'>/home/ryszard/.local/share/akonadi/db_data/mysql.err</a>' contains errors.
File content of '/home/ryszard/.local/share/akonadi/db_data/mysql.err':
2014-08-01 12:06:46 5764 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
2014-08-01 12:06:46 5764 [Warning] Buffered warning: Changed limits: max_connections: 214 (requested 256)
2014-08-01 12:06:46 7f4f6a5ac740 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-08-01 12:06:46 5764 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-08-01 12:06:46 5764 [Note] InnoDB: The InnoDB memory heap is disabled
2014-08-01 12:06:46 5764 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-08-01 12:06:46 5764 [Note] InnoDB: Compressed tables use zlib 1.2.8
2014-08-01 12:06:46 5764 [Note] InnoDB: Using Linux native AIO
2014-08-01 12:06:46 5764 [Note] InnoDB: Using CPU crc32 instructions
2014-08-01 12:06:46 5764 [Note] InnoDB: Initializing buffer pool, size = 80.0M
2014-08-01 12:06:46 5764 [Note] InnoDB: Completed initialization of buffer pool
2014-08-01 12:06:46 5764 [Note] InnoDB: Highest supported file format is Barracuda.
2014-08-01 12:06:46 5764 [Note] InnoDB: The log sequence numbers 3468882600 and 3468882600 in ibdata files do not match the log sequence number 3469766062 in the ib_logfiles!
2014-08-01 12:06:46 5764 [Note] InnoDB: Database was not shutdown normally!
2014-08-01 12:06:46 5764 [Note] InnoDB: Starting crash recovery.
2014-08-01 12:06:46 5764 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-08-01 12:06:46 5764 [Note] InnoDB: Restoring possible half-written data pages
2014-08-01 12:06:46 5764 [Note] InnoDB: from the doublewrite buffer...
11:06:46 UTC - mysqld got signal 11 ;
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=16384
read_buffer_size=131072
max_used_connections=0
max_threads=214
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 = 85119 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+0x2c)[0x8d025c]
/usr/sbin/mysqld(handle_fatal_signal+0x364)[0x649924]
/lib64/libpthread.so.0(+0xfeb0)[0x7f4f69331eb0]
/usr/sbin/mysqld[0xa67920]
/usr/sbin/mysqld[0xa68ee8]
/usr/sbin/mysqld[0x9e08fb]
/usr/sbin/mysqld[0x92aaa4]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x580838]
/usr/sbin/mysqld[0x6d7c86]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x888)[0x6dddb8]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x9c1)[0x579c41]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f4f689a3a65]
/usr/sbin/mysqld[0x56d4ca]
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='/usr/share/config/akonadi/mysql-global.conf'>/usr/share/config/akonadi/mysql-global.conf</a>.
File content of '/usr/share/config/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
# 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/ryszard/.local/share/akonadi/mysql.conf'>/home/ryszard/.local/share/akonadi/mysql.conf</a> and is readable.
File content of '/home/ryszard/.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
# We use InnoDB, so don't let MyISAM eat up memory
key_buffer_size=16K
[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.12.1
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: 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 13: 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/local/share:/usr/share'; make sure this includes all paths where Akonadi agents are installed.
Directory listing of '/usr/share/akonadi/agents':
akonadibalooindexingagent.desktop
akonadinepomukfeederagent.desktop
akonotesresource.desktop
archivemailagent.desktop
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.desktop
folderarchiveagent.desktop
icaldirresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kabcresource.desktop
kalarmdirresource.desktop
kalarmresource.desktop
kcalresource.desktop
kdeaccountsresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mailfilteragent.desktop
mboxresource.desktop
migrationagent.desktop
mixedmaildirresource.desktop
mtdummyresource.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/local/share:/usr/share'
Test 14: 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/ryszard/.local/share/akonadi/akonadiserver.error'>/home/ryszard/.local/share/akonadi/akonadiserver.error</a>.
File content of '/home/ryszard/.local/share/akonadi/akonadiserver.error':
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/home/ryszard/.local/share/akonadi/mysql.conf", "--datadir=/home/ryszard/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-ryszard.8sXCg7/mysql.socket")
stdout: ""
stderr: "2014-08-01 12:06:46 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
"
exit code: 1
process error: "Unknown error"
"[
0: akonadiserver(_Z11akBacktracev+0x37) [0x464ef7]
1: akonadiserver() [0x465152]
2: /lib64/libc.so.6(+0x352d0) [0x7f118f5272d0]
3: /lib64/libc.so.6(gsignal+0x39) [0x7f118f527259]
4: /lib64/libc.so.6(abort+0x148) [0x7f118f5285b8]
5: /usr/lib64/qt4/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64) [0x7f1191009af4]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9d) [0x46709d]
7: /usr/lib64/qt4/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f11910a56a0]
8: /usr/lib64/qt4/libQtCore.so.4(+0x119c4d) [0x7f11910b2c4d]
9: /usr/lib64/qt4/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x7f11910bb961]
10: akonadiserver(_ZN7Akonadi6Server13DbConfigMysql19startInternalServerEv+0x1dd6) [0x5021e6]
11: akonadiserver(_ZN7Akonadi6Server13AkonadiServer20startDatabaseProcessEv+0xd7) [0x467c47]
12: akonadiserver(_ZN7Akonadi6Server13AkonadiServer4initEv+0xa5) [0x46a5e5]
13: /usr/lib64/qt4/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7f119112ecae]
14: /usr/lib64/qt4/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f119111674d]
15: /usr/lib64/qt4/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ea) [0x7f119111986a]
16: /usr/lib64/qt4/libQtCore.so.4(+0x1ab56e) [0x7f119114456e]
17: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x254) [0x7f118f207984]
18: /usr/lib64/libglib-2.0.so.0(+0x48bc8) [0x7f118f207bc8]
19: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f118f207c6c]
20: /usr/lib64/qt4/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x7e) [0x7f1191143d3e]
21: /usr/lib64/qt4/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7f119111537f]
22: /usr/lib64/qt4/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7f1191115675]
23: /usr/lib64/qt4/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x89) [0x7f119111a939]
24: akonadiserver(main+0x1bf) [0x45f66f]
25: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f118f513a65]
26: akonadiserver() [0x45fe08]
]
"
Test 15: 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/ryszard/.local/share/akonadi/akonadiserver.error.old'>/home/ryszard/.local/share/akonadi/akonadiserver.error.old</a>.
File content of '/home/ryszard/.local/share/akonadi/akonadiserver.error.old':
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/home/ryszard/.local/share/akonadi/mysql.conf", "--datadir=/home/ryszard/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-ryszard.8sXCg7/mysql.socket")
stdout: ""
stderr: "2014-08-01 12:06:46 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
"
exit code: 1
process error: "Unknown error"
"[
0: akonadiserver(_Z11akBacktracev+0x37) [0x464ef7]
1: akonadiserver() [0x465152]
2: /lib64/libc.so.6(+0x352d0) [0x7f82073272d0]
3: /lib64/libc.so.6(gsignal+0x39) [0x7f8207327259]
4: /lib64/libc.so.6(abort+0x148) [0x7f82073285b8]
5: /usr/lib64/qt4/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64) [0x7f8208e09af4]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9d) [0x46709d]
7: /usr/lib64/qt4/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f8208ea56a0]
8: /usr/lib64/qt4/libQtCore.so.4(+0x119c4d) [0x7f8208eb2c4d]
9: /usr/lib64/qt4/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x7f8208ebb961]
10: akonadiserver(_ZN7Akonadi6Server13DbConfigMysql19startInternalServerEv+0x1dd6) [0x5021e6]
11: akonadiserver(_ZN7Akonadi6Server13AkonadiServer20startDatabaseProcessEv+0xd7) [0x467c47]
12: akonadiserver(_ZN7Akonadi6Server13AkonadiServer4initEv+0xa5) [0x46a5e5]
13: /usr/lib64/qt4/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7f8208f2ecae]
14: /usr/lib64/qt4/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f8208f1674d]
15: /usr/lib64/qt4/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ea) [0x7f8208f1986a]
16: /usr/lib64/qt4/libQtCore.so.4(+0x1ab56e) [0x7f8208f4456e]
17: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x254) [0x7f8207007984]
18: /usr/lib64/libglib-2.0.so.0(+0x48bc8) [0x7f8207007bc8]
19: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f8207007c6c]
20: /usr/lib64/qt4/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x7e) [0x7f8208f43d3e]
21: /usr/lib64/qt4/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7f8208f1537f]
22: /usr/lib64/qt4/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7f8208f15675]
23: /usr/lib64/qt4/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x89) [0x7f8208f1a939]
24: akonadiserver(main+0x1bf) [0x45f66f]
25: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f8207313a65]
26: akonadiserver() [0x45fe08]
]
"
Test 16: SUCCESS
--------
No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.
Test 17: SUCCESS
--------
No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.
|
|
|
| Back to top |
|
 |
miket
Guru
Joined: 28 Apr 2007
Posts: 488
Location: Gainesville, FL, USA
|
| Posted: Sat Aug 02, 2014 9:20 pm Post subject: |
|
|
Were you on mysql 5.6 before the update? It's keyworded, after all. I would take it that there have been problems in Gentoo with versions of MySQL after the 5.1 series. (One nasty problem as far as I am concerned: the use of libedit rather than readline.) If you're doing a long-distance upgrade as from 5.1 to 5.6, you certainly need to attend to conversion of the data.
I certainly would be slow to use 5.6. Downgrading to 5.1 is possible, but I'm afraid it might entail having to dump the data from the 5.6 version and then importing it into a 5.1 server. |
|
| Back to top |
|
|
friesia
Apprentice
Joined: 23 Mar 2007
Posts: 202
|
| Posted: Sun Aug 03, 2014 8:49 am Post subject: |
|
|
I was also hit by the problem.
Rebuilt @world just in case and downgraded to mysql 5.5 — everything back to shape now.
As you see there:
| Code: | | stderr: "2014-08-01 12:06:46 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). |
this is why mysqld crashes, probably akonadi should be fixed for mysql 5.6.
upd: oh wait, it's just a warning, probably not it |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
