diff options
author | Sergei Golubchik <serg@mariadb.org> | 2023-04-05 23:34:03 +0200 |
---|---|---|
committer | Sergei Golubchik <serg@mariadb.org> | 2023-04-05 23:41:30 +0200 |
commit | 79e27a6bf9e05eb2296e59a4ea4cd1334195faca (patch) | |
tree | 06586998108defdc9805df13e3853e0a5f528d4c | |
parent | 06393cd8f81e6c9a01e9ae1c8783a7f6dac21fbd (diff) | |
download | mariadb-git-79e27a6bf9e05eb2296e59a4ea4cd1334195faca.tar.gz |
MDEV-25887 "Got notification message from PID xxxx, but reception only permitted for main PID yyyy" in systemd during SST
server has systemd support and calls sd_notify() to communicate
the status to systemd.
mariabackup links the whole server in, but it should not notify
systemd, because it's not started or managed by systemd.
-rw-r--r-- | extra/mariabackup/xtrabackup.cc | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/extra/mariabackup/xtrabackup.cc b/extra/mariabackup/xtrabackup.cc index 5e01e64f490..ad35749d0ff 100644 --- a/extra/mariabackup/xtrabackup.cc +++ b/extra/mariabackup/xtrabackup.cc @@ -113,6 +113,12 @@ Street, Fifth Floor, Boston, MA 02110-1335 USA #define MB_CORRUPTED_PAGES_FILE "innodb_corrupted_pages" +// disable server's systemd notification code +extern "C" { +int sd_notify() { return 0; } +int sd_notifyf() { return 0; } +} + int sys_var_init(); /* === xtrabackup specific options === */ |