Mariabackup error - Error writing file UNKNOWN errno 32 Broken pipe

Mariabackup error - Error writing file UNKNOWN errno 32 Broken pipe

Colleagues hello to all.

In today's article, we will talk about a very common error in MariaDB called Error writing file 'UNKNOWN' (errno: 32 "Broken pipe"). This error happens when we back up the database with Mariabackup using  xbstream compression. This error means that Mariabackup cannot write the file due to broken pipe, it means that SST stopped the connection because mysqld was stopped and the SST process was restarted using a different connection socket.

 

Error.

mariabackup_compression_error_broken_pipe


 

To solve this problem, we need to fix the start timeout timeout settings after a database crash, the default timeout is 90 seconds.

 

First option.

In the  /etc/systemd/system/mariadb.service.d directory, create a file timeoutsec.conf

$. vim /etc/systemd/system/mariadb.service.d/timeoutsec.conf

and add to it:

[Service]
TimeoutStartSec=0
TimeoutStopSec=0

mariabackup_compression_error_broken_pipe

You need to restart daemon-reload and the database after making the change.

$. systemctl daemon-reload

$. service mariadb restart


 

The second option is to set these parameters in the mariadb service itself.

$. systemctl edit --full mariadb.service

Find the parameters TimeoutStartSec, and TimeoutStopSec and set the values ​​to 0.

mariabackup_compression_error_broken_pipe

After making a change, you must restart the database.

$. service mariadb restart


 

Thank you all, I hope that my article helped you in some way.

 

SIMILAR ARTICLES

MariaDB - ERROR Incorrect definition of table
MariaDB - ERROR Incorrect definition of table
MARIADB
Read more
Mariabackup backup - gzip compression
Mariabackup backup - gzip compression
MARIADB
Read more
Mariabackup backup - Store history in database
Mariabackup backup - Store history in database
MARIADB
Read more