maria-discuss team mailing list archive

[Reindl Harald <h.reindl@xxxxxxxxxxxxx>]

Am 02.09.19 um 18:05 schrieb Faustin Lammler:
> After reading the recent thread on systemd devel ML (/etc/fstab 
> obsolete?) I kind of find your tone a bit inappropriate. May I
> suggest you to try to start by applying your advice to yourself.

that stupid behavior of mariadb was pointed out often enough

> This is clearly not a
>> good start for a discussion
> 
> https://lists.freedesktop.org/archives/systemd-devel/2019-August/043349.html
>
>  Reindl Harald <h.reindl@xxxxxxxxxxxxx>, 02/09/2019 – 17:20:36
> (+0200):
> 
>> bullshit
>> 
>> the part you skipped in your quote contains clearly "Version: 
>> '10.2.26-MariaDB'" and is a full mysqld log (cleaned before
>> restart) with 'innodb_support_xa=1' in the config
> Maybe giving us the version you are upgrading from would have been
> a better starting point.

maybe read what i wrote instead cut down my post by the first line
would be a god start too or simply shut up when you are too lazy read
a log starting with "Normal shutdown" and ending with "Version:
'10.2.26-MariaDB'" leaded by "come on and show me!" would be a good start!

* one pretends 10.2 has a deprecation warning
* i repsoned with "show me" and a full log of a recent 10.2 restart
* you come up with "since you skipped over directly to 10.3"

seriously?

-----------

Am 02.09.19 um 17:09 schrieb Marko Mäkelä:
> On Mon, Sep 2, 2019 at 5:43 PM Reindl Harald
<h.reindl@xxxxxxxxxxxxx> wrote:
>> unknown variable 'innodb_support_xa=1'
>> 
>> would you funny guys consider things like deperectaion warnings
>> in previous releases
> 
> A deprecation warning was added in the MariaDB Server 10.2.2, well 
> before it was Generally Available. That said, maybe there is a
> nontrivial amount of users who skipped the 10.2 release and
> upgraded straight from 10.1 to 10.3.

come on and show me!

[root@localhost:~]$ cat mysql_error.log
2019-09-02 17:11:43 139645497730816 [Note] /usr/libexec/mysqld
(initiated by: unknown): Normal shutdown
2019-09-02 17:11:43 139645073479424 [Note] InnoDB: FTS optimize thread
exiting.
2019-09-02 17:11:43 139645497730816 [Note] Event Scheduler: Purging the
queue. 0 events
2019-09-02 17:11:43 139645498156800 [Note] Error reading relay log
event: slave SQL thread was killed
2019-09-02 17:11:43 139645498156800 [Note] Slave SQL thread exiting,
replication stopped in log 'bin.002679' at position 49489
2019-09-02 17:11:43 139645498464000 [Note] Slave I/O thread exiting,
read up to log 'bin.002679', position 49489
2019-09-02 17:11:43 139645497730816 [Note] InnoDB: Starting shutdown...
2019-09-02 17:11:45 139645497730816 [Note] InnoDB: Shutdown completed;
log sequence number 201835120033
2019-09-02 17:11:45 139645497730816 [Note] InnoDB: Removed temporary
tablespace data file: "ibtmp1"
2019-09-02 17:11:45 139645497730816 [Note] /usr/libexec/mysqld: Shutdown
complete

2019-09-02 17:11:45 139893743717888 [Note] InnoDB: Mutexes and rw_locks
use GCC atomic builtins
2019-09-02 17:11:45 139893743717888 [Note] InnoDB: Uses event mutexes
2019-09-02 17:11:45 139893743717888 [Note] InnoDB: Compressed tables use
zlib 1.2.11
2019-09-02 17:11:45 139893743717888 [Note] InnoDB: Using Linux native AIO
2019-09-02 17:11:45 139893743717888 [Note] InnoDB: Number of pools: 1
2019-09-02 17:11:45 139893743717888 [Note] InnoDB: Using SSE2 crc32
instructions
2019-09-02 17:11:45 139893743717888 [Note] InnoDB: Initializing buffer
pool, total size = 64M, instances = 1, chunk size = 64M
2019-09-02 17:11:45 139893743717888 [Note] InnoDB: Completed
initialization of buffer pool
2019-09-02 17:11:45 139893416630016 [Note] InnoDB: page_cleaner
coordinator priority: -20
2019-09-02 17:11:45 139893743717888 [Note] InnoDB: Highest supported
file format is Barracuda.
2019-09-02 17:11:46 139893743717888 [Note] InnoDB: 128 out of 128
rollback segments are active.
2019-09-02 17:11:46 139893743717888 [Note] InnoDB: Creating shared
tablespace for temporary tables
2019-09-02 17:11:46 139893743717888 [Note] InnoDB: Setting file
'./ibtmp1' size to 12 MB. Physically writing the file full; Please
wait ...
2019-09-02 17:11:46 139893743717888 [Note] InnoDB: File './ibtmp1' size
is now 12 MB.
2019-09-02 17:11:46 139893743717888 [Note] InnoDB: Waiting for purge to
start
2019-09-02 17:11:46 139893743717888 [Note] InnoDB: 5.7.27 started; log
sequence number 201835120033
2019-09-02 17:11:46 139893275596544 [Note] InnoDB: Loading buffer
pool(s) from /Volumes/dune/mysql/mysql_dbmail/ib_buffer_pool
2019-09-02 17:11:46 139893275596544 [Note] InnoDB: Cannot open
'/Volumes/dune/mysql/mysql_dbmail/ib_buffer_pool' for reading: No such
file or directory
2019-09-02 17:11:46 139893743717888 [Note] Server socket created on IP:
'0.0.0.0'.
2019-09-02 17:11:46 139893743717888 [Note] /usr/libexec/mysqld: ready
for connections.
Version: '10.2.26-MariaDB'  socket: '/var/lib/mysql/mysqld_dbmail.sock'
 port: 3307  thelounge
2019-09-02 17:11:46 139893708191488 [Note] Slave SQL thread initialized,
starting replication in log 'bin.002679' at position 49489, relay log
'./mysql-relay-bin.983139' position: 549
2019-09-02 17:11:46 139893708498688 [Note] Slave I/O thread: connected
to master 'replication@c*********:3307',replication started in log
'bin.002679' at position 49489
[root@localhost:~]$