MariaDB on OpenSuSE

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

MariaDB on OpenSuSE

Hans Scheffers-2
Hi,

I am using a mariadb on opensuse 13.1 ppc as slave to a mariadb on a opensuse x86.
The database is a ido2db  from icinga2, with 303 servers and 8300 services, a lot of services are checked every 2 miniutes (business need), so there is some database traffic (query logging overnoight is about 5G).

almost every 5  minutes, MariaDB crashes & restarts:

150424 10:03:06  InnoDB: Assertion failure in thread 35184305402272 in file buf0buf.ic line 1277
InnoDB: Failing assertion: block->page.buf_fix_count> 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
150424 10:03:06 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 5.5.33-MariaDB-log
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=4
max_threads=153
thread_count=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466709 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x10030a4fcb0
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 = 0x1ffffc0666b8 thread_stack 0x48000
??:0(??)[0x107dfbb4]
??:0(??)[0x10341264]
??:0(??)[0x1ffffffa0478]
??:0(??)[0x1fffff7109ec]
??:0(??)[0x10764dd8]
??:0(??)[0x1064ddb8]
??:0(??)[0x1061ab80]
??:0(??)[0x1034e02c]
??:0(??)[0x1022181c]
??:0(??)[0x102102a0]
??:0(??)[0x10204410]
??:0(??)[0x102102b8]
??:0(??)[0x10204410]
??:0(??)[0x102102f0]
??:0(??)[0x10204410]
??:0(??)[0x102102b8]
??:0(??)[0x10204410]
??:0(??)[0x102102b8]
??:0(??)[0x10204410]
??:0(??)[0x102102f0]
??:0(??)[0x102206b0]
??:0(??)[0x10232318]
??:0(??)[0x1026f440]
??:0(??)[0x101b4ed8]
??:0(??)[0x101b6740]
??:0(??)[0x10210098]
??:0(??)[0x1021045c]
??:0(??)[0x102206b0]
??:0(??)[0x10232318]
??:0(??)[0x1022d89c]
??:0(??)[0x1022e12c]
??:0(??)[0x101d3de8]
??:0(??)[0x101dcc74]
??:0(??)[0x101e11b8]
??:0(??)[0x101e347c]
??:0(??)[0x101e3ea8]
??:0(??)[0x102adee4]
??:0(??)[0x102adfe0]
??:0(??)[0x1fffffe9c8b0]
??:0(??)[0x1fffff7cc4e0]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x1fffac0f0d08): is an invalid pointer
Connection ID (thread ID): 106
Status: NOT_KILLED

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

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.
150424 10:03:06 mysqld_safe Number of processes running now: 0
150424 10:03:06 mysqld_safe Number of processes running now: 0
150424 10:03:06 mysqld_safe mysqld restarted
150424 10:03:06 mysqld_safe mysqld restarted
150424 10:03:07 InnoDB: The InnoDB memory heap is disabled
150424 10:03:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150424 10:03:07 InnoDB: Compressed tables use zlib 1.2.8
150424 10:03:07 InnoDB: Using Linux native AIO
150424 10:03:07 InnoDB: Initializing buffer pool, size = 128.0M
150424 10:03:07 InnoDB: Completed initialization of buffer pool
150424 10:03:07 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 5044365839
150424 10:03:07  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 5044919067
150424 10:03:07  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: In a MySQL replication slave the last master binlog file
InnoDB: position 298320530, file name mysql-bin.003594
InnoDB: and relay log file
InnoDB: position 44279422, file name ./mysql-relay-bin.000182
InnoDB: Last MySQL binlog file position 0 44277256, file name ./mysql-bin.000092
150424 10:03:07  InnoDB: Waiting for the background threads to start
150424 10:03:08 Percona XtraDB (http://www.percona.com) 5.5.33-MariaDB-31.1 started; log sequence number 5044919067
150424 10:03:08 [Note] Recovering after a crash using mysql-bin
150424 10:03:08 [Note] Starting crash recovery...
150424 10:03:08 [Note] Crash recovery finished.
150424 10:03:08 [Note] Server socket created on IP: '0.0.0.0'.
150424 10:03:08 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.003594' at position 298320530, relay log './mysql-relay-bin.000182' position: 44279422
150424 10:03:08 [Note] Event Scheduler: Loaded 0 events
150424 10:03:08 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.33-MariaDB-log'  socket: '/var/run/mysql/mysql.sock'  port: 3306  openSUSE package
150424 10:03:08 [Note] Slave I/O thread: connected to master 'nagadmin@172.17.99.37:3306',replication started in log 'mysql-bin.003594' at position 298320530
150424 10:03:08 [Warning] Slave I/O: Notifying master by SET @master_binlog_checksum= @@global.binlog_checksum failed with error: Unknown system variable 'binlog_checksum', Error_code: 1193
I have seen this error on internet, solutions seems to be an update... But for opensuse 13.1 there is no update for mariadb 5.5.33-2.16
Anyone an idea how to solve this?


Hans Scheffers
AIX / Linux Systeembeheer    --
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: MariaDB on OpenSuSE

Alexander Graf-4
Hi Hans,

On 04/24/2015 10:49 AM, Hans Scheffers wrote:
> Hi,
>
> I am using a mariadb on opensuse 13.1 ppc as slave to a mariadb on a opensuse x86.

Is this big endian or little endian ppc? I seem to recall that there
were some fixes in mariadb necessary for LE.


Alex

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

FW: [opensuse-ppc] MariaDB on OpenSuSE

Hans Scheffers-2
Hi Alex

The system runs on IBM Power 7, so that should be Big Endian, am i correct?


Hans Scheffers

AIX / Linux Systeembeheer


> Date: Mon, 27 Apr 2015 15:59:32 +0200
> From: [hidden email]
> To: [hidden email]; [hidden email]
> Subject: Re: [opensuse-ppc] MariaDB on OpenSuSE
>
> Hi Hans,
>
> On 04/24/2015 10:49 AM, Hans Scheffers wrote:
>> Hi,
>>
>> I am using a mariadb on opensuse 13.1 ppc as slave to a mariadb on a opensuse x86.
>
> Is this big endian or little endian ppc? I seem to recall that there
> were some fixes in mariadb necessary for LE.
>
>
> Alex
>
> --
> To unsubscribe, e-mail: [hidden email]
> To contact the owner, e-mail: [hidden email]
>
         --
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: MariaDB on OpenSuSE

Alexander Graf-4
In reply to this post by Alexander Graf-4


On 27.04.15 22:26, Hans Scheffers wrote:
> Hi Alex
>
> The system runs on IBM Power 7, so that should be Big Endian, am i correct?

Power7 can run both LE and BE. What does uname -a say?


Alex
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: MariaDB on OpenSuSE

Andreas Färber
Am 27.04.2015 um 22:30 schrieb Alexander Graf:
> On 27.04.15 22:26, Hans Scheffers wrote:
>> The system runs on IBM Power 7, so that should be Big Endian, am i correct?
>
> Power7 can run both LE and BE. What does uname -a say?

13.1 did not yet have ppc64le, so BE. :)

