maria-discuss team mailing list archive
-
maria-discuss team
-
Mailing list archive
-
Message #05790
Error writing to binary log file
-
To:
maria-discuss@xxxxxxxxxxxxxxxxxxx
-
From:
Gustavo Vieira <gustavo@xxxxxxxxxxxxxxx>
-
Date:
Thu, 28 May 2020 16:24:23 -0300
-
Feedback-id:
MjAyMDA1Mjg=:Z3VzdGF2b0BkaWdpcmF0aS5jb20uYnI=:ZGlnaXJhdGkuY29tLmJy:k8networks
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
Hello,
I have several MariaDB 10.1.45 instances running in Linux containers
with memory limits.
This week I have enabled binary logging on all of them with the
following parameters:
log-bin = mysqld-bin
binlog-format = mixed
expire_logs_days = 1
After that I have been getting several errors like this in a few of them:
[ERROR] mysqld: Error writing file 'mysqld-bin' (errno: 11 "Resource
temporarily unavailable")
A few also show these other two errors mixed with the previous one:
[ERROR] mysqld: Error writing file 'mysqld-bin' (errno: 12 "Cannot
allocate memory")
[ERROR] mysqld: Error writing file 'mysqld-bin' (errno: 0 "Internal
error/check (Not system error)")
It gets stuck on this state, reporting errors to every attempt of
executing a query.
A restart on the service seems to solve the problem, at least temporarily.
Does anybody have a clue on why it gets stuck like that? If the
container ran out of memory, should not mariadb crash?
I could not find any information about this error and binary logs being
related.
Thanks in advance,
Gustavo Vieira
Follow ups