- discuss - lists.mariadb.org

[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

[Maria-discuss] New Question: Consistently able to crash MariaDB 10.0.25 and 10.1.4 - Signal 11
by AskMonty KB 02 Jun '16

02 Jun '16

Hello, A new question has been asked in "MariaDB Community" by gaurav_sharma_g1. Please answer it at http://mariadb.com/kb/en/consistently-able-to-crash-mariadb-10025-and-1014-… as the person asking the question may not be subscribed to the mailing list. -------------------------------- We are able to consistently reproduce the crash of MariaDB with the following query: {{{ drop procedure if exists sp_getServerAndAgentHeartbeats; DELIMITER $$ CREATE PROCEDURE sp_getServerAndAgentHeartbeats() begin select allof.* from (select bothof.Name fullname, bothof.instanceid name, bothof.DMSUrl id, bothof.ts heartbeat, bothof.tz, bothof.local_time, bothof.pdfagentsetup, bothof.origin, bothof.dmsid, bothof.DealerID dealerid, bothof.server_group, bothof.hasNotes from ( select d.Name, dlrurl.DealerID, DMSUrl, DMSSuff, psh.* , (select OptionValue from DealerSetupOption where DealerID = d.ID and OptionKey = 'Dealer.timezone.id') tz , (select timestampadd(minute, (480 + OptionValue), current_timestamp()) from DealerSetupOption where DealerID = d.ID and OptionKey = 'Dealer.timezone' ) local_time , (select OptionValue from DealerSetupOption where DealerID = d.ID and OptionKey = 'pdfserver.settings') pdfagentsetup , "server" origin , (select DMSID from DealerDMS where DealerID = d.ID) dmsid , (select guid from dms_staging_db.server_groups sg where sg.ip = DMSUrl and find_in_set(DMSSuff, sg.suffix) > 0 limit 1) server_group , IF((select count(*) from dms_staging_db.server_notes sn where sn.uuid = server_group) >= 1,'true','false') hasNotes from (select DealerID, OptionValue as DMSUrl from DealerSetupOption dso1 where OptionKey = 'Dealer.Pdf.Source.Url') dlrurl inner join (select DealerID, OptionValue as DMSSuff from DealerSetupOption dso1 where OptionKey = 'ADP.SessionSuffix') dlrsuff on dlrsuff.DealerID = dlrurl.DealerID inner join Dealer d on dlrurl.DealerID = d.ID inner join PdfServerHeartbeat psh on psh.dealerurl = DMSUrl and psh.instanceid = concat_ws('', '_', DMSSuff) where coalesce(DMSUrl, '') !='' and coalesce(DMSSuff, '') !='' ) bothof union ( select d.Name fullname , aih.DealerIdentifier name , aih.DealerMarker id , aih.lastgotdata heartbeat , (select OptionValue from DealerSetupOption where DealerID = d.ID and OptionKey = 'Dealer.timezone.id') tz , (select timestampadd(minute, (480 + OptionValue), current_timestamp()) from DealerSetupOption where DealerID = d.ID and OptionKey = 'Dealer.timezone' ) local_time , (select OptionValue from DealerSetupOption where DealerID = d.ID and OptionKey = 'pdfserver.settings') pdfagentsetup , "agent" origin , (select DMSID from DealerDMS where DealerID = d.ID) dmsid , d.ID DealerID , (select guid from dms_staging_db.server_groups sg where sg.ip = aih.DealerMarker and find_in_set(aih.DealerIdentifier, sg.suffix) > 0 limit 1) server_group , IF((select count(*) from dms_staging_db.server_notes sn where sn.uuid = server_group) >= 1,'true','false') hasNotes from (select DealerMarker, DealerIdentifier, count(1) pcount, max(ts) lastgotdata from AgentInstanceHeartbeat where Instance != 'pdf_server' group by DealerMarker, DealerIdentifier ) aih inner join ( select dlrurl.DealerID, DMSUrl, DMSSuff from (select DealerID, OptionValue as DMSUrl from DealerSetupOption dso1 where OptionKey = 'Dealer.Pdf.Source.Url') dlrurl inner join (select DealerID, OptionValue as DMSSuff from DealerSetupOption dso1 where OptionKey = 'ADP.SessionSuffix') dlrsuff on dlrsuff.DealerID = dlrurl.DealerID where coalesce(DMSUrl, '') !='' and coalesce(DMSSuff, '') !='' ) dsodata on (aih.DealerMarker = dsodata.DMSUrl and aih.DealerIdentifier = dsodata.DMSSuff) inner join Dealer d on (dsodata.DealerID = d.ID) where d.isValid = 1 ) order by 1 asc) allof; end$$ }}} **Our developer wrote this query as a modification to an existing query and upon executing the above SP, we consistently see the following stack trace in the MariaDB logs:** {{{ Thread pointer: 0x0x7f301afa0008 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 = 0x7f2fdce88140 thread_stack 0x48400 /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f48c34c197b] /usr/sbin/mysqld(handle_fatal_signal+0x475)[0x7f48c3020825] /lib64/libpthread.so.0(+0xf7e0)[0x7f48c26267e0] /usr/sbin/mysqld(_ZN17Dependency_marker11visit_fieldEP10Item_field+0x4b)[0x7f48c304765b] /usr/sbin/mysqld(_ZN10Item_field30enumerate_field_refs_processorEPh+0x12)[0x7f48c302d612] mysys/stacktrace.c:247(my_print_stacktrace)[0x7f48c3043c43] sql/signal_handler.cc:160(handle_fatal_signal)[0x7f48c30a2690] sql/item.cc:6707(Dependency_marker::visit_field(Item_field*))[0x7f48c303ddc4] sql/item_subselect.cc:329(Item_subselect::enumerate_field_refs_processor(unsigned char*))[0x7f48c303ef5e] sql/item.cc:5054(Item_field::fix_fields(THD*, Item**))[0x7f48c3040098] /usr/sbin/mysqld(_ZN9Item_func10fix_fieldsEP3THDPP4Item+0x1a7)[0x7f48c30732a7] sql/item_func.cc:208(Item_func::fix_fields(THD*, Item**))[0x7f48c2e713cb] sql/sql_base.cc:8629(setup_conds(THD*, TABLE_LIST*, List<TABLE_LIST>&, Item**))[0x7f48c2ef5160] sql/sql_select.cc:646(setup_without_group)[0x7f48c30a5b44] sql/item_subselect.cc:259(Item_subselect::fix_fields(THD*, Item**))[0x7f48c30a9a0d] sql/item_func.cc:208(Item_func::fix_fields(THD*, Item**))[0x7f48c30732a7] sql/item_func.cc:208(Item_func::fix_fields(THD*, Item**))[0x7f48c30732a7] sql/sql_base.cc:7901(setup_fields(THD*, Item**, List<Item>&, enum_mark_columns, List<Item>*, bool))[0x7f48c2e70c13] sql/sql_select.cc:791(JOIN::prepare(Item***, TABLE_LIST*, unsigned int, Item*, unsigned int, st_order*, bool, st_order*, Item*, st_order*, st_select_lex*, st_select_lex_unit*))[0x7f48c2ef50a2] sql/sql_union.cc:454(st_select_lex_unit::prepare(THD*, select_result*, unsigned long))[0x7f48c2f400ec] sql/sql_derived.cc:671(mysql_derived_prepare(THD*, LEX*, TABLE_LIST*))[0x7f48c2e8e570] sql/sql_derived.cc:195(mysql_handle_single_derived(LEX*, TABLE_LIST*, unsigned int))[0x7f48c2e8f327] sql/sql_lex.cc:3820(st_select_lex::handle_derived(LEX*, unsigned int))[0x7f48c2ea46b7] sql/table.cc:7126(TABLE_LIST::handle_derived(LEX*, unsigned int))[0x7f48c2f55767] sql/sql_lex.cc:3820(st_select_lex::handle_derived(LEX*, unsigned int))[0x7f48c2ea46b7] sql/sql_select.cc:711(JOIN::prepare(Item***, TABLE_LIST*, unsigned int, Item*, unsigned int, st_order*, bool, st_order*, Item*, st_order*, st_select_lex*, st_select_lex_unit*))[0x7f48c2ef4e31] sql/sql_select.cc:3429(mysql_select(THD*, Item***, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*))[0x7f48c2f01aed] sql/sql_select.cc:384(handle_select(THD*, LEX*, select_result*, unsigned long))[0x7f48c2f04bfd] /usr/sbin/mysqld(+0x451102)[0x7f48c2ea7102] sql/sql_parse.cc:5895(execute_sqlcom_select)[0x7f48c2eb33bf] sql/sp_head.cc:3215(sp_instr_stmt::exec_core(THD*, unsigned int*))[0x7f48c311c9be] sql/sp_head.cc:2979(sp_lex_keeper::reset_lex_and_exec_core(THD*, unsigned int*, bool, sp_instr*))[0x7f48c312243e] sql/sp_head.cc:3129(sp_instr_stmt::execute(THD*, unsigned int*))[0x7f48c312293d] sql/sp_head.cc:1319(sp_head::execute(THD*, bool))[0x7f48c311f91c] sql/sp_head.cc:2104(sp_head::execute_procedure(THD*, List<Item>*))[0x7f48c3120cc6] sql/sql_parse.cc:2405(do_execute_sp)[0x7f48c2eb3b30] sql/sp_head.cc:3215(sp_instr_stmt::exec_core(THD*, unsigned int*))[0x7f48c311c9be] sql/sp_head.cc:2979(sp_lex_keeper::reset_lex_and_exec_core(THD*, unsigned int*, bool, sp_instr*))[0x7f48c312243e] sql/sp_head.cc:3129(sp_instr_stmt::execute(THD*, unsigned int*))[0x7f48c312293d] sql/sp_head.cc:1319(sp_head::execute(THD*, bool))[0x7f48c311f91c] sql/sp_head.cc:2104(sp_head::execute_procedure(THD*, List<Item>*))[0x7f48c3120cc6] sql/sql_parse.cc:2405(do_execute_sp)[0x7f48c2eb3b30] sql/sql_parse.cc:7314(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x7f48c2eb68fd] sql/sql_parse.cc:1486(dispatch_command(enum_server_command, THD*, char*, unsigned int))[0x7f48c2eb955b] sql/sql_parse.cc:1109(do_command(THD*))[0x7f48c2eb9b0b] sql/sql_connect.cc:1350(do_handle_one_connection(THD*))[0x7f48c2f7569f] sql/sql_connect.cc:1264(handle_one_connection)[0x7f48c2f757f7] /lib64/libpthread.so.0(+0x7aa1)[0x7f48c261eaa1] /lib64/libc.so.6(clone+0x6d)[0x7f48c0b03aad] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7f302e2a8020): is an invalid pointer Connection ID (thread ID): 264 Status: NOT_KILLED }}} After this MariaDB crashes and restarts. **For now we have reverted the changes back to the old code which is shown below:** {{{ drop procedure if exists sp_getServerAndAgentHeartbeats; DELIMITER $$ CREATE PROCEDURE sp_getServerAndAgentHeartbeats() begin select allof.*, IF((select count(*) from dms_staging_db.server_notes sn where sn.uuid = concat(allof.dealerid,'-notes')) >= 1,'true','false') hasNotes from (select bothof.Name fullname, bothof.instanceid name, bothof.DMSUrl id, bothof.ts heartbeat, bothof.tz, bothof.local_time, bothof.pdfagentsetup, bothof.origin, bothof.dmsid, bothof.DealerID dealerid from ( ( select d.Name, dlrurl.DealerID, DMSUrl, DMSSuff, psh.* , (select OptionValue from DealerSetupOption where DealerID = d.ID and OptionKey = 'Dealer.timezone.id') tz , (select timestampadd(minute, (480 + OptionValue), current_timestamp()) from DealerSetupOption where DealerID = d.ID and OptionKey = 'Dealer.timezone' ) local_time , (select OptionValue from DealerSetupOption where DealerID = d.ID and OptionKey = 'pdfserver.settings') pdfagentsetup , "server" origin , (select DMSID from DealerDMS where DealerID = d.ID) dmsid from (select DealerID, OptionValue as DMSUrl from DealerSetupOption dso1 where OptionKey = 'Dealer.Pdf.Source.Url') dlrurl inner join (select DealerID, OptionValue as DMSSuff from DealerSetupOption dso1 where OptionKey = 'ADP.SessionSuffix') dlrsuff on dlrsuff.DealerID = dlrurl.DealerID inner join Dealer d on dlrurl.DealerID = d.ID inner join PdfServerHeartbeat psh on psh.dealerurl = DMSUrl and psh.instanceid = concat_ws('', '_', DMSSuff) where coalesce(DMSUrl, '') !='' and coalesce(DMSSuff, '') !='' ) union ( select d.Name, data.* , (select OptionValue from DealerSetupOption where DealerID = d.ID and OptionKey = 'Dealer.timezone.id') tz , (select timestampadd(minute, (480 + OptionValue), current_timestamp()) from DealerSetupOption where DealerID = d.ID and OptionKey = 'Dealer.timezone' ) local_time , (select OptionValue from DealerSetupOption where DealerID = d.ID and OptionKey = 'pdfserver.settings') pdfagentsetup , "server" origin , (select DMSID from DealerDMS where DealerID = d.ID) dmsid from ( select replace(dealerurl, 'dealer-', '') DealerID, dealerurl DMSUrl, null DMSSuff, psh1.* from PdfServerHeartbeat psh1 where dealerurl like 'dealer-%' ) data inner join Dealer d on data.DealerID = d.ID ) ) bothof union ( select d.Name fullname , aih.DealerIdentifier name , aih.DealerMarker id , aih.lastgotdata heartbeat , (select OptionValue from DealerSetupOption where DealerID = d.ID and OptionKey = 'Dealer.timezone.id') tz , (select timestampadd(minute, (480 + OptionValue), current_timestamp()) from DealerSetupOption where DealerID = d.ID and OptionKey = 'Dealer.timezone' ) local_time , (select OptionValue from DealerSetupOption where DealerID = d.ID and OptionKey = 'pdfserver.settings') pdfagentsetup , "agent" origin , (select DMSID from DealerDMS where DealerID = d.ID) dmsid , d.ID DealerID from (select DealerMarker, DealerIdentifier, count(1) pcount, max(ts) lastgotdata from AgentInstanceHeartbeat where Instance != 'pdf_server' group by DealerMarker, DealerIdentifier ) aih inner join ( select dlrurl.DealerID, DMSUrl, DMSSuff from (select DealerID, OptionValue as DMSUrl from DealerSetupOption dso1 where OptionKey = 'Dealer.Pdf.Source.Url') dlrurl inner join (select DealerID, OptionValue as DMSSuff from DealerSetupOption dso1 where OptionKey = 'ADP.SessionSuffix') dlrsuff on dlrsuff.DealerID = dlrurl.DealerID where coalesce(DMSUrl, '') !='' and coalesce(DMSSuff, '') !='' ) dsodata on (aih.DealerMarker = dsodata.DMSUrl and aih.DealerIdentifier = dsodata.DMSSuff) inner join Dealer d on (dsodata.DealerID = d.ID) where d.isValid = 1 ) order by 1 asc) allof; end$$ }}} -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/consistently-able-to-crash-mariadb-10025-and-1014-…

1 0

[Maria-discuss] Fwd: Undelivered Mail Returned to Sender
by Reindl Harald 01 Jun '16

01 Jun '16

what is that for a bullshit? MariaDB newsletters not use proper mail-headers to not trigger autoresponders? in 2016? seriously? with a invalid sender? seriously? in 2016? -------- Weitergeleitete Nachricht -------- Betreff: Undelivered Mail Returned to Sender Datum: Wed, 1 Jun 2016 19:53:55 +0200 (CEST) Von: Mail Delivery System <postmaster(a)thelounge.net> An: h.reindl(a)thelounge.net This is the mail system at host mail.thelounge.net I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below For assistance, forward this report to <postmaster(a)thelounge.net> You can delete your own text from the attached returned message <no-reply(a)mariaDB.com>: host aspmx.l.google.com[173.194.65.27] said: 550-5.1.1 The email account that you tried to reach does not exist. Please try 550-5.1.1 double-checking the recipient's email address for typos or 550-5.1.1 unnecessary spaces. Learn more at 550 5.1.1 https://support.google.com/mail/answer/6596 d83si44788327wmf.53 - gsmtp (in reply to RCPT TO command)

1 0

[Maria-discuss] Backing up tables with data at rest encryption
by Lee Bennett 01 Jun '16

01 Jun '16

Hi We are in the process of setting up data at rest encryption encryption with MariaDB 10.1.13 so we can encrypt specific table. This works without any problem however when I try and backup with Percona Xtrabackup it fails saying table appears to be corrupted: 60601 14:53:46 [01] ...done 160601 14:53:46 [01] Streaming ./mytest/customers_big.ibd [01] xtrabackup: Database page corruption detected at page 1, retrying... [01] xtrabackup: Database page corruption detected at page 1, retrying... 160601 14:53:46 >> log scanned up to (3146117051) [01] xtrabackup: Database page corruption detected at page 1, retrying... [01] xtrabackup: Database page corruption detected at page 1, retrying... [01] xtrabackup: Database page corruption detected at page 1, retrying... [01] xtrabackup: Database page corruption detected at page 1, retrying... [01] xtrabackup: Database page corruption detected at page 1, retrying... [01] xtrabackup: Database page corruption detected at page 1, retrying... [01] xtrabackup: Database page corruption detected at page 1, retrying... [01] xtrabackup: Error: failed to read page after 10 retries. File ./mytest/customers_big.ibd seems to be corrupted. [01] xtrabackup: Error: xtrabackup_copy_datafile() failed. [01] xtrabackup: Error: failed to copy datafile. This says to me that Xtrabackup isn’t compatible with MariaDB encryption however the documents kind of give the impression it is: https://mariadb.com/kb/en/mariadb/data-at-rest-encryption/ <https://mariadb.com/kb/en/mariadb/data-at-rest-encryption/> Regards Lee

3 3

[Maria-discuss] Long email about a replication issue
by Rhys.Campbell＠swisscom.com 01 Jun '16

01 Jun '16

Hi All, This weekend I had to repair a replication problem on one of our clusters. I've attempted to get to the root cause but not sure where I can go from here. Replication broke on Friday night because of foreign key errors. I initially retrieved the correct row, restarted replication, which then broke again due to a different tables FK error. I fixed this and then started replication again. All was well for an hour and then it broke again with a similar issue. We called it a night and decided to address on Saturday AM as there was no immediate production impact. The next day I discovered that records were missing from a bunch of tables so I recovered the cluster using a backup. I initially recovered the slaves attached to M2 from a backup but using the binlogs from M2. This caused the slaves to break. So instead I then recovered from the binlog on M1, before pointing them back to M2. This worked fine and everything in the cluster is currently well. Clearly something is wrong with the binlogs of M2. This is the first time I have seen this issue on the cluster that has been running fine for the last year. There have been no recent changes in the version of MariaDB or the applications using the cluster. We are running version 10.0.23-MariaDB-log. We are running replication with GTIDs, semi-sync repl between masters, and we run regular pt-table-checksum jobs. slave_sql_verify_checksum is on but master_sql_verify_checksum is off. The setup is M1<->M2 (with attached slaves). M1 is the active master receiving all writes. Access is controlled through an F5 and I don't think any errant transactions have occurred on the inactive master (M2). I've checked this by grepping the binlogs for the M2 server_id. The initial associated record that broke replication was attached to a "user" table record. This user was created on Friday at 16:21PM. Replication broke around 11:30PM that night. The user record had a GTID of GTID 0-1-36823254 (recovered from M1) I've looked into the appropriate binlog from M2... The head mysqlbinlog mysql-bin.002133 | grep GTID | head #160521 5:02:32 server id 1 end_log_pos 392 CRC32 0x97a118a8 GTID 0-1-36613622 #160521 5:02:32 server id 1 end_log_pos 768 CRC32 0x1859f6fb GTID 0-1-36613623 The tail... mysqlbinlog mysql-bin.002133 | grep GTID | tail #160528 11:58:04 server id 1 end_log_pos 103889368 CRC32 0x66e7c623 GTID 0-1-36851211 #160528 11:58:04 server id 1 end_log_pos 103971892 CRC32 0xe55c4842 GTID 0-1-36851212 If I grep for the specific GTID on M2 I get nothing... mysqlbinlog mysql-bin.002133 | grep "GTID 0-1-36823254"; <- Note the GTID is between the head & tail range. If I grep for this record by email address I also get nothing. So I must conclude this record (and a bunch of others), never got to master 2. We have pretty extensive monitoring of these servers and we should have been alerted to replication lag, locking etc but we got nothing until replication broke due to the FK errors. You would expect replication to break here because of a gap in the GTIDs. This did not happen and I'm almost certain that GTID replication could not have been deactivated and the positions messed around with. I'm unsure of where to go now. Any ideas? Any thoughts are appreciated. Regards, Rhys

2 2

[Maria-discuss] MariaDB 10.1.14 with galera results in Signal 11
by Bill Mair 27 May '16

27 May '16

A new install and instance crashes when I try to start it with galera, I don't know what I'm doing wrong. I built galera from source according to the instructions here: https:// mariadb.com/kb/en/mariadb/installating-galera-from-source/ I had to use "scons strict_build_flags=0" (warnings were being flagged up as errors). # uname -a Linux alarm 4.6.0-3-ARCH #1 Fri May 20 20:21:01 MDT 2016 armv7l GNU/Linux # grep wsrep /etc/mysql/my.cnf wsrep_on=ON wsrep_provider=/usr/lib/galera/libgalera_smm.so wsrep_cluster_address=gcomm://192.168.1.91,192.168.1.92,192.168.1.93 wsrep_node_address='192.168.1.91' wsrep_node_name='node1' wsrep_cluster_name='mariadb_cluster' wsrep_sst_method=rsync wsrep_provider_options=pc.bootstrap=true # sudo -u mysql mysqld --wsrep-new-cluster 2016-05-25 22:10:31 3061874688 [Note] mysqld (mysqld 10.1.14-MariaDB) starting as process 8527 ... 2016-05-25 22:10:31 3061874688 [Note] WSREP: Read nil XID from storage engines, skipping position init 2016-05-25 22:10:31 3061874688 [Note] WSREP: wsrep_load(): loading provider library '/usr/lib/galera/libgalera_smm.so' 2016-05-25 22:10:31 3061874688 [Note] WSREP: wsrep_load(): Galera 3.16(rXXXX) by Codership Oy <info(a)codership.com> loaded successfully. 2016-05-25 22:10:31 3061874688 [Note] WSREP: CRC-32C: using "slicing- by-8" algorithm. 2016-05-25 22:10:31 3061874688 [Note] WSREP: Found saved state: 00000000-0000-0000-0000-000000000000:-1 2016-05-25 22:10:31 3061874688 [Note] WSREP: Passing config to GCS: base_dir = /var/lib/mysql/; base_host = 192.168.1.91; base_port = 4567; cert.log_conflicts = no; debug = no; evs.auto_evict = 0; evs.delay_margin = PT1S; evs.delayed_keep_period = PT30S; evs.inactive_check_period = PT0.5S; evs.inactive_timeout = PT15S; evs.join_retrans_period = PT1S; evs.max_install_timeouts = 3; evs.send_window = 4; evs.stats_report_period = PT1M; evs.suspect_timeout = PT5S; evs.user_send_window = 2; evs.view_forget_timeout = PT24H; gcache.dir = /var/lib/mysql/; gcache.keep_pages_size = 0; gcache.mem_size = 0; gcache.name = /var/lib/mysql//galera.cache; gcache.page_size = 128M; gcache.size = 128M; gcomm.thread_prio = ; gcs.fc_debug = 0; gcs.fc_factor = 1.0; gcs.fc_limit = 16; gcs.fc_master_slave = no; gcs.max_packet_size = 64500; gcs.max_throttle = 0.25; gcs.recv_q_hard_limit = 2147483647; gcs.recv_q_soft_limit = 0.25; gcs.sync_donor = no; gmcast.segment = 0; gmcast.version = 0; pc.announce_timeout = PT3S; pc.bootstrap = true; pc.checksum = false; pc.ignore_quo 2016-05-25 22:10:31 2908746768 [Note] WSREP: Service thread queue flushed. 2016-05-25 22:10:31 3061874688 [Note] WSREP: Assign initial position for certification: -1, protocol version: -1 2016-05-25 22:10:31 3061874688 [Note] WSREP: wsrep_sst_grab() 2016-05-25 22:10:31 3061874688 [Note] WSREP: Start replication 2016-05-25 22:10:31 3061874688 [Note] WSREP: 'wsrep-new-cluster' option used, bootstrapping the cluster 2016-05-25 22:10:31 3061874688 [Note] WSREP: Setting initial position to 00000000-0000-0000-0000-000000000000:-1 2016-05-25 22:10:31 3061874688 [Note] WSREP: protonet asio version 0 2016-05-25 22:10:31 3061874688 [Note] WSREP: Using CRC-32C for message checksums. 2016-05-25 22:10:31 3061874688 [Note] WSREP: backend: asio 2016-05-25 22:10:31 3061874688 [Note] WSREP: gcomm thread scheduling priority set to other:0 2016-05-25 22:10:31 3061874688 [Note] WSREP: restore pc from disk successfully 2016-05-25 22:10:31 3061874688 [Note] WSREP: GMCast version 0 2016-05-25 22:10:31 3061874688 [Note] WSREP: (8708eb25, 'tcp://0.0.0.0:4567') listening at tcp://0.0.0.0:4567 2016-05-25 22:10:31 3061874688 [Note] WSREP: (8708eb25, 'tcp://0.0.0.0:4567') multicast: , ttl: 1 2016-05-25 22:10:31 3061874688 [Note] WSREP: EVS version 0 2016-05-25 22:10:31 3061874688 [Note] WSREP: gcomm: bootstrapping new group 'mariadb_cluster' 2016-05-25 22:10:31 3061874688 [Note] WSREP: start_prim is enabled, turn off pc_recovery 2016-05-25 22:10:31 3061874688 [Note] WSREP: Node 8708eb25 state prim 2016-05-25 22:10:31 3061874688 [Note] WSREP: view(view_id(PRIM,8708eb25,17) memb { 8708eb25,0 } joined { } left { } partitioned { }) 2016-05-25 22:10:31 3061874688 [Note] WSREP: save pc into disk 2016-05-25 22:10:31 3061874688 [Note] WSREP: discarding pending addr without UUID: tcp://192.168.1.91:4567 2016-05-25 22:10:31 3061874688 [Note] WSREP: discarding pending addr proto entry 0xb652e2a0 2016-05-25 22:10:31 3061874688 [Note] WSREP: discarding pending addr without UUID: tcp://192.168.1.92:4567 2016-05-25 22:10:31 3061874688 [Note] WSREP: discarding pending addr proto entry 0xb652e380 2016-05-25 22:10:31 3061874688 [Note] WSREP: discarding pending addr without UUID: tcp://192.168.1.93:4567 2016-05-25 22:10:31 3061874688 [Note] WSREP: discarding pending addr proto entry 0xb652e460 2016-05-25 22:10:31 3061874688 [Note] WSREP: clear restored view 2016-05-25 22:10:31 3061874688 [Note] WSREP: gcomm: connected 2016-05-25 22:10:31 3061874688 [Note] WSREP: Changing maximum packet size to 64500, resulting msg size: 32636 2016-05-25 22:10:31 3061874688 [Note] WSREP: Shifting CLOSED -> OPEN (TO: 0) 2016-05-25 22:10:31 3061874688 [Note] WSREP: Opened channel 'mariadb_cluster' 2016-05-25 22:10:31 3061874688 [Note] WSREP: Waiting for SST to complete. 2016-05-25 22:10:31 2860512272 [Note] WSREP: New COMPONENT: primary = yes, bootstrap = no, my_idx = 0, memb_num = 1 2016-05-25 22:10:31 2860512272 [Note] WSREP: Starting new group from scratch: 1d570213-22bd-11e6-a70b-6aae917d4541 2016-05-25 22:10:31 2860512272 [Note] WSREP: STATE_EXCHANGE: sent state UUID: 1d574d2d-22bd-11e6-8936-86e5eb8c6c4c 2016-05-25 22:10:31 2860512272 [Note] WSREP: STATE EXCHANGE: sent state msg: 1d574d2d-22bd-11e6-8936-86e5eb8c6c4c 2016-05-25 22:10:31 2860512272 [Note] WSREP: STATE EXCHANGE: got state msg: 1d574d2d-22bd-11e6-8936-86e5eb8c6c4c from 0 (node1) 2016-05-25 22:10:31 2860512272 [Note] WSREP: Quorum results: version = 4, component = PRIMARY, conf_id = 0, members = 1/1 (joined/total), act_id = 0, last_appl. = -1, protocols = 0/7/3 (gcs/repl/appl), group UUID = 1d570213-22bd-11e6-a70b-6aae917d4541 2016-05-25 22:10:31 2860512272 [Note] WSREP: Flow-control interval: [16, 16] 2016-05-25 22:10:31 2860512272 [Note] WSREP: Restored state OPEN -> JOINED (0) 160525 22:10:31 [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.14-MariaDB key_buffer_size=0 read_buffer_size=262144 max_used_connections=0 max_threads=153 thread_count=2 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 119520 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0xb65d7008 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 = 0xad90edc4 thread_stack 0x48400 Trying to get some variables. Some pointers may be invalid and cause the dump to abort. 2016-05-25 22:10:31 2860512272 [Note] WSREP: Member 0.0 (node1) synced with group. 2016-05-25 22:10:31 2860512272 [Note] WSREP: Shifting JOINED -> SYNCED (TO: 0) Query (0x0): Connection ID (thread ID): 1 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_mer ge_intersection=on,index_merge_sort_intersection=off,engine_condition_p ushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_k eys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,se mijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subq uery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_w ith_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cach e_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimi nation=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.

2 4

[Maria-discuss] New Question: Can't configure using BUILD/autorun.sh, missing component
by AskMonty KB 26 May '16

26 May '16

Hello, A new question has been asked in "MariaDB Documentation" by Chico008. Please answer it at http://mariadb.com/kb/en/cant-configure-using-buildautorunsh-missing-compon… as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hi I'm trying to install MardiaDB on a RH7 enterprise linux server, from the mariadb source (10.1.14) when trying to configure i got this error : CMake Error at storage/tokudb/PerconaFT/cmake_modules/TokuSetupCompiler.cmake:180 (message): /usr/bin/c++ doesn't support -std=c++11 or -std=c++0x, you need one that does. I already have the latest version, can your help ? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/cant-configure-using-buildautorunsh-missing-compon…

1 0

[Maria-discuss] need help with “show engine innodb mutex” output
by Lukas Lehner 22 May '16

22 May '16

Hi https://dba.stackexchange.com/questions/139149/howto-read-interpret-show-en… thank you very much for explanations Lukas

1 0

[Maria-discuss] Bls: ask tool mariadb auto update latest for windows
by Irwanto 21 May '16

21 May '16

nice share mr. chris Pada Minggu, 22 Mei 2016 1:30, Chris Calender <chris.calender(a)mariadb.com> menulis: Hello, I have a custom .bat script I use on Windows which I use to upgrade both MariaDB and MySQL instances. It's not a supported 'tool' by any means, but works great for me in my Windows environment. You'll see 9 variables at the beginning which you will need to set for your environment, like basedir, datadir, config file, user, pass, port, service name, the download link, and download directory. I've attached it as a .txt file. Just edit those 9 variables, rename it to upgrade.bat, and invoke it from the command line: C:/location/of/file> upgrade.bat Once you have it set up for you instance, then future upgrades really only require you changing your download link. Beware I have all of the gnuwin32 utils, which this script uses, so you would either need those (e.g., wget, cp, mv, mkdir, unzip), or you would need to convert those commands to their native Windows equivalents. I also mention any caveats at the top of the file. In a nutshell, it downloads and unzips the package you specify. Then stops the service, copies out the old, replaces with the new, copies in existing datadir and config file, and then restarts the service. At the end, it runs mysql_upgrade, and then displays the new version number for your reference. Here is some sample output from an upgrade I just ran using it last night (from MariaDB 10.1.13 to 10.1.14). You can see at the end it took ~6 minutes, most of which was the download and extraction: ... inflating: C:\mysql/ma inflating: C:\mysql/ma +-----------------+ | version() | +-----------------+ | 10.1.13-MariaDB | +-----------------+ net stop "maria101" The maria101 service is stopping. The maria101 service was stopped successfully. rm -rf "C:\mysql\mariadb-10.1.14-winx64\data\*" cp -r "C:\Program Files\MariaDB 10.1\data\*" "C:\mysql\mariadb-10.1.14-winx64\data" cp "C:\Program Files\MariaDB 10.1\data\my.ini" "C:\mysql\mariadb-10.1.14-winx64\data" mkdir "C:\mysql\maria101-backup\" mv "C:\Program Files\MariaDB 10.1\*" "C:\mysql/maria101-backup/" mv "C:\mysql\mariadb-10.1.14-winx64\*" "C:\Program Files\MariaDB 10.1/" net start "maria101" The maria101 service is starting. The maria101 service was started successfully. mysql_upgrade.exe" -uroot -pxxx -P3316 Phase 1/6: Checking and upgrading mysql database Processing databases mysql mysql.column_stats OK .... test test.mem1 OK test.tbl_name OK Phase 6/6: Running 'FLUSH PRIVILEGES' OK +-----------------+ | version() | +-----------------+ | 10.1.14-MariaDB | +-----------------+ start=20:40:40.14 end = 20:46:59.55 Hope this helps. Best wishes, Chris -- Chris Calender, M.S., Principal Support Engineer MariaDB Corporation > On 5/13/2016 7:20 PM, Irwanto wrote: >> hi, >> i have 5-15 pc as server using mariadb. >> i always copy and update latest release one by one to server. >> is there any tool to download, stop service and extract update my >> mariadb in windows. >> maybe some one know it >> >> thanks b4 >> >> >> >> _______________________________________________ >> 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: Format of GRANT ALL PRIVELEGES command
by AskMonty KB 19 May '16

19 May '16

Hello, A new question has been asked in "Getting, Installing, and Upgrading MariaDB" by mark_watts_g. Please answer it at http://mariadb.com/kb/en/format-of-grant-all-priveleges-command/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- What is format of this command in version 10.1.8 -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/format-of-grant-all-priveleges-command/

1 0

[Maria-discuss] Encryption
by Ghazi Btissam 16 May '16

16 May '16

Hi, -Oracle has the tablespace feature ,does MariaDb has the same feature ? -If yes how MariaDb encrypt a tablespace ? Thanks

2 1

[Maria-discuss] ask tool mariadb auto update latest for windows
by Irwanto 15 May '16

15 May '16

hi,i have 5-15 pc as server using mariadb.i always copy and update latest release one by one to server.is there any tool to download, stop service and extract update my mariadb in windows.maybe some one know it thanks b4

4 3

[Maria-discuss] New Question: how to create fake DATA inside MariaDB SQL database???
by AskMonty KB 14 May '16

14 May '16

Hello, A new question has been asked in "MariaDB Community" by cyberdome. Please answer it at http://mariadb.com/kb/en/how-to-create-fake-data-inside-mariadb-sql-databas… as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hello World, I am trying to create some TEST DATA, meaning fake date for playing around with MariaDB tables and databases. I need to create some fake random data using SQL RDBMS. So, why not use Mockaroo.com , but on that website I can only do 1000 rows at one time. Which is extremely time consuming. How can I create random fake data. Tons of it. For example, Let us say I want 2 millions rows of random data with ID, NAME, ADDRESS, PHONE, EMAIL. I hope I am making sense. Any help is greatly appreciated!!!!! Thanks __________________ __________________ Linux Newbie - Information is Power! Download Linux @ http://www.fedora.redhat.com/ May the Linux force be with you! Fedora 23 - MariaDB 10.1 -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/how-to-create-fake-data-inside-mariadb-sql-databas…

1 0

[Maria-discuss] New Question: backup maria db with out shutdown db
by AskMonty KB 13 May '16

13 May '16

Hello, A new question has been asked in "Backing Up and Restoring" by eboylan_50460. Please answer it at http://mariadb.com/kb/en/backup-maria-db-with-out-shutdown-db/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- what is the best way to backup a 3 server VM installation of Maria DB without being able to shutdown the database -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/backup-maria-db-with-out-shutdown-db/

1 0

[Maria-discuss] New Question: MariaDB 10.1.13 Changing MySQL version
by AskMonty KB 11 May '16

11 May '16

Hello, A new question has been asked in "MariaDB Community" by dominic_ray_g. Please answer it at http://mariadb.com/kb/en/mariadb-10113-changing-mysql-version/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hi, At present I have MariaDB version 10.1.13 installed on a Debian 8 server and by default it is using MySQL 5.6.28-76-1. I have looked around your site and even googled for answers only to find it no use. How do I set MariaDB to use MySQL 5.7? Regards Dominic -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/mariadb-10113-changing-mysql-version/

1 0

[Maria-discuss] New Question: "wsrep_local_replays" greater than zero
by AskMonty KB 10 May '16

10 May '16

Hello, A new question has been asked in "MariaDB FAQ" by alexandraarreaza. Please answer it at http://mariadb.com/kb/en/wsrep_local_replays-greater-than-zero/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hi there, I've been having this situation with two different Galera DB Clusters (let's say Cluster A and Cluster B) for two different customers, where the "wsrep_local_replays" shows "1" on one of the DB nodes on each DB Cluster. I'd like to know: 1. Which is reason why this variable is now 1. 2. How can this be fixed. 3. As Cluster A and Cluster B are in Production, I'm worried that this may cause a problem in the long term... Would it cause it? One fix that worked for me was restarting mysql service on the node with this "issue" in Cluster A, which thankfully joined the cluster with an IST. However, I cannot do the same for Cluster B, since DBs are massive ( > 300GB). Even though gcache is big enough, that won't guarantee an IST and I cannot afford to do an SST. Also, the donor is the one having "wsrep_local_replays=1". The app doesn't write to the donor (so how did it happen?). Cluster A: 10.0.19-MariaDB-wsrep-log MariaDB Server, wsrep_25.10.r4144 Cluster B: 5.5.41-MariaDB-wsrep-log MariaDB Server, wsrep_25.11.r4026 Please let me know if you need any more details. Thanks in advance! -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/wsrep_local_replays-greater-than-zero/

1 0

[Maria-discuss] MariaDB 10.1.14 and Connector/J 1.4.4 now available
by Daniel Bartholomew 10 May '16

10 May '16

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.1.14 and MariaDB Connector/J 1.4.4. These are both Stable (GA) releases. See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.1.14 - Release Notes: https://mariadb.com/kb/en/mdb-10114-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10114-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.1.14 About MariaDB 10.1: - https://mariadb.com/kb/en/what-is-mariadb-101/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB Connector/J 1.4.4 - Release Notes: https://mariadb.com/kb/en/mcj-144-rn/ - Changelog: https://mariadb.com/kb/en/mcj-144-cl/ - Downloads: https://downloads.mariadb.org/connector-java/1.4.4/ About MariaDB Connector/J: - https://mariadb.com/kb/en/about-mariadb-connector-j/ - - 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: Poor performance on inserts MariaDB
by AskMonty KB 09 May '16

09 May '16

Hello, A new question has been asked in "MariaDB Documentation" by aferrett. Please answer it at http://mariadb.com/kb/en/poor-performance-on-inserts-mariadb/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- We are running MariaDB Community Edition 10.1.11. We are benchmarking inserts for an application that requires high volume inserts. With MariaDB, we can insert about 476 rows for second. The same job is able to load 2,500 rows/ second on Oracle. Both environments are VMware with RedHat Linux. We have the same number of vCPUs and memory. Overall performance declines if we try multiple jobs. I tried increasing innodb_autoinc_lock_mode from 1 to 2 and bouncing without seeing improvement. I see a of processes waiting on system locks such as this one: SQL thread id 14, OS thread handle 0x7f9237bff700, query id 6743478 zlx70603.vci.att.com 130.9.221.47 pedadba System lock. I see lots of WRITES for each insert: 20160509 09:16:29,zlx70756,pedadba,zlx70603.vci.att.com,32,11812785,QUERY,ped,'insert into ped_location_load (SRC_CPL_ID, STR_ADDR, CITY_NM, ST_CD, ZIP_CD, LAT_COORD, LONG_COORD, CLLI_8, FIBR_LIT_IND, FIBR_LIT_BLDG_IND, EGIS_FIBR_LIT_BLDG_IND, SRVG_WC_CLLI_8, LEIS_WC_CD, DA_PSA_NAME, DA_PSA_ID, DSTNC_TO_FIBR_FEET_MSRMT, DSTNC_TO_FIBR_MILE_MSRMT, GIS_LAT_COORD, GIS_LONG_COORD, SAG_HSE_NBR, SAG_STR_PRFX, SAG_STR_NM, SAG_CITY_NM, SAG_ST_CD, SAG_ZIP_CD, SAG_MTCH_CD, SITE_STS_CD, AREA_MGR_PLNG_NM, AREA_MGR_DSGN_NM, RGN_CD, SUB_TURF_CD, TERR_TYPE_CD, LATA_CD, BUS_UNIT_CNT, PRRTY_NBR, PRRTY_YR, ALT_SRVG_WC_CLLI_8, PROJ_MGT_TOOL_NBR, BLDG_NM, PROJ_ACTVN_DT, REACTVN_DT, UVERSE_GREEN_AREA_IND, CELL_SITE_IN_BLDG_IND, CELL_SITE_N_BLDG_FXD_ASSET_NBR, VCNTY_CELL_SITE_FXD_ASSET_NBR, EXSTG_ORD_NBR, SMALL_CELL_PLAN_FOR_BLDG_IND, LOC_CMNT_TXT, CRTD_DT, CRTD_BY, LAST_UPDTD_DT, LAST_UPDTD_BY, SVC_ORD_NBR, MKTG_STR_PRFX, MKTG_STR_DRCTN, RVISD_BUS_UNIT_CNT, BUS_JSTFCN, BLD_YR, BLDG_PASSED, BLDG_ON _NET, FAP_STS, FAP_LOC, FDA_NM, FAA_NM, FAP_JOB_NBR, CLDS_REQUEST_ID, CLDS_STATUS, FIBR_RISER_RQRD, SAG_MTCH_MSG,',0 20160509 09:16:29,zlx70756,pedadba,zlx70603.vci.att.com,32,11812788,QUERY,ped,'SELECT FLOOR(RAND()*(50-1)+50) into st_rand',0 20160509 09:16:29,zlx70756,pedadba,zlx70603.vci.att.com,32,11812789,QUERY,ped,'SELECT FLOOR(RAND()*(6-1)+6) into reg_rand',0 20160509 09:16:29,zlx70756,isaac_all,%,32,11812791,WRITE,ped,ped_location_load, 20160509 09:16:29,zlx70756,isaac_all,%,32,11812791,WRITE,ped,ped_location_load, < many more WRITES> Here is the full innodb engine status: to shorten it, I put the full statement only once: -------------- SHOW ENGINE INNODB STATUS -------------- *************************** 1. row *************************** Type: InnoDB Name: Status: ===================================== 2016-05-09 08:43:37 7f92323ff700 INNODB MONITOR OUTPUT ===================================== Per second averages calculated from the last 34 seconds ----------------- BACKGROUND THREAD ----------------- srv_master_thread loops: 2785 srv_active, 0 srv_shutdown, 461 srv_idle srv_master_thread log flush and writes: 3246 ---------- SEMAPHORES ---------- OS WAIT ARRAY INFO: reservation count 8038 OS WAIT ARRAY INFO: signal count 9256 Mutex spin waits 5940, rounds 76361, OS waits 1957 RW-shared spins 2417, rounds 70030, OS waits 2234 RW-excl spins 5242, rounds 133769, OS waits 3264 Spin rounds per wait: 12.86 mutex, 28.97 RW-shared, 25.52 RW-excl ------------ TRANSACTIONS ------------ Trx id counter 88326197 Purge done for trx's n:o < 88326196 undo n:o < 0 state: running but idle History list length 180 LIST OF TRANSACTIONS FOR EACH SESSION: ---TRANSACTION 0, not started MySQL thread id 20, OS thread handle 0x7f92323ff700, query id 6743576 zlx70603.vci.att.com 130.9.221.47 isaac_all init SHOW ENGINE INNODB STATUS ---TRANSACTION 88325944, not started MySQL thread id 5, OS thread handle 0x7f92781db700, query id 955255 vpn-135-70-5-32.vpn.west.att.com 135.70.5.32 isaac_all cleaning up ---TRANSACTION 0, not started MySQL thread id 4, OS thread handle 0x7f9281962700, query id 955574 vpn-135-70-5-32.vpn.west.att.com 135.70.5.32 isaac_all cleaning up ---TRANSACTION 88322307, not started MySQL thread id 1, OS thread handle 0x7f92b3d84700, query id 0 Waiting for background binlog tasks ---TRANSACTION 88326196, ACTIVE 52 sec mysql tables in use 131, locked 131 1 lock struct(s), heap size 360, 0 row lock(s), undo log entries 2238 MySQL thread id 13, OS thread handle 0x7f92459f3700, query id 6743448 zlx70603.vci.att.com 130.9.221.47 pedadba System lock insert into ped_location_load (SRC_CPL_ID, STR_ADDR, CITY_NM, ST_CD, ZIP_CD, LAT_COORD, LONG_COORD, CLLI_8, FIBR_LIT_IND, FIBR_LIT_BLDG_IND, EGIS_FIBR_LIT_BLDG_IND, SRVG_WC_CLLI_8, LEIS_WC_CD, DA_PSA_NAME, DA_PSA_ID, DSTNC_TO_FIBR_FEET_MSRMT, DSTNC_TO_FIBR_MILE_MSRMT, GIS_LAT_COORD, GIS_LONG_COORD, SAG_HSE_NBR, SAG_STR_PRFX, SAG_STR_NM, SAG_CITY_NM, SAG_ST_CD, SAG_ZIP_CD, SAG_MTCH_CD, SITE_STS_CD, AREA_MGR_PLNG_NM, AREA_MGR_DSGN_NM, RGN_CD, SUB_TURF_CD, TERR_TYPE_CD, LATA_CD, BUS_UNIT_CNT, PRRTY_NBR, PRRTY_YR, ALT_SRVG_WC_CLLI_8, PROJ_MGT_TOOL_NBR, BLDG_NM, PROJ_ACTVN_DT, REACTVN_DT, UVERSE_GR Trx #rec lock waits 0 #table lock waits 0 Trx total rec lock wait time 0 SEC Trx total table lock wait time 0 SEC ---TRANSACTION 88326191, ACTIVE 83 sec mysql tables in use 52, locked 52 1 lock struct(s), heap size 360, 0 row lock(s), undo log entries 3584 MySQL thread id 16, OS thread handle 0x7f9235fff700, query id 6743430 zlx70603.vci.att.com 130.9.221.47 pedadba System lock insert into ped_location_load (SRC_CPL_ID, STR_ADDR, <complete statement same as above> Trx #rec lock waits 0 #table lock waits 0 Trx total rec lock wait time 0 SEC Trx total table lock wait time 0 SEC ---TRANSACTION 88326190, ACTIVE 83 sec mysql tables in use 5, locked 5 1 lock struct(s), heap size 360, 0 row lock(s), undo log entries 3658 MySQL thread id 19, OS thread handle 0x7f92333ff700, query id 6743606 zlx70603.vci.att.com 130.9.221.47 pedadba System lock insert into ped_location_load (SRC_CPL_ID, <complete statement same as above> Trx #rec lock waits 0 #table lock waits 0 Trx total rec lock wait time 0 SEC Trx total table lock wait time 0 SEC ---TRANSACTION 88326188, ACTIVE 86 sec mysql tables in use 59, locked 59 1 lock struct(s), heap size 360, 0 row lock(s), undo log entries 3697 MySQL thread id 15, OS thread handle 0x7f9236fff700, query id 6743327 zlx70603.vci.att.com 130.9.221.47 pedadba System lock insert into ped_location_load (SRC_CPL_ID, <complete statement same as above> Trx #rec lock waits 0 #table lock waits 0 Trx total rec lock wait time 0 SEC Trx total table lock wait time 0 SEC ---TRANSACTION 88326187, ACTIVE 98 sec mysql tables in use 66, locked 66 1 lock struct(s), heap size 360, 0 row lock(s), undo log entries 4320 MySQL thread id 12, OS thread handle 0x7f924ddee700, query id 6743575 zlx70603.vci.att.com 130.9.221.47 pedadba System lock insert into ped_location_load (SRC_CPL_ID, <complete statement same as above> Trx #rec lock waits 0 #table lock waits 0 Trx total rec lock wait time 0 SEC Trx total table lock wait time 0 SEC ---TRANSACTION 88326186, ACTIVE 99 sec mysql tables in use 33, locked 33 1 lock struct(s), heap size 360, 0 row lock(s), undo log entries 4506 MySQL thread id 17, OS thread handle 0x7f92353ff700, query id 6743630 zlx70603.vci.att.com 130.9.221.47 pedadba System lock insert into ped_location_load (SRC_CPL_ID, <complete statement same as above> Trx #rec lock waits 0 #table lock waits 0 Trx total rec lock wait time 0 SEC Trx total table lock wait time 0 SEC ---TRANSACTION 88326185, ACTIVE 116 sec mysql tables in use 59, locked 59 1 lock struct(s), heap size 360, 0 row lock(s), undo log entries 5086 MySQL thread id 11, OS thread handle 0x7f9281a63700, query id 6743446 zlx70603.vci.att.com 130.9.221.47 pedadba System lock insert into ped_location_load (SRC_CPL_ID, <complete statement same as above> Trx #rec lock waits 0 #table lock waits 0 Trx total rec lock wait time 0 SEC Trx total table lock wait time 0 SEC ---TRANSACTION 88326184, ACTIVE 172 sec mysql tables in use 7, locked 7 1 lock struct(s), heap size 360, 0 row lock(s), undo log entries 7919 MySQL thread id 18, OS thread handle 0x7f92343ff700, query id 6743538 zlx70603.vci.att.com 130.9.221.47 pedadba System lock insert into ped_location_load (SRC_CPL_ID, <complete statement same as above> Trx #rec lock waits 0 #table lock waits 0 Trx total rec lock wait time 0 SEC Trx total table lock wait time 0 SEC ---TRANSACTION 88326183, ACTIVE 203 sec mysql tables in use 52, locked 52 1 lock struct(s), heap size 360, 0 row lock(s), undo log entries 9102 MySQL thread id 8, OS thread handle 0x7f92393ff700, query id 6743600 zlx70603.vci.att.com 130.9.221.47 pedadba System lock insert into ped_location_load (SRC_CPL_ID, <complete statement same as above> Trx #rec lock waits 0 #table lock waits 0 Trx total rec lock wait time 0 SEC Trx total table lock wait time 0 SEC ---TRANSACTION 88326178, ACTIVE 212 sec mysql tables in use 75, locked 75 1 lock struct(s), heap size 360, 0 row lock(s), undo log entries 9706 MySQL thread id 14, OS thread handle 0x7f9237bff700, query id 6743478 zlx70603.vci.att.com 130.9.221.47 pedadba System lock insert into ped_location_load (SRC_CPL_ID, <complete statement same as above> Trx #rec lock waits 0 #table lock waits 0 Trx total rec lock wait time 0 SEC Trx total table lock wait time 0 SEC -------- FILE I/O -------- I/O thread 0 state: waiting for completed aio requests (insert buffer thread) I/O thread 1 state: waiting for completed aio requests (log thread) I/O thread 2 state: waiting for completed aio requests (read thread) I/O thread 3 state: waiting for completed aio requests (read thread) I/O thread 4 state: waiting for completed aio requests (read thread) I/O thread 5 state: waiting for completed aio requests (read thread) I/O thread 6 state: waiting for completed aio requests (write thread) I/O thread 7 state: waiting for completed aio requests (write thread) I/O thread 8 state: waiting for completed aio requests (write thread) I/O thread 9 state: waiting for completed aio requests (write thread) Pending normal aio reads: 0 [0, 0, 0, 0] , aio writes: 0 [0, 0, 0, 0] , ibuf aio reads: 0, log i/o's: 0, sync i/o's: 0 Pending flushes (fsync) log: 0; buffer pool: 0 4272 OS file reads, 78139 OS file writes, 20899 OS fsyncs 0.00 reads/s, 0 avg bytes/read, 21.68 writes/s, 4.32 fsyncs/s ------------------------------------- INSERT BUFFER AND ADAPTIVE HASH INDEX ------------------------------------- Ibuf: size 1, free list len 62, seg size 64, 0 merges merged operations: insert 0, delete mark 0, delete 0 discarded operations: insert 0, delete mark 0, delete 0 5981.97 hash searches/s, 406.66 non-hash searches/s --- LOG --- Log sequence number 375449925793 Log flushed up to 375449653000 Pages flushed up to 375438050350 Last checkpoint at 375435460923 Max checkpoint age 84223550 Checkpoint age target 81591565 Modified age 11875443 Checkpoint age 14464870 0 pending log writes, 0 pending chkp writes 6332 log i/o's done, 1.91 log i/o's/second ---------------------- BUFFER POOL AND MEMORY ---------------------- Total memory allocated 553648128; in additional pool allocated 0 Total memory allocated by read views 288 Internal hash tables (constant factor + variable factor) Adaptive hash index 8888016 (8851048 + 36968) Page hash 553976 (buffer pool 0 only) Dictionary cache 46879130 (2214224 + 44664906) File system 1307376 (812272 + 495104) Lock system 1334216 (1329176 + 5040) Recovery system 0 (0 + 0) Dictionary memory allocated 44664906 Buffer pool size 32767 Buffer pool size, bytes 536854528 Free buffers 1014 Database pages 31748 Old database pages 11699 Modified db pages 500 Percent of dirty pages(LRU & free pages): 1.526 Max dirty pages percent: 75.000 Pending reads 0 Pending writes: LRU 0, flush list 0, single page 0 Pages made young 3251, not young 49414 0.06 youngs/s, 0.00 non-youngs/s Pages read 2853, created 52673, written 60872 0.00 reads/s, 16.56 creates/s, 18.56 writes/s Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000 Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s LRU len: 31748, unzip_LRU len: 0 I/O sum[982]:cur[0], unzip sum[0]:cur[0] -------------- ROW OPERATIONS -------------- 0 queries inside InnoDB, 0 queries in queue 0 read views open inside InnoDB 10 RW transactions active inside InnoDB 0 RO transactions active inside InnoDB 10 out of 1000 descriptors used Main thread process no. 2676, id 140266283443968, state: sleeping Number of rows inserted 1123943, updated 0, deleted 0, read 20 423.72 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.00 reads/s Number of system rows inserted 0, updated 0, deleted 0, read 0 0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.00 reads/s ---------------------------- END OF INNODB MONITOR OUTPUT ============================ -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/poor-performance-on-inserts-mariadb/

1 0

[Maria-discuss] New Question: Mr
by AskMonty KB 09 May '16

09 May '16

Hello, A new question has been asked in "Replication, Cluster, & Multi-Master" by Adetunji. Please answer it at http://mariadb.com/kb/en/mr/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- My company will like to use mariadb for our next project as we're currently using mysql, we'll like to know how the clustering and the replication works. Thanks -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/mr/

1 0

[Maria-discuss] New Question: Trigger error
by AskMonty KB 07 May '16

07 May '16

Hello, A new question has been asked in "Triggers" by shadowfoxx_49588. Please answer it at http://mariadb.com/kb/en/trigger-error/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hello, i'm trying to create check trigger between two columns. But get query error. Structure of columns is: ,,`start_t` (time) , `end_t` (time),, The goal is hours in `end_t` don't be same with `start_t` (e.g. 11:00 > 11:00) Here is query code: ,,CREATE TRIGGER `check_times` BEFORE INSERT ON `schedule` FOR EACH ROW BEGIN DECLARE v_end_time time; SELECT end_t INTO v_end_time FROM `schedule` WHERE fn_stud = NEW.fn_stud; IF NEW.start_t > v_end_time THEN SET NEW.fn_stud = NULL; END IF; END;,, MySQL says: #1064 - 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 '' at line 1 Don't understand what is wrong. Can anyone explain? Thanks. -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/trigger-error/

1 0

[Maria-discuss] New Question: Which OS to use for MariaDB?
by AskMonty KB 06 May '16

06 May '16

Hello, A new question has been asked in "General FAQ" by dbamaria. Please answer it at http://mariadb.com/kb/en/which-os-to-use-for-mariadb/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hi, What is the best OS environnement for MariaDB database ?(in term of varity of features, stability, performance..) I've seen that ,for instance, the Galera solution couldn't be installed under Windows..Are there any kind of such limitations and constraints to install it in Linux or Windows platform? Regards -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/which-os-to-use-for-mariadb/

1 0

[Maria-discuss] SST with 10.1.13 + xtrabackup-v2 is failing
by Erik Mathis 06 May '16

06 May '16

I cant seem to get past this problem when using xtrabackup-v2 to preform an SST. Everything works fine when I use rsync method. This is a new cluster. I know the sst user/password is working which I confirmed. 2016-05-06 14:34:31 140258805017344 [Note] WSREP: State transfer required: Group state: b5013090-12e9-11e6-ba99-bf6bb7612fa3:8 Local state: 00000000-0000-0000-0000-000000000000:-1 2016-05-06 14:34:31 140258805017344 [Note] WSREP: New cluster view: global state: b5013090-12e9-11e6-ba99-bf6bb7612fa3:8, view# 43: Primary, number of nodes: 3, my index: 0, protocol version 3 2016-05-06 14:34:31 140258805017344 [Warning] WSREP: Gap in state sequence. Need state transfer. 2016-05-06 14:34:31 140258796631808 [Note] WSREP: Running: 'wsrep_sst_xtrabackup-v2 --role 'joiner' --address '10.1.5.42' --datadir '/var/lib/mysql/' --parent '28455' --binlog 'mysql-bin' ' WSREP_SST: [INFO] Streaming with xbstream (20160506 14:34:32.597) WSREP_SST: [INFO] Using socat as streamer (20160506 14:34:32.605) WSREP_SST: [INFO] Evaluating timeout -s9 100 socat -u TCP-LISTEN:4444,reuseaddr stdio | xbstream -x; RC=( ${PIPESTATUS[@]} ) (20160506 14:34:32.740) 2016-05-06 14:34:32 140258805017344 [Note] WSREP: Prepared SST request: xtrabackup-v2|10.1.5.42:4444/xtrabackup_sst//1 2016-05-06 14:34:32 140258805017344 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification. 2016-05-06 14:34:32 140258805017344 [Note] WSREP: REPL Protocols: 7 (3, 2) 2016-05-06 14:34:32 140258905679616 [Note] WSREP: Service thread queue flushed. 2016-05-06 14:34:32 140258805017344 [Note] WSREP: Assign initial position for certification: 8, protocol version: 3 2016-05-06 14:34:32 140258905679616 [Note] WSREP: Service thread queue flushed. 2016-05-06 14:34:32 140258805017344 [Warning] WSREP: Failed to prepare for incremental state transfer: Local state UUID (00000000-0000-0000-0000-000000000000) does not match group state UUID (b5013090-12e9-11e6-ba99-bf6bb7612fa3): 1 (Operation not permitted) at galera/src/replicator_str.cpp:prepare_for_IST():482. IST will be unavailable. 2016-05-06 14:34:32 140258832279296 [Note] WSREP: Member 0.0 () requested state transfer from '*any*'. Selected 1.0 ()(SYNCED) as donor. 2016-05-06 14:34:32 140258832279296 [Note] WSREP: Shifting PRIMARY -> JOINER (TO: 8) 2016-05-06 14:34:32 140258805017344 [Note] WSREP: Requesting state transfer: success, donor: 1 WSREP_SST: [INFO] Proceeding with SST (20160506 14:34:33.153) WSREP_SST: [INFO] Evaluating socat -u TCP-LISTEN:4444,reuseaddr stdio | xbstream -x; RC=( ${PIPESTATUS[@]} ) (20160506 14:34:33.152) WSREP_SST: [INFO] Cleaning the existing datadir and innodb-data/log directories (20160506 14:34:33.163) removed `/var/lib/mysql/ib_logfile0' removed `/var/lib/mysql/aria_log_control' removed `/var/lib/mysql/aria_log.00000001' removed `/var/lib/mysql/mysql-bin.index' removed `/var/lib/mysql/ib_logfile1' removed `/var/lib/mysql/ibdata1' removed `/var/lib/mysql/mysql.sock' removed `/var/lib/mysql/mysql-bin.state' removed `/var/lib/mysql/mysql-bin.000001' WSREP_SST: [INFO] Waiting for SST streaming to complete! (20160506 14:34:33.252) 2016-05-06 14:34:34 140258842769152 [Note] WSREP: (a4dbb726, 'tcp://0.0.0.0:4567') turning message relay requesting off 2016-05-06 14:34:44 140258832279296 [Note] WSREP: 1.0 (): State transfer to 0.0 () complete. 2016-05-06 14:34:44 140258832279296 [Note] WSREP: Member 1.0 () synced with group. ls: cannot access mysql-bin.[0-9]*: No such file or directory WSREP_SST: [INFO] Preparing the backup at /var/lib/mysql//.sst (20160506 14:34:45.012) WSREP_SST: [INFO] Evaluating innobackupex --no-version-check --apply-log $rebuildcmd ${DATA} &>${DATA}/innobackup.prepare.log (20160506 14:34:45.021) rm: cannot remove `/var/lib/mysql//innobackup.prepare.log': No such file or directory rm: cannot remove `/var/lib/mysql//innobackup.move.log': No such file or directory WSREP_SST: [INFO] Moving the backup to /var/lib/mysql/ (20160506 14:34:50.126) WSREP_SST: [INFO] Evaluating innobackupex --no-version-check --move-back --force-non-empty-directories ${DATA} &>${DATA}/innobackup.move.log (20160506 14:34:50.135) WSREP_SST: [ERROR] Cleanup after exit with status:2 (20160506 14:34:50.167) 2016-05-06 14:34:50 140258796631808 [ERROR] WSREP: Process completed with error: wsrep_sst_xtrabackup-v2 --role 'joiner' --address '10.1.5.42' --datadir '/var/lib/mysql/' --parent '28455' --binlog 'mysql-bin' : 2 (No such file or directory) 2016-05-06 14:34:50 140258796631808 [ERROR] WSREP: Failed to read uuid:seqno and wsrep_gtid_domain_id from joiner script. 2016-05-06 14:34:50 140260071184416 [ERROR] WSREP: SST failed: 2 (No such file or directory) 2016-05-06 14:34:50 140260071184416 [ERROR] Aborting Error in my_thread_global_end(): 1 threads didn't exit The Joiner innobackup.move.log has this error innobackupex version 2.4.2 based on MySQL server 5.7.11 Linux (x86_64) (revision id: 8e86a84) Error: Move file ib_logfile0 to ./ib_logfile0 failed: Destination file exists 14:34:50 UTC - xtrabackup got signal 11 ; This could be because you hit a bug or data is corrupted. This error can also be caused by malfunctioning hardware. Attempting to collect some information that could help diagnose the problem. As this is a crash and something is definitely wrong, the information collection process might fail. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x10000 innobackupex(my_print_stacktrace+0x35)[0xedd1a5] innobackupex(handle_fatal_signal+0x273)[0xa3fce3] /lib64/libpthread.so.0(+0xf7e0)[0x7f5527d2b7e0] /lib64/libc.so.6(cfree+0x1c)[0x7f552618593c] innobackupex(_Z9copy_backv+0x377)[0x74f437] innobackupex(main+0xc0f)[0x73e00f] /lib64/libc.so.6(__libc_start_main+0xfd)[0x7f5526128d5d] innobackupex[0x72db39]

2 2

[Maria-discuss] New Question: Deadlock with foreign key constraints
by AskMonty KB 05 May '16

05 May '16

Hello, A new question has been asked in "MariaDB Community" by sjangra. Please answer it at http://mariadb.com/kb/en/deadlock-with-foreign-key-constraints/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- We are using MariaDB 10.1 and facing some weird deadlock issues. While investigating we ran a sample program to test the foreign keys and found a deadlock error. Can someone please explain this in bit detail so we understand how locking works in galera. We used a 2 node cluster for this testing. Session 1 (Node1): ------------------------ create table dl1(pk int primary key, data varchar(100)); create table dl2(pk int primary key, pk1 int not null, constraint dl2_fk foreign key(pk1) references dl1(pk), data varchar(100)); set autocommit=off; insert into dl1 values(1, 'a'); Session 2 (Node2): ------------------------ set autocommit=off; insert into dl2(pk, pk1, data) values(10, 1, 'a0'); ERROR 1452 (23000): Cannot add or update a child row: a foreign key constraint fails (`demoApp`.`dl2`, CONSTRAINT `dl2_fk` FOREIGN KEY (`pk1`) REFERENCES `dl1` (`pk`)) -- as expected select * from dl1; Empty set (0.00 sec) -- as expected Session 1 (Node1): ------------------------ commit; Session 2 (Node2): ------------------------ select * from dl1; ERROR 1213 (40001): Deadlock found when trying to get lock; try restarting transaction --- strange Once I got this error I ran the 'SHOW ENGINE INNODB STATUS\G' on node2 and here is the truncated output. ------------------------ LATEST FOREIGN KEY ERROR ------------------------ 2016-05-04 17:46:34 7ff98ead8b00 Transaction: TRANSACTION 3852, ACTIVE 0 sec inserting, thread declared inside InnoDB 5000 mysql tables in use 1, locked 1 3 lock struct(s), heap size 1184, 1 row lock(s), undo log entries 1 --------------------> (LOOK HERE) MySQL thread id 2507, OS thread handle 0x7ff98ead8b00, query id 73514 localhost root update insert into dl2(pk, pk1, data) values(10, 1, 'a0') Foreign key constraint fails for table `test`.`dl2`: , CONSTRAINT `dl2_fk` FOREIGN KEY (`pk1`) REFERENCES `dl1` (`pk`) Trying to add in child table, in index `dl2_fk` tuple: DATA TUPLE: 2 fields; 0: len 4; hex 80000001; asc ;; 1: len 4; hex 8000000a; asc ;; But in parent table `test`.`dl1`, in index `PRIMARY`, the closest match we can find is record: PHYSICAL RECORD: n_fields 1; compact format; info bits 0 0: len 8; hex 696e66696d756d00; asc infimum ;; -------------- ROW OPERATIONS -------------- 0 queries inside InnoDB, 0 queries in queue 0 read views open inside InnoDB 1 RW transactions active inside InnoDB ------------------> (LOOK HERE) 0 RO transactions active inside InnoDB 1 out of 1000 descriptors used Main thread process no. 1242, id 140706194630400, state: sleeping Number of rows inserted 0, updated 0, deleted 0, read 0 0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.00 reads/s Number of system rows inserted 0, updated 0, deleted 0, read 0 0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.00 reads/s -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/deadlock-with-foreign-key-constraints/

1 0

[Maria-discuss] configuration changes to consider in 10.2
by Daniel Black 05 May '16

05 May '16

As major versions are really the only time to consider changing default settings perhaps getting onto the following MDEV soon. https://jira.mariadb.org/browse/MDEV-7635 My main objective is to move the required configuration file down to approximately 0 settings and to work for the majority of people. The sql_mode will cause pain because years of bad practice haven't been fixed, however MySQL-5.7 has gone first and common frameworks are beginning to fix their implementations. They are usually fairly simple fixes to work with the sql_mode of "ONLY_FULL_GROUP_BY STRICT_TRANS_TABLES NO_ZERO_IN_DATE NO_ZERO_DATE ERROR_FOR_DIVISION_BY_ZERO NO_AUTO_CREATE_USER NO_ENGINE_SUBSTITUTION". Finding/making some documentation to describe how to fix this would be good so the google answer doesn't become set sql_mode=''. Lots of suggestions here model MySQL-5.7 defaults with a few of my additions. Please let the list know which changes you agree with, disagree with (any why).

1 0

[Maria-discuss] New Question: Excessive contexting running MariaDB CE Query
by AskMonty KB 04 May '16

04 May '16

Hello, A new question has been asked in "MariaDB Community" by aferrett. Please answer it at http://mariadb.com/kb/en/excessive-contexting-running-mariadb-ce-query/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- I'm working on a MariaDB vs. Oracle query performance issue. We have about 25 queries that we run on MariaDB 10.1.11 vs. Oracle 11.2.0.4. In all cases Oracle is several times faster than MariaDB. The environments are similar: running RHEL 6.5 on VMware guest. I focused on one representative query to drill down. This query runs in 13 seconds on Oracle and 30 seconds on MariaDB. The access plans look the same using the index with columns in the where clause to access the data. I don't see heavy I/O. The longest running step in the profile is below: | Sending data | 29.728961 | 32.786016 | 1.111831 | 100822 | 67799 | The 100822 is Context_voluntary and the 67799 is context involuntary. A the "cs" field in a vmstat jumps up to around 8,000 as soon as I start the query and goes back to hundreds when it ends: procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu----- r b swpd free buff cache si so bi bo in cs us sy id wa st 2 3 89744 74424 103624 6447400 0 0 0 12 2322 9256 56 3 38 4 0 << query running 0 0 89744 74424 103636 6447404 0 0 0 0 152 241 1 0 91 9 0 << query ends My assessment is that the problem is excessive context switches. I tried increasing thread_pool_oversubscribe from 3 to 10, thread_pool_size from 2 to 10, and thread_pool_stall_limit to 1,000 each parameter one at a time and bouncing the instance. In all cases the query runs at a consistent 27-29 seconds. We are also doing heavy parallel insert testing. When we run the job, vmstat cs jumps to the same 8,000 or so. Our Linux SA cannot see any context related configuration differences between the Oracle and MariaDB servers. Any ideas will be appreciated. -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/excessive-contexting-running-mariadb-ce-query/

1 0

[Maria-discuss] ALGORITHM INPLACE for 10.0.24-MariaDB
by Rhys.Campbell＠swisscom.com 04 May '16

04 May '16

Hi All, For the following statement... ALTER ONLINE TABLE dom_audit_event ENGINE=INNODB, ALGORITHM=INPLACE; I can still see that MariaDB is still using the value of tmpdir. We have this set to tmpfs on some of our servers and this causes some ALTER statements on big tables to fail. It was my understanding that if you specified INPLACE then the statement would fail if this was not possible. Am I missing something? Cheers, Rhys

3 3

[Maria-discuss] MariaDB Galera Cluster 10.0.25 now available
by Daniel Bartholomew 03 May '16

03 May '16

The MariaDB project is pleased to announce the immediate availability of MariaDB Galera Cluster 10.0.25. This is a Stable (GA) release. See the Release Notes and Changelog for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB Galera Cluster 10.0.25 - Release Notes: https://mariadb.com/kb/en/mgc-10025-rn/ - Changelog: https://mariadb.com/kb/en/mgc-10025-cl/ - Downloads: https://downloads.mariadb.org/mariadb-galera/10.0.25 About MariaDB Galera Cluster: - https://mariadb.com/kb/en/what-is-mariadb-galera-cluster/ 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: Can't connect to MariaDB through mysql command line client
by AskMonty KB 02 May '16

02 May '16

Hello, A new question has been asked in "MariaDB Community" by chuck_lyon_g. Please answer it at http://mariadb.com/kb/en/cant-connect-to-mariadb-through-mysql-command-line… as the person asking the question may not be subscribed to the mailing list. -------------------------------- I have installed the xampp stack which now includes MariaDB. I have been connecting to it with phpMyAdmin and php scripts through Apache as localhost. This all works with no problem. Today I tried to use the mysql command line tool and got the following error: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory") I checked, and indeed that path does not exist. I did, however find the following path: /opt/lampp/var/mysql/mysql.soc Is it possible that the xampp stack installs the database files in a non-standard location and I need to tell mysql about the change? If so, how? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/cant-connect-to-mariadb-through-mysql-command-line…

1 0

[Maria-discuss] New Question: JDBC driver configuration error
by AskMonty KB 02 May '16

02 May '16

Hello, A new question has been asked in "MariaDB Community" by Intrinsic. Please answer it at http://mariadb.com/kb/en/jdbc-driver-configuration-error/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- I am attempting to connect to MariaDB from a command line Java program. I am getting the "no suitable driver found" error. I am using the mariaDB Type 4 JDBC driver, the JDK 1.8, Windows 10. I have added the maria driver to the lib directory of the JRE, and added this directory to the PATH and CLASSPATH environment variables. I can connect to the mariaDB database using DBVisualizer, when I manually point the configuration of DBVisualizer to the maria driver, so I know that the driver works fine. Here is the Java code: Connection con = DriverManager.getConnection("jdbc:mariadb://localhost:3306/DB?user=root&password=myPassword"); and the error C:\Users\Documents\VTK\Dev>java -cp . VTK3 java.sql.SQLException: No suitable driver found for jdbc:mariadb://localhost:3306/DB?user=root&password=myPassword at java.sql.DriverManager.getConnection(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at VTK3.main(VTK3.java:38) Thanks -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/jdbc-driver-configuration-error/

2 1

[Maria-discuss] MariaDB 10.1.13 sysbench and Fusion-IO PCIE card lock question ?
by Ljr Yang 02 May '16

02 May '16

Hi, All Recently, We use Sysbench Test MariaDB 10.1.13. In Test ,We found server lock and can't write . Testing environment: server1: 10.2.1.242 (HP OEM Fusion IO PCIE Card 3.2TB ) server2: 10.2.1.239 (ScanDisk Fusion IO PCIE Card 3.2TB) sysbench test script: sysbench --test=/usr/share/doc/sysbench/tests/db/oltp.lua --num-threads=16 --mysql-host=localhost --mysql-port=3306 --mysql-socket=/data/mysql2/data/mysql.sock --mysql-user=root --mysql-password=123456 --mysql-db=test --max-time=0 --max-requests=0 --report-interval=1 --oltp-tables-count=16 run when *wsrep_on = on *, after run a few minutes or a few hours, both server1 and server2 were stucked, all write stoped ,only select statement run normal : ................ [ 815s] threads: 16, tps: 6176.00, reads: 86431.00, writes: 24699.00, response time: 3.37ms (95%), errors: 0.00, reconnects: 0.00 [ 816s] threads: 16, tps: 6064.99, reads: 84907.86, writes: 24256.96, response time: 3.66ms (95%), errors: 0.00, reconnects: 0.00 [ 817s] threads: 16, tps: 6097.00, reads: 85394.05, writes: 24394.02, response time: 3.54ms (95%), errors: 0.00, reconnects: 0.00 [ 818s] threads: 16, tps: 6131.97, reads: 85819.52, writes: 24529.86, response time: 3.65ms (95%), errors: 0.00, reconnects: 0.00 [ 819s] threads: 16, tps: 6143.04, reads: 86036.63, writes: 24575.18, response time: 3.44ms (95%), errors: 0.00, reconnects: 0.00 [ 820s] threads: 16, tps: 5819.80, reads: 81532.22, writes: 23332.20, response time: 3.60ms (95%), errors: 0.00, reconnects: 0.00 [ 821s] threads: 16, tps: 0.00, reads: 0.00, writes: 0.00, response time: 0.00ms (95%), errors: 0.00, reconnects: 0.00 [ 822s] threads: 16, tps: 0.00, reads: 0.00, writes: 0.00, response time: 0.00ms (95%), errors: 0.00, reconnects: 0.00 [ 823s] threads: 16, tps: 0.00, reads: 0.00, writes: 0.00, response time: 0.00ms (95%), errors: 0.00, reconnects: 0.00 [ 824s] threads: 16, tps: 0.00, reads: 0.00, writes: 0.00, response time: 0.00ms (95%), errors: 0.00, reconnects: 0.00 [ 825s] threads: 16, tps: 0.00, reads: 0.00, writes: 0.00, response time: 0.00ms (95%), errors: 0.00, reconnects: 0.00 [ 826s] threads: 16, tps: 0.00, reads: 0.00, writes: 0.00, response time: 0.00ms (95%), errors: 0.00, reconnects: 0.00 ................ In error log file not error info , after execute* pstack `pidof mysqld` > pstack.log*, sysbench run normal again , and start write data. Every time have this problem, in pstack.log file contains a few lock: #0 0x00007f2b04fe0334 in __lll_lock_wait () from /lib64/libpthread.so.0 #1 0x00007f2b04fdb5d8 in _L_lock_854 () from /lib64/libpthread.so.0 #2 0x00007f2b04fdb4a7 in pthread_mutex_lock () from /lib64/libpthread.so.0 .................... When *set wsrep_on = off*, Sysbench test MariaDB 10.1.13 normal. As contrast ,We download Percona-XtraDB-Cluster-5.6.28-rel76.1-25.14.1.Linux.x86_64.ssl101.tar.gz and run sysbench test, found same problem too. We can't confirm , is it hardware or galera question ? please help analyze ,thank you. Reference link: https://en.wikibooks.org/wiki/Linux_Applications_Debugging_Techniques/Deadl… http://www.linuxprogrammingblog.com/threads-and-fork-think-twice-before-usi… -- 杨建军

2 1

[Maria-discuss] MariaDB 10.0.25 now available
by Daniel Bartholomew 30 Apr '16

30 Apr '16

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.0.25. This is a Stable (GA) release. See the Release Notes and Changelog for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.0.25 - Release Notes: https://mariadb.com/kb/en/mdb-10025-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10025-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.0.25 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] ERROR 1242 (21000): Subquery returns more than 1 row
by Tristan AURIOL 29 Apr '16

29 Apr '16

Hi everyone, I have a big problem with my application. My application execute this request : INSERT INTO `mydb`.`service_request` ( `id_z`, `id_app`, `request_time`, `priority` ) ( SELECT sc.`id_z`, sc.`id_app`, NOW(), 0 FROM `mydb`.`service_connection` sc JOIN `mydb`.`service` s ON ( s.`id_service` = sc.`id_service` ) WHERE 1=1 AND sc.`id_app` = _utf8'afr' AND s.`status` = 'available' AND ( sc.`last_synchronized_time` < SUBDATE( NOW(), INTERVAL 600 SECOND ) OR sc.`last_synchronized_time` IS NULL ) AND sc.`nb_errors` < 2 AND sc.`id_z` NOT IN ( SELECT sr.`id_z` FROM `mydb`.`service_request` sr WHERE sr.`id_app` = _utf8'afr' AND sr.`status` IN ( 'waiting thu', 'waiting sez', 'in progress' ) ) ) ; This request works well into MySQL 5.6.25-1~dotdeb+7.1 but when I run into 10.1.11-MariaDB-1~jessie-log I have this error: ERROR 1242 (21000): Subquery returns more than 1 row Do you have an idea? Thanks -- *Tristan AURIOL*

3 2

[Maria-discuss] New Question: Coding in MariaDB
by AskMonty KB 27 Apr '16

27 Apr '16

Hello, A new question has been asked in "MariaDB FAQ" by dbamaria. Please answer it at http://mariadb.com/kb/en/coding-in-mariadb/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- hi, I have the following questions: -What is the language used for coding in MariaDB? -As the Oracle package doesn't exist, how MariaDB structure its code ? -Is there a plugin which can call a Java proc in MariaDB , other than the UDF function (as MariaDB cannot call directly a java proc)? Thanks -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/coding-in-mariadb/

1 0

[Maria-discuss] New Question: server do not permit root to log in
by AskMonty KB 26 Apr '16

26 Apr '16

Hello, A new question has been asked in "MariaDB Community" by xav795. Please answer it at http://mariadb.com/kb/en/server-do-not-permit-root-to-log-in/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hi I am trying to start the db with mysqld command the server is getting ready for connections but i cant log in with root because access is denied. I tried to start the server with the skip-grant-access options, and i saw that root does not exist in mysql.USER table. I have many error message when the server starts : 2016-04-27 01:24:11 b7074740 InnoDB: Operating system error number 2 in a file operation. InnoDB: The error means the system cannot find the path specified. InnoDB: If you are installing InnoDB, remember that you must create InnoDB: directories yourself, InnoDB does not create them. 160427 1:24:11 [ERROR] InnoDB: Could not find a valid tablespace file for 'mysql/gtid_slave_pos'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue. 160427 1:24:11 [ERROR] InnoDB: Tablespace open failed for '"mysql"."gtid_slave_pos"', ignored. 2016-04-27 01:24:11 b7074740 InnoDB: Operating system error number 2 in a file operation. InnoDB: The error means the system cannot find the path specified. InnoDB: If you are installing InnoDB, remember that you must create InnoDB: directories yourself, InnoDB does not create them. 160427 1:24:11 [ERROR] InnoDB: Could not find a valid tablespace file for 'mysql/innodb_index_stats'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue. 160427 1:24:11 [ERROR] InnoDB: Tablespace open failed for '"mysql"."innodb_index_stats"', ignored. 160427 1:24:11 [Note] InnoDB: 128 rollback segment(s) are active. 160427 1:24:11 [Note] InnoDB: Waiting for purge to start 160427 1:24:12 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.28-76.1 started; log sequence number 1729734 handlersocket: initialized 160427 1:24:12 server_audit: MariaDB Audit Plugin version 1.4.0 STARTED. 160427 1:24:12 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it 160427 1:24:12 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist Does anybody no what to do with this informations? Regards Xavier -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/server-do-not-permit-root-to-log-in/

1 0

[Maria-discuss] MariaDB Galera Cluster 5.5.49 and Connector updates now available
by Daniel Bartholomew 26 Apr '16

26 Apr '16

The MariaDB project is pleased to announce the immediate availability of: - MariaDB Galera Cluster 5.5.49 - MariaDB Connector/J 1.4.3 - MariaDB Connector/C 2.2.3 These are all Stable (GA) releases. See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB Galera Cluster 5.5.49 - Release Notes: https://mariadb.com/kb/en/mgc-5549-rn/ - Changelog: https://mariadb.com/kb/en/mgc-5549-cl/ - Downloads: https://downloads.mariadb.org/mariadb-galera/5.5.49 About MariaDB Galera Cluster: - https://mariadb.com/kb/en/what-is-mariadb-galera-cluster/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB Connector/J 1.4.3 - Release Notes: https://mariadb.com/kb/en/mcj-143-rn/ - Changelog: https://mariadb.com/kb/en/mcj-143-cl/ - Downloads: https://downloads.mariadb.org/connector-java/1.4.3/ About MariaDB Connector/J: - https://mariadb.com/kb/en/about-mariadb-connector-j/ MariaDB Connector/C 2.2.3 - Release Notes: https://mariadb.com/kb/en/mcc-223-rn/ - Changelog: https://mariadb.com/kb/en/mcc-223-cl/ - Downloads: https://downloads.mariadb.org/connector-c/2.2.3/ About MariaDB Connector/J: - https://mariadb.com/kb/en/about-mariadb-connector-c/ - - 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: Error Starting service
by AskMonty KB 26 Apr '16

26 Apr '16

Hello, A new question has been asked in "MaxScale Getting Started" by cisaksen. Please answer it at http://mariadb.com/kb/en/error-starting-service/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Background: 3 Mariadb Galera servers - 'maxscaleuser'@'hostname%' configured as directed Maxscale 1.4 for SUSE 12 In the maxscale log I see the following errors: Failed to obtain address for host hostname%, Name or service not known. Failed to add user maxscaleuser@hostname% for service [galera service]. This user will be unavailable via maxscale. So I have my maxscaleuser account setup in mysql correctly but it appears that maxscale doesn't like the wildcard % ? is there a way to fix this ? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/error-starting-service/

1 0

[Maria-discuss] MariaDB coding questions
by Ghazi Btissam 26 Apr '16

26 Apr '16

Hi, - As the Oracle package does'nt exist, how MariaDB structure its code ? - Is there a plugin which can call a Java proc in MariaDB , other than the UDF function (as MariaDB cannot call directly a java proc)? Thanks

1 0

[Maria-discuss] InnoDB fake changes
by Federico Razzoli 25 Apr '16

25 Apr '16

Hi all I see that 10.2 still has the innodb_fake_changes variable (OFF by default). That feature was stable in Percona Server 5.5, is beta in 5.6, and was removed in 5.7. Is it still there just for compatibility with old configuration files, or is there still a reason to use it? And in that case, is it stable or not? Regards, Federico

4 3

[Maria-discuss] New Question: Mariadb Columnstore on Windows
by AskMonty KB 25 Apr '16

25 Apr '16

Hello, A new question has been asked in "MariaDB Community" by brian_demilia_g. Please answer it at http://mariadb.com/kb/en/mariadb-columnstore-on-windows/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Does anyone know if the upcoming Columnstore storage engine will be usable on Windows? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/mariadb-columnstore-on-windows/

1 0