Re: [Maria-discuss] MariaDB crashes when running DESCRIBE command

[Elena Stepanova]

Hi Andy,


On 6/24/20 6:13 PM, Ling, Andy wrote:
I am running MariaDB 10.4.12 on Windows Server 2018. I am connecting to 
it from a Java application using mariadb-java-client-2.5.4


I use Statement.executeQuery(string) to execute a query on the database. 
Most of the time this works without a problem, but I have just found 
that if the query is “DESCRIBE servers”, where servers is the name of a 
table, it crashes the MariaDB service.


Indeed, there was such problem in 10.4.12 (and some previous versions): 
https://jira.mariadb.org/browse/MDEV-21616


It was fixed in 10.4.13. Could you please upgrade and check whether the 
failure goes away?


Regards,
Elena Stepanova



I can run the query without a problem from the mysql shell, it is only 
when running it through the java connector.


The error log crash data is shown below.

Is this a bug or am I doing something wrong?

Regards

Andy Ling

Version: '10.4.12-MariaDB-log'  socket: ''  port: 3306  mariadb.org 
binary distribution


200624 15:48:11 [ERROR] mysqld got exception 0xc005 ;

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 https://mariadb.com/kb/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: 10.4.12-MariaDB-log

key_buffer_size=65536

read_buffer_size=131072

max_used_connections=16

max_threads=65537

thread_count=22

It is possible that mysqld could use up to

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 
5380 K  bytes of memory


Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x209c95a8

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...

mysqld.exe!st_select_lex::init_select()[sql_lex.cc:2428]

mysqld.exe!mysql_init_select()[sql_parse.cc:7492]

mysqld.exe!MYSQLparse()[sql_yacc.yy:14556]

mysqld.exe!parse_sql()[sql_parse.cc:10210]

mysqld.exe!mysql_parse()[sql_parse.cc:7856]

mysqld.exe!dispatch_command()[sql_parse.cc:1844]

mysqld.exe!do_command()[sql_parse.cc:1359]

mysqld.exe!threadpool_process_request()[threadpool_common.cc:366]

mysqld.exe!tp_callback()[threadpool_common.cc:193]

ntdll.dll!RtlDllShutdownInProgress()

ntdll.dll!DbgUiRemoteBreakin()

kernel32.dll!BaseThreadInitThunk()

ntdll.dll!RtlUserThreadStart()

Trying to get some variables.

Some pointers may be invalid and cause the dump to abort.

Query (0x209c15c0): SET STATEMENT max_statement_time=5 FOR describe servers

Connection ID (thread ID): 52

Status: NOT_KILLED

Optimizer switch: 
index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on


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.

Writing a core file at C:\Data\MySQL\data\


DISCLAIMER:
Privileged and/or Confidential information may be contained in this 
message. If you are not the addressee of this message, you may not copy, 
use or deliver this message to anyone. In such event, you should destroy 
the message and kindly notify the sender by reply e-mail. It is 
understood that opinions or conclusions that do not relate to the 
official business of the company are neither given nor endorsed by the 
company. Thank You.


___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] MariaDB upgrade 10.1 to 10.2 CentOS7

[Elena Stepanova]

Hi Karthick,


On 11/13/2017 03:30 PM, Karthick Subramanian wrote:

Hi Elena,

Do you think the yum update causing issue instead of yum remove and yum 
install in the first place. Please advise.


No, I don't see how the failed yum update could possibly cause this. The 
failure itself upon yum update is easily reproducible and sadly 
expected, currently major upgrades of the server package are not 
supported. It does not cause the magic appearance of unix_socket in the 
root configuration. I tried it just in case, in different variations 
(hence the delay with the answer), and it does nothing of the kind.


There is a known easy way to get this problem. If your 10.1.18 was 
installed from the *enterprise* set of packages, it would have had 
exactly this configuration, single local root with unix_socket and the 
plugin linked statically and enabled. Then, after you switch to the 
community 10.2 server, it of course preserves the datadir, including 
user configuration, but it does not have the statically linked plugin; 
it's a dynamic library there, not loaded by default. So, when you start 
the server, you can't connect.


At first it seemed to contradict the output you pasted in the initial email:

> In my previous version:
>
> select user, plugin from mysql.user;
>
> +---+--+-+
> | Host  | User | plugin  |
> +---+--+-+
> | localhost | root ||
> 

It reads as if that's what you had on 10.1. But after your last lists of 
RPM packages I'm not so sure. If this is *not* the output from the 10.1 
server before the upgrade, then the explanation above is by far the most 
likely one.


If you are sure that's the output from 10.1 before the upgrade, the next 
question is how reliable it is. It is obviously edited, but unclear to 
which extent.



Regards,
Elena




On Nov 13, 2017 5:13 PM, "Karthick Subramanian" 
<ksubraman...@paycommerce.com <mailto:ksubraman...@paycommerce.com>> wrote:


Hi Elena,

[root@one server ~]# rpm -qa | grep -iE 'mariadb|mysql'
MariaDB-client-10.2.9-1.el7.centos.x86_64
MariaDB-compat-10.2.9-1.el7.centos.x86_64
MariaDB-common-10.2.9-1.el7.centos.x86_64
MariaDB-server-10.2.9-1.el7.centos.x86_64

[root@another server~]#  rpm -qa | grep -iE 'mariadb|mysql'
pcp-pmda-mysql-3.10.6-2.el7.x86_64
MariaDB-client-10.2.10-1.el7.centos.x86_64
MariaDB-server-10.2.10-1.el7.centos.x86_64
MariaDB-common-10.1.18-1.el7.centos.x86_64



Steps:

I did the upgrade in two servers:

In both servers (both 10.1), I follow the below steps and got ssame
unix-socket not loaded error.

set-up repo:

curl -sShttps://downloads.mariadb.com/MariaDB/mariadb_repo_setup
<https://downloads.mariadb.com/MariaDB/mariadb_repo_setup>  | sudo bash

*yum update MariaDB-server MariaDB-client*

MariaDB-Client installed successfully, but MariaDB-server thrown
error that it couldn't update.

then I remove the mariaDb-Server using below command:

*yum remove MariaDB-server*

then install:

*yum install MariaDB-server*

then mysql-upgrade:

I got the error with unix-socket.

Do you think yum update MariaDB-server caused this issue? Do I need
to remove and then install, instead of update. Please advise.




On Mon, Nov 13, 2017 at 4:49 PM, Elena Stepanova
<ele...@montyprogram.com <mailto:ele...@montyprogram.com>> wrote:

Hi Karthick,

On 11/13/2017 11:11 AM, Karthick Subramanian wrote:

All,

Did anyone face issues after upgrading the mariadb from 10.1
to 10.2 to login to root user as shown below:

mysql -u root

I got the error - unix_socket not loaded.

I noticed that the unix_socket authentication is required
after the upgrade for root login from localhost. Can anyone
confirm whether this is part of the feature after upgrades.


This is strange, upgrade to packages *provided by MariaDB*
shouldn't do it. Packages provided by another party could be a
different story. Could you please paste the output of rpm -qa |
grep -iE 'mariadb|mysql' or alike?


In my previous version:

select user, plugin from mysql.user;

+---+--+-+
| Host  | User | plugin  |
+---+--+-+
| localhost | root ||


After upgrade:

select user, plugin from mysql.user;

+---+--+-+
| Host  | User | plugin  |
+---

Re: [Maria-discuss] MariaDB upgrade 10.1 to 10.2 CentOS7

[Elena Stepanova]

Hi Karthick,

On 11/13/2017 11:11 AM, Karthick Subramanian wrote:

All,

Did anyone face issues after upgrading the mariadb from 10.1 to 10.2 to 
login to root user as shown below:


mysql -u root

I got the error - unix_socket not loaded.

I noticed that the unix_socket authentication is required after the 
upgrade for root login from localhost. Can anyone confirm whether this 
is part of the feature after upgrades.


This is strange, upgrade to packages *provided by MariaDB* shouldn't do 
it. Packages provided by another party could be a different story. Could 
you please paste the output of rpm -qa | grep -iE 'mariadb|mysql' or alike?




In my previous version:

select user, plugin from mysql.user;

+---+--+-+
| Host  | User | plugin  |
+---+--+-+
| localhost | root ||


After upgrade:

select user, plugin from mysql.user;

+---+--+-+
| Host  | User | plugin  |
+---+--+-+
| localhost | root | unix_socket |
---


The other way round is more common -- some variations of 10.1 did set 
unix_socket authentication for local root and could have it enabled by 
default, and then after upgrade to regular 10.2 unix_socket would become 
disabled while root would still require it.


Is it possible that your previous installation points at a different 
data directory, while the old one that 10.2 now uses had this kind of 
configuration before?


Regards,
Elena




Regards,
Karthick



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] Upgrading From MySQL 5.6 to MariaDB 10.1

[Elena Stepanova]

Hi Mike [mike bayer],

On 02/24/2017 12:03 AM, mike bayer wrote:



On 02/23/2017 03:17 PM, Michael Caplan wrote:

Hi there,

