- discuss - lists.mariadb.org

[Maria-discuss] Regarding DR site set-up
by Karthick Subramanian 05 Jul '16

05 Jul '16

Dear Experts, I have a question on Max Scale requirement: In prod - we have two DB server as Primary(Master) and Secondary(Slave). Both being controlled via MaxScale. Do we need to really set it up similar way in DR site also? I meant - Do we need to keep Max Scale set it up in DR as well. Anyway, DR is going to be exceptional scenarios in which entire application servers also work out of DR site and we can still point all the app servers in DR site configured directly to access the Maria DB server at DR instead of Max Scale. Note: We are currently not using MaxScale for any complex needs, we are using MaxScale for normal routing like RW split etc. I know ideal is keep both Prod site and DR site equivalent. But as cost cutting on servers etc, shall we keep DR the way I mentioned. Could you please provide your opinion on this. Regards, Karthick

2 3

[Maria-discuss] MariaDB 10.2.1 Alpha and other releases now available
by Daniel Bartholomew 04 Jul '16

04 Jul '16

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.2.1 Alpha. Also now available are the following Stable (GA) releases: MariaDB Connector/C 2.3.0, MariaDB Galera Cluster 5.5.50, and MariaDB Galera Cluster 10.0.26. See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.2.1 Alpha - Release Notes: https://mariadb.com/kb/en/mdb-1021-rn/ - Changelog: https://mariadb.com/kb/en/mdb-1021-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.2.1 About MariaDB 10.2: - https://mariadb.com/kb/en/what-is-mariadb-102/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB Connector/C 2.3.0 - Release Notes: https://mariadb.com/kb/en/mcc-230-rn/ - Changelog: https://mariadb.com/kb/en/mcc-230-cl/ - Downloads: https://downloads.mariadb.org/connector-c/2.3.0/ About MariaDB Connector/C: - https://mariadb.com/kb/en/about-mariadb-connector-c/ MariaDB Galera Cluster 5.5.50 - Release Notes: https://mariadb.com/kb/en/mgc-5550-rn/ - Changelog: https://mariadb.com/kb/en/mgc-5550-cl/ - Downloads: https://downloads.mariadb.org/mariadb-galera/5.5.50/ About MariaDB Galera Cluster: - https://mariadb.com/kb/en/about-mariadb-galera-cluster/ MariaDB Galera Cluster 10.0.26 - Release Notes: https://mariadb.com/kb/en/mgc-10026-rn/ - Changelog: https://mariadb.com/kb/en/mgc-10026-cl/ - Downloads: https://downloads.mariadb.org/mariadb-galera/10.0.26/ About MariaDB Galera Cluster: - https://mariadb.com/kb/en/about-mariadb-galera-cluster/ - - 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/donate/ 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

1 0

[Maria-discuss] Expanding Galera cluster
by Thorvald Hallvardsson 04 Jul '16

04 Jul '16

Hi guys, I need some help as I'm preparing to expand my existing Galera cluster. Generally the purpose of it is I need to replace 3 VMs I have a cluster running on to 2 physical servers I have been given for that purpose. My idea was to join 2 physical cluster to the existing cluster of 3 and then remove all 3 VMs from the cluster leaving 2 physical nodes within. I have a arbitrator box within the cluster as well. The config at the moment contains 2 maxscale proxy nodes on the front balancing the read queries across the entire cluster of 3 and write queries to the elected master. What I want to achieve is as I said above but + I will need another help with maxscale to expand and then shrink the cluster down to 2 nodes afterwards. I have had a situation before when I had to do a simple config change on the Galera cluster and I was trying to mark nodes and put them into maintenance mode to stop traffic coming to them but the commands like set server NODE master didn't actually do anything. I had situations when I had 2 masters in the cluster for a second because then something was happening that my manually selected master was becoming a slave again. I couldn't find anything on the internet what would point me into right direction and explain the whole procedure in details. My cluster is quite busy at the moment even overnight so there is no perfect time to do anything on it. I need to do it the least disruptive way and the most controlled way as well. Hence I'm asking for help and suggestions as I found both Galera and maxscale documentation very very brief not actually providing any decent details or procedures. I found much more help from Percona but descriptions don't match sometimes. Please help. Regards, TH

2 2

[Maria-discuss] New Question: Aggregating data with help tables will raise open table cache - solution?
by AskMonty KB 04 Jul '16

04 Jul '16

Hello, A new question has been asked in "MariaDB Community" by TDS. Please answer it at http://mariadb.com/kb/en/aggregating-data-with-help-tables-will-raise-open-… as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hello, I need some inspiration :-) Currently we have ~10 tables, each around 3 million rows and about 100 columns in MyISAM format. These table are only for writing data. A cronjob will aggregate data from these tables to time defined tables, e.g. min, hour, day, etc. And here is the problem: With CREATE TABLE and CREATE TEMPORARY TABLE there are difficulties. We create a table, read in data from main table, calculating values and write new data to time table. After that we delete the help table. But the table open cache gets bigger and bigger (>4000 in a day). So how can we avoid this? Switching to InnoDB or use another schema of aggregating values? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/aggregating-data-with-help-tables-will-raise-open-…

1 0

[Maria-discuss] New Question: explanation of the salt statement
by AskMonty KB 04 Jul '16

04 Jul '16

Hello, A new question has been asked in "Encryption, Hashing and Compression Functions" by max-well_57049. Please answer it at http://mariadb.com/kb/en/explanation-of-the-salt-statement/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hello together, I just saw the 'salt' Statement as I traces a login to MariaDB database. Could you explain me what this string is used for? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/explanation-of-the-salt-statement/

1 0

[Maria-discuss] bootstrap okay but wsrep_cluster_size 0
by Umarzuki Mochlis 04 Jul '16

04 Jul '16

2 1

[Maria-discuss] MariaDB 10.1.15 Released and Crash
by Alex 02 Jul '16

02 Jul '16

Hi, Last night one of my servers updated MariaDB to 10.1.15 and it started to crash every few minutes since the update ( from 10.1.14 -> 10.1.15 ). ------------ 160702 10:22:13 [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 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.1.15-MariaDB key_buffer_size=268435456 read_buffer_size=524288 max_used_connections=8 max_threads=1001 thread_count=4 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1804821 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x7f5a89876008 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 = 0x7f5ab5dd9058 thread_stack 0x48400 /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f5c9736641b] /usr/sbin/mysqld(handle_fatal_signal+0x475)[0x7f5c96ec29f5] /lib64/libpthread.so.0(+0xf7e0)[0x7f5c964c77e0] /usr/sbin/mysqld(_ZN10SQL_SELECT17test_quick_selectEP3THD6BitmapILj64EEyybbb+0x1fe5)[0x7f5c96fae535] /usr/sbin/mysqld(+0x49bb90)[0x7f5c96d92b90] /usr/sbin/mysqld(_ZN4JOIN14optimize_innerEv+0x1e2e)[0x7f5c96da1e9e] /usr/sbin/mysqld(_ZN4JOIN8optimizeEv+0x20)[0x7f5c96da2fe0] /usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x9d)[0x7f5c96da313d] /usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x25d)[0x7f5c96da6add] /usr/sbin/mysqld(+0x451d52)[0x7f5c96d48d52] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x5d7f)[0x7f5c96d5500f] /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x28d)[0x7f5c96d5854d] /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x243b)[0x7f5c96d5b1ab] /usr/sbin/mysqld(_Z10do_commandP3THD+0x16b)[0x7f5c96d5b75b] /usr/sbin/mysqld(_Z26threadpool_process_requestP3THD+0xa7)[0x7f5c96e51777] mysys/stacktrace.c:247(my_print_stacktrace)[0x7f5c96e9c425] sql/signal_handler.cc:160(handle_fatal_signal)[0x7f5c964bfaa1] sql/opt_range.cc:12843(get_sel_arg_for_keypart)[0x7f5c949a4a8d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7f5aaf1b5020): is an invalid pointer Connection ID (thread ID): 456 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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=off ------------ Anyone else encountered crashes on 10.1.15 ? Regards

2 3

[Maria-discuss] New Question: statement metadata
by AskMonty KB 01 Jul '16

01 Jul '16

Hello, A new question has been asked in "Stored Programs and Views" by raphael.quadrini. Please answer it at http://mariadb.com/kb/en/statement-metadata/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hi, Is there an equivalent function or stored procedure to Sql Server sys.dm_exec_describe_first_result_set? The goal is not to get the table or view metadata but the returned dataset metadata of a statement indead. thanks -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/statement-metadata/

1 0

[Maria-discuss] New Question: No of MariaDB Instances on MONyog
by AskMonty KB 01 Jul '16

01 Jul '16

Hello, A new question has been asked in "MariaDB FAQ" by palash.harchandani93_43595. Please answer it at http://mariadb.com/kb/en/no-of-mariadb-instances-on-monyog/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- How many instances of mariadb can be installed with MONyog. If it depends on license please mention various licences and no of instances of types of licences. -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/no-of-mariadb-instances-on-monyog/

1 0

[Maria-discuss] New Question: MONyog version detection
by AskMonty KB 30 Jun '16

30 Jun '16

Hello, A new question has been asked in "MariaDB FAQ" by palash.harchandani93_43595. Please answer it at http://mariadb.com/kb/en/monyog-version-detection/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Is it possible to identify which version of MONyog is currently running when we are using the tarball installation?? This situation arises when I havent installed MONyog and I am a user who wwants to find which MONyog version is being used. -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/monyog-version-detection/

1 0

[Maria-discuss] New Question: Swap usage won't decrease
by AskMonty KB 28 Jun '16

28 Jun '16

Hello, A new question has been asked in "MariaDB FAQ" by alexandraarreaza. Please answer it at http://mariadb.com/kb/en/swap-usage-wont-decrease/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- We have a 5 DB nodes Galera Cluster in Production (MariaDB 10.0). About a week ago a DB import was performed over an existing DB (Its size ~30G) and during this process, all DB nodes started complaining about swap usage and haven't stopped complaining since then (e.g: One of them would be using 814 MB out of 4095 MB). I have read a good few articles about MySQL and swapping issues (this is a good one: https://blog.jcole.us/2010/09/28/mysql-swap-insanity-and-the-numa-architect…) and also about swapping in MariaDB (https://mariadb.com/kb/en/mariadb/configuring-swappiness/) but still can't find out a way of solving this problem without restarting MySQL. We have NUMA architecture with 2 nodes and 96G of RAM. Our buffer pool size is 70G and it is set to use 12 innodb_buffer_pool_instances. 1) Is there any fix to this situation besides restarting MySQL? 2) Is there a way of tuning our cluster to avoid swapping in the future? Thanks. -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/swap-usage-wont-decrease/

1 0

[Maria-discuss] columnstore
by Roberto Spadim 28 Jun '16

28 Jun '16

Hi guys! anyone testing columnstore? i will test in a SCADA system this week, news and problems i will report here -- Roberto Spadim

2 2

[Maria-discuss] No Response From MariaDB Support Admin
by Tom Jay 28 Jun '16

28 Jun '16

Hello, I emailed support-admin(a)mariadb.com about a problem with the mariadb.com website. I have not yet received a response. Is there anyone else I can contact with my query? Thanks. Tom

2 1

[Maria-discuss] New Question: Problem Connector ODBC between MariaDB and ACCESS
by AskMonty KB 27 Jun '16

27 Jun '16