Cheers,
Andreas

--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: MariaDB on OpenSuSE

Alexander Graf-4


On 28.04.15 01:28, Andreas Färber wrote:
> Am 27.04.2015 um 22:30 schrieb Alexander Graf:
>> On 27.04.15 22:26, Hans Scheffers wrote:
>>> The system runs on IBM Power 7, so that should be Big Endian, am i correct?
>>
>> Power7 can run both LE and BE. What does uname -a say?
>
> 13.1 did not yet have ppc64le, so BE. :)

Oh, I didn't realize it's 13.1, sorry ;). Then I don't know. Does it
work on 13.2?


Alex
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: MariaDB on OpenSuSE

Hans Scheffers-2
Hi

I haven't upgraded any of our partitions to 13.2 yet, so I can't say it  would work on 13.2

I did try to install the mariaDB version included with 13.2 (mariadb-10.0.13-2.3.1.ppc64), this version also crashed, but even more harsh (database corruption), so i went back to the current version.

Over the weekend the mysql threads have crashed, but recovered by mySQL self (and a lot less). The only difference with normal working hours is that there are no requests from icinga-web2 to read out the data.

So it looks like select queries (including all kind of joins ;) ) are the biggest reason for crashing...


Hans Scheffers
AIX / Linux Systeembeheer


----------------------------------------

> Date: Tue, 28 Apr 2015 09:52:28 +0200
> From: [hidden email]
> To: [hidden email]; [hidden email]
> CC: [hidden email]
> Subject: Re: [opensuse-ppc] MariaDB on OpenSuSE
>
>
>
> On 28.04.15 01:28, Andreas Färber wrote:
>> Am 27.04.2015 um 22:30 schrieb Alexander Graf:
>>> On 27.04.15 22:26, Hans Scheffers wrote:
>>>> The system runs on IBM Power 7, so that should be Big Endian, am i correct?
>>>
>>> Power7 can run both LE and BE. What does uname -a say?
>>
>> 13.1 did not yet have ppc64le, so BE. :)
>
> Oh, I didn't realize it's 13.1, sorry ;). Then I don't know. Does it
> work on 13.2?
>
>
> Alex
> --
> To unsubscribe, e-mail: [hidden email]
> To contact the owner, e-mail: [hidden email]
>
     --
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: MariaDB on OpenSuSE

Hans Scheffers-3
Does someone have rpm's voor mariadb 5.5.42 or so?

Hans Scheffers
AIX / Linux Systeembeheer


----------------------------------------

> From: [hidden email]
> To: [hidden email]
> Subject: RE: [opensuse-ppc] MariaDB on OpenSuSE
> Date: Tue, 28 Apr 2015 10:45:34 +0200
>
> Hi
>
> I haven't upgraded any of our partitions to 13.2 yet, so I can't say it  would work on 13.2
>
> I did try to install the mariaDB version included with 13.2 (mariadb-10.0.13-2.3.1.ppc64), this version also crashed, but even more harsh (database corruption), so i went back to the current version.
>
> Over the weekend the mysql threads have crashed, but recovered by mySQL self (and a lot less). The only difference with normal working hours is that there are no requests from icinga-web2 to read out the data.
>
> So it looks like select queries (including all kind of joins ;) ) are the biggest reason for crashing...
>
>
> Hans Scheffers
> AIX / Linux Systeembeheer
>
>
> ----------------------------------------
>> Date: Tue, 28 Apr 2015 09:52:28 +0200
>> From: [hidden email]
>> To: [hidden email]; [hidden email]
>> CC: [hidden email]
>> Subject: Re: [opensuse-ppc] MariaDB on OpenSuSE
>>
>>
>>
>> On 28.04.15 01:28, Andreas Färber wrote:
>>> Am 27.04.2015 um 22:30 schrieb Alexander Graf:
>>>> On 27.04.15 22:26, Hans Scheffers wrote:
>>>>> The system runs on IBM Power 7, so that should be Big Endian, am i correct?
>>>>
>>>> Power7 can run both LE and BE. What does uname -a say?
>>>
>>> 13.1 did not yet have ppc64le, so BE. :)
>>
>> Oh, I didn't realize it's 13.1, sorry ;). Then I don't know. Does it
>> work on 13.2?
>>
>>
>> Alex
>> --
>> To unsubscribe, e-mail: [hidden email]
>> To contact the owner, e-mail: [hidden email]
>>
> --
> To unsubscribe, e-mail: [hidden email]
> To contact the owner, e-mail: [hidden email]
>
     --
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: MariaDB on OpenSuSE

Dinar Valeev-2
On Wed, Apr 29, 2015 at 12:40 PM, Hans Scheffers
<[hidden email]> wrote:
> Does someone have rpm's voor mariadb 5.5.42 or so?
If you're looking more recent version, it is not a problem to build one.

>
> Hans Scheffers
> AIX / Linux Systeembeheer
>
>
> ----------------------------------------
>> From: [hidden email]
>> To: [hidden email]
>> Subject: RE: [opensuse-ppc] MariaDB on OpenSuSE
>> Date: Tue, 28 Apr 2015 10:45:34 +0200
>>
>> Hi
>>
>> I haven't upgraded any of our partitions to 13.2 yet, so I can't say it  would work on 13.2
>>
>> I did try to install the mariaDB version included with 13.2 (mariadb-10.0.13-2.3.1.ppc64), this version also crashed, but even more harsh (database corruption), so i went back to the current version.
>>
>> Over the weekend the mysql threads have crashed, but recovered by mySQL self (and a lot less). The only difference with normal working hours is that there are no requests from icinga-web2 to read out the data.
>>
>> So it looks like select queries (including all kind of joins ;) ) are the biggest reason for crashing...
>>
>>
>> Hans Scheffers
>> AIX / Linux Systeembeheer
>>
>>
>> ----------------------------------------
>>> Date: Tue, 28 Apr 2015 09:52:28 +0200
>>> From: [hidden email]
>>> To: [hidden email]; [hidden email]
>>> CC: [hidden email]
>>> Subject: Re: [opensuse-ppc] MariaDB on OpenSuSE
>>>
>>>
>>>
>>> On 28.04.15 01:28, Andreas Färber wrote:
>>>> Am 27.04.2015 um 22:30 schrieb Alexander Graf:
>>>>> On 27.04.15 22:26, Hans Scheffers wrote:
>>>>>> The system runs on IBM Power 7, so that should be Big Endian, am i correct?
>>>>>
>>>>> Power7 can run both LE and BE. What does uname -a say?
>>>>
>>>> 13.1 did not yet have ppc64le, so BE. :)
>>>
>>> Oh, I didn't realize it's 13.1, sorry ;). Then I don't know. Does it
>>> work on 13.2?
>>>
>>>
>>> Alex
>>> --
>>> To unsubscribe, e-mail: [hidden email]
>>> To contact the owner, e-mail: [hidden email]
>>>
>> --
>> To unsubscribe, e-mail: [hidden email]
>> To contact the owner, e-mail: [hidden email]
>>
>                                           --
> To unsubscribe, e-mail: [hidden email]
> To contact the owner, e-mail: [hidden email]
>
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: MariaDB on OpenSuSE

Hans Scheffers
Hi Dinar,

It would be nice to be able to test with newer versions on OpenSuSE 13.1 ppc



Hans Scheffers
AIX / Linux Systeembeheer


----------------------------------------

> From: [hidden email]
> Date: Wed, 29 Apr 2015 13:27:51 +0200
> Subject: Re: [opensuse-ppc] MariaDB on OpenSuSE
> To: [hidden email]
> CC: [hidden email]
>
> On Wed, Apr 29, 2015 at 12:40 PM, Hans Scheffers
> <[hidden email]> wrote:
>> Does someone have rpm's voor mariadb 5.5.42 or so?
> If you're looking more recent version, it is not a problem to build one.
>>
>> Hans Scheffers
>> AIX / Linux Systeembeheer
>>
>>
>> ----------------------------------------
>>> From: [hidden email]
>>> To: [hidden email]
>>> Subject: RE: [opensuse-ppc] MariaDB on OpenSuSE
>>> Date: Tue, 28 Apr 2015 10:45:34 +0200
>>>
>>> Hi
>>>
>>> I haven't upgraded any of our partitions to 13.2 yet, so I can't say it would work on 13.2
>>>
>>> I did try to install the mariaDB version included with 13.2 (mariadb-10.0.13-2.3.1.ppc64), this version also crashed, but even more harsh (database corruption), so i went back to the current version.
>>>
>>> Over the weekend the mysql threads have crashed, but recovered by mySQL self (and a lot less). The only difference with normal working hours is that there are no requests from icinga-web2 to read out the data.
>>>
>>> So it looks like select queries (including all kind of joins ;) ) are the biggest reason for crashing...
>>>
>>>
>>> Hans Scheffers
>>> AIX / Linux Systeembeheer
>>>
>>>
>>> ----------------------------------------
>>>> Date: Tue, 28 Apr 2015 09:52:28 +0200
>>>> From: [hidden email]
>>>> To: [hidden email]; [hidden email]
>>>> CC: [hidden email]
>>>> Subject: Re: [opensuse-ppc] MariaDB on OpenSuSE
>>>>
>>>>
>>>>
>>>> On 28.04.15 01:28, Andreas Färber wrote:
>>>>> Am 27.04.2015 um 22:30 schrieb Alexander Graf:
>>>>>> On 27.04.15 22:26, Hans Scheffers wrote:
>>>>>>> The system runs on IBM Power 7, so that should be Big Endian, am i correct?
>>>>>>
>>>>>> Power7 can run both LE and BE. What does uname -a say?
>>>>>
>>>>> 13.1 did not yet have ppc64le, so BE. :)
>>>>
>>>> Oh, I didn't realize it's 13.1, sorry ;). Then I don't know. Does it
>>>> work on 13.2?
>>>>
>>>>
>>>> Alex
>>>> --
>>>> To unsubscribe, e-mail: [hidden email]
>>>> To contact the owner, e-mail: [hidden email]
>>>>
>>> --
>>> To unsubscribe, e-mail: [hidden email]
>>> To contact the owner, e-mail: [hidden email]
>>>
>> --
>> To unsubscribe, e-mail: [hidden email]
>> To contact the owner, e-mail: [hidden email]
>>
> --
> To unsubscribe, e-mail: [hidden email]
> To contact the owner, e-mail: [hidden email]
>
     --
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]