I'm not seeing any concise information in the MariaDB docs about the
recommended upgrade plan from MySQL 5.6 to MariaDB 10.1. Should I
install MariaDB 10.0 and then 10.1?  Or can I run right to 10.1?


I asked about this in depth about a month ago here:

https://lists.launchpad.net/maria-discuss/msg04248.html

I didn't get any reply, perhaps because it was too detailed or was too
much asking for an "official" reply.   But it looks very much like
mysql_upgrade can be run against a 5.x database straight to 10.1.


Sorry about missing the question.

I would stay cautious claiming anything about "5.x", but for MariaDB 5.5 
=> 10.1 it should be okay, there are no known reasons for it not to work.


Generally we encourage small jumps rather than big, but 5.5=>10.1 is not 
too big, it has been tested internally to some extent, and a lot of 
users must have done it by now, no complaints. If you encounter any 
issues, please file a bug report.


Data backup before upgrade is always highly recommended.

Regards,
Elena






I'm running an older version of Ubuntu (12.04 Precise).  Looking at the
repo, it looks like I can stick with Precise, and hand that upgrade
later.  Or are there recommended min version of Ubuntu I should hit
first?


Thanks!


Mike



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] Upgrading From MySQL 5.6 to MariaDB 10.1

[Elena Stepanova]

Hi Michael,

On 02/23/2017 10:17 PM, Michael Caplan wrote:

Hi there,

I'm not seeing any concise information in the MariaDB docs about the
recommended upgrade plan from MySQL 5.6 to MariaDB 10.1. Should I
install MariaDB 10.0 and then 10.1?  Or can I run right to 10.1?

I'm running an older version of Ubuntu (12.04 Precise).  Looking at the
repo, it looks like I can stick with Precise, and hand that upgrade
later.  Or are there recommended min version of Ubuntu I should hit first?



There is no point installing 10.0 as an intermediate step, you can go 
directly to 10.1.


Precise is okay for now, but I wouldn't recommend to stick with it for 
long, as it has EOL in 2 months, which means MariaDB might stop 
producing packages soon afterwards. The next LTS would be a better choice.


Data-wise, simple upgrade 5.6 => 10.1 should work all right. That is, 
you have 5.6 datadir, install MariaDB 10.1, start it with the existing 
datadir, run mysql_upgrade, it should work.


Package-wise, it's a bit more complicated.
We are trying to support, whenever possible, upgrade from MySQL/MariaDB 
packages built by Debian/Ubuntu to MariaDB's packages. But you're using 
Oracle's own packages, currently we don't monitor or maintain direct 
upgrade from them, and I'm quite certain it won't "just work". To 
perform the upgrade, I would recommend to


- backup the data dir (in case something goes very wrong);
- uninstall all 5.6.x-1ubuntu12.04 packages that you have (don't purge);
- add MariaDB 10.1 repo to the source list and install MariaDB;
- run mysql_upgrade.

Please keep in mind that there are some differences between MariaDB and
MySQL 5.6, including (but not limited to) server options. So, if you 
keep your old config file and if there are options which MariaDB does 
not have, server startup might choke. You will see in the error log 
which options it didn't recognize.


Regards,
Elena




Thanks!


Mike



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] for years failing tests

[Elena Stepanova]

 using
statement format since BINLOG_FORMAT = STATEMENT. Statements writing to
a table with an auto-increment column after selecting from another table
are unsafe because the order in which rows are retrieved determines what
(if any) rows will be written. This order cannot be predicted and may
differ on master and the slave.
 show binlog events limit 16, 100;
___

main.vieww3 [ fail ]
Test ended at 2017-01-21 15:15:15

CURRENT_TEST: main.view
mysqltest: At line 5501: query 'alter table v1 check partition p1'
failed: 1289: The 'partitioning' feature is disabled; you need MariaDB
built with '--with-plugin-partition' to have it working
___

maria.encrypt-wrong-key  w3 [ fail ]
Test ended at 2017-01-21 15:15:24

CURRENT_TEST: maria.encrypt-wrong-key


Server [mysqld.1 - pid: 30821, winpid: 30821, exit: 512] failed during
test run
Server log from this test:
--SERVER LOG START---
2017-01-21 15:15:23 139933618535168 [Note] /usr/libexec/mysqld: Normal
shutdown

2017-01-21 15:15:23 139933618535168 [Note] Event Scheduler: Purging the
queue. 0 events
2017-01-21 15:15:23 139933618535168 [Note] /usr/libexec/mysqld: Shutdown
complete

2017-01-21 15:15:24 139668697172288 [Note] /usr/libexec/mysqld (mysqld
10.1.21-MariaDB) starting as process 30823 ...
2017-01-21 15:15:24 139668697172288 [Warning] Could not increase number
of max_open_files to more than 1024 (request: 4162)
2017-01-21 15:15:24 139668697172288 [ERROR] Can't open shared library
'/usr/lib64/mysql/plugin/file_key_management.so' (errno: 2, cannot open
shared object file: No such file or directory)
___


Am 21.01.2017 um 14:28 schrieb Elena Stepanova:

Hi Reindl,

On 01/21/2017 05:11 AM, Reindl Harald wrote:



Am 20.01.2017 um 22:58 schrieb Elena Stepanova:

Hi Reindl,

On 01/20/2017 06:03 PM, Reindl Harald wrote:

shouldn't the testsuite at some point in time run without errors?


The testsuite should run without errors with some combinations of
build/run server options which it's tuned for and which we normally run
it with.

Unfortunately, with arbitrary non-default options in general MTR cannot
be guaranteed to run successfully, it's just not that kind of tool.
Some
problems are easy to fix though, and we'll do it whenever we can.
Please
in future just file bug reports right away, no need to suffer for
years.
We can only fix something that we are aware of.



"run STOP SLAVE '' first" - uhm did i start it? it's scripted by
shipped
scripts


It happens because of --mysqld=--binlog-format=mixed on the command
line, more specifically due to a non-clean exit of a previous test
which
realizes too late that binlog format has been overridden from a command
line, and skips the rest of execution, including the clean-up


well, with --mysqld=--binlog-format=mixed at least it did somehow finish
at all, i started it without at 7:00 PM as i left home, i came back home
10 minutes ago (4:00 AM) and it still did not finish

but maybe that's just because the new encryption features where the
test-suite just don't realize that they are not built and insetad sakip
them all togehter it waits for every peice 3 seconds


Well, some failures can prolong the torture, but really it's probably a
combination of factors. Still, 9 hours is very long even for a
worst-case scenario, so it would be interesting to look at the full MTR
output to understand what's happening.

Without seeing it, importantly execution times of successful tests, I
can only guess, but if binlog_format setting was the only thing that
changed between the runs, and if you always run with '--max-test-fail=0
--force', most likely the culprit is the execution time of rpl suite,
worsened by general low performance.

rpl is the longest suite of all, and since it's running in full now, it
can take a lot of time (which is why I agree that running tests with
only one binlog_format is a reasonable demand). Before, when you ran
tests with '--mysqld=--binlog-format=mixed', a big part of this suite
and parts of some other suites either were skipped or failed.

You are running tests on disk, rather than in memory. Latency for
on-disk runs can be quite bad, depending on the machine. Replication
tests in particular are quite sensitive to this. Here is an example from
my laptop:

on disk:
rpl.rpl_partition_innodb 'mix,xtradb'[ pass ]  41647
in memory:
rpl.rpl_partition_innodb 'mix,xtradb'[ pass ]251

The fact that tests run without parallel also doesn't help. If you have
enough memory, it's worth considering parallel execution -- every test
will take longer, but the overall duration might decrease significantly.


Regards,
Elena




Failed to start mysqld.1

 - skipping
'/usr/share/mysql-test/var/log/encryption.innodb-page_encryption-cbc,xtradb/'



***Warnings generated in error logs during shutdown after running tests:
enc

Re: [Maria-discuss] for years failing tests

[Elena Stepanova]

Hi Reindl,

On 01/21/2017 05:11 AM, Reindl Harald wrote:



Am 20.01.2017 um 22:58 schrieb Elena Stepanova:

Hi Reindl,

On 01/20/2017 06:03 PM, Reindl Harald wrote:

shouldn't the testsuite at some point in time run without errors?


The testsuite should run without errors with some combinations of
build/run server options which it's tuned for and which we normally run
it with.

Unfortunately, with arbitrary non-default options in general MTR cannot
be guaranteed to run successfully, it's just not that kind of tool. Some
problems are easy to fix though, and we'll do it whenever we can. Please
in future just file bug reports right away, no need to suffer for years.
We can only fix something that we are aware of.



"run STOP SLAVE '' first" - uhm did i start it? it's scripted by shipped
scripts


It happens because of --mysqld=--binlog-format=mixed on the command
line, more specifically due to a non-clean exit of a previous test which
realizes too late that binlog format has been overridden from a command
line, and skips the rest of execution, including the clean-up


well, with --mysqld=--binlog-format=mixed at least it did somehow finish
at all, i started it without at 7:00 PM as i left home, i came back home
10 minutes ago (4:00 AM) and it still did not finish

but maybe that's just because the new encryption features where the
test-suite just don't realize that they are not built and insetad sakip
them all togehter it waits for every peice 3 seconds


