November 2016 - discuss - lists.mariadb.org

[Maria-discuss] why stdout? -> [Note] /usr/libexec/mysqld (mysqld 10.0.20-MariaDB) starting as process 115096
by Reindl Harald 05 Jul '20

05 Jul '20

Aug 6 12:24:24 testserver mysqld: 150806 12:24:24 [Note] /usr/libexec/mysqld (mysqld 10.0.20-MariaDB) starting as process 115096 ... why is this now stdout instead mysql logs? on systemd based distributions that spits now to the global syslog and finally on machines restarting 2 instances every hour for backup reasons it annoys until 10.0.19 or 10.0.20 that was not this way

5 13

[Maria-discuss] Missing MariaDB Seal logos?
by Colin Charles 20 Mar '17

20 Mar '17

Hi! Visiting: https://mariadb.com/kb/en/mariadb/branding-guidelines/ You’ll note that the Powered by MariaDB badges still exist (https://mariadb.org/about/logos/) — they should really say Powered by MariaDB Server But what is missing are all the seal logos? Currently beyond the archives at Wikimedia Commons (https://commons.wikimedia.org/wiki/File:Mariadb-seal-browntext.svg), they seem to have disappeared Is this just an oversight and something that needs fixing? Thanks -- Colin Charles, http://bytebot.net/blog/ twitter: @bytebot | skype: colincharles "First they ignore you, then they laugh at you, then they fight you, then you win." -- Mohandas Gandhi

2 1

[Maria-discuss] ON update timestamp replication
by Artem Kuchin 14 Jan '17

14 Jan '17

Hello! Both master and slave run: Server version: 10.1.14-MariaDB FreeBSD Ports Replication is based on mixed format. Slave is used for backups without locking and going off line. I have a script that runs once a day and checksums all tables, so all tables are 100% in match (it wait for sync, locks and checksums). One table is very often out of sync. ON MASTER: show create table Message193; CREATE TABLE `Message193` ( `Message_ID` int(11) NOT NULL AUTO_INCREMENT, `User_ID` int(11) NOT NULL, `Subdivision_ID` int(11) NOT NULL, `Sub_Class_ID` int(11) NOT NULL, `Priority` int(11) NOT NULL DEFAULT '0', `Keyword` char(255) NOT NULL, `ncTitle` varchar(255) DEFAULT NULL, `ncKeywords` varchar(255) DEFAULT NULL, `ncDescription` text, `ncSMO_Title` varchar(255) DEFAULT NULL, `ncSMO_Description` text, `ncSMO_Image` char(255) DEFAULT NULL, `Checked` tinyint(4) NOT NULL DEFAULT '1', `IP` char(15) DEFAULT NULL, `UserAgent` char(255) DEFAULT NULL, `Parent_Message_ID` int(11) NOT NULL DEFAULT '0', `Created` datetime NOT NULL, `LastUpdated` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, `LastUser_ID` int(11) NOT NULL, `LastIP` char(15) DEFAULT NULL, `LastUserAgent` char(255) DEFAULT NULL, `Type` char(255) DEFAULT NULL, `Title` char(255) DEFAULT NULL, `Background` char(255) DEFAULT NULL, `Link` char(255) DEFAULT NULL, PRIMARY KEY (`Message_ID`), UNIQUE KEY `Sub_Class_ID` (`Sub_Class_ID`,`Message_ID`,`Keyword`), KEY `User_ID` (`User_ID`), KEY `LastUser_ID` (`LastUser_ID`), KEY `Subdivision_ID` (`Subdivision_ID`), KEY `Parent_Message_ID` (`Parent_Message_ID`), KEY `Priority` (`Priority`,`LastUpdated`), KEY `Checked` (`Checked`), KEY `Created` (`Created`) ) ENGINE=MyISAM AUTO_INCREMENT=5 DEFAULT CHARSET=utf8 | ON SLAVE CREATE TABLE `Message193` ( `Message_ID` int(11) NOT NULL AUTO_INCREMENT, `User_ID` int(11) NOT NULL, `Subdivision_ID` int(11) NOT NULL, `Sub_Class_ID` int(11) NOT NULL, `Priority` int(11) NOT NULL DEFAULT '0', `Keyword` char(255) NOT NULL, `ncTitle` varchar(255) DEFAULT NULL, `ncKeywords` varchar(255) DEFAULT NULL, `ncDescription` text, `ncSMO_Title` varchar(255) DEFAULT NULL, `ncSMO_Description` text, `ncSMO_Image` char(255) DEFAULT NULL, `Checked` tinyint(4) NOT NULL DEFAULT '1', `IP` char(15) DEFAULT NULL, `UserAgent` char(255) DEFAULT NULL, `Parent_Message_ID` int(11) NOT NULL DEFAULT '0', `Created` datetime NOT NULL, `LastUpdated` timestamp NOT NULL, `LastUser_ID` int(11) NOT NULL, `LastIP` char(15) DEFAULT NULL, `LastUserAgent` char(255) DEFAULT NULL, `Type` char(255) DEFAULT NULL, `Title` char(255) DEFAULT NULL, `Background` char(255) DEFAULT NULL, `Link` char(255) DEFAULT NULL, PRIMARY KEY (`Message_ID`), UNIQUE KEY `Sub_Class_ID` (`Sub_Class_ID`,`Message_ID`,`Keyword`), KEY `User_ID` (`User_ID`), KEY `LastUser_ID` (`LastUser_ID`), KEY `Subdivision_ID` (`Subdivision_ID`), KEY `Parent_Message_ID` (`Parent_Message_ID`), KEY `Priority` (`Priority`,`LastUpdated`), KEY `Checked` (`Checked`), KEY `Created` (`Created`) ) ENGINE=MyISAM AUTO_INCREMENT=5 DEFAULT CHARSET=utf8 | Notice that `LastUpdated` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, on slave becomes `LastUpdated` timestamp NOT NULL, This is already bad enough because if master is lost then slave will not be the same as master, trigger are not restored. Now check records: MASTER MariaDB [anapolisdom_ru]> select * from Message193 limit 1\G *************************** 1. row *************************** Created: 2016-11-25 13:25:09 LastUpdated: 2016-11-25 13:25:09 MariaDB [anapolisdom_ru]> select * from Message193 limit 1\G Created: 2016-11-25 13:25:09 LastUpdated: 0000-00-00 00:00:00 As you see lastupdated field is not replicated at all. Two questions, problems: 1) How to replicate default value and on update part for this field? 2) How to make it replicate the timestamp value? Artem

