Question skip-name-resolve, bind-address and backup

[quattro123]

Server operating system version

Debian 11

Plesk version and microupdate number

18.0.43

Hi, I have upgradet to Maria DB 10.6.8 and since then I am having problems by using skip-name-resolve = 1 in my my.cnf.

Warning: Database "xxx"
Unable to make database dump. Error: Failed to exec mysqldump: Exit code: 2: WARNING: Forcing protocol to TCP due to option specification. Please explicitly state intended protocol. mysqldump: Got error: 1130: "Host '::1' is not allowed to connect to this MariaDB server" when trying to connect

my.cnf
[mysqld]
bind-address = ::


I know that there are some changes with bind-adress = :: since maria 10.6.8, but I don't understand which value exactly I need to enter here for the bind adress to get skip-name-resolve working.

Can someone help?

 

[IgorG]

What about

bind-address = 127.0.0.1

?

 

[quattro123]

Then I get this:

Warning: Database "xxx"
Unable to make database dump. Error: Failed to exec mysqldump: Exit code: 2: WARNING: Forcing protocol to TCP due to option specification. Please explicitly state intended protocol. mysqldump: Got error: 1130: "Host '127.0.0.1' is not allowed to connect to this MariaDB server" when trying to connect

 

[quattro123]

Any idea how to solve this?

 

[Maarten]

This works for me using MariaDB 10.6.8:

[mysqld]
sql_mode=ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
bind-address = ::
skip-name-resolve = 1

 

[quattro123]

Hey, thanks for the reply.

The only difference to my original setting is the first line:

sql_mode=ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION

What exactly does this do? I guess this is not related to my problem. Seems like the issue is somewhere else then, when the rest works for you using mariadb 10.6.8 as well.

 

[Maarten]

The sql_mode is not related to your problem, it's the default in MariaDB:

SQL_MODE

Used to emulate behavior from other SQL servers.

mariadb.com

Did you check the contents of the files in /etc/my.cfn.d/? Is there anything in there that could cause your problem?

 

[quattro123]

There is no my.cnf.d - ony a my.cnf

The content right now looks like this

# The MariaDB configuration file
#
# The MariaDB/MySQL tools read configuration files in the following order:
# 1. "/etc/mysql/mariadb.cnf" (this file) to set global defaults,
# 2. "/etc/mysql/conf.d/*.cnf" to set global options.
# 3. "/etc/mysql/mariadb.conf.d/*.cnf" to set MariaDB-only options.
# 4. "~/.my.cnf" to set user-specific options.
#
# If the same option is defined multiple times, the last one will apply.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.

#
# This group is read both both by the client and the server
# use it for options that affect everything
#
[client-server]

# Import all .cnf files from configuration directory
!includedir /etc/mysql/conf.d/
!includedir /etc/mysql/mariadb.conf.d/
[mysqld]
bind-address = 127.0.0.1
# bind-address = ::







# GENERAL #
# user = mysql
default-storage-engine = InnoDB



# DATA STORAGE #
# datadir = /var/lib/mysql/


#TIMEOUTS#
# wait_timeout = 600


#NO DNS#
# skip-name-resolve = 1


# MyISAM #
key-buffer-size = 3M #war 32M und deaktiviert
# myisam-recover = FORCE,BACKUP


# SAFETY #
# max_connections = 250
# max-allowed-packet = 16M
# max-connect-errors = 10000


# CACHES AND LIMITS #
tmp_table_size = 32M #was 128M
max_heap_table_size = 32M
join_buffer_size = 2M #was 512k
# query_cache_size = 128M
# query_cache_type = 0
# thread-cache-size = 32
# open-files-limit = 65535
table-definition-cache = 3000
# table-open-cache = 2000
# sort_buffer_size = 2M
# read_rnd_buffer_size = 512k


# table_definition_cache = 400
performance_schema = ON


# INNODB #
innodb_lock_wait_timeout = 350
# innodb_flush_method = O_DIRECT
innodb_buffer_pool_size = 16G
innodb_log_file_size = 4G #war 4G
# innodb_log_buffer_size = 64M
# innodb_flush_log_at_trx_commit = 2
innodb_stats_on_metadata = 0 #Metadata statistic updates can impact strongly performance of database servers and MySQLTuner. Be sure that innodb_stats_on_metadata is disabled.
# innodb_buffer_pool_instances = 1
# innodb_file_per_table = 1

#LOG QUERIES#
# slow_query_log = 1
# long_query_time = 1
# log_queries_not_using_indexes



[mysqld]
# Skip reverse DNS lookup of clients
# skip-name-resolve

 

[manos]

It seems that mariadb 10.6.x with plesk, in order database backups and migrations to work
need bind address 127.0.0.1 or :: but skip-name-resolve disabled.

With skip-name-resolve = 1 mariadb 10.6 and plesk working ok though except for database backups and migrations!