Well, some failures can prolong the torture, but really it's probably a 
combination of factors. Still, 9 hours is very long even for a 
worst-case scenario, so it would be interesting to look at the full MTR 
output to understand what's happening.


Without seeing it, importantly execution times of successful tests, I 
can only guess, but if binlog_format setting was the only thing that 
changed between the runs, and if you always run with '--max-test-fail=0 
--force', most likely the culprit is the execution time of rpl suite, 
worsened by general low performance.


rpl is the longest suite of all, and since it's running in full now, it 
can take a lot of time (which is why I agree that running tests with 
only one binlog_format is a reasonable demand). Before, when you ran 
tests with '--mysqld=--binlog-format=mixed', a big part of this suite 
and parts of some other suites either were skipped or failed.


You are running tests on disk, rather than in memory. Latency for 
on-disk runs can be quite bad, depending on the machine. Replication 
tests in particular are quite sensitive to this. Here is an example from 
my laptop:


on disk:
rpl.rpl_partition_innodb 'mix,xtradb'[ pass ]  41647
in memory:
rpl.rpl_partition_innodb 'mix,xtradb'[ pass ]251

The fact that tests run without parallel also doesn't help. If you have 
enough memory, it's worth considering parallel execution -- every test 
will take longer, but the overall duration might decrease significantly.



Regards,
Elena




Failed to start mysqld.1

 - skipping
'/usr/share/mysql-test/var/log/encryption.innodb-page_encryption-cbc,xtradb/'

***Warnings generated in error logs during shutdown after running tests:
encryption.innodb-page_encryption

2017-01-20 19:01:51 140487478450496 [ERROR] /usr/libexec/mysqld: unknown
variable 'file-key-management-encryption-algorithm=aes_cbc'
2017-01-20 19:01:51 140487478450496 [ERROR] Aborting

worker[1] mysql-test-run: WARNING: Process [mysqld.1 - pid: 7618,
winpid: 7618, exit: 1792] died after mysql-test-run waited 3.1 seconds
for /usr/share/mysql-test/var/run/mysqld.1.pid to be created.
worker[1] mysql-test-run: WARNING: Process [mysqld.1 - pid: 7641,
winpid: 7641, exit: 1792] died after mysql-test-run waited 0.3 seconds
for /usr/share/mysql-test/var/run/mysqld.1.pid to be created.
worker[1] mysql-test-run: WARNING: Process [mysqld.1 - pid: 7646,
winpid: 7646, exit: 1792] died after mysql-test-run waited 0.3 seconds
for /usr/share/mysql-test/var/run/mysqld.1.pid to be created.
worker[1] mysql-test-run: WARNING: Process [mysqld.1 - pid: 7651,
winpid: 7651, exit: 1792] died after mysql-test-run waited 0.3 seconds
for /usr/share/mysql-test/var/run/mysqld.1.pid to be created.
worker[1] mysql-test-run: WARNING: Process [mysqld.1 - pid: 7656,
winpid: 7656, exit: 1792] died after mysql-test-run waited 0.3 seconds
for /usr/share/mysql-test/var/run/mysqld.1.pid to be created.
worker[1] mysql-test-run: WARNING: Process [mysqld.1 - pid: 7661,
winpid: 7661, exit: 1792] died after mysql-test-run waited 0.3 seconds
for /usr/share/mysql-test/var/run/mysqld.1.pid to be created.
worker[1] mysql-test-run: WARNING: Process [mysqld.1 - pid: 7666,
winpid: 7666, exit: 1792] died after mysql-test-run waited 3.1 seconds
for /usr/share/mysql-test/var/run/mysqld.1.pid to be created.
worker[1] mysql-test-run: WARNING: Process [mysqld.1 - pid: 7701,
winpid: 7701, exit: 1792] died after mysql-test-run waited 2.9 seconds
for /usr/share/mysql-test/var/run/my

Re: [Maria-discuss] for years failing tests

[Elena Stepanova]

Hi Reindl,

On 01/20/2017 06:03 PM, Reindl Harald wrote:

shouldn't the testsuite at some point in time run without errors?


The testsuite should run without errors with some combinations of 
build/run server options which it's tuned for and which we normally run 
it with.


Unfortunately, with arbitrary non-default options in general MTR cannot 
be guaranteed to run successfully, it's just not that kind of tool. Some 
problems are easy to fix though, and we'll do it whenever we can. Please 
in future just file bug reports right away, no need to suffer for years. 
We can only fix something that we are aware of.




"run STOP SLAVE '' first" - uhm did i start it? it's scripted by shipped
scripts


It happens because of --mysqld=--binlog-format=mixed on the command 
line, more specifically due to a non-clean exit of a previous test which 
realizes too late that binlog format has been overridden from a command 
line, and skips the rest of execution, including the clean-up.