3 5

[Maria-discuss] rejoin timeout?
by l vic 30 Nov '16

30 Nov '16

How long can it take for a node to sync during a rejoin? Is there environmental variable for that? Thanks, -V

1 0

Re: [Maria-discuss] Aborted connection (CLOSE_CONNECTION)
by Federico Razzoli 30 Nov '16

30 Nov '16

Woops, sorry, I missed the GLOBAL word :) Federico -------------------------------------------- Mer 30/11/16, Ian Gilfillan <ian(a)mariadb.org> ha scritto: Oggetto: Re: [Maria-discuss] Aborted connection (CLOSE_CONNECTION) A: maria-discuss(a)lists.launchpad.net Data: Mercoledì 30 novembre 2016, 15:13 On 30/11/2016 15:13, Federico Razzoli wrote: > This always shows the global value: > SHOW VARIABLES LIKE ... > > This always shows the current session value: > SHOW SESSION VARIABLES LIKE ... This is not correct. SHOW VARIABLES shows the session value: SET GLOBAL wait_timeout=601; SET SESSION wait_timeout=599; SHOW SESSION VARIABLES LIKE 'wait_%'; +---------------+-------+ | Variable_name | Value | +---------------+-------+ | wait_timeout | 599 | +---------------+-------+ SHOW GLOBAL VARIABLES LIKE 'wait_%'; +---------------+-------+ | Variable_name | Value | +---------------+-------+ | wait_timeout | 601 | +---------------+-------+ SHOW VARIABLES LIKE 'wait_%'; +---------------+-------+ | Variable_name | Value | +---------------+-------+ | wait_timeout | 599 | +---------------+-------+ _______________________________________________ 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

Re: [Maria-discuss] Aborted connection (CLOSE_CONNECTION)
by Federico Razzoli 30 Nov '16

30 Nov '16

