#maria Log v0.1

logs Catalogue

This page loads from the db, refresh as and when. It displays 24 hrs
For older data http://marialog.archivist.info/previous.php, logs go back to 2009-01-18
Some user stats
Table logs
date_time
user
message
2016-07-01 08:44:37
MrTopless
Hi
2016-07-01 08:44:59
MrTopless
I have some problems with 10.0.26-MariaDB MariaDB Server
2016-07-01 08:45:08
MrTopless
on Centos 7
2016-07-01 08:45:37
MrTopless
Sometimes it crashes and after crash it becomes undefinable by process manager
2016-07-01 08:45:56
MrTopless
And as well php7 module disappear, and after reboot i have to reinstall it again with ym
2016-07-01 08:45:58
MrTopless
yum
2016-07-01 08:46:41
MrTopless
php70w-mysql x86_64 7.0.7-1.w7 webtatic 82 k
2016-07-01 08:46:49
MrTopless
MariaDB-shared x86_64 10.0.26-1.el7.centos mariadb 1.2 M
2016-07-01 10:02:31
chargen
Hi. I'm having problems setting the galera cluster. I'm testing with 3 does but seem they aren't connected.
2016-07-01 10:02:43
chargen
I get that the cluster size is 1 in all of them.
2016-07-01 10:20:23
jplindst
chargen: Do you get any error messages to joining side or donor side ?
2016-07-01 10:21:08
chargen
I'm getting some errors now running "mysqld bootstrap"
2016-07-01 10:21:26
chargen
https://gist.github.com/abc08f775277d5606d2308ee438842c5
2016-07-01 10:31:45
chargen
jplindst: How can I see these errors?
2016-07-01 10:34:05
jplindst
chargen: looking from error log
2016-07-01 10:35:32
jplindst
ok, your joiner can't connect to donor, either the problem is on configuration or network settings
2016-07-01 10:36:04
jplindst
11490816 [ERROR] WSREP: failed to open gcomm backend connection: 110: failed to reach primary view: 110 (Connection timed out)
2016-07-01 10:36:04
jplindst
at gcomm/src/pc.cpp:connect():162
2016-07-01 10:44:02
chargen
wsrep_incoming_addresses | 192.168.99.106:3306
2016-07-01 10:44:13
chargen
that address is right
2016-07-01 10:44:49
chargen
I can connect to other nodes from mysql cli with no problem
2016-07-01 10:45:46
chargen
jplindst: do galera use a specific user?
2016-07-01 10:46:24
jplindst
for sst yes
2016-07-01 10:52:53
jplindst
chargen: see http://galeracluster.com/documentation-webpages/sst.html
2016-07-01 10:53:47
chargen
I'm using rsync
2016-07-01 10:54:19
jplindst
ok, then it has to be network issue
2016-07-01 11:00:47
chargen
I'm using docker
2016-07-01 11:01:04
chargen
For some reason it uses that weird ip 172.17.0.1
2016-07-01 11:01:21
chargen
and it wasn't in /etc/hosts
2016-07-01 11:01:31
chargen
there was 172.17.0.2 instead
2016-07-01 11:02:20
chargen
jplindst: I got only this error now: 2016-07-01 9:59:38 139798445652736 [Note] WSREP: New cluster view: global state: :-1, view# 0: Primary, number of nodes: 1, my index: 0, protocol version 3
2016-07-01 11:02:20
chargen
2016-07-01 9:59:38 139798445967616 [ERROR] WSREP: SST failed: 1 (Operation not permitted)
2016-07-01 11:02:29
chargen
do you know what it means?
2016-07-01 11:03:03
chargen
here's the gist: https://gist.github.com/jmolero/0e06038b0b519c54f50b69b1892d0075
2016-07-01 11:17:20
chargen
jplindst: I got it working. I just had to add the set user
2016-07-01 11:17:31
chargen
thanks a lot for your help :)
2016-07-01 11:17:41
chargen
sst*
2016-07-01 11:18:01
jplindst
np
2016-07-01 14:37:13
ctarquini
hey guys
2016-07-01 14:37:51
ctarquini
could this error: WSREP: Failed to report last committed [...] -4 (Interrupted system call) be the result of high disk I/O?
2016-07-01 14:38:06
ctarquini
it's in the logs right before a galera node starts kernel panicking
2016-07-01 16:11:18
tom[]
is it possible to monitor the galera replicated operations from a given node? like watching a log of the replicated writesets?
2016-07-01 16:17:49
nirbhay_
tom[], enable binary logging on that node (--log-bin) and the statements/transactions (writesets) originating from that node will get logged.
2016-07-01 16:18:29
tom[]
nirbhay_: tnx
2016-07-01 16:19:36
nirbhay_
ctarquini, IIUC that's a warning and can be ignored.
2016-07-01 16:19:57
nirbhay_
ctarquini, What's up with kernel panic? Could you elaborate?
2016-07-01 17:35:09
ctarquini
nirbhay: not sure, it seems to happen every once and a while on all the nodes, it certainly wasn't doing that for the last 6 months. The dump looks like it was doing ext4 related things but the logs were cleared after it rebooted
2016-07-01 17:35:36
ctarquini
nirbhay: from what I can tell, it seems to coincide with a spike in I/O
2016-07-01 17:38:45
nirbhay
ctarquini, ok
2016-07-01 20:29:39
YesMan
Hello
2016-07-01 20:31:13
YesMan
I was looking for a database system for my webserver, and this one seems to best suit my needs (which are limited). However the debian package for v10 is 150MB and I was wondering if there wasn't a lighter version
2016-07-01 20:31:37
mgriffin
YesMan: did you consider sqlite?
2016-07-01 20:32:56
YesMan
Yes however I was recommended mariaDb because of the compatibility with OwnCloud and OctoPrint
2016-07-01 20:33:35
thumbs
so anyway, what's wrong with a 150 package?
2016-07-01 20:34:41
YesMan
Nothing, it's just that's its quite large compared to the rest of the software I require, and the whole thing is running of a raspberry pi with a small system partition
2016-07-01 20:37:51
mgriffin
YesMan: i did a sandbox install just now of mysql 5.5 from tar, just binaries and the ib_logfile files and it was ~250M
2016-07-01 20:38:03
mgriffin
YesMan: so expect another ~100M just for an empty datadir
2016-07-01 20:44:07
YesMan
mgriffin: Thanks you for the information, well my 800kB nginx server will have a new fat friend ;)
2016-07-02 01:41:11
jak2000
when execute a mysqldump command i get this error: "mysqldump: mysqldump: Couldn't execute 'SET OPTION SQL_QUOTE_SHOW_CREATE=1': Unknown system variable 'OPTION' (1193)"
2016-07-02 01:41:17
jak2000
how to fix?
2016-07-02 02:01:01
mgriffin
sounds like old server with new client.
2016-07-02 02:01:22
mgriffin
or flip that..