[root@testserver:~]$ cat /usr/local/bin/mysql-test.sh
#!/usr/bin/dash
/usr/bin/su -c 'cd /usr/share/mysql-test; ./mysql-test-run.pl
--parallel=1 --max-test-fail=0 --mysqld=--binlog-format=mixed --force'
mysql
rm -rf /usr/share/mysql-test/var/*


rpl.rpl_binlog_index 'row'   [ fail ]
Test ended at 2017-01-20 16:56:16
CURRENT_TEST: rpl.rpl_binlog_index
mysqltest: In included file "./include/rpl_init.inc":
included from ./include/master-slave.inc at line 38:
included from /usr/share/mysql-test/suite/rpl/t/rpl_binlog_index.test at
line 20:
At line 165: query 'SET GLOBAL gtid_slave_pos= ""' failed: 1198: This
operation cannot be performed as you have a running slave ''; run STOP
SLAVE '' first
The result from queries just before the failure was:
include/master-slave.inc
 - saving '/usr/share/mysql-test/var/log/rpl.rpl_binlog_index-row/' to
'/usr/share/mysql-test/var/log/rpl.rpl_binlog_index-row/'

rpl.sec_behind_master-5114 'stmt'[ fail ]
Test ended at 2017-01-20 16:58:33
CURRENT_TEST: rpl.sec_behind_master-5114
mysqltest: In included file "./include/rpl_init.inc":
included from ./include/master-slave.inc at line 38:
included from
/usr/share/mysql-test/suite/rpl/t/sec_behind_master-5114.test at line 1:
At line 165: query 'SET GLOBAL gtid_slave_pos= ""' failed: 1198: This
operation cannot be performed as you have a running slave ''; run STOP
SLAVE '' first
The result from queries just before the failure was:
include/master-slave.inc


rpl.rpl_semi_sync_event_after_sync 'mix,xtradb' [ fail ]
Test ended at 2017-01-20 16:59:24
CURRENT_TEST: rpl.rpl_semi_sync_event_after_sync
mysqltest: At line 1: query 'set global
rpl_semi_sync_master_wait_point=AFTER_SYNC' failed: 1193: Unknown system
variable 'rpl_semi_sync_master_wait_point'
The result from queries just before the failure was:
set global rpl_semi_sync_master_wait_point=AFTER_SYNC;
 - saving
'/usr/share/mysql-test/var/log/rpl.rpl_semi_sync_event_after_sync-mix,xtradb/'
to
'/usr/share/mysql-test/var/log/rpl.rpl_semi_sync_event_after_sync-mix,xtradb/'



it fails because there is no semisync plugin (you build without dynamic 
plugins, right?), but the test checks for that too late. A similar 
problem affects encryption tests that you mentioned in another email.



Regards,
Elena




___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] MariaDB Server 10.3 notes

[Elena Stepanova]

Hi all!

On 10/14/2016 11:10 AM, jocelyn fournier wrote:

Hi!

Regarding the TokuDB bugs, they are so far fixed quite quickly by
Percona.


I want to clarify the source of the question (FUD) about Percona not 
fixing TokuDB bugs, and hopefully bring it to an end. It apparently 
comes from me, saying so during the discussion at the meetup.


My impression was based on interaction with community bug reporters, 
which is one of my chores. We ask them to re-file TokuDB bugs to 
Percona, and then after a while they would tell me, via JIRA or 
otherwise, that there is no progress on the re-filed ticket. It happened 
several times at least, and given that TokuDB doesn't come up in our 
JIRA all that often, it did not seem to be negligible.


But then again, it happens to everyone that bugs get stalled, MariaDB is 
certainly no saint in this regard, either. Besides, I must admit that my 
statistics is biased, because I only hear from TokuDB reporters again 
when things don't go well, while success stories might well remain 
unnoticed by me. So, since involved parties confirm that there is in 
fact good progress, I readily retrieve my previous statement with due 
apologies to everyone who I unwillingly upset by it.


Regards,
Elena



https://bugs.launchpad.net/percona-server/+bug/1607300 was investigated
and fixed in less than 10 days, and George answered the same day of the
bug report.

And hopefully, the latest remaining patch from Rich needed to enable
optimistic parallel replication will be merged quickly as well (
https://github.com/percona/PerconaFT/pull/360 ). The same is true for
the RFR patchs on the MariaDB side, (
https://github.com/MariaDB/server/pull/213 +
https://github.com/percona/percona-server/pull/1070 ) and the tokubackup
script ( https://jira.mariadb.org/browse/MDEV-8843 ) ;)

As for the performance of TokuDB with concurrent read/write queries,
from my experience it depends if you try to read immediately the rows
which have just been inserted/updated or not. Is this case the messages
in the fractal tree have to be propagated and you loose the TokuDB speed
insert/update advantage, but they are still a few workload where TokuDB
is performing quite well.


Jocelyn Fournier
Founder
M : +33 6 51 21 54 10
https://www.softizy.com
Softizy - At your side to Optimize your PHP / MySQL applications

Le 14/10/2016 à 09:11, Sergei Golubchik a écrit :

Hi, MARK!

On Oct 13, MARK CALLAGHAN wrote:

On Thu, Oct 13, 2016 at 4:00 PM, Sergei Golubchik 
wrote:

There is development and support for TokuDB. The main reason for
dropping it could be RocksDB based engine covering all TokuDB use
cases, but better. I mean, *if* RocksDB will be able to do that,
then TokuDB won't be needed (it's *if*, not a certainty).

Is MariaDB.com providing the development for TokuDB or are you
speculating about the commitment to it provided by someone else? If
the latter, then it would be better to hear directly from them. If the
former, can you be more specific about what MariaDB.com plans to do
for TokuDB?

I am speculating about the commitment to it provided by Percona.
Based on what (I believe) Peter said, and it's in the Colin email too:


Peter says that bugs are fixed for customers... and there is ongoing
development to make it better

but mainly based on the changes I see in TokuDB codebase inside
Percona Server:

5.6.32-78.1 -  73 files changed,  4192 insertions(+), 3715 deletions(-)
5.6.31-77.0 -  35 files changed,   153 insertions(+),   79 deletions(-)
5.6.30-76.3 -  77 files changed,   862 insertions(+),  309 deletions(-)
5.6.29-76.2 -  25 files changed,   487 insertions(+),  153 deletions(-)
5.6.28-76.1 -  14 files changed,   997 insertions(+),  182 deletions(-)
5.6.27-76.0 - 206 files changed, 15619 insertions(+), 5969 deletions(-)
5.6.26-74.0 - initial checkin (into mergetrees/tree/merge-tokudb-5.6
repo)

I agree that it doesn't prove that they will continue to do so in the
future.

If MariaDB.com has any plans about TokuDB - I don't know about them.

Regards,
Sergei
Chief Architect MariaDB
and secur...@mariadb.org

___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] WHY are TMM files never removed in 10.0.x

[Elena Stepanova]

Hi Reindl,

On 22.08.2015 15:42, Reindl Harald wrote:



Am 22.08.2015 um 14:37 schrieb Elena Stepanova:

Hi Reindl,

On 22.08.2015 13:20, Reindl Harald wrote:

i was flooded once again with mcron-mails ERROR 144 (HY000) at line 1:
Table './asterisk/cdr' is marked as crashed and last (automatic?) repair
failed

well, because mariadb creates such temp files and don't remove them
which makes myisam-recover-options = FORCE useless


Please check https://mariadb.atlassian.net/browse/MDEV-8475, it's
probably the same problem that you are experiencing. If so, it's fixed
in 10.1.6.


sounds similar

this really needs to be fixed in 10.0.x and was introduced with 10.0.x


There are two parts of the problem: that these stale files appear at 
all, and that they are not removed.


MDEV-8475 describes and fixes the second part, and it exists at least in 
5.5 as well, both MySQL and MariaDB, so it was not introduced in 10.0.x. 
I suppose Monty had good reasons to fix it only in 10.1; but since there 
seems to be a strong interest in this bugfix for 10.0, maybe he will 
want to reconsider.


There is, however, still the first part, why these files appear. We have 
a separate JIRA issue for it, 
https://mariadb.atlassian.net/browse/MDEV-8571 -- still open with no 
good way to reproduce. It is quite possible that *this* was indeed 
introduced with 10.0.x, at least that's when people started observing 
it. If you have any information on it, especially if you know how to 
reproduce it reliably, please comment on the bug report (or here, if you 
so prefer).


Regards,
Elena






-rw-rw 1 mysql mysql 0 2015-08-21 13:47 cdr.TMM

MariaDB [asterisk] optimize table cdr;
+--+--+--++



| Table| Op   | Msg_type | Msg_text
   |
+--+--+--++



| asterisk.cdr | optimize | error| Can't create new tempfile:
'/Volumes/dune/mysql_data/asterisk/cdr.TMM' |
| asterisk.cdr | optimize | status   | Operation failed
   |
+--+--+--++





___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] innodb_file_per_table default setting in the online documentation

[Elena Stepanova]

Hi Ian, Pantelis,

What MySQL docs say is true, however confusing.
The value was switched ON in early versions of MySQL 5.5; caused some 
problems; was switched back to OFF in 5.5.7; stayed OFF in all further 
5.5 releases and early releases of 5.6; and was switched ON from 5.6.6.


For MariaDB it's a bit simpler for 5.5 and more complicated for 10.0.

As Ian said the first release was 5.5.20, so in MariaDB 5.5 it's just 
OFF by default.


In 10.0, it was OFF in 10.0.0-10.0.3; from 10.0.4, where InnoDB 5.6.10 
was merged, it was ON for the the InnoDB plugin (which was the default 
InnoDB then) but still OFF for XtraDB; and later when XtraDB was 
upgraded, it became ON for it too. All in all, in 10.0.10 which was the 
first GA release, it was already ON for both flavors, as it is now.


Regards,
Elena



On 08.05.2015 11:04, Ian Gilfillan wrote:

Although the first MariaDB 5.5 release was 5.5.20... Anyway, fixed in
the docs now, thanks for the report.


On 08/05/2015 09:50, Ian Gilfillan wrote:


You're right that ON and OFF are switched around. I'll double check
the version that this changed - the 5.5 version of the MySQL docs at
http://dev.mysql.com/doc/refman/5.5/en/innodb-parameters.html#sysvar_innodb_file_per_table
also say that this was changed in 5.5.7 (so it was probably changed in
both MySQL 5.5.7 and 5.6.6), but I'll check the MariaDB diffs to be sure.

Sending to this list is fine, although there's also a docs-specific
list: maria-d...@lists.launchpad.net

ian

On 08/05/2015 01:50, Pantelis Theodosiou wrote:

I was looking for the default setting of this variable and the
MariaDB documentation
https://mariadb.com/kb/en/mariadb/xtradbinnodb-server-system-variables/#innodb_file_per_table
has:

 *Default Value:* |OFF| (= MariaDB/MySQL 5.5.7), |ON|
(MariaDB/MySQL 5.5.0 to 5.5.6)

while MySQL documentation
http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_file_per_table
has (I think correctly):

*Permitted Values* (= 5.6.5)*
Type*|boolean|*Default *|OFF

|*Permitted Values* (= 5.6.6)
*Type *|boolean|*  Default *|ON

|
|So, I see two issues:
- first, the changing version is 5.6.6 (not 5.5.7), at least in
MySQL, and
- second, the values OFF / ON in the Maria documentation are reversed.

|
|Apologies if this is not the correct list to raise the issue.


|
|Pantelis Theodosiou
|
|
|








___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] Table encryption 10.1.4

[Elena Stepanova]

Hi Rhys,

Thank you for reporting all of this.

Could you please file a bug report at our JIRA 
(https://mariadb.atlassian.net) for the last assertion failure?


Please by all means file documentation issues as well, but I can do it 
on your behalf if you so prefer; for the crash, however, we might need 
additional information from you, it will be easier to request and track 
via JIRA.


Thanks again,
Regards,
Elena



On 16.04.2015 19:38, Rhys Campbell wrote:

In addition to the below flow...

Adding both, or either one of...

aria-encrypt-tables=1
encrypt-tmp-disk-tables=1

Results in a crash on startup...

[cid:image003.png@01D0786C.31DF1910]

From: Maria-discuss 
[mailto:maria-discuss-bounces+rhys.campbell=tradingscreen@lists.launchpad.net]
 On Behalf Of Rhys Campbell
Sent: 16 April 2015 17:24
To: maria-discuss@lists.launchpad.net
Subject: [Maria-discuss] Table encryption 10.1.4

Hi All,

Been playing with encryption in 10.1.4 today and there's a few issues...

Firstly the manualhttps://mariadb.com/kb/en/mariadb/table-encryption/ gives 
the following example...

Example my.cnf to enable XtraDB encryption:

[mysqld]
file-key-management
file-key-management-filename = /mount/usb1/keys.txt
innodb-encrypt-tables
innodb-encrypt-logs
innodb-encryption-threads=4

But doesn't make mention of the fact you need to add..

plugin-load-add=file_key_management.so

for this to work.

Secondly...

With this config..

plugin-load-add=file_key_management.so
file_key_management
file_key_management_filename = /home/rcampbel/key.enc
file_key_management_filekey = FILE:/home/rcampbel/keyfile.txt
file_key_management_encryption_algorithm = AES_CBC
innodb-encrypt-tables
innodb-encrypt-logs
innodb-encryption-threads = 4

I receive the following error...

ERROR Innodb: Tablespace id 0 encrypted but encryption service not available. Can't 
continue opening tablespace.

Then if I comment out inndob-encrypt-tables we get a step further but it 
complains..

unknown option -innodb-encrypt-logs - documentation for 10.1.4 says 
differenthttps://mariadb.com/kb/en/mariadb/table-encryption/

If I change this to...

innodb-encrypt-log

The server then starts up successfully. Here's a snip of some relevant 
variables...

[cid:image004.png@01D0786C.31DF1910]

After this I do seem to be able to dynamically set innodb_encrypt_tables and 
create an encrypted table...

[cid:image005.png@01D0786C.31DF1910]


Side note file_key_management_plugin.so is missing from the 10.1.3 .tar.gz 
bundles


Rhys Campbell
Database Administrator
TradingScreen, Inc.
23 York House, 5th Floor
London WC2B 6UJ
Email: rhys.campb...@tradingscreen.commailto:rhys.campb...@tradingscreen.com

Follow TradingScreen on Twitterhttp://twitter.com/#!/TradingScreen , 
Facebookhttp://www.facebook.com/pages/TradingScreen/214046251945650 and our blog Trading 
Smartertradingsmarter.tradingscreen.com
This message is intended only for the recipient(s) named above and may contain 
confidential information. If you are not an intended recipient, you should not 
review, distribute or copy this message. Please notify the sender immediately 
by e-mail if you have received this message in error and delete it from your 
system.




___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] Giving up on dynamic columns

[Elena Stepanova]

Hi Tom,

On 01.03.2015 22:38, Tom Worster wrote:

I discovered this showstopper on Friday while working with real data in
development of a new app. I managed to narrow it down today and filed the
bug report.

https://mariadb.atlassian.net/browse/MDEV-7650

Looks like Maria saves an illegally formatted dyncol string if a dynamic
column is longer than 64kB and is not alphabetically last by name among the
dynamic column in the blob.


Please note that regardless any particular feature, an application 
working with real data should either check for warnings which happen 
upon DML -- in your case, INSERTs produce Data truncated for column 
'dcols', -- or, better still, set a strict sql_mode which will convert 
these warnings to errors, so the illegal data could never be inserted in 
the first place.


Regards,
Elena



Tbh, even is this were fixed tomorrow so I could proceed with my work, I'm
not sure I would use dyncols. My confidence in the feature has been shaken.
It's a pity because the Active Record ORM extension I wrote was working.

Tom





___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] MariaDB 5.5.41 now available

[Elena Stepanova]

Hi Peter,

Which mirror are you using? I tried a couple, it worked for me; but some 
mirrors can probably take longer to update (or are really broken).


Regards,
/E

On 22.12.2014 13:30, Peter Laursen wrote:

Downloads or download links are broken. Nothing downloads. page not
found.

-- Peter

On Sun, Dec 21, 2014 at 11:30 PM, Daniel Bartholomew db...@mariadb.com
wrote:


The MariaDB project is pleased to announce the immediate availability
of MariaDB 5.5.41

This is a Stable (GA) release. See the Release Notes and Changelog
for details.


- - Links  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

MariaDB 5.5.41
  - Release Notes: https://mariadb.com/kb/en/mariadb-5541-release-notes
  - Changelog: https://mariadb.com/kb/en/mariadb-5541-changelog
  - Downloads: https://downloads.mariadb.org/mariadb/5.5.41

  About MariaDB 5.5:
   - https://mariadb.com/kb/en/what-is-mariadb-55/

  APT and YUM Repository Configuration Generator:
   - https://downloads.mariadb.org/mariadb/repositories/


- - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - -

There are several upcoming MariaDB-focused webinars and many
previously held ones available to watch on an on-demand basis at:

  - https://mariadb.com/news-events/webinars


- - MariaDB Books  - - - - - - - - - - - - - - - - - - - - - - - - - -

There is an ever-growing library of MariaDB books available to help
you get the most out of MariaDB. See the MariaDB Books page for
details and links:

  - https://mariadb.com/kb/en/mariadb/books/


- - User Feedback plugin - - - - - - - - - - - - - - - - - - - - - - -

MariaDB includes a User Feedback plugin. This plugin is disabled by
default. If enabled, it submits basic, completely anonymous MariaDB
usage information. This information is used by the developers to track
trends in MariaDB usage to better guide development efforts.

If you would like to help make MariaDB better, please add
feedback=ON to your my.cnf or my.ini file!

See http://mariadb.com/kb/en/user-feedback-plugin for more
information.


- - Quality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

The project always strives for quality, but in reality, nothing is
perfect. Please take time to report any issues you encounter at:

  - http://mariadb.org/jira


- - Support MariaDB - - - - - - - - - - - - - - - - - - - - - - - - - -

If you would like to contribute to the MariaDB Foundation, please see
the contributing and donations pages. We also have merchandise
available in a cafepress store. All proceeds go to support the MariaDB
Foundation.

  - https://mariadb.com/kb/en/contributing

  - https://mariadb.org/en/donate/

  - http://www.cafepress.com/mariadb


We hope you enjoy MariaDB!

--
MariaDB
 Website - http://mariadb.org
 Twitter - http://twitter.com/mariadb
 Google+ - http://google.com/+mariadb
Facebook - http://fb.com/MariaDB.dbms
  Knowledge Base - http://mariadb.com/kb

___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp





___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] MariaDB 5.5.41 now available

[Elena Stepanova]

On 22.12.2014 14:40, Peter Laursen wrote:

Ok .. it looks like the server at ftp://ftp.ulak.net.tr/ is down. .tr is
top-level domain for Turkey.  I don't understand why I get redirected
there. I am in Denmark.


On whatever reason, it's preselected in your mirror list on the 
downloads page. When you go here 
https://downloads.mariadb.org/mariadb/5.5.41 , there is a section 
'Mirror' on the right side, just choose another one (expand it to show 
all mirrors if necessary).


Regards,
/E




-- Peter

On Mon, Dec 22, 2014 at 12:36 PM, Peter Laursen peter_laur...@webyog.com
wrote:


The links redirect to  the mirror at ...from/ftp%3A//
ftp.ulak.net.tr/pub/MariaDB. Is this really a correct URL?

-- Peter



On Mon, Dec 22, 2014 at 12:34 PM, Peter Laursen peter_laur...@webyog.com
wrote:


I don't use *mirrors*. I use *links*. :-)

Nothing here https://downloads.mariadb.org/mariadb/5.5.41/ works for me.
It could of course be a DNS problem at my end.


-- Peter

On Mon, Dec 22, 2014 at 12:02 PM, Elena Stepanova 
ele...@montyprogram.com wrote:


Hi Peter,

Which mirror are you using? I tried a couple, it worked for me; but some
mirrors can probably take longer to update (or are really broken).

Regards,
/E


On 22.12.2014 13:30, Peter Laursen wrote:


Downloads or download links are broken. Nothing downloads. page not
found.

-- Peter

On Sun, Dec 21, 2014 at 11:30 PM, Daniel Bartholomew db...@mariadb.com



wrote:

  The MariaDB project is pleased to announce the immediate availability

of MariaDB 5.5.41

This is a Stable (GA) release. See the Release Notes and Changelog
for details.


- - Links  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

MariaDB 5.5.41
   - Release Notes: https://mariadb.com/kb/en/
mariadb-5541-release-notes
   - Changelog: https://mariadb.com/kb/en/mariadb-5541-changelog
   - Downloads: https://downloads.mariadb.org/mariadb/5.5.41

   About MariaDB 5.5:
- https://mariadb.com/kb/en/what-is-mariadb-55/

   APT and YUM Repository Configuration Generator:
- https://downloads.mariadb.org/mariadb/repositories/


- - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - -

There are several upcoming MariaDB-focused webinars and many
previously held ones available to watch on an on-demand basis at:

   - https://mariadb.com/news-events/webinars


- - MariaDB Books  - - - - - - - - - - - - - - - - - - - - - - - - - -

There is an ever-growing library of MariaDB books available to help
you get the most out of MariaDB. See the MariaDB Books page for
details and links:

   - https://mariadb.com/kb/en/mariadb/books/


- - User Feedback plugin - - - - - - - - - - - - - - - - - - - - - - -

MariaDB includes a User Feedback plugin. This plugin is disabled by
default. If enabled, it submits basic, completely anonymous MariaDB
usage information. This information is used by the developers to track
trends in MariaDB usage to better guide development efforts.

If you would like to help make MariaDB better, please add
feedback=ON to your my.cnf or my.ini file!

See http://mariadb.com/kb/en/user-feedback-plugin for more
information.


- - Quality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

The project always strives for quality, but in reality, nothing is
perfect. Please take time to report any issues you encounter at:

   - http://mariadb.org/jira


- - Support MariaDB - - - - - - - - - - - - - - - - - - - - - - - - - -

If you would like to contribute to the MariaDB Foundation, please see
the contributing and donations pages. We also have merchandise
available in a cafepress store. All proceeds go to support the MariaDB
Foundation.

   - https://mariadb.com/kb/en/contributing

   - https://mariadb.org/en/donate/

   - http://www.cafepress.com/mariadb


We hope you enjoy MariaDB!

--
MariaDB
  Website - http://mariadb.org
  Twitter - http://twitter.com/mariadb
  Google+ - http://google.com/+mariadb
 Facebook - http://fb.com/MariaDB.dbms
   Knowledge Base - http://mariadb.com/kb

___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp





___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp










___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] Doubt about 'atomic' insert

[Elena Stepanova]

Hi Roberto,

On 13.12.2014 21:13, Roberto Spadim wrote:

Hi guys
i'm with a doubt about the standard (sql standand?) error reporting ,
about INSERT SELECT...

should this insert select return duplicate key?
INSERT INTO errorsX (id) SELECT MAX(id)+1 FROM errorsX;


considering:

CREATE TABLE errorsX(
  id INT NOT NULL DEFAULT 0,
  PRIMARY KEY (id)
) ;



I suppose you forgot to mention that you are doing it on an Aria table, 
concurrently, simultaneously from several threads?


Regards,
/E






___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] MariaDB for OpenSuSE 12.3

[Elena Stepanova]

Hi Peter,

http://hasky.askmonty.org/archive/pack/10.0/build-6865/kvm-zyp-opensuse13_1-x86_64/

Regards,
Elena


On 24.11.2014 15:17, Peter Laursen wrote:

I am sorry, but I really do not understand at all how to get acces to RPMs
(or anything) from the page linked to (
http://buildbot.askmonty.org/buildbot/builders/kvm-zyp-opensuse13_1-x86_64
).


-- Peter

On Sun, Nov 23, 2014 at 9:50 PM, Sergei Golubchik s...@mariadb.org wrote:


Hi, Peter!

We've recently started building on SuSE:
http://buildbot.askmonty.org/buildbot/builders/kvm-zyp-opensuse13_1-x86_64
http://buildbot.askmonty.org/buildbot/builders/kvm-zyp-opensuse13_1-x86

This is a new builder and we haven't made any releases of these
binaries yet, as far as I remember.

Still the source code is the same, so it is as stable as any other 10.0
build. But the packaging - like dependencies or conflicts - might be not
completely polished yet.

So, if you'd like, you can try our suse rpms that were built on opensuse,
as above.

On Nov 23, Peter Laursen wrote:

I have OpenSuSE 12.3.  It ships with MariaDB 1.0.13 - and with no TokuDB
and no Galera options. I would like to upgrade to 10.0.14 and also enable
TokuDB. And it does not seem that an upgrade will be available from SuSE
software repositories.

There are a lot of RPMs in the yum repository
http://mirror.23media.de/mariadb/mariadb-10.0.14/yum/. But does anyone

know

if they will work with SuSE 12.3? Runtime environment (kernel, glibc

etc.)

should be compatible of course, and also  RPMs for Redhat/Fedora/CentOS
systems will not alwyas work on SuSE, as SuSE has some specific
requirements for the SPECS.

When I used SuSE 10.x many years ago, the generic glibc23 RPMs

available

worked perfectly.

Note: I *only* want to install a server that can be handled by SuSE's

YaST

package manager! So suggestons for any other solution (such as using the
tarball) is not an option. Or it would be last resort.

I would not mind give it a try if someone can advise what I should try. I
have SuSE running in a VM and I will be able to return to a snapshot of

the

system easily if something goes wrong.


Regards,
Sergei





___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] R: transactions and UNLOCK TABLES

[Elena Stepanova]

Hi Federico,

On 23.09.2014 12:50, Federico Razzoli wrote:

Let's make the snippet simpler. Only one table, non-transactional, please look 
at the difference from what docs say and the real behaviour. If one could 
explain what UNLOCK TABLES exactly does, it would be great.

MariaDB [test] SELECT @@in_transaction, @@autocommit;
+--+--+
| @@in_transaction | @@autocommit |
+--+--+
|0 |1 |
+--+--+
1 row in set (0.00 sec)

MariaDB [test] CREATE OR REPLACE TABLE t (c INT) ENGINE = MEMORY;
Query OK, 0 rows affected (0.12 sec)

MariaDB [test] LOCK TABLE t WRITE;
Query OK, 0 rows affected (0.00 sec)

MariaDB [test] START TRANSACTION;
Query OK, 0 rows affected (0.00 sec)


Beginning a transaction causes table locks acquired with LOCK TABLES to 
be released, as though you had executed UNLOCK TABLES.


http://dev.mysql.com/doc/refman/5.5/en/commit.html



MariaDB [test] INSERT INTO t VALUES (1);
Query OK, 1 row affected (0.01 sec)

MariaDB [test] UNLOCK TABLES;
Query OK, 0 rows affected (0.00 sec)


So, this UNLOCK is not actually doing anything.

Regards,
Elena



MariaDB [test] SELECT @@in_transaction;
+--+
| @@in_transaction |
+--+
|1 |
+--+
1 row in set (0.00 sec)


Regards
Federico


___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] Mariadb 10.0.11 ERROR 2013 (HY000): Lost connection to MySQL server during query. Help fixing?

[Elena Stepanova]

Hi,


On 13.06.2014 9:53, grantksupp...@operamail.com wrote:

I'm running Mariadb 10.0.11 on linux/64.

Connected to my DB, executing similar queries, one succeeds, the next
fails @ error

ERROR 2013 (HY000): Lost connection to MySQL server during
query

There's a backtrace included below.  I'm not sure what it tells me about
the problem, or what to do about.  Any help or suggestions would be
appreciated.


Could you please file a bug report at 
https://mariadb.atlassian.net/secure/Dashboard.jspa?


If it's possible, please include a dump of dTEST.system table (structure 
and data). If the dump is big or private, you can upload it to our ftp 
into the private section (ftp://ftp.askmonty.org/private), this way only 
MariaDB developers will have access to it.


Also, try to run
EXPLAIN EXTENDED UPDATE system SET status='0' WHERE name='system_charts'
and if it does not crash, include its output into the bug report as well.

If the data is confidential and you can't share it even in the private 
section, please at least include into the bug report:


SHOW CREATE TABLE system;
SHOW INDEX IN system;
SHOW TABLE STATUS LIKE 'system';


Thanks,
Elena





Here are the queries

MariaDB [dTEST] UPDATE system SET status='0' WHERE
name='tagclouds';
Query OK, 0 rows affected (0.00 sec)
Rows matched: 1  Changed: 0  Warnings: 0

MariaDB [dTEST] UPDATE system SET status='0' WHERE
name='tagclouds';
Query OK, 0 rows affected (0.00 sec)
Rows matched: 1  Changed: 0  Warnings: 0

MariaDB [dTEST] UPDATE system SET status='0' WHERE
name='system_charts';
ERROR 2013 (HY000): Lost connection to MySQL server during query
MariaDB [dTEST] UPDATE system SET status='0' WHERE
name='system_charts';
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id:3
Current database: dTEST

ERROR 2013 (HY000): Lost connection to MySQL server during query
MariaDB [dTEST] UPDATE system SET status='0' WHERE
name='system_charts';
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id:3
Current database: dTEST

ERROR 2013 (HY000): Lost connection to MySQL server during query
MariaDB [dTEST] UPDATE system SET status='0' WHERE
name='tagclouds';
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id:3
Current database: dTEST

Query OK, 0 rows affected (0.09 sec)
Rows matched: 1  Changed: 0  Warnings: 0

MariaDB [dTEST]

Here's the -err log on failed exec of

UPDATE system SET status='0' WHERE name='system_charts';

tail -f /var/log/mariadb/mariadb-err.log

140612 22:34:39 [ERROR] 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.

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: 10.0.11-MariaDB-log
key_buffer_size=268435456
read_buffer_size=1048576
max_used_connections=1
max_threads=66
thread_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size +
sort_buffer_size)*max_threads = 601410 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7f2de93f1008
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 = 0x7f2e11fe5e78 thread_stack 0x10
/usr/local/mariadb/bin/mysqld(my_print_stacktrace+0x2e)[0xacb60e]
/usr/local/mariadb/bin/mysqld(handle_fatal_signal+0x390)[0x6f5a10]
/lib64/libpthread.so.0(+0xf9f0)[0x7f2e177f79f0]
/usr/local/mariadb/bin/mysqld[0x915cba]
/usr/local/mariadb/bin/mysqld[0x909e27]
/usr/local/mariadb/bin/mysqld[0x90a35b]
/usr/local/mariadb/bin/mysqld[0x916853]
/usr/local/mariadb/bin/mysqld[0x8a9aa6]
/usr/local/mariadb/bin/mysqld[0x8ab639]
/usr/local/mariadb/bin/mysqld[0x8cd5a7]
/usr/local/mariadb/bin/mysqld[0x8d0cfc]
/usr/local/mariadb/bin/mysqld[0x8b5777]
/usr/local/mariadb/bin/mysqld[0x82ef43]

/usr/local/mariadb/bin/mysqld(_ZN7handler13ha_update_rowEPKhPh+0xe5)[0x6fedc5]
 

Re: [Maria-discuss] query cache and galera

[Elena Stepanova]

Hi Roberto,

On 27.05.2014 5:06, Roberto Spadim wrote:

Hi guys, i was testing mariadb-galera and checked that query cache is
disabled with galera
Is it ok or i'm doing something wrong?


See the discussion regarding the query cache on Codership mailing list: 
https://groups.google.com/forum/?hl=rufromgroups=#!topic/codership-team/VZyOuXFDSdQ


The last update was that although the limitation had been lifted, the 
query cache was still disabled on startup, and was to be configured 
dynamically if needed. Apparently it's still the case.


Regards,
Elena

___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] Building on Windows with cmake 2.8.12.2 and Visul Studio 2012

[Elena Stepanova]

Quick follow-up for other interested parties.

Wlad found the reason -- a new cmake bug-feature -- and suggested a 
workaround for it, which solved the problem. See 
https://mariadb.atlassian.net/browse/MDEV-6016 for more details.


The workaround has been pushed into maria/5.5 tree and will appear in 
5.5.37 and 10.0.11 releases.


MySQL 5.6 is also affected, i didn't check other branches.

Regards,
/E


On 4/1/2014 3:35 PM, Wes Bullard wrote:

I’ve been trying for a few days now first with 10.0.9 and now with
10.0.10 to build on windows x64 both by command line and in visual
studio 2012. Straight building seems to go fine but if I try and build
--target package or even --target msi I get errors about missing pdb
files.  This is both in RelWithDebInfo and Release configuration.

The following are outputs from the builds

RelWithDebInfo - http://paste.chainscriptz.net/?paste=5

Release - http://paste.chainscriptz.net/?paste=6

This is in Visual Studio 2012 Ultimate update 4. Sorry if this is in the
wrong format first time using a mailing list.



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] MariaDB 10.0.10 now available

[Elena Stepanova]

Hi,

On 3/31/2014 1:13 PM, Michael Paulini wrote:

Just to be controversial, shouldn't
the mariadb-10.0.10-linux-x86_64.tar.gz (GLIBC 2.14+) tarball contain a
lib/plugin/ha_cassandra.so

(according to https://mariadb.com/kb/en/cassandra-storage-engine/)


The bintar should indeed have Cassandra, and will have it again, at the 
moment there is a known configuration issue in the build system which is 
waiting to be solved, sorry about it.


Some (but not all) OS-specific packages have Cassandra, so does the 
source tarball. Please note that in for RPM-based systems it comes as a 
separate package.


Regards,
Elena



Cassandra also doesn't show up with show storage engines

thanks,

Michael


On 31 March 2014 06:49, Daniel Bartholomew db...@mariadb.com
mailto:db...@mariadb.com wrote:

The MariaDB project is pleased to announce the immediate availability
of MariaDB 10.0.10.

This is a Stable (GA) release. See the Release Notes and Changelog
for details.


- - Links  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

MariaDB 10.0.10
  - Release Notes: https://mariadb.com/kb/en/mariadb-10010-release-notes
  - Changelog: https://mariadb.com/kb/en/mariadb-10010-changelog
  - Downloads: https://downloads.mariadb.org/mariadb/10.0.10

  About MariaDB 10.0:
   - https://mariadb.com/kb/en/what-is-mariadb-100/

  APT and YUM Repository Configuration Generator:
   - https://downloads.mariadb.org/mariadb/repositories/


- - MariaDB  MySQL community event, 3 Apr 2014  - - - - - - - - - - -

The MariaDB Foundation is holding a community event to complement the
Percona Live conference and expo in Santa Clara, CA. The event is
free. Visit the Community Events page on mariadb.org
http://mariadb.org for full details,
including the speaker schedule and to register.

  - https://mariadb.org/en/community-events/


- - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - -

SkySQL has held several MariaDB-focused Webinars recently which are
available on an on-demand basis at:

  - http://www.skysql.com/why-skysql/webinars/

They are also planning several more MariaDB-focused webinars that will
be held over the comming months. Details available at the above link.


- - MariaDB Books  - - - - - - - - - - - - - - - - - - - - - - - - - -

The newly published MariaDB Cookbook contains nearly 100 recipes
covering a variety of features in MariaDB.
  -
http://www.packtpub.com/exclusive-and-unique-features-of-mariadb/book

Another book, Getting Started with MariaDB is a how-to guide for
beginners to help them get up to speed quickly with MariaDB. No prior
database experience required.
  - http://www.packtpub.com/getting-started-with-mariadb/book


- - User Feedback plugin - - - - - - - - - - - - - - - - - - - - - - -

MariaDB includes a User Feedback plugin. This plugin is disabled by
default. If enabled, it submits basic, completely anonymous MariaDB
usage information. This information is used by the developers to track
trends in MariaDB usage to better guide development efforts.

If you would like to help make MariaDB better, please add
feedback=ON to your my.cnf or my.ini file!

See http://mariadb.com/kb/en/user-feedback-plugin for more
information.


- - Quality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

The project always strives for quality, but in reality, nothing is
perfect. Please take time to report any issues you encounter at:

  - http://mariadb.org/jira


- - Support MariaDB - - - - - - - - - - - - - - - - - - - - - - - - - -

If you would like to contribute to the MariaDB Foundation, please see
the contributing and donations pages. We also have merchandise
available in a cafepress store. All proceeds go to support the MariaDB
Foundation.

  - https://mariadb.com/kb/en/contributing

  - https://mariadb.org/en/donate/

  - http://www.cafepress.com/mariadb


We hope you enjoy MariaDB!

--
MariaDB: An Enhanced Drop-in Replacement for MySQL
 Website - http://mariadb.org
 Twitter - http://twitter.com/mariadb
 Google+ - http://google.com/+mariadb
Facebook - http://fb.com/MariaDB.dbms
  Knowledge Base - http://mariadb.com/kb

___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
mailto:maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] MariaDB 5.5.35 now available

[Elena Stepanova]

Hi,

On 2/11/2014 3:56 AM, David Timothy Strauss wrote:

In the Fedora 20 Yum repository [1], I see the following:
MariaDB-Galera-5.5.34-fedora19-x86_64-server.rpm

That can't be right.


Yes, this is actually right.
The repository contains latest versions of both MariaDB server and 
MariaDB-Galera.
MariaDB server 5.5.35 has been released, but MariaDB-Galera hasn't yet 
(it will be soon).


Regards,
Elena



[1] http://yum.mariadb.org/5.5/fedora20-amd64/rpms/



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] Mariadb upgrade issues

[Elena Stepanova]

Hi Constantine,

On 1/27/2014 8:48 AM, Constantine wrote:

Recently we migrate to mariadb and every version upgrade failed (last
failed from 10.0.6 to 10.0.7). After investigation I find this thread
http://mirzmaster.wordpress.com/2009/01/16/mysql-access-denied-for-user-debian-sys-maintlocalhost/and
after password update issue fixed. I find bug
https://bugs.launchpad.net/maria/+bug/983322 but it marked as incomplete



Nowadays we use JIRA for bug tracking, that's why the LP bug you are 
referring to is so outdated. There are some open JIRA issues related to 
the suboptimal system of using debian-sys-maint and storing its 
passwords, e.g. https://mariadb.atlassian.net/browse/MDEV-5500. If you 
have additional information, please feel free to comment on it. For 
example, it would be interesting to know how the password in the cnf 
file went out of sync with the data in the system tables in the first 
place. You did not mention any replication, and I assume you did not 
change the password manually earlier, so in your case the reason has to 
be at least somewhat different from the one that MDEV-5500 suggests.


Thanks,
Elena


___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] Left Join Bug?

[Elena Stepanova]

Hi Jamie,

On 10/4/2013 9:39 PM, Jamie Jackson wrote:

Hi Folks,

I'm seeing a difference in a query result between MariaDB 5.5.32 and
MySQL 5.1.69.

I've distilled things down as far as I can get them, while still being
able to reproduce the issue. Anything else I do to get the sample to
make it smaller or more focused seems to make the issue disappear.

The data: https://www.dropbox.com/s/m02sqjl2y2cq4ky/sampledump1.zip

The query, and the results (and explains) in both MySQL and MariaDB:

https://gist.github.com/jamiejackson/6829118

What's going on here? Is there an oustanding bug for this? Should I file
a bug?


Yes, please file a bug at 
https://mariadb.atlassian.net/secure/Dashboard.jspa. We have a few bugs 
with wrong results currently in work, but I can't find right away any 
that matches your scenario.


As a workaround, please try
set optimizer_switch='derived_merge=off';

Regards,
Elena



Thanks,
Jamie



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] New server, switch to MariaDB, different versions

[Elena Stepanova]

Hi,

On 4/27/2013 10:54 PM, Tanstaafl wrote:

Hello,

My current (8 yr old bare metal) server is currently running mysql
5.1.62, with just a couple of very small databases:

postfixadmin
and
roundcube

I am setting up a shiny new virtualized (ESXi host) server, that now has
MariaDB 5.5.30 on it...

My question is, can I do a dump from my old server running mysql 5.1.62,
then restore that dump to my new server running MariaDB 5.5.30, run
mysql_upgrade, and have any kind of reasonable expectation of it working?


Yes, it would be a very reasonable expectation. It's supposed to work.

Regards,
Elena



I'd rather not update the current (production) server to MariaDB (I'm
gunshy when it comes to major changes on a production system).

If not, then my other option would be to downgrade MariaDB on  the new
server to 5.1.66... but again, I'd rather not do that if it isn't
necessary.

Thanks - I'm really looking forward to saying goodbye to mysql (for
political reasons, the software itself has served me well these 8 years,
it's just too bad that they got bought by Oracle)...

Charles

___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] testing Galera

[Elena Stepanova]

Hi Jan,

I recommend to ask for advice regarding Galera fine-tuning and tricks on 
the Codership mail list: codership-t...@googlegroups.com. It's an active 
group, and as far as I can tell, Galera experts there are quite responsive.


While we might be able to provide _some_ views on the subject, Codership 
people have far more intimate knowledge of Galera internals and 
specifics, and besides there are subscribers with different working 
configurations and environments, possibly in some cases similar to 
yours, so they might share their experience.


Regards,
Elena

On 2/11/2013 7:38 PM, Jan Kirchhoff wrote:

Hi everybody,

I installed Galera on 2 servers, imported a database dump (took almost 2
days to import a 100GB gzipped sql-dump ...) and set up one of the two
servers as a replication slave of our main database.

Now as I try to understand all the new variables and want to get an idea
of do's and dont's some questions pop up:

While the traditional replication slave on the first galera-server is
still catching up (still 20 seconds behind...) I had our main
data-proxy starting to write to that server.
Most of the data coming into our databases is not going its way trough
the replication but via our self-written proxy application. This
application connects to all databases, sets SQL_LOG_BIN=0 and then
starts updating just a few tables (up to 15-20GB of pure sql statements
per hour depending on the time of the day). This works fine, the server
was processing the statements no slower than the other non-galera servers.

I couldn't see the updates on the second galera-server and figured that
was because of the SQL_LOG_BIN=0. Now things got complicated. How to
resolve this? I gave it a try, hacked the proxy not to set SQL_LOG_BIN=0
for that specific server and started it again, but this made the second
server crash almost immidiatly with HA_ERR_KEY_NOT_FOUND - actually  I
was expecting something like that to happen as the tables were out of
sync now.

Is there something like slave_skip_counter, aka I Know what I do, skip
that update? I think I have to take a new snapshot to get the second
node up and consistent again. It tried to to that automatically but
stopped because of the hanging rsync-daemon problem. I'll let it catch
up with the replication lag first and then start that again...

If I take a node down or just restart mariadb after changing variables,
it pulls the changes it missed (IST) from another server, right? These
are saved in the galera-cache on all servers? How do I figure out what a
reasonable size for the gcache would be for me? The default size of
128MB is way to small for me if I want to take a node down for a few
hours to do backups/upgrades/whatever, but do I need 5, 10 or 50 GBs?
Some information on number of bytes written to the gcache I could look
at? Or is wsrep_replicated_bytes the number to look at?

Finding all documentation and understanding the details is a little bit
difficult and time-consuming, but I'm making my way...

btw: is maria-developers a better place to post this as I am not writing
on production software but alpha releases?

thanks
Jan

Am 28.01.2013 17:18, schrieb Jan Kirchhoff:

Alex,

regarding the transaction rates: we currently have a peak at around
400-500/sec at certain times of the day. We'll see how that works

I just found there are no mariadb-galera-debs around for ubuntu 12.10.
Can we expect them soon? Otherwise I'd have to reinstall the test
servers with 12.04 - couldn't get the dependency problems resolved when
trying to get the 12.04-debs into 12.10 and I don't want to compile
myself :-(

Jan

Am 25.01.2013 10:24, schrieb Alex Yurchenko:

Hi Jan,

1) the load and the database size you described is nothing special to
Galera, we have users running it on bigger databases and with higher
transaction rates, Specifically those bulk inserts are perfectly fine.

2) notice that to get most of Galera (e.g. parallel applying) you have
to use ROW binlog format at least on all Galera nodes. Using
statement-based replication from master should be fine, but inside
Galera cluster it should be ROW.

3) your plan looks fine, just don't forget to set log_slave_updates when
mixing Galera and native MySQL replication.

4) the latest MariaDB-Galera has support for xtrabackup for new node
provisioning.

Regards,
Alex

On 2013-01-24 00:09, Jan Kirchhoff wrote:

Hi,

I'd like to evaluate mariadb-galera on some test databases. Our load
is at least 90% writes coming from a datastream and I would try to set
up a real-world situation and test with real data.
Most of the work load is insert ... on duplicate key update
mass-inserts (actually updates) of about 4MB/1 rows each. 99% of
these run onto 3-4 tables (each around 10GB/7 million rows of size).
Total database size is around 800 GB.
We have a traditional statement-based master-slave replication, but
all these mass-inserts run over a proxy with SET SQL_LOG_BIN=0 in
parallel on all systems - no way to process this 

Re: [Maria-discuss] Problem in replication with NOW('2012-03-07 17:32:03')

[Elena Stepanova]

Hi Jan,

The function NOW() was never supposed to take a timestamp as an 
argument, neither in MySQL nor in MariaDB. In earlier versions any 
argument was ignored. Starting from MariaDB 5.3 (and MySQL 5.6), when 
microseconds support was implemented, it takes an optional integer 
argument, which indicates a microsecond precision, so a value which 
cannot be interpreted as such causes a parsing error.


I'd say that the application that produces these statements should be 
fixed -- depending on where it takes the argument from, best case 
scenario is that it just does something meaningless, but it's also quite 
possible that it does not work as expected.


If you cannot change the behavior of the application, you might want to 
consider switching to row-based replication, this way you won't have a 
problem with the statement on newer servers.


Regards,
Elena


On 2/12/2013 1:56 AM, Jan Kirchhoff wrote:

Hi,

I set up 2 hosts as a galera cluster, one of them is a slave of my main
database.

The galera hosts are 5.5.28a-MariaDB-a1~precise-log, all other databases
are
  5.2.12-MariaDB-mariadb115~squeeze-log.

The 5.5 slave stops with 1064 errors. I figured this is because of
updates using NOW() on timestamp columns, I think they come from a
phpmyadmin frontend.
In the error log the queries look like this:

UPDATE ..., some_timestamp_field = NOW('2012-03-07 17:32:03') WHERE
...primary keys...

when I manually execute the query and just remove the NOW so it is a
simple update some_timestamp_field = '2012-03-07 17:32:03' and then
execute  set global sql_slave_skip_counter=1;slave start; everything is
fine again.

All 5.2 hosts replicate just fine.

is this a bug in 5.5?

Thanks
Jan


___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Re: [Maria-discuss] service on port 4567 is not starting

[Elena Stepanova]

Hi Daniel,

On 2/12/2013 3:30 AM, Kőszegi Dániel wrote:

Hi All,

I would appreciate a little help.

I have done everything how it is in the installation steps, but the
galera service on the port 4567 is not starting.

No errors in mysql or syslog :( Tried on debian and centos as well.

Right now server version: 5.5.28a-MariaDB-a1~squeeze-log mariadb.org
binary distribution, wsrep_23.7rc1.r but I have tried with relevant
mysql binaries as well. Do you have any idea why is it not starting the
cluster service?

wsrep.conf on node1:

root@mariaclu01:/etc/mysql# cat /etc/mysql/conf.d/wsrep.cnf

[wsrep]


These are server options. You need to name the config section [mysqld], 
or [mariadb], or [server] -- whichever you prefer -- but not [wsrep].


Please be prepared that there might be more configuration problems on 
the way, don't lose your resolve; but once you fix this one, your syslog 
should become very verbose and contain a lot of records starting with 
WSREP.


Regards,
Elena



wsrep_provider=/usr/lib/galera/libgalera_smm.so

wsrep_cluster_address=gcomm://

wsrep_sst_auth=sst:sstpass123

wsrep.conf on node2:

root@mariaclu02:~#  cat /etc/mysql/conf.d/wsrep.cnf

[wsrep]

wsrep_provider=/usr/lib/galera/libgalera_smm.so

wsrep_cluster_address=gcomm://192.168.1.30:4567

wsrep_sst_auth=sst:sstpass123

MariaDB [(none)] show status like 'wsrep%';

+--+--+

| Variable_name| Value|

+--+--+

| wsrep_cluster_conf_id| 18446744073709551615 |

| wsrep_cluster_size   | 0|

| wsrep_cluster_state_uuid |  |

| wsrep_cluster_status | Disconnected |

| wsrep_connected  | OFF  |

| wsrep_local_index| 18446744073709551615 |

| wsrep_provider_name  |  |

| wsrep_provider_vendor|  |

| wsrep_provider_version   |  |

| wsrep_ready  | ON   |

+--+--+

root@mariaclu01:/etc/mysql# netstat -tulpn | grep -e 4567 -e 3306

tcp0  0 0.0.0.0:33060.0.0.0:*
LISTEN  3387/mysqld

Thank you in advance!

Cheers,

Daniel

d...@ihd.hu



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp