【问题标题】:Remote connection is intermittent远程连接断断续续
【发布时间】:2018-03-27 14:06:54
【问题描述】:

我的 MariaDB 服务器有问题。

服务器 A Debian:MariaDB + apache2。

服务器 B Debian:apache2 + 从 (A) 服务器远程访问 MariaDB。

问题是服务器 B 经常失去与 MariaDB 的连接。 有时连接正常,但有时会显示错误:“服务器已消失”。

在服务器上 A apache 通过 localhost 与 MariaBD 一起工作,一切正常。

我认为这可能是 iptables 的问题。

root@xxx:/home/x# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:mysql state NEW,ESTABLISHED

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     tcp  --

这里还有 my.cnf 文件:

#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
# 
# 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.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port        = 3306
socket      = /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket      = /var/run/mysqld/mysqld.sock
nice        = 0

[mysqld]
#
# * Basic Settings
#
user        = mysql
pid-file    = /var/run/mysqld/mysqld.pid
socket      = /var/run/mysqld/mysqld.sock
port        = 3306
basedir     = /usr
datadir     = /var/lib/mysql
tmpdir      = /tmp
lc-messages-dir = /usr/share/mysql
external-locking
delay-key-write=OFF
query-cache-size=0
skip-name-resolve
default-storage-engine=INNODB
    character-set-server=utf8
    collation-server=utf8_bin

# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address        = 195....
#
# * Fine Tuning
#
key_buffer      = 16M
max_allowed_packet  = 16M
thread_stack        = 192K
thread_cache_size       = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover         = BACKUP
max_connections        = 10000
table_cache            = 128
#thread_concurrency     = 10
#
# * Query Cache Configuration
#
query_cache_limit   = 10M
query_cache_size        = 160M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file        = /var/log/mysql/mysql.log
#general_log             = 1
#
# Error log - should be very few entries.
#
log_error = /var/log/mysql/error.log
#
# Here you can see queries with especially long duration
#slow_query_log_file = /var/log/mysql/mysql-slow.log
#slow_query_log      = 1
#long_query_time = 2
#log_queries_not_using_indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
#       other settings you may need to change.
#server-id      = 1
#log_bin            = /var/log/mysql/mysql-bin.log
expire_logs_days    = 10
max_binlog_size         = 100M
#binlog_do_db       = include_database_name
#binlog_ignore_db   = include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem



[mysqldump]
quick
quote-names
max_allowed_packet  = 16M

[mysql]
#no-auto-rehash # faster start of mysql but no tab completition

[isamchk]
key_buffer      = 16M

#
# * IMPORTANT: Additional settings that can override those from this file!
#   The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/

我不知道我该如何解决这个问题...... 我还测试了从其他服务器到 MariaDB 的连接,但它们也失去了连接。 我也做了这里写的一切: https://dev.mysql.com/doc/refman/5.7/en/gone-away.html

没有任何帮助。 谢谢。

【问题讨论】:

  • 客户端或服务器在家吗?在这种情况下,请考虑路由器可能是问题(ISP提供的廉价路由器)。如果你愿意接受,为什么还要检查连接的状态?
  • 顺便说一句,你确定max_connections 吗? 10000似乎太多了。 100 应该足够了。
  • 都是在 oneprovider.com 购买的专用服务器
  • 好吧,我试图更改一些设置,因为我不知道为什么它不起作用
  • 好的,所以路由器应该没问题,也有 10000 个连接(无论如何它都是坏的。你应该在 apache 站点上“缓存”连接,

标签: apache connection debian mariadb


【解决方案1】:

问题似乎是,每个请求都会生成一个到数据库服务器的新连接。由于它只能处理定义数量的连接,因此将不再允许连接,这将导致上面显示的错误。

使用 Apache 服务器上的(微)服务来处理 Apache 请求并与数据库有一个或多个永久连接。

Apache -> 服务 -> _permanent_connection_ -> 数据库

【讨论】:

  • 感谢您的回答。所以你的意思是我想用户持久连接对吗?
  • 持久连接只有在进程的两端持久存在时才有意义。您的连接可能会在每个 HTTP 请求上更新。这就是为什么您需要介于两者之间的服务(守护程序)。持久连接可能有助于在一个请求期间访问多个数据库。
  • 我不确定如何制作这个守护进程。你能给我发我可以阅读的页面链接吗?谢谢
猜你喜欢
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
  • 2015-12-15
  • 1970-01-01
  • 1970-01-01
相关资源
最近更新 更多