This always shows the global value: SHOW VARIABLES LIKE ... This always shows the current session value: SHOW SESSION VARIABLES LIKE ... Global value is read from the files when the server starts, and later can be changed with SET GLOBAL var = val. Session value is copied from global value when the session starts (so changing the global value doesn't affect existing sessions) and can later be changed with SET var = val. In other words, the global value is important because it is used by all new sessions by default, but the session value is what really takes effect. I beleive that your application sets a session value. Federico -------------------------------------------- Mer 30/11/16, Florent B <florent(a)coppint.com> ha scritto: Oggetto: Re: [Maria-discuss] Aborted connection (CLOSE_CONNECTION) A: "Federico Razzoli" <federico_raz(a)yahoo.it>, maria-discuss(a)lists.launchpad.net Data: Mercoledì 30 novembre 2016, 10:44 Ok, I found the problem thanks to you Federico. On Debian, mysql-common package provided by MariaDB repository contains "wait_timeout = 600" in my.cnf. This is not the default value specified in documentation (28800). And when I use "mysql -u root -p -h my_host" command to show variables, the default value is displayed (28800), I never saw 600 in here ! Why ? But displaying variables in my PHP app showed me that wait_timeout was effectively set to 600. Setting wait_timeout=28800 in a config file in /etc/mysql/conf.d directory fixes this. Should we consider "wait_timeout = 600" in my.cnf as a bug ? That's not default value... On 11/29/2016 11:17 PM, Federico Razzoli wrote: > Interesting. A couple ideas: > > 1 > Try this query: > SHOW SESSION VARIABLES LIKE '%timeout%'; > But this time, this should be executed by PHP, using the same library used by the application. Why? To check if a library changes a timeout at session level. > > 2 > Have you checked if your application reconnects N times? For example, 600 could be a 60 seconds timeout * 10 attempts. > > Federico > > > -------------------------------------------- > Mar 29/11/16, Florent B <florent(a)coppint.com> ha scritto: > > Oggetto: Re: [Maria-discuss] Aborted connection (CLOSE_CONNECTION) > A: "Reindl Harald" <h.reindl(a)thelounge.net>, maria-discuss(a)lists.launchpad.net > Data: Martedì 29 novembre 2016, 12:22 > > On 11/29/2016 12:03 PM, > Reindl Harald wrote: > > > > > > Am 29.11.2016 um > 11:49 schrieb Florent B: > >> For > example, if I try this in PHP: > >> > >> 1/ Connect to mariadb > >> > >> 2/ sleep 610 > seconds > >> > >> 3/ > ping mariadb > >> > >> => I got Server has gone away > error. > >> > >> > With a 590 sleep time, no error. > >> > >> I use MariaDB 10.1, didn't change > any "timeout" value in MariaDB : > >> interactive_timeout & wait_timeout > are 28800 > > > > http://php.net/manual/en/mysqlnd.config.php#ini.mysqlnd.net-read-timeout > > > > Hi, and > thank you. But I cannot find any timeout of 600 > seconds... > default_socket_timeout = 60 > mysqlnd.net_read_timeout = 31536000 > > And I have the exactly same > problem using this algorithm in Python, it's > not related to PHP... > > _______________________________________________ > 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 > > > _______________________________________________ > 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

2 1

Re: [Maria-discuss] Aborted connection (CLOSE_CONNECTION)
by Federico Razzoli 29 Nov '16

29 Nov '16

Interesting. A couple ideas: 1 Try this query: SHOW SESSION VARIABLES LIKE '%timeout%'; But this time, this should be executed by PHP, using the same library used by the application. Why? To check if a library changes a timeout at session level. 2 Have you checked if your application reconnects N times? For example, 600 could be a 60 seconds timeout * 10 attempts. Federico -------------------------------------------- Mar 29/11/16, Florent B <florent(a)coppint.com> ha scritto: Oggetto: Re: [Maria-discuss] Aborted connection (CLOSE_CONNECTION) A: "Reindl Harald" <h.reindl(a)thelounge.net>, maria-discuss(a)lists.launchpad.net Data: Martedì 29 novembre 2016, 12:22 On 11/29/2016 12:03 PM, Reindl Harald wrote: > > > Am 29.11.2016 um 11:49 schrieb Florent B: >> For example, if I try this in PHP: >> >> 1/ Connect to mariadb >> >> 2/ sleep 610 seconds >> >> 3/ ping mariadb >> >> => I got Server has gone away error. >> >> With a 590 sleep time, no error. >> >> I use MariaDB 10.1, didn't change any "timeout" value in MariaDB : >> interactive_timeout & wait_timeout are 28800 > > http://php.net/manual/en/mysqlnd.config.php#ini.mysqlnd.net-read-timeout > Hi, and thank you. But I cannot find any timeout of 600 seconds... default_socket_timeout = 60 mysqlnd.net_read_timeout = 31536000 And I have the exactly same problem using this algorithm in Python, it's not related to PHP... _______________________________________________ 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

Re: [Maria-discuss] Aborted connection (CLOSE_CONNECTION)
by Reindl Harald 29 Nov '16

29 Nov '16

Am 29.11.2016 um 12:22 schrieb Florent B: > On 11/29/2016 12:03 PM, Reindl Harald wrote: >> Am 29.11.2016 um 11:49 schrieb Florent B: >>> For example, if I try this in PHP: >>> >>> 1/ Connect to mariadb >>> 2/ sleep 610 seconds >>> 3/ ping mariadb >>> => I got Server has gone away error. >>> With a 590 sleep time, no error. >>> I use MariaDB 10.1, didn't change any "timeout" value in MariaDB : >>> interactive_timeout & wait_timeout are 28800 >> >> http://php.net/manual/en/mysqlnd.config.php#ini.mysqlnd.net-read-timeout > > Hi, and thank you. But I cannot find any timeout of 600 seconds... > default_socket_timeout = 60 > mysqlnd.net_read_timeout = 31536000 > > And I have the exactly same problem using this algorithm in Python, it's > not related to PHP... then pretty sure you mysqld timeouts are not what you think, otherwise we would see the same issues on our dbmail machines when after hours of idle postfix tries to re-use it's connections (and we did have such events when that values where too low) so why don't you ask the server instead pretend they are not lowered? MariaDB [(none)]> show variables like 'wait_timeout'; +---------------+-------+ | Variable_name | Value | +---------------+-------+ | wait_timeout | 300 | +---------------+-------+ 1 row in set (0.00 sec) MariaDB [(none)]> show variables like 'wait_timeout'; +---------------+--------+ | Variable_name | Value | +---------------+--------+ | wait_timeout | 604800 | +---------------+--------+ 1 row in set (0.00 sec) wait_timeout = 604800 interactive_timeout = 604800

1 0

Re: [Maria-discuss] Aborted connection (CLOSE_CONNECTION)
by Stephane VAROQUI 29 Nov '16

29 Nov '16

Stéphane Varoqui, Senior Consultant Phone: +33 695-926-401, skype: svaroqui http://www.mariadb.com <http://www.mariadb.com/> > Le 29 Nov 2016 à 12:22, Florent B <florent(a)coppint.com> a écrit : > > On 11/29/2016 12:03 PM, Reindl Harald wrote: >> >> >> Am 29.11.2016 um 11:49 schrieb Florent B: >>> For example, if I try this in PHP: >>> >>> 1/ Connect to mariadb >>> >>> 2/ sleep 610 seconds >>> >>> 3/ ping mariadb >>> >>> => I got Server has gone away error. >>> >>> With a 590 sleep time, no error. >>> >>> I use MariaDB 10.1, didn't change any "timeout" value in MariaDB : >>> interactive_timeout & wait_timeout are 28800 >> >> http://php.net/manual/en/mysqlnd.config.php#ini.mysqlnd.net-read-timeout >> > > Hi, and thank you. But I cannot find any timeout of 600 seconds... > default_socket_timeout = 60 > mysqlnd.net_read_timeout = 31536000 > > And I have the exactly same problem using this algorithm in Python, it's > not related to PHP… > Have you check your TCP settings or may be some firewall or proxy that would just sit in the middle ? > _______________________________________________ > 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

Re: [Maria-discuss] Aborted connection (CLOSE_CONNECTION)
by Reindl Harald 29 Nov '16

29 Nov '16

Am 29.11.2016 um 11:49 schrieb Florent B: > For example, if I try this in PHP: > > 1/ Connect to mariadb > > 2/ sleep 610 seconds > > 3/ ping mariadb > > => I got Server has gone away error. > > With a 590 sleep time, no error. > > I use MariaDB 10.1, didn't change any "timeout" value in MariaDB : > interactive_timeout & wait_timeout are 28800 http://php.net/manual/en/mysqlnd.config.php#ini.mysqlnd.net-read-timeout

1 0