Hello, A new question has been asked in "MariaDB Connector/ODBC" by jlpierrey_52563. Please answer it at http://mariadb.com/kb/en/problem-connector-odbc-between-mariadb-and-access/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hello, I have a problem with the connection between ACCESS (2010), running with W7, and a MariaDB installed on a Synology NAS (DS212J). Test of DSN is OK. Import and link tables from NAS towards ACCESS are OK. But export from ACCESS is impossible: alert message says: " "ODBC l'appel a échoué (the call failed) [ma-2.0.10][5.5.49-MariaDB]You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '#O),'C_UFR' INTEGER('#O),'U_SECRETARIAT' VARCHAR,'U-2SECRETARIAT' VAR at line 1 (#1064)" I thank you Complementary Infos: The pb is the same with 1.0.6 2.0.10 2.0.11 releases of mariadb connector (32 and 64 bits) C_UFR, U_SECRETARIAT ant U_2SECRETARIAT are the three first fields of the table i try to export. Setting of the NAS: • Serveur : Localhost via UNIX socket • Type de serveur : MariaDB • Version du serveur : 5.5.49-MariaDB - Source distribution • Version du protocole : 10 • Jeu de caractères du serveur : UTF-8 Unicode (utf8) Serveur Web: • nginx/1.9.11 • Version du client de base de données : libmysql - mysqlnd 5.0.11-dev - 20120503 - $Id: 76b08b24596e12d4553bd41fc93cccd5bac2fe7a $ • Extension PHP : mysqli curl mbstring • Version de PHP : 5.6.21 -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/problem-connector-odbc-between-mariadb-and-access/

1 0

[Maria-discuss] New Question: MariaDB Backup using CommVault MYSQL iDataAgent
by AskMonty KB 27 Jun '16

27 Jun '16

Hello, A new question has been asked in "MariaDB FAQ" by palash.harchandani93_43595. Please answer it at http://mariadb.com/kb/en/mariadb-backup-using-commvault-mysql-idataagent/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Commvault idatagent supports mariadb but i want to know which backup utility scripts are used by idataagent to backup the database. Also does it Backup all storage engines or not? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/mariadb-backup-using-commvault-mysql-idataagent/

1 0

[Maria-discuss] New Question: MONyog Monitoring when password changed
by AskMonty KB 27 Jun '16

27 Jun '16

Hello, A new question has been asked in "MariaDB FAQ" by palash.harchandani93_43595. Please answer it at http://mariadb.com/kb/en/monyog-monitoring-when-password-changed/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Is it possible to get an alert whenever the user with which we are monitoring changes password in the mariadb database ?? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/monyog-monitoring-when-password-changed/

1 0

[Maria-discuss] New Question: Snchronizing MONyog on two servers
by AskMonty KB 27 Jun '16

27 Jun '16

Hello, A new question has been asked in "MariaDB FAQ" by palash.harchandani93_43595. Please answer it at http://mariadb.com/kb/en/snchronizing-monyog-on-two-servers/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Is it possible to monitor MariaDB database from two servers where MONyog is installed and keep them synchronized. By Synchronization i mean if i add a new monitor on one server then that monitor should automatically be added on the second server?? This is important as if one server where monitoring is done goes down MONyog wil stop monitoring the database. -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/snchronizing-monyog-on-two-servers/

1 0

[Maria-discuss] Reg .Net with Entity Framework (ORM)
by Karthick Subramanian 27 Jun '16

27 Jun '16

Hi All, We would like to check whether any of you using .Net with Entity Framework to access Maria DB. If yes, 1. What connector is being used 2. What challenges are facing 3. Any other points that I need to take care while workign with .Net Entity Framework with MariaDB Regards, Karthick

3 2

[Maria-discuss] Include TokuDB Hot Backup in the bundled plugin list
by jocelyn fournier 26 Jun '16

26 Jun '16

Hi, In MariaDB, TokuDB is bundled as a plugin, but it's not the case for the Hot Backup plugin (https://github.com/percona/tokudb-backup-plugin) I have to compile it manually against the server source code to have it working properly. Would it be possible to include it in the bundled plugins ? Thanks! Jocelyn -- Jocelyn Fournier Founder M : +33 6 51 21 54 10 https://www.softizy.com Softizy - At your side to Optimize your PHP / MySQL applications

2 1

[Maria-discuss] New Question: Enabling SSL in mariaDB running on Synology NAS
by AskMonty KB 25 Jun '16

25 Jun '16

Hello, A new question has been asked in "Secure Connections" by og_117488504109613889882. Please answer it at http://mariadb.com/kb/en/enabling-ssl-in-mariadb-running-on-synology-nas/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- I am having problems with enabling SSL in MariaDB running on Synology NAS (DSM version 6.0) using self signed certificates. I have modified the my.cnf file to point to certificate files and the DB seems to be loading the .cnf file ok, the ssl variables are listing the corect location of the cert files (verified over phpmyadmin) however it still says that ssl is diabled (variable have_ssl=disabled) and the DB is refusing incoming ssl connections. This is my first time working with Synology NAS so I have no idea what to try, so any help or suggestion is most welcome. Thank you in advance. -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/enabling-ssl-in-mariadb-running-on-synology-nas/

1 0

[Maria-discuss] MariaDB 10.0.26 now available
by Daniel Bartholomew 24 Jun '16

24 Jun '16

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.0.26. This is a Stable (GA) release. See the Release Notes and Changelog for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.0.26 - Release Notes: https://mariadb.com/kb/en/mdb-10026-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10026-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.0.26 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 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/donate/ 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

1 0

[Maria-discuss] New Question: Traffic Handling For Database Monitoring
by AskMonty KB 24 Jun '16

24 Jun '16

Hello, A new question has been asked in "MariaDB FAQ" by palash.harchandani93_43595. Please answer it at http://mariadb.com/kb/en/traffic-handling-for-database-monitoring/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- MONyog uses port 5555 for Monitoring the mariadb database which creates a connection on port 3306 on database server. Does this connection creates more load on the 3306 port??? and is there any way to change the port and get the connection established at some other port on which mysqld is not running?? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/traffic-handling-for-database-monitoring/

1 0

[Maria-discuss] New Question: US Export Control Classification Number (ECCN)
by AskMonty KB 21 Jun '16

21 Jun '16

Hello, A new question has been asked in "MariaDB Community" by Gareth Smith. Please answer it at http://mariadb.com/kb/en/us-export-control-classification-number-eccn/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- I can't find reference to this on any of the pages, so apologies if this is a duplicate. Does MariaDB (specifically 10.1, although others if that version doesn't) have an ECCN from the US Bureau of Industry and Security? If so, what is it please? Thanks very much, Gareth -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/us-export-control-classification-number-eccn/

1 0

Re: [Maria-discuss] MariaDB non-blocking with EPOLL
by Kristian Nielsen 20 Jun '16

20 Jun '16

Dave C <dave.zap(a)gmail.com> writes: > With you help I was able to get the whole thing working this afternoon, > although I will need to spend a lot more time testing and checking I've > caught all the traps. Ok, great! > The core application uses edge triggered epoll for the sake of efficiency > and so far I have not found any problems running the queries now with the > non-blocking API. Yes, I agree edge-triggered is a good way, and it is supposed to work (and if you should find something that does not, I'll fix it). > At this point it's simple so I'm only checking POLLIN as that seems to work > for the connect and query and fetch_row that I'm going. > > I guess the MYSQL_WAIT_TIMEOUT is not being passed because I've just not > run in to that case yet, but will unset it as you mention before passing it > to _cont() > > The timeout on epoll_wait() is set to 1 second, but we never reach that due > the amount of traffic. One second is the max because we must service other > things no later then that, for things such as automatically destroying non > responsive sockets after 30 seconds, including the MariaDB ones. The case > of queries that timeout can be handled in the same way, or else I can check > for standard mysql error codes? Yes, I think you can handle it the same way. It is probably safe to ignore MYSQL_WAIT_TIMEOUT completely. Then the MYSQL_OPT_*_TIMEOUT options for mysql_options() will do nothing, but if you handle non responsive sockets differently anyway, that might be fine. > Thanks again for your help. If I find anything weird I'll drop a post here, > but more often then not the weirdness is on my side. > > One interesting side effect of passing 0 to _cont() functions was the > multitude of segfaults I was getting on other random / unrelated functions > I'll see If I can replicate that once I've bedded everything down. - Kristian.

1 0

[Maria-discuss] MariaDB non-blocking with EPOLL
by Dave C 20 Jun '16

20 Jun '16

Originally posted to : http://stackoverflow.com/questions/37909652/mariadb-non-blocking-with-epoll Edited for context. I have single threaded server written in C that accepts TCP/UDP connections based on EPOLL and supports plugins for the multitude of protocol layers we need to support. That bit is fine. Due to the single threaded nature I wanted to implement a database layer that could utilize the same EPOLL architecture rather then separately iterating over all of the open connections. We use MariaDB and the MariaDB C connector that supports non blocking functions in it's API as described here. https://mariadb.com/kb/en/mariadb/using-the-non-blocking-library/ But what I'm finding is not what I expected, and what I was expecting is described below. First I fire the mysql_real_connect_start() and if it returns zero we dispatch the query immediately as this indicates no blocking was required, although this never happens. Otherwise I fetch the file descriptor that seems to be immediate and register it with EPOLL and bail back to the main EPOLL loop waiting for events. s = mysql_get_socket(mysql); if(s > 0){ brt_socket_set_fds(endpoint, s); struct epoll_event event; event.data.fd = s; event.events = EPOLLRDHUP | EPOLLIN | EPOLLET | EPOLLOUT; s = epoll_ctl(efd, EPOLL_CTL_ADD, s, &event); if (s == -1) { syslog(LOG_ERR, "brd_db : epoll error."); // handle error. }... So then some time later I do get the EPOLLOUT indicating the socket has been opened. And I dutifully call mysql_real_connect_cont() but at this stage it is still returning a non-zero value, indicating I must wait longer? But then that is the last EPOLL event I get, except for the EPOLLRDHUP when I guess the MariaDB hangs up after 10 seconds. Can anyone help me understand if this idea is even workable? Thanks David

2 1

[Maria-discuss] MariaDB 5.5.50 and updated connectors now available
by Daniel Bartholomew 18 Jun '16

18 Jun '16

The MariaDB project is pleased to announce the immediate availability of MariaDB 5.5.50, MariaDB Connector/J 1.4.6, and MariaDB Connector/ODBC 2.0.11. These are all Stable (GA) releases. See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 5.5.50 - Release Notes: https://mariadb.com/kb/en/mdb-5550-rn/ - Changelog: https://mariadb.com/kb/en/mdb-5550-cl/ - Downloads: https://downloads.mariadb.org/mariadb/5.5.50 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 Connector/J 1.4.6 - Release Notes: https://mariadb.com/kb/en/mcj-146-rn/ - Changelog: https://mariadb.com/kb/en/mcj-146-cl/ - Downloads: https://downloads.mariadb.org/connector-java/1.4.6/ About MariaDB Connector/J: - https://mariadb.com/kb/en/about-mariadb-connector-j/ MariaDB Connector/ODBC 2.0.11 - Release Notes: https://mariadb.com/kb/en/mco-2011-rn/ - Changelog: https://mariadb.com/kb/en/mco-2011-cl/ - Downloads: https://downloads.mariadb.org/connector-odbc/2.0.11/ About MariaDB Connector/J: - https://mariadb.com/kb/en/about-mariadb-connector-odbc/ - - 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/donate/ 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

3 3

[Maria-discuss] New Question: MariaDB Backup using Percona XtraBackup
by AskMonty KB 16 Jun '16

16 Jun '16

Hello, A new question has been asked in "MariaDB FAQ" by palash.harchandani93_43595. Please answer it at http://mariadb.com/kb/en/mariadb-backup-using-percona-xtrabackup/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Does percona xtrabackup backs up binary log files also and does it backup all storage engines when using innobackupex as on percona website it says it backs up only Innodb xtradb and myiasm?? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/mariadb-backup-using-percona-xtrabackup/

1 0

[Maria-discuss] New Question: Could you suggest a connector which can work for Django and mariaDB?
by AskMonty KB 15 Jun '16

15 Jun '16

Hello, A new question has been asked in "MariaDB Community" by cpwen. Please answer it at http://mariadb.com/kb/en/could-you-suggest-a-connector-which-can-work-for-d… as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hi, sirs. I am a new guy to learn Django and MariaDB. Could you suggest a connector which can work for Django and mariaDB? The environment is Python3.4, Django1.9, MariaDB10.0. Ubuntu15.10. Thanks a lot in advance. -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/could-you-suggest-a-connector-which-can-work-for-d…

1 0

[Maria-discuss] New Question: MONyog Auto-Discovery of MariaDB Databases
by AskMonty KB 15 Jun '16

15 Jun '16

Hello, A new question has been asked in "MariaDB FAQ" by palash.harchandani93_43595. Please answer it at http://mariadb.com/kb/en/monyog-auto-discovery-of-mariadb-databases/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Is it possible to discover all the mariadb instance running on a particular server and register them automtically in monyog..suppose i have mariadb 1 running on port 3306 and mariadb 2 on 3307 and what monyog should do is i give the ip address of the server and mariadb 1 and mariadb 2 should get confgured automatically and start monitoring. -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/monyog-auto-discovery-of-mariadb-databases/

1 0

[Maria-discuss] New Question: ST_AsGeoJSON Support
by AskMonty KB 14 Jun '16

14 Jun '16

Hello, A new question has been asked in "Geographic Features" by jerome_savin. Please answer it at http://mariadb.com/kb/en/st_asgeojson-support/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hi, Are there some plans to support ST_AsGeoJSON function ? Will ST_AsGeoJSON be available soon ? Many Thanks. -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/st_asgeojson-support/

1 0

[Maria-discuss] Odd behavior with query and connection pool
by Stu Smith 14 Jun '16

14 Jun '16

Hello, Forgive me for reporting this on the behalf of some other developers, I will gather more details as needed. But the basic problem we're having is with a query that: - is always fast the first time ( < 3 seconds ) - is very slow the following time, when using a connection pool (~ 30 seconds) - is pretty fast the following time, when not using a connection pool (5 or 6 seconds) This is even on a single DB with no other load. It's a fairly complicated query with sub queries, grouping, and such. I've been told it creates two temp tables. I know this is not a whole lot to go one - but are there any pointer for connection pool vs no connection pool on a lightly loaded DB? This was actually tried and reproduced with multiple connection pools - hikari-db, c3p0, and apache connection pool. Take care, -stu

3 2

[Maria-discuss] R: Odd behavior with query and connection pool
by Federico Razzoli 14 Jun '16

14 Jun '16

Weird issue. I'm trying to figure out how the connection pool can add an overhead to a single query. The only case I can think is if you use a network storage engine (Federated, Connect, Spider) pointing to tables on localhost. Is this the case? More likely... are you sure this problem is caused by the connection pool? * After the first execution, do a SHOW STATUS. Then FLUSH STATUS. Then execute again and, if it takes long time, do another SHOW STATUS. Post your results here, so we can see what happened. * While the query takes a long time, try a SHOW PROCESSLIST from another client. See if the connection is waiting for a lock. Regards Federico -------------------------------------------- Mar 14/6/16, Stu Smith <stu26code(a)gmail.com> ha scritto: Oggetto: [Maria-discuss] Odd behavior with query and connection pool A: maria-discuss(a)lists.launchpad.net Data: Martedì 14 giugno 2016, 03:36 Hello, Forgive me for reporting this on the behalf of some other developers, I will gather more details as needed. But the basic problem we're having is with a query that: - is always fast the first time ( < 3 seconds ) - is very slow the following time, when using a connection pool (~ 30 seconds) - is pretty fast the following time, when not using a connection pool (5 or 6 seconds) This is even on a single DB with no other load. It's a fairly complicated query with sub queries, grouping, and such. I've been told it creates two temp tables. I know this is not a whole lot to go one - but are there any pointer for connection pool vs no connection pool on a lightly loaded DB? This was actually tried and reproduced with multiple connection pools - hikari-db, c3p0, and apache connection pool. Take care, -stu -----Segue allegato----- _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss(a)lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp

1 0

[Maria-discuss] New Question: the difference
by AskMonty KB 14 Jun '16

14 Jun '16

Hello, A new question has been asked in "What is in the Different MariaDB Releases?" by hongyan_0318_54417. Please answer it at http://mariadb.com/kb/en/the-difference/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- About MariaDB I am a new boy,now I am using version 5.5.36 ,I want to upgrade version to 10.0.2 ,so the quesion is what's the question between them ,my English is poor ,give me a simply apply please ,thanks a lot . -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/the-difference/

1 0

[Maria-discuss] F5 iRules for galera
by Umarzuki Mochlis 14 Jun '16

14 Jun '16

I found a article related to monitoring galera at https://devcentral.f5.com/articles/monitoring-open-source-databases-with-bi…. but it did no into detail of iRules used for multi-master. Anyone have sample(s) to share? Mariadb 10.1 Big-IP 11

1 0

[Maria-discuss] Problems with running out of connections in cluster
by Lee Bennett 13 Jun '16

13 Jun '16

Hi We are running a 7 node cluster (6 data nodes and 1 arbiter node) which span 2 data centers using version 10.1.13. We have had several occasions where the application have gone off and created so many connections that the max connections are filled up which leads to the database becoming unresponsive. The connections cannot be killed and and in the ‘killed’ state forever. Today when this occurred all six cluster node maxed out on connections. The only way to get the servers back is by restarting the databases but when the first node we restarted it tried to connect to the cluster is to IST it could not connected. After shutdown a second node the cluster seemed to sort its self out and everything came back. Is anyone aware of any bugs that might cause this issue. Regards LB

1 0

[Maria-discuss] New Question: MariaDB Monitoring Using MONyog
by AskMonty KB 13 Jun '16

13 Jun '16

Hello, A new question has been asked in "MariaDB FAQ" by palash.harchandani93_43595. Please answer it at http://mariadb.com/kb/en/mariadb-monitoring-using-monyog/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- can we get summary of all the servers registered which are online and which are not with help of charts like in OEM?? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/mariadb-monitoring-using-monyog/

1 0

[Maria-discuss] New Question: MariaDB with Galera on RedHat 7.2 not starting
by AskMonty KB 12 Jun '16

12 Jun '16

Hello, A new question has been asked in "Starting and Stopping MariaDB" by veselin_vasilev_g. Please answer it at http://mariadb.com/kb/en/mariadb-with-galera-on-redhat-72-not-starting/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hi, can someone please help as I couldn't find relevant information online. When trying to initialize the first node of the cluster, I get this: Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Note] WSREP: wsrep_load(): loading provider library '/usr/lib64/galera/libgalera_smm.so' Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Note] WSREP: wsrep_load(): Galera 25.3.15(r3578) by Codership Oy <info(a)codership.com> loaded Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Note] WSREP: CRC-32C: using hardware acceleration. Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Note] WSREP: Found saved state: 00000000-0000-0000-0000-000000000000:-1 Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Note] WSREP: Passing config to GCS: base_dir = /var/lib/mysql/; base_host = 172.20.1.56; bas Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510378977024 [Note] WSREP: Service thread queue flushed. Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Note] WSREP: Assign initial position for certification: -1, protocol version: -1 Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Note] WSREP: wsrep_sst_grab() Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Note] WSREP: Start replication Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Note] WSREP: Setting initial position to 00000000-0000-0000-0000-000000000000:-1 Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Note] WSREP: protonet asio version 0 Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Note] WSREP: Using CRC-32C for message checksums. Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Note] WSREP: backend: asio Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Warning] WSREP: access file(/var/lib/mysql//gvwstate.dat) failed(No such file or directory) Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Note] WSREP: restore pc from disk failed Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Note] WSREP: GMCast version 0 Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Note] WSREP: (b5e7b88e, 'tcp://0.0.0.0:4567') listening at tcp://0.0.0.0:4567 Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Note] WSREP: (b5e7b88e, 'tcp://0.0.0.0:4567') multicast: , ttl: 1 Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Note] WSREP: EVS version 0 Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Note] WSREP: gcomm: connecting to group 'galera_cluster', peer '172.20.1.56:,172.20.1.57:,17 Jun 12 11:14:40 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:40 140510611449984 [Warning] WSREP: (b5e7b88e, 'tcp://0.0.0.0:4567') address 'tcp://172.20.1.56:4567' points to Jun 12 11:14:43 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:43 140510611449984 [Warning] WSREP: no nodes coming from prim view, prim not possible Jun 12 11:14:43 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:43 140510611449984 [Note] WSREP: view(view_id(NON_PRIM,b5e7b88e,1) memb { Jun 12 11:14:43 mariadb-N1.intelligene.local mysqld[10404]: b5e7b88e,0 Jun 12 11:14:43 mariadb-N1.intelligene.local mysqld[10404]: } joined { Jun 12 11:14:43 mariadb-N1.intelligene.local mysqld[10404]: } left { Jun 12 11:14:43 mariadb-N1.intelligene.local mysqld[10404]: } partitioned { Jun 12 11:14:43 mariadb-N1.intelligene.local mysqld[10404]: }) Jun 12 11:14:43 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:14:43 140510611449984 [Warning] WSREP: last inactive check more than PT1.5S ago (PT3.50184S), skipping check Jun 12 11:15:13 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:15:13 140510611449984 [Note] WSREP: view((empty)) Jun 12 11:15:13 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:15:13 140510611449984 [ERROR] WSREP: failed to open gcomm backend connection: 110: failed to reach primary view: 11 Jun 12 11:15:13 mariadb-N1.intelligene.local mysqld[10404]: at gcomm/src/pc.cpp:connect():162 Jun 12 11:15:13 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:15:13 140510611449984 [ERROR] WSREP: gcs/src/gcs_core.cpp:gcs_core_open():208: Failed to open backend connection: - Jun 12 11:15:13 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:15:13 140510611449984 [ERROR] WSREP: gcs/src/gcs.cpp:gcs_open():1379: Failed to open channel 'galera_cluster' at 'g Jun 12 11:15:13 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:15:13 140510611449984 [ERROR] WSREP: gcs connect failed: Connection timed out Jun 12 11:15:13 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:15:13 140510611449984 [ERROR] WSREP: wsrep::connect(gcomm://172.20.1.56,172.20.1.57,172.20.1.58) failed: 7 Jun 12 11:15:13 mariadb-N1.intelligene.local mysqld[10404]: 2016-06-12 11:15:13 140510611449984 [ERROR] Aborting Jun 12 11:15:14 mariadb-N1.intelligene.local systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE Jun 12 11:15:14 mariadb-N1.intelligene.local systemd[1]: Failed to start MariaDB database server. -- Subject: Unit mariadb.service has failed -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/mariadb-with-galera-on-redhat-72-not-starting/

1 0

[Maria-discuss] New Question: MariaDB Galera cluster gtid's falling out of sync inspite of setting wsrep_cluster
by AskMonty KB 11 Jun '16

11 Jun '16

Hello, A new question has been asked in "MariaDB Community" by kk1674. Please answer it at http://mariadb.com/kb/en/mariadb-galera-cluster-gtids-falling-out-of-sync-i… as the person asking the question may not be subscribed to the mailing list. -------------------------------- I have asynchronous replication between 2 clusters (calling master cluster, slave cluster). As expected a node in the slave cluster receives async replication and galera transmits to the rest of the nodes of the slave cluster. When the gtid counter is being incremented on the nodes of this slave cluster, the node acting as the slave node is keeping track of master server id and incrementing the gtid by wsrep_domain_id, server_id, galera counter+1. However the other nodes of the slave cluster are not keeping track of the server id variable and increment gtid by wsrep_domain_id, galera counter+1. See below Slave node of the slave cluster show variables like '%gtid%'; +------------------------+-------------------------+ | Variable_name | Value | +------------------------+-------------------------+ | gtid_binlog_pos | 2-100-36261 | | gtid_binlog_state | 2-200-36263,2-100-36261 | | gtid_current_pos | 1-100-36261 | | gtid_domain_id | 22 | | gtid_ignore_duplicates | OFF | | gtid_seq_no | 0 | | gtid_slave_pos | 1-100-36261 | | gtid_strict_mode | OFF | | last_gtid | 2-200-36263 | | wsrep_gtid_domain_id | 2 | | wsrep_gtid_mode | ON | +------------------------+-------------------------+ 11 rows in set (0.00 sec) Another node in the slave cluster show variables like '%gtid%'; +------------------------+-------------------------+ | Variable_name | Value | +------------------------+-------------------------+ | gtid_binlog_pos | 2-100-36265 | | gtid_binlog_state | 2-200-36264,2-100-36265 | | gtid_current_pos | 1-100-36259 | | gtid_domain_id | 22 | | gtid_ignore_duplicates | OFF | | gtid_seq_no | 0 | | gtid_slave_pos | 1-100-36259 | | gtid_strict_mode | OFF | | last_gtid | | | wsrep_gtid_domain_id | 2 | | wsrep_gtid_mode | ON | +------------------------+-------------------------+ 11 rows in set (0.00 sec) This behavior has been noted in MariaDB 10.1.11, 10.1.13 and 10.1.14. In 10.1.11, gtid_slave_pos table is being replicated by galera hence if the slave node goes down it is possible to move the slave process to another node, by first setting the gtid_slave_pos variable. However starting 10.1.13 the table is not longer being replicated I see it as a fix for another issue agreeably, but now there is no means to determine the slave position to be able to start replication on another node of the cluster. Can this behavior be classified as bug and a bug request opened? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/mariadb-galera-cluster-gtids-falling-out-of-sync-i…

1 0

[Maria-discuss] New Question: MariaDB relocatable rpm packages
by AskMonty KB 10 Jun '16

10 Jun '16

Hello, A new question has been asked in "MariaDB FAQ" by palash.harchandani93_43595. Please answer it at http://mariadb.com/kb/en/mariadb-relocatable-rpm-packages/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- I want to know if the mariadb 10.1.13 packages are relocatable or not as i want to install the rpm packages in some other directory rather than the default installation directory. -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/mariadb-relocatable-rpm-packages/

1 0

[Maria-discuss] Event types in performance schema
by Rhys.Campbell＠swisscom.com 10 Jun '16

10 Jun '16

Hi All, I'm doing some stuff with the performance_Schema and have a quick question about event types. These appear in the events_statements_summary_by_account_by_event_name table (and others) and look like... statement/com/Ping statement/sql/select statement/sql/insert statement/sql/commit statement/sql/update Am I correct in thinking the COMMIT type would be a total of all the events of a transaction. So if we did something like... START TRANSACTION SELECT EVENT UPDATE EVENT INSERT EVENT DELETE EVENT COMMIT The performance_schema would log this as EVENTS for SELECT, UPDATE, INSERT and DELETE individual times. While the COMMIT would be a sum of these times? Cheers, Rhys

2 1

[Maria-discuss] New Question: MyISAM plus INNODB enable query cache?
by AskMonty KB 09 Jun '16

09 Jun '16

Hello, A new question has been asked in "MariaDB Community" by chrismatthews. Please answer it at http://mariadb.com/kb/en/myisam-plus-innodb-enable-query-cache/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- We have 2GB of MyISAM plus 2GB INNODB data. Running MariaDB 10.* Should we enable or disable query_cache ? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/myisam-plus-innodb-enable-query-cache/

1 0

[Maria-discuss] AUTO_COMMIT=0 for a session - READ inconsistencyi - ssue or no issue
by Karthick Subramanian 09 Jun '16

09 Jun '16

Observation: If we set the AUTOCOMMIT=0 in a session, then in that session, I noticed a data inconsistency. Whatever data committed in other sessions, when we select in this session showing until we start any new transaction in this session. The moement we sstart any new transaction in this session, then its not showing any latest data for a table (data inserted by other sessions) in this session, unless we explicitly issue the commit. Usually AUTOCOMMIT=0 means any specific transactions in that session will be visible to other sessions only when we explicitly issue a COMMIT, but we can read a consistent data from that session. It doesn't seem to be working. Is this my misunderstanding on how a Transaction management works or a bug? Session 1: MariaDB [employees]> select * from tab; Empty set (0.00 sec) MariaDB [employees]> INSERT INTO tab -> (c1, c2) -> VALUES -> ('a1', 'a11'); Query OK, 1 row affected, 1 warning (0.00 sec) MariaDB [employees]> select * from tab; +------+------+ | c1 | c2 | +------+------+ | a1 | a1 | +------+------+ 1 row in set (0.00 sec) MariaDB [employees]> Session 2: MariaDB [employees]> select * from tab; +------+------+ | c1 | c2 | +------+------+ | a1 | a1 | +------+------+ 1 row in set (0.00 sec) MariaDB [employees]> INSERT INTO tab -> (c1, c2) -> VALUES -> ('a2', 'a22'); Query OK, 1 row affected, 1 warning (0.01 sec) MariaDB [employees]> select * from tab; +------+------+ | c1 | c2 | +------+------+ | a1 | a1 | | a2 | a2 | +------+------+ 2 rows in set (0.00 sec) back to Session 1: MariaDB [employees]> select * from tab; +------+------+ | c1 | c2 | +------+------+ | a1 | a1 | | a2 | a2 | +------+------+ 2 rows in set (0.00 sec) Back to session 2: MariaDB [employees]> set auto_commit=0; ERROR 1193 (HY000): Unknown system variable 'auto_commit' MariaDB [employees]> set autocommit=0; Query OK, 0 rows affected (0.00 sec) MariaDB [employees]> Move to Session 3: MariaDB [employees]> select * from tab; +------+------+ | c1 | c2 | +------+------+ | a1 | a1 | | a2 | a2 | +------+------+ 2 rows in set (0.00 sec) MariaDB [employees]> Move to session 1: MariaDB [employees]> INSERT INTO tab -> (c1, c2) -> VALUES -> ('a3', 'a33'); Query OK, 1 row affected, 1 warning (0.00 sec) MariaDB [employees]> select * from tab; +------+------+ | c1 | c2 | +------+------+ | a1 | a1 | | a2 | a2 | | a3 | a3 | +------+------+ 3 rows in set (0.01 sec) Move to session 2: MariaDB [employees]> select * from tab; +------+------+ | c1 | c2 | +------+------+ | a1 | a1 | | a2 | a2 | | a3 | a3 | +------+------+ 3 rows in set (0.00 sec) Move to Session 3: MariaDB [employees]> select * from tab; +------+------+ | c1 | c2 | +------+------+ | a1 | a1 | | a2 | a2 | | a3 | a3 | +------+------+ 3 rows in set (0.00 sec) Across all 3 sessions, the data is consistent. Move to session 1: MariaDB [employees]> INSERT INTO tab -> (c1, c2) -> VALUES -> ('a4', 'a44'); Query OK, 1 row affected, 1 warning (0.00 sec) MariaDB [employees]> select * from tab; +------+------+ | c1 | c2 | +------+------+ | a1 | a1 | | a2 | a2 | | a3 | a3 | | a4 | a4 | +------+------+ 4 rows in set (0.00 sec) Move to Session 2: MariaDB [employees]> INSERT INTO tab -> (c1, c2) -> VALUES -> ('a5', 'a55'); Query OK, 1 row affected, 1 warning (0.01 sec) MariaDB [employees]> INSERT INTO tab -> (c1, c2) -> VALUES -> ('a6', 'a66'); Query OK, 1 row affected, 1 warning (0.00 sec) MariaDB [employees]> select * from tab; +------+------+ | c1 | c2 | +------+------+ | a1 | a1 | | a2 | a2 | | a3 | a3 | | a5 | a5 | | a6 | a6 | +------+------+ 5 rows in set (0.00 sec) a4 record is missing here in session 2 - inconsistency started. move to session 3: MariaDB [employees]> select * from tab; +------+------+ | c1 | c2 | +------+------+ | a1 | a1 | | a2 | a2 | | a3 | a3 | | a4 | a4 | +------+------+ 4 rows in set (0.00 sec) In Session 3 - a5 and a6 records are mising because in session 2 - autocommit=0, so its expected that a5 and a6 are missing in session1,3. BUT, why in session 2, the a4 record is missing?

2 2

[Maria-discuss] New Question: MariaDB installation in a different directory using RPMs
by AskMonty KB 09 Jun '16

09 Jun '16

Hello, A new question has been asked in "MariaDB FAQ" by palash.harchandani93_43595. Please answer it at http://mariadb.com/kb/en/mariadb-installation-in-a-different-directory-usin… as the person asking the question may not be subscribed to the mailing list. -------------------------------- I am trying to install MariaDB using RPMs packages in a user created directory but i am not able to do it. Is it possible to do it?? i have tried --prefix option but couldnt start the mysql service and also yum --installroot option but couldnt start the service. Please suggest a way to do it if its possible -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/mariadb-installation-in-a-different-directory-usin…

1 0

[Maria-discuss] New Question: how to install ColumnStore?
by AskMonty KB 08 Jun '16

08 Jun '16

Hello, A new question has been asked in "ColumnStore" by robertsilen. Please answer it at http://mariadb.com/kb/en/how-to-install-columnstore/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- how do I install ColumnStore? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/how-to-install-columnstore/

1 0

[Maria-discuss] New Question: how add string on value of result on mysql mariadb
by AskMonty KB 07 Jun '16

07 Jun '16

Hello, A new question has been asked in "String functions" by design_buanalabel_g. Please answer it at http://mariadb.com/kb/en/how-add-string-on-value-of-result-on-mysql-mariadb/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- dear Mr. / Mrs. how add string on value of result on mysql mariadb ? Thank you Agustino Design buana -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/how-add-string-on-value-of-result-on-mysql-mariadb/

1 0

Re: [Maria-discuss] Horrendeous InnoDB crash
by Mark 07 Jun '16

07 Jun '16

No, honestly, that wasn't it. :) As per the Jira link Jan Lindström provided, the data becomes corrupted as a result of certain queries! (I didn't know why, but it was pretty repeatable: wipe the database, re-populate it again, run the scheduled script, and bam, the 'xovers' table immediately crashes). Without the fix provided in 10.1.14, I would have never been able to solve this (except maybe to revert to myisam). A big thanks again to Jan Lindström, for identifying the issue, and to everyone else willing to think along with me! :) -----Original Message----- From: Jan Steinman [mailto:Jan@EcoReality.org] Sent: Tuesday, June 7, 2016 01:05 To: Mark <asarian(a)xs4all.nl> Cc: chris(a)mariadb.com; maria-discuss(a)lists.launchpad.net Subject: Re: [Maria-discuss] Horrendeous InnoDB crash > So, with almost certainty, the scheduled task corrupts the database. No, it looks to me like the scheduled task is trying to access corrupted data — important distinction! To rule this out, dump the database, move your datadir to a safe place, run mysql_install_db, then load the dump: “mysql <dump.sql”. Then run your scheduled task again. My bet is it will work fine, then. :::: :::: Jan Steinman, EcoReality Co-op :::: > On 2016-06-06, at 08:59, Mark <asarian(a)xs4all.nl> wrote: > > The log starts just with: > > 2016-06-06 16:39:16 7716 [Note] Server socket created on IP: '::'. > 2016-06-06 16:39:16 7716 [Note] C:\xampp\mysql\bin\mysqld.exe: ready > for connections. > Version: '10.1.13-MariaDB' socket: '' port: 3306 mariadb.org binary > distribution > > No errors at startup (database prefilled with manually run retrieval > script). Then, at 16:47, when the scheduled retrieve task starts for > the first time, the log adds: > > InnoDB: Error: trying to access page number 250370 in space 69, > InnoDB: space name news/commentsxover, > InnoDB: which is outside the tablespace bounds. > InnoDB: Byte offset 0, len 16384, i/o type 10. > InnoDB: If you get this error at mysqld startup, please check that > InnoDB: your my.cnf matches the ibdata files that you have in the > InnoDB: MySQL server. > 2016-06-06 16:47:38 a74 InnoDB: Assertion failure in thread 2676 in > file fil0fil.cc line 5866 > > So, with almost certainty, the scheduled task corrupts the database. > Especially since I was now (unfortunately) able to replicate the same > conditions for the crash. But there's nothing in that php script that > could normally do that. (Especially since it runs manually just fine, > without corrupting anything). The scheduled task runs as me, but is > 'hidden', though (i.e., doesn't open a console). > > > -----Original Message----- > From: Chris Calender [mailto:chris.calender@mariadb.com] > Sent: Monday, June 6, 2016 17:44 > To: Mark <asarian(a)xs4all.nl>; maria-discuss(a)lists.launchpad.net > Subject: Re: [Maria-discuss] Horrendeous InnoDB crash > > Hello, > > No need for the config file, you have corruption in your tablespace, > hence the crash. > > It starts up here, at 16:39:16: > >> 2016-06-06 16:39:16 1e24 InnoDB: Warning: Using... >> ... >> 2016-06-06 16:39:16 7716 [Note] C:\xampp\mysql\bin\mysqld.exe: ready >> for connections. >> Version: '10.1.13-MariaDB' socket: '' port: 3306 mariadb.org >> binary > distribution > > At the exact same time, we see the corruption (thus this corruption > was both detected and mentioned at startup): > >> InnoDB: Error: trying to access page number 250370 in space 69, > > InnoDB: space name spotweb/commentsxover, > InnoDB: which is outside > the tablespace bounds. >> InnoDB: Byte offset 0, len 16384, i/o type 10. >> InnoDB: If you get this error at mysqld startup, please check that > > InnoDB: your my.cnf matches the ibdata files that you have in the > InnoDB: > MySQL server. > > Then, about 8 minutes later, you attempt to select from the same table > that is corrupted ("spotweb.commentsxover"), hence the immediate > assertion > failure: > >> 2016-06-06 16:47:38 a74 InnoDB: Assertion failure in thread 2676 in >> > > file fil0fil.cc line 5866 > > And the stack trace confirms the query: > >> Query (0x4b01740): SELECT messageid FROM commentsxover ORDER BY id >> DESC LIMIT 5000 > > Since that is the only table referenced as being corrupted, you could > probably get by with dropping it and then restoring it from a backup. > If you do not have a current backup, then you will need to enable > innodb_force_recovery (read below link for details), then dump from > the table, dumping "around" the corruption using mysqldump with ORDER > BY pk and LIMIT, and then once you have as much data as possible, then > DROP the table, and import your dump. > > http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html > > Hope this helps! > > Best wishes, > Chris > > > On 6/6/2016 11:17 AM, Mark wrote: >> And yet the same 9*&^%^&*()_ crash (see below). I'm beginning to get >> real tired of this. >> >> The corruption starts almost immediately upon running a scheduled >> task that's retrieving posts (at 16:47 hours). It's the same task I >> ran manually first. There's absolutely no reason why a simple >> scheduled post retrieval script should immediately corrupt MariaDB >> beyond all recognition. The scheduled task consists of nothing more >> than a script (that runs as me), like: >> >> c:\xampp\php\php.exe c:\xampp\htdocs\news\retrieve.php -force >> >> It runs every 30 mins. >> >> And no, no write-delays, or computer crashes that preceded this. >> >> 2016-06-06 15:52:27 3552 [Note] C:\xampp\mysql\bin\mysqld.exe: Normal >> shutdown >> >> 2016-06-06 15:52:27 3552 [Note] Event Scheduler: Purging the queue. 0 >> events >> >> 2016-06-06 15:52:27 3504 [Note] InnoDB: FTS optimize thread exiting. >> >> 2016-06-06 15:52:27 3552 [Note] InnoDB: Starting shutdown... >> >> 2016-06-06 15:52:29 3552 [Note] InnoDB: Shutdown completed; log >> sequence number 6767908697 >> >> 2016-06-06 15:52:29 3552 [Note] C:\xampp\mysql\bin\mysqld.exe: >> Shutdown complete >> >> 2016-06-06 16:39:16 1e24 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. >> >> 2016-06-06 16:39:16 7716 [Note] InnoDB: Using mutexes to ref count >> buffer pool pages >> >> 2016-06-06 16:39:16 7716 [Note] InnoDB: The InnoDB memory heap is >> disabled >> >> 2016-06-06 16:39:16 7716 [Note] InnoDB: Mutexes and rw_locks use >> Windows interlocked functions >> >> 2016-06-06 16:39:16 7716 [Note] InnoDB: Memory barrier is not used >> >> 2016-06-06 16:39:16 7716 [Note] InnoDB: Compressed tables use zlib >> 1.2.3 >> >> 2016-06-06 16:39:16 7716 [Note] InnoDB: Using generic crc32 >> instructions >> >> 2016-06-06 16:39:16 7716 [Note] InnoDB: Initializing buffer pool, >> size = 16.0M >> >> 2016-06-06 16:39:16 7716 [Note] InnoDB: Completed initialization of >> buffer pool >> >> 2016-06-06 16:39:16 7716 [Note] InnoDB: Highest supported file format >> is Barracuda. >> >> 2016-06-06 16:39:16 7716 [Note] InnoDB: 128 rollback segment(s) are > active. >> >> 2016-06-06 16:39:16 7716 [Note] InnoDB: Waiting for purge to start >> >> 2016-06-06 16:39:16 7716 [Note] InnoDB: Percona XtraDB >> (http://www.percona.com) 5.6.28-76.1 started; log sequence number >> 6767908697 >> >> 2016-06-06 16:39:16 7100 [Note] InnoDB: Dumping buffer pool(s) not >> yet started >> >> 2016-06-06 16:39:16 7716 [Note] Plugin 'FEEDBACK' is disabled. >> >> 2016-06-06 16:39:16 7716 [Note] Server socket created on IP: '::'. >> >> 2016-06-06 16:39:16 7716 [Note] C:\xampp\mysql\bin\mysqld.exe: ready >> for connections. >> >> Version: '10.1.13-MariaDB' socket: '' port: 3306 mariadb.org >> binary distribution >> >> InnoDB: Error: trying to access page number 250370 in space 69, >> >> InnoDB: space name spotweb/commentsxover, >> >> InnoDB: which is outside the tablespace bounds. >> >> InnoDB: Byte offset 0, len 16384, i/o type 10. >> >> InnoDB: If you get this error at mysqld startup, please check that >> >> InnoDB: your my.cnf matches the ibdata files that you have in the >> >> InnoDB: MySQL server. >> >> 2016-06-06 16:47:38 a74 InnoDB: Assertion failure in thread 2676 in >> file fil0fil.cc line 5866 >> >> InnoDB: We intentionally generate a memory trap. >> >> InnoDB: Submit a detailed bug report to http://bugs.mysql.com. >> >> InnoDB: If you get repeated assertion failures or crashes, even >> >> InnoDB: immediately after the mysqld startup, there may be >> >> InnoDB: corruption in the InnoDB tablespace. Please refer to >> >> InnoDB: >> http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html >> >> InnoDB: about forcing recovery. >> >> 160606 16:47:38 [ERROR] mysqld got exception 0x80000003 ; >> >> 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.1.13-MariaDB >> >> key_buffer_size=16777216 >> >> read_buffer_size=262144 >> >> max_used_connections=1 >> >> max_threads=1001 >> >> thread_count=1 >> >> It is possible that mysqld could use up to >> >> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = >> 787100 K bytes of memory >> >> Hope that's ok; if not, decrease some variables in the equation. >> >> Thread pointer: 0x0x4af7270 >> >> 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!my_parameter_handler() >> >> mysqld.exe!my_mb_ctype_mb() >> >> mysqld.exe!?get_ctx@MDL_ticket@@QBEPAVMDL_context@@XZ() >> >> mysqld.exe!?get_ctx@MDL_ticket@@QBEPAVMDL_context@@XZ() >> >> mysqld.exe!?functype@Item_func_dyncol_create@@UBE?AW4Functype@Item_fu >> n >> c@@XZ() >> >> mysqld.exe!?get_ctx@MDL_ticket@@QBEPAVMDL_context@@XZ() >> >> mysqld.exe!??0Global_read_lock@@QAE@XZ() >> >> mysqld.exe!??0Global_read_lock@@QAE@XZ() >> >> mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ() >> >> mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ() >> >> mysqld.exe!?ha_open@handler@@QAEHPAUTABLE@@PBDHI@Z() >> >> mysqld.exe!?open_table_from_share@@YA?AW4open_frm_error@@PAVTHD@@PAUT >> A >> BLE_SHARE@@PBDIIIPAUTABLE@@_N@Z() >> >> mysqld.exe!?open_table@@YA_NPAVTHD@@PAUTABLE_LIST@@PAVOpen_table_cont >> e >> xt@@@Z() >> >> mysqld.exe!?recover_from_failed_open@Open_table_context@@QAE_NXZ() >> >> mysqld.exe!?open_tables@@YA_NPAVTHD@@ABUDDL_options_st@@PAPAUTABLE_LI >> S >> T@@PAIIPAVPrelocking_strategy@@@Z() >> >> mysqld.exe!?open_and_lock_tables@@YA_NPAVTHD@@ABUDDL_options_st@@PAUT >> A >> BLE_LIST@@_NIPAVPrelocking_strategy@@@Z() >> >> mysqld.exe!??0Table_scope_and_contents_source_st@@QAE@ABU0@@Z() >> >> mysqld.exe!?mysql_execute_command@@YAHPAVTHD@@@Z() >> >> mysqld.exe!?mysql_parse@@YAXPAVTHD@@PADIPAVParser_state@@@Z() >> >> mysqld.exe!?dispatch_command@@YA_NW4enum_server_command@@PAVTHD@@PADI >> @ >> Z() >> >> mysqld.exe!?do_command@@YA_NPAVTHD@@@Z() >> >> mysqld.exe!?threadpool_process_request@@YAHPAVTHD@@@Z() >> >> mysqld.exe!?tp_end@@YAXXZ() >> >> KERNEL32.DLL!SetUserGeoID() >> >> ntdll.dll!TpSimpleTryPost() >> >> ntdll.dll!EtwNotificationRegister() >> >> KERNEL32.DLL!BaseThreadInitThunk() >> >> ntdll.dll!RtlUnicodeStringToInteger() >> >> ntdll.dll!RtlUnicodeStringToInteger() >> >> Trying to get some variables. >> >> Some pointers may be invalid and cause the dump to abort. >> >> Query (0x4b01740): SELECT messageid FROM commentsxover ORDER BY id >> DESC LIMIT 5000 >> >> Connection ID (thread ID): 2 >> >> Status: NOT_KILLED >> >> Optimizer switch: >> index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_m >> e >> rge_intersection=on,index_merge_sort_intersection=off,engine_conditio >> n >> _pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_wi >> t >> h_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists= >> o >> n,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=o >> n >> ,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,j >> o >> in_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,ta >> b le_elimination=on,extended_keys=on,exists_to_in=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. >> >> *From:*Justin Swanhart [mailto:greenlion@gmail.com] >> *Sent:* Monday, June 6, 2016 16:16 >> *To:* Mark <asarian(a)xs4all.nl> >> *Cc:* maria-discuss(a)lists.launchpad.net >> *Subject:* Re: [Maria-discuss] Horrendeous InnoDB crash >> >> Hi, >> >> Do you have write-behind caching turned on? Do you have RAID card >> without BBU? Did your computer crash? If the OS or hardware (like >> IDE HDD cache) lies about actually writing to disk, InnoDB can become >> corrupted, and this is not the fault of innodb. Be aware that if >> this is a VM, many VM lie about disk writes, a "feature" you must turn off. >> >> Sent from my iPhone >> >> >> On Jun 6, 2016, at 6:23 AM, Mark <asarian(a)xs4all.nl >> <mailto:asarian@xs4all.nl>> wrote: >> >> Sorry I wiped the database; but it got to the point where MariaDB >> immediately crashed upon startup (so the usual repair attempts were >> futile, as they all kinda assume a MariaDB server that's up and >> running). I have years of experience (FreeBSD) with myisam tables; >> but a crash like this is a first for me, really, where the entire >> database was foobarred to the point MariaDB wouldn't even start any >> more. >> >> Thanks for creating the bug report. I shall investigate myself too, >> in trying to find a way to integrate the MariaDB shutdown gracefully >> (in UNIX this is all much simpler and straightforward). >> >> -Mark >> >> *From:*Vladislav Vaintroub [mailto:vvaintroub@gmail.com] >> *Sent:* Monday, June 6, 2016 11:39 >> *To:* Mark <asarian(a)xs4all.nl <mailto:asarian@xs4all.nl>>; >> maria-discuss(a)lists.launchpad.net >> <mailto:maria-discuss@lists.launchpad.net> >> *Subject:* Re: [Maria-discuss] Horrendeous InnoDB crash >> >> Yes, it is possible that Windows does not give enough time to >> MariaDB to shut down gracefully. I just created a task for this one >> here https://jira.mariadb.org/browse/MDEV-10183. >> >> Still, Innodb should handle this situation gracefully, and recover >> on startup, so what you see is a bug. It is a pity that you wiped >> down the database, it would be useful for a bug report. >> >> On 06.06.2016 11:08, Mark wrote: >> >> Got a huge crash today, right after initializing my first >> MariaDB database (see below). Got several more errors about >> tables having crashed later on, and MariaDB wouldn't even start >> up any more (I wound up wiping the entire database). >> >> So, my question is, what could cause MariaDB to fail so >> horrendeously?! I though InnoDB was supposed to be *better* than >> myisam!? Is is because maybe Windows 10 doesn't give MariaDB >> enough time to shut down gracefully? Could it be because a >> Windows scheduler job (potentially) aborts the fetcher script >> when it's still running? (Again, I though InnoDB was supposed to >> be transaction-safe). >> >> In its current state, MariaDB is completely unusable for me. >> >> And no, I don't have hard disk errors. :) >> >> Seriously, though, I could use some major insight! >> >> Thanks. >> >> 2016-06-06 10:32:15 2552 [Note] Server socket created on IP: '::'. >> >> 2016-06-06 10:32:15 2552 [Note] C:\xampp\mysql\bin\mysqld.exe: >> ready for connections. >> >> Version: '10.1.13-MariaDB' socket: '' port: 3306 mariadb.org >> <http://mariadb.org> binary distribution >> >> InnoDB: Error: trying to access page number 251010 in space >> 69, >> >> InnoDB: space name news/commentsxover, >> >> InnoDB: which is outside the tablespace bounds. >> >> InnoDB: Byte offset 0, len 16384, i/o type 10. >> >> InnoDB: If you get this error at mysqld startup, please check >> that >> >> InnoDB: your my.cnf matches the ibdata files that you have in >> the >> >> InnoDB: MySQL server. >> >> 2016-06-06 08:47:46 e08 InnoDB: Assertion failure in thread >> 3592 in file fil0fil.cc <http://fil0fil.cc> line 5866 >> >> InnoDB: We intentionally generate a memory trap. >> >> InnoDB: Submit a detailed bug report to http://bugs.mysql.com. >> >> InnoDB: If you get repeated assertion failures or crashes, >> even >> >> InnoDB: immediately after the mysqld startup, there may be >> >> InnoDB: corruption in the InnoDB tablespace. Please refer to >> >> InnoDB: >> >> http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html >> >> InnoDB: about forcing recovery. >> >> 160606 8:47:46 [ERROR] mysqld got exception 0x80000003 ; >> >> 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. >> >> >> >> >> >> _______________________________________________ >> >> 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(a)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(a)lists.launchpad.net >> Unsubscribe : https://launchpad.net/~maria-discuss >> More help : https://help.launchpad.net/ListHelp >> > > > -- > Chris Calender, M.S., Principal Support Engineer MariaDB Corporation > > > _______________________________________________ > Mailing list: https://launchpad.net/~maria-discuss > Post to : maria-discuss(a)lists.launchpad.net > Unsubscribe : https://launchpad.net/~maria-discuss > More help : https://help.launchpad.net/ListHelp

1 0

[Maria-discuss] Horrendeous InnoDB crash
by Mark 07 Jun '16

07 Jun '16

Got a huge crash today, right after initializing my first MariaDB database (see below). Got several more errors about tables having crashed later on, and MariaDB wouldn't even start up any more (I wound up wiping the entire database). So, my question is, what could cause MariaDB to fail so horrendeously?! I though InnoDB was supposed to be *better* than myisam!? Is is because maybe Windows 10 doesn't give MariaDB enough time to shut down gracefully? Could it be because a Windows scheduler job (potentially) aborts the fetcher script when it's still running? (Again, I though InnoDB was supposed to be transaction-safe). In its current state, MariaDB is completely unusable for me. And no, I don't have hard disk errors. :) Seriously, though, I could use some major insight! Thanks. 2016-06-06 10:32:15 2552 [Note] Server socket created on IP: '::'. 2016-06-06 10:32:15 2552 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections. Version: '10.1.13-MariaDB' socket: '' port: 3306 mariadb.org binary distribution InnoDB: Error: trying to access page number 251010 in space 69, InnoDB: space name news/commentsxover, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 2016-06-06 08:47:46 e08 InnoDB: Assertion failure in thread 3592 in file fil0fil.cc line 5866 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 160606 8:47:46 [ERROR] mysqld got exception 0x80000003 ; 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.

4 12

Re: [Maria-discuss] Horrendeous InnoDB crash
by Mark 06 Jun '16

06 Jun '16

The log starts just with: 2016-06-06 16:39:16 7716 [Note] Server socket created on IP: '::'. 2016-06-06 16:39:16 7716 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections. Version: '10.1.13-MariaDB' socket: '' port: 3306 mariadb.org binary distribution No errors at startup (database prefilled with manually run retrieval script). Then, at 16:47, when the scheduled retrieve task starts for the first time, the log adds: InnoDB: Error: trying to access page number 250370 in space 69, InnoDB: space name news/commentsxover, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 2016-06-06 16:47:38 a74 InnoDB: Assertion failure in thread 2676 in file fil0fil.cc line 5866 So, with almost certainty, the scheduled task corrupts the database. Especially since I was now (unfortunately) able to replicate the same conditions for the crash. But there's nothing in that php script that could normally do that. (Especially since it runs manually just fine, without corrupting anything). The scheduled task runs as me, but is 'hidden', though (i.e., doesn't open a console). -----Original Message----- From: Chris Calender [mailto:chris.calender@mariadb.com] Sent: Monday, June 6, 2016 17:44 To: Mark <asarian(a)xs4all.nl>; maria-discuss(a)lists.launchpad.net Subject: Re: [Maria-discuss] Horrendeous InnoDB crash Hello, No need for the config file, you have corruption in your tablespace, hence the crash. It starts up here, at 16:39:16: > 2016-06-06 16:39:16 1e24 InnoDB: Warning: Using... > ... > 2016-06-06 16:39:16 7716 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for > connections. > Version: '10.1.13-MariaDB' socket: '' port: 3306 mariadb.org binary distribution At the exact same time, we see the corruption (thus this corruption was both detected and mentioned at startup): > InnoDB: Error: trying to access page number 250370 in space 69, > InnoDB: space name spotweb/commentsxover, > InnoDB: which is outside the tablespace bounds. > InnoDB: Byte offset 0, len 16384, i/o type 10. > InnoDB: If you get this error at mysqld startup, please check that > InnoDB: your my.cnf matches the ibdata files that you have in the > InnoDB: MySQL server. Then, about 8 minutes later, you attempt to select from the same table that is corrupted ("spotweb.commentsxover"), hence the immediate assertion failure: > 2016-06-06 16:47:38 a74 InnoDB: Assertion failure in thread 2676 in > file fil0fil.cc line 5866 And the stack trace confirms the query: > Query (0x4b01740): SELECT messageid FROM commentsxover ORDER BY id DESC > LIMIT 5000 Since that is the only table referenced as being corrupted, you could probably get by with dropping it and then restoring it from a backup. If you do not have a current backup, then you will need to enable innodb_force_recovery (read below link for details), then dump from the table, dumping "around" the corruption using mysqldump with ORDER BY pk and LIMIT, and then once you have as much data as possible, then DROP the table, and import your dump. http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html Hope this helps! Best wishes, Chris On 6/6/2016 11:17 AM, Mark wrote: > And yet the same 9*&^%^&*()_ crash (see below). I'm beginning to get > real tired of this. > > The corruption starts almost immediately upon running a scheduled task > that's retrieving posts (at 16:47 hours). It's the same task I ran > manually first. There's absolutely no reason why a simple scheduled > post retrieval script should immediately corrupt MariaDB beyond all > recognition. The scheduled task consists of nothing more than a script > (that runs as me), like: > > c:\xampp\php\php.exe c:\xampp\htdocs\news\retrieve.php -force > > It runs every 30 mins. > > And no, no write-delays, or computer crashes that preceded this. > > 2016-06-06 15:52:27 3552 [Note] C:\xampp\mysql\bin\mysqld.exe: Normal > shutdown > > 2016-06-06 15:52:27 3552 [Note] Event Scheduler: Purging the queue. 0 > events > > 2016-06-06 15:52:27 3504 [Note] InnoDB: FTS optimize thread exiting. > > 2016-06-06 15:52:27 3552 [Note] InnoDB: Starting shutdown... > > 2016-06-06 15:52:29 3552 [Note] InnoDB: Shutdown completed; log > sequence number 6767908697 > > 2016-06-06 15:52:29 3552 [Note] C:\xampp\mysql\bin\mysqld.exe: > Shutdown complete > > 2016-06-06 16:39:16 1e24 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. > > 2016-06-06 16:39:16 7716 [Note] InnoDB: Using mutexes to ref count > buffer pool pages > > 2016-06-06 16:39:16 7716 [Note] InnoDB: The InnoDB memory heap is > disabled > > 2016-06-06 16:39:16 7716 [Note] InnoDB: Mutexes and rw_locks use > Windows interlocked functions > > 2016-06-06 16:39:16 7716 [Note] InnoDB: Memory barrier is not used > > 2016-06-06 16:39:16 7716 [Note] InnoDB: Compressed tables use zlib > 1.2.3 > > 2016-06-06 16:39:16 7716 [Note] InnoDB: Using generic crc32 > instructions > > 2016-06-06 16:39:16 7716 [Note] InnoDB: Initializing buffer pool, size > = 16.0M > > 2016-06-06 16:39:16 7716 [Note] InnoDB: Completed initialization of > buffer pool > > 2016-06-06 16:39:16 7716 [Note] InnoDB: Highest supported file format > is Barracuda. > > 2016-06-06 16:39:16 7716 [Note] InnoDB: 128 rollback segment(s) are active. > > 2016-06-06 16:39:16 7716 [Note] InnoDB: Waiting for purge to start > > 2016-06-06 16:39:16 7716 [Note] InnoDB: Percona XtraDB > (http://www.percona.com) 5.6.28-76.1 started; log sequence number > 6767908697 > > 2016-06-06 16:39:16 7100 [Note] InnoDB: Dumping buffer pool(s) not yet > started > > 2016-06-06 16:39:16 7716 [Note] Plugin 'FEEDBACK' is disabled. > > 2016-06-06 16:39:16 7716 [Note] Server socket created on IP: '::'. > > 2016-06-06 16:39:16 7716 [Note] C:\xampp\mysql\bin\mysqld.exe: ready > for connections. > > Version: '10.1.13-MariaDB' socket: '' port: 3306 mariadb.org binary > distribution > > InnoDB: Error: trying to access page number 250370 in space 69, > > InnoDB: space name spotweb/commentsxover, > > InnoDB: which is outside the tablespace bounds. > > InnoDB: Byte offset 0, len 16384, i/o type 10. > > InnoDB: If you get this error at mysqld startup, please check that > > InnoDB: your my.cnf matches the ibdata files that you have in the > > InnoDB: MySQL server. > > 2016-06-06 16:47:38 a74 InnoDB: Assertion failure in thread 2676 in > file fil0fil.cc line 5866 > > InnoDB: We intentionally generate a memory trap. > > InnoDB: Submit a detailed bug report to http://bugs.mysql.com. > > InnoDB: If you get repeated assertion failures or crashes, even > > InnoDB: immediately after the mysqld startup, there may be > > InnoDB: corruption in the InnoDB tablespace. Please refer to > > InnoDB: > http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html > > InnoDB: about forcing recovery. > > 160606 16:47:38 [ERROR] mysqld got exception 0x80000003 ; > > 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.1.13-MariaDB > > key_buffer_size=16777216 > > read_buffer_size=262144 > > max_used_connections=1 > > max_threads=1001 > > thread_count=1 > > It is possible that mysqld could use up to > > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = > 787100 K bytes of memory > > Hope that's ok; if not, decrease some variables in the equation. > > Thread pointer: 0x0x4af7270 > > 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!my_parameter_handler() > > mysqld.exe!my_mb_ctype_mb() > > mysqld.exe!?get_ctx@MDL_ticket@@QBEPAVMDL_context@@XZ() > > mysqld.exe!?get_ctx@MDL_ticket@@QBEPAVMDL_context@@XZ() > > mysqld.exe!?functype@Item_func_dyncol_create@@UBE?AW4Functype@Item_fun > c@@XZ() > > mysqld.exe!?get_ctx@MDL_ticket@@QBEPAVMDL_context@@XZ() > > mysqld.exe!??0Global_read_lock@@QAE@XZ() > > mysqld.exe!??0Global_read_lock@@QAE@XZ() > > mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ() > > mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ() > > mysqld.exe!?ha_open@handler@@QAEHPAUTABLE@@PBDHI@Z() > > mysqld.exe!?open_table_from_share@@YA?AW4open_frm_error@@PAVTHD@@PAUTA > BLE_SHARE@@PBDIIIPAUTABLE@@_N@Z() > > mysqld.exe!?open_table@@YA_NPAVTHD@@PAUTABLE_LIST@@PAVOpen_table_conte > xt@@@Z() > > mysqld.exe!?recover_from_failed_open@Open_table_context@@QAE_NXZ() > > mysqld.exe!?open_tables@@YA_NPAVTHD@@ABUDDL_options_st@@PAPAUTABLE_LIS > T@@PAIIPAVPrelocking_strategy@@@Z() > > mysqld.exe!?open_and_lock_tables@@YA_NPAVTHD@@ABUDDL_options_st@@PAUTA > BLE_LIST@@_NIPAVPrelocking_strategy@@@Z() > > mysqld.exe!??0Table_scope_and_contents_source_st@@QAE@ABU0@@Z() > > mysqld.exe!?mysql_execute_command@@YAHPAVTHD@@@Z() > > mysqld.exe!?mysql_parse@@YAXPAVTHD@@PADIPAVParser_state@@@Z() > > mysqld.exe!?dispatch_command@@YA_NW4enum_server_command@@PAVTHD@@PADI@ > Z() > > mysqld.exe!?do_command@@YA_NPAVTHD@@@Z() > > mysqld.exe!?threadpool_process_request@@YAHPAVTHD@@@Z() > > mysqld.exe!?tp_end@@YAXXZ() > > KERNEL32.DLL!SetUserGeoID() > > ntdll.dll!TpSimpleTryPost() > > ntdll.dll!EtwNotificationRegister() > > KERNEL32.DLL!BaseThreadInitThunk() > > ntdll.dll!RtlUnicodeStringToInteger() > > ntdll.dll!RtlUnicodeStringToInteger() > > Trying to get some variables. > > Some pointers may be invalid and cause the dump to abort. > > Query (0x4b01740): SELECT messageid FROM commentsxover ORDER BY id > DESC LIMIT 5000 > > Connection ID (thread ID): 2 > > Status: NOT_KILLED > > Optimizer switch: > index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_me > rge_intersection=on,index_merge_sort_intersection=off,engine_condition > _pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_wit > h_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=o > n,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,jo > in_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,tab > le_elimination=on,extended_keys=on,exists_to_in=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. > > *From:*Justin Swanhart [mailto:greenlion@gmail.com] > *Sent:* Monday, June 6, 2016 16:16 > *To:* Mark <asarian(a)xs4all.nl> > *Cc:* maria-discuss(a)lists.launchpad.net > *Subject:* Re: [Maria-discuss] Horrendeous InnoDB crash > > Hi, > > Do you have write-behind caching turned on? Do you have RAID card > without BBU? Did your computer crash? If the OS or hardware (like > IDE HDD cache) lies about actually writing to disk, InnoDB can become > corrupted, and this is not the fault of innodb. Be aware that if this > is a VM, many VM lie about disk writes, a "feature" you must turn off. > > Sent from my iPhone > > > On Jun 6, 2016, at 6:23 AM, Mark <asarian(a)xs4all.nl > <mailto:asarian@xs4all.nl>> wrote: > > Sorry I wiped the database; but it got to the point where MariaDB > immediately crashed upon startup (so the usual repair attempts were > futile, as they all kinda assume a MariaDB server that's up and > running). I have years of experience (FreeBSD) with myisam tables; > but a crash like this is a first for me, really, where the entire > database was foobarred to the point MariaDB wouldn't even start any > more. > > Thanks for creating the bug report. I shall investigate myself too, > in trying to find a way to integrate the MariaDB shutdown gracefully > (in UNIX this is all much simpler and straightforward). > > -Mark > > *From:*Vladislav Vaintroub [mailto:vvaintroub@gmail.com] > *Sent:* Monday, June 6, 2016 11:39 > *To:* Mark <asarian(a)xs4all.nl <mailto:asarian@xs4all.nl>>; > maria-discuss(a)lists.launchpad.net > <mailto:maria-discuss@lists.launchpad.net> > *Subject:* Re: [Maria-discuss] Horrendeous InnoDB crash > > Yes, it is possible that Windows does not give enough time to > MariaDB to shut down gracefully. I just created a task for this one > here https://jira.mariadb.org/browse/MDEV-10183. > > Still, Innodb should handle this situation gracefully, and recover > on startup, so what you see is a bug. It is a pity that you wiped > down the database, it would be useful for a bug report. > > On 06.06.2016 11:08, Mark wrote: > > Got a huge crash today, right after initializing my first > MariaDB database (see below). Got several more errors about > tables having crashed later on, and MariaDB wouldn't even start > up any more (I wound up wiping the entire database). > > So, my question is, what could cause MariaDB to fail so > horrendeously?! I though InnoDB was supposed to be *better* than > myisam!? Is is because maybe Windows 10 doesn't give MariaDB > enough time to shut down gracefully? Could it be because a > Windows scheduler job (potentially) aborts the fetcher script > when it's still running? (Again, I though InnoDB was supposed to > be transaction-safe). > > In its current state, MariaDB is completely unusable for me. > > And no, I don't have hard disk errors. :) > > Seriously, though, I could use some major insight! > > Thanks. > > 2016-06-06 10:32:15 2552 [Note] Server socket created on IP: '::'. > > 2016-06-06 10:32:15 2552 [Note] C:\xampp\mysql\bin\mysqld.exe: > ready for connections. > > Version: '10.1.13-MariaDB' socket: '' port: 3306 mariadb.org > <http://mariadb.org> binary distribution > > InnoDB: Error: trying to access page number 251010 in space > 69, > > InnoDB: space name news/commentsxover, > > InnoDB: which is outside the tablespace bounds. > > InnoDB: Byte offset 0, len 16384, i/o type 10. > > InnoDB: If you get this error at mysqld startup, please check > that > > InnoDB: your my.cnf matches the ibdata files that you have in > the > > InnoDB: MySQL server. > > 2016-06-06 08:47:46 e08 InnoDB: Assertion failure in thread > 3592 in file fil0fil.cc <http://fil0fil.cc> line 5866 > > InnoDB: We intentionally generate a memory trap. > > InnoDB: Submit a detailed bug report to http://bugs.mysql.com. > > InnoDB: If you get repeated assertion failures or crashes, > even > > InnoDB: immediately after the mysqld startup, there may be > > InnoDB: corruption in the InnoDB tablespace. Please refer to > > InnoDB: > > http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html > > InnoDB: about forcing recovery. > > 160606 8:47:46 [ERROR] mysqld got exception 0x80000003 ; > > 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. > > > > > > _______________________________________________ > > 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(a)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(a)lists.launchpad.net > Unsubscribe : https://launchpad.net/~maria-discuss > More help : https://help.launchpad.net/ListHelp > -- Chris Calender, M.S., Principal Support Engineer MariaDB Corporation

1 0

Re: [Maria-discuss] Horrendeous InnoDB crash
by Federico Razzoli 06 Jun '16

06 Jun '16

InnoDB is different from MyISAM. It crashed intentionally, as stated in the log you posted, to avoid data corruption propagation. Take a look at this page, so next time you can try to repair tables: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html Regards, Federico -------------------------------------------- Lun 6/6/16, Mark <asarian(a)xs4all.nl> ha scritto: Oggetto: Re: [Maria-discuss] Horrendeous InnoDB crash A: maria-discuss(a)lists.launchpad.net Data: Lunedì 6 giugno 2016, 12:23 #yiv2481875527 #yiv2481875527 -- _filtered #yiv2481875527 {font-family:Wingdings;panose-1:5 0 0 0 0 0 0 0 0 0;} _filtered #yiv2481875527 {panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv2481875527 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv2481875527 {font-family:Consolas;panose-1:2 11 6 9 2 2 4 3 2 4;} #yiv2481875527 #yiv2481875527 p.yiv2481875527MsoNormal, #yiv2481875527 li.yiv2481875527MsoNormal, #yiv2481875527 div.yiv2481875527MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:11.0pt;color:black;} #yiv2481875527 a:link, #yiv2481875527 span.yiv2481875527MsoHyperlink {color:#0563C1;text-decoration:underline;} #yiv2481875527 a:visited, #yiv2481875527 span.yiv2481875527MsoHyperlinkFollowed {color:#954F72;text-decoration:underline;} #yiv2481875527 p {margin-right:0in;margin-left:0in;font-size:11.0pt;color:black;} #yiv2481875527 pre {margin:0in;margin-bottom:.0001pt;font-size:10.0pt;color:black;} #yiv2481875527 p.yiv2481875527MsoListParagraph, #yiv2481875527 li.yiv2481875527MsoListParagraph, #yiv2481875527 div.yiv2481875527MsoListParagraph {margin-top:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;font-size:11.0pt;color:black;} #yiv2481875527 p.yiv2481875527msonormal0, #yiv2481875527 li.yiv2481875527msonormal0, #yiv2481875527 div.yiv2481875527msonormal0 {margin-right:0in;margin-left:0in;font-size:12.0pt;color:black;} #yiv2481875527 span.yiv2481875527EmailStyle19 {color:windowtext;} #yiv2481875527 span.yiv2481875527HTMLPreformattedChar {color:black;} #yiv2481875527 span.yiv2481875527EmailStyle22 {color:windowtext;} #yiv2481875527 .yiv2481875527MsoChpDefault {font-size:10.0pt;} _filtered #yiv2481875527 {margin:1.0in 1.0in 1.0in 1.0in;} #yiv2481875527 div.yiv2481875527WordSection1 {} #yiv2481875527 _filtered #yiv2481875527 {} _filtered #yiv2481875527 {} _filtered #yiv2481875527 {} _filtered #yiv2481875527 {font-family:Wingdings;} _filtered #yiv2481875527 {font-family:Symbol;} _filtered #yiv2481875527 {} _filtered #yiv2481875527 {font-family:Wingdings;} _filtered #yiv2481875527 {font-family:Symbol;} _filtered #yiv2481875527 {} _filtered #yiv2481875527 {font-family:Wingdings;} #yiv2481875527 ol {margin-bottom:0in;} #yiv2481875527 ul {margin-bottom:0in;} #yiv2481875527 Sorry I wiped the database; but it got to the point where MariaDB immediately crashed upon startup (so the usual repair attempts were futile, as they all kinda assume a MariaDB server that’s up and running). I have years of experience (FreeBSD) with myisam tables; but a crash like this is a first for me, really, where the entire database was foobarred to the point MariaDB wouldn’t even start any more. Thanks for creating the bug report. I shall investigate myself too, in trying to find a way to integrate the MariaDB shutdown gracefully (in UNIX this is all much simpler and straightforward). - Mark From: Vladislav Vaintroub [mailto:vvaintroub@gmail.com] Sent: Monday, June 6, 2016 11:39 To: Mark <asarian(a)xs4all.nl>; maria-discuss(a)lists.launchpad.net Subject: Re: [Maria-discuss] Horrendeous InnoDB crash Yes, it is possible that Windows does not give enough time to MariaDB to shut down gracefully. I just created a task for this one here https://jira.mariadb.org/browse/MDEV-10183.Still, Innodb should handle this situation gracefully, and recover on startup, so what you see is a bug. It is a pity that you wiped down the database, it would be useful for a bug report. On 06.06.2016 11:08, Mark wrote:Got a huge crash today, right after initializing my first MariaDB database (see below). Got several more errors about tables having crashed later on, and MariaDB wouldn't even start up any more (I wound up wiping the entire database). So, my question is, what could cause MariaDB to fail so horrendeously?! I though InnoDB was supposed to be *better* than myisam!? Is is because maybe Windows 10 doesn't give MariaDB enough time to shut down gracefully? Could it be because a Windows scheduler job (potentially) aborts the fetcher script when it's still running? (Again, I though InnoDB was supposed to be transaction-safe). In its current state, MariaDB is completely unusable for me. And no, I don't have hard disk errors. :) Seriously, though, I could use some major insight! Thanks. 2016-06-06 10:32:15 2552 [Note] Server socket created on IP: '::'.2016-06-06 10:32:15 2552 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.Version: '10.1.13-MariaDB' socket: '' port: 3306 mariadb.org binary distributionInnoDB: Error: trying to access page number 251010 in space 69,InnoDB: space name news/commentsxover,InnoDB: which is outside the tablespace bounds.InnoDB: Byte offset 0, len 16384, i/o type 10.InnoDB: If you get this error at mysqld startup, please check thatInnoDB: your my.cnf matches the ibdata files that you have in theInnoDB: MySQL server.2016-06-06 08:47:46 e08 InnoDB: Assertion failure in thread 3592 in file fil0fil.cc line 5866InnoDB: We intentionally generate a memory trap.InnoDB: Submit a detailed bug report to http://bugs.mysql.com.InnoDB: If you get repeated assertion failures or crashes, evenInnoDB: immediately after the mysqld startup, there may beInnoDB: corruption in the InnoDB tablespace. Please refer toInnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.htmlInnoDB: about forcing recovery.160606 8:47:46 [ERROR] mysqld got exception 0x80000003 ;This could be because you hit a bug. It is also possible that this binaryor one of the libraries it was linked against is corrupt, improperly built,or misconfigured. This error can also be caused by malfunctioning hardware. _______________________________________________Mailing list: https://launchpad.net/~maria-discussPost to : maria-discuss(a)lists.launchpad.netUnsubscribe : https://launchpad.net/~maria-discussMore help : https://help.launchpad.net/ListHelp -----Segue allegato----- _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss(a)lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp

1 0

[Maria-discuss] Galera Cluster on FreeBSD
by Niklaas Baudet von Gersdorff 03 Jun '16

03 Jun '16

Hello, I'm trying to setup a galera cluster on FreeBSD. I followed the instructions on [1] but every time I issue SHOW STATUS LIKE 'wsrep_cluster_size'; I get +--------------------+-------+ | Variable_name | Value | +--------------------+-------+ | wsrep_cluster_size | 0 | +--------------------+-------+ 1 row in set (0.00 sec) So, the cluster is not working. This is the configuration of the node that I want to set as primary: -----------------------------------8<----------------------------------- [mysqld] datadir=/var/db/mysql socket=/tmp/mysql.sock user=mysql binlog_format=ROW bind-address=0.0.0.0 default_storage_engine=innodb innodb_autoinc_lock_mode=2 innodb_flush_log_at_trx_commit=0 innodb_buffer_pool_size=122M wsrep_provider=/usr/local/lib/libgalera_smm.so wsrep_provider_options="gcache.size=300M; gcache.page_size=300M" wsrep_cluster_name="klaas_cluster" wsrep_cluster_address="gcomm://" #wsrep_cluster_address="gcomm://10.1.7.1,10.1.7.2,10.3.7.1" wsrep_sst_method=rsync [mysql] wsrep_cluster_name=klaas_cluster wsrep_cluster_address="gcomm://10.1.7.1,10.1.7.2,10.3.7.1" wsrep_node_name=box-hlm-01 wsrep_node_address="10.1.7.1" [mysql_safe] log-error=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid ----------------------------------->8----------------------------------- On the other two nodes the configuration is the same, except (1) only the second `wsrep_cluster_address` exists; (2) `wsrep_node_address` differs, obviously. Instead of using an "empty" `wsrep_cluster_address` I also tried setting mysql_args="--wsrep-new-cluster" in /etc/rc.conf without getting the desired result. The logs lack any relevant warnings or errors: -----------------------------------8<----------------------------------- 160602 07:59:44 mysqld_safe mysqld from pid file /var/db/mysql/mariadb1.box-hlm-01.klaas.pid ended 160602 08:00:34 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql 2016-06-02 8:00:34 34426872832 [Note] /usr/local/libexec/mysqld (mysqld 10.1.13-MariaDB) starting as process 22580 ... 2016-06-02 8:00:34 34426872832 [Warning] You need to use --log-bin to make --binlog-format work. 2016-06-02 8:00:34 34426872832 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2016-06-02 8:00:34 34426872832 [Note] InnoDB: The InnoDB memory heap is disabled 2016-06-02 8:00:34 34426872832 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2016-06-02 8:00:34 34426872832 [Note] InnoDB: Memory barrier is not used 2016-06-02 8:00:34 34426872832 [Note] InnoDB: Compressed tables use zlib 1.2.8 2016-06-02 8:00:34 34426872832 [Note] InnoDB: Using SSE crc32 instructions 2016-06-02 8:00:34 34426872832 [Note] InnoDB: Initializing buffer pool, size = 122.0M 2016-06-02 8:00:34 34426872832 [Note] InnoDB: Completed initialization of buffer pool 2016-06-02 8:00:34 34426872832 [Note] InnoDB: Highest supported file format is Barracuda. 2016-06-02 8:00:34 34426872832 [Note] InnoDB: 128 rollback segment(s) are active. 2016-06-02 8:00:34 34426872832 [Note] InnoDB: Waiting for purge to start 2016-06-02 8:00:34 34426872832 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.28-76.1 started; log sequence number 1616955 2016-06-02 8:00:34 34426872832 [Note] Plugin 'FEEDBACK' is disabled. 2016-06-02 8:00:34 34426899456 [Note] InnoDB: Dumping buffer pool(s) not yet started 2016-06-02 8:00:34 34426872832 [Note] Server socket created on IP: '0.0.0.0'. 2016-06-02 8:00:34 34426872832 [Note] /usr/local/libexec/mysqld: ready for connections. Version: '10.1.13-MariaDB' socket: '/tmp/mysql.sock' port: 3306 FreeBSD Ports ----------------------------------->8----------------------------------- Any help is very much appreciated. Niklaas 1: http://galeracluster.com/documentation-webpages/index.html

3 6