msg: the TiDB port 4000 is not up

为提高效率,提问时请提供以下信息,问题描述清晰可优先响应。

  • 【TiDB 版本】:最新版本,https://github.com/pingcap/tidb-ansible
  • 【问题描述】: 2020-01-06 02:39:17,142 p=24202 u=tidb | fatal: [10.0.0.3]: FAILED! => changed=false elapsed: 300 msg: the TiDB port 4000 is not up

内网端口全开,不知道如何排查,查日志也没有具体端口为何起不来的信息,只有这个信息

原因:

报错信息是验证 TiDB server 对应的 40000 端口的状态,是通过一下脚本段进行 check

解决思路:

  1. 确认 tidb server 状态是否正常,是否通过脚本启动
  1. 检查 tidb server 状态和日志是否具体的报错
  2. 检查 tidb server 服务和端口是否存在冲突导致 tidb server 启动失败
  3. 检查 tidb server 对应的启动参数配置是否正确。

tidb_stderr.log 日志文件就报以下的错误,是否有关系呢? invalid config txn-total-size-limit should be less than 104857600 with binlog enabled

tidb 参数配置超过 104857600 ,可以调整到范围内,然后 rolling_update 滚动生效。

有关系的,是因为参数配置查过了 Max size ,导致参数无效,最终导致 TiDB 启动失败。所以要将参数修改一下。

请问改哪个配置文件呢?

原因:

tidb 参数配置超过 104857600 ,可以调整到范围内,然后 rolling_update 滚动生效。有关系的,是因为参数配置查过了 Max size ,导致参数无效,最终导致 TiDB 启动失败。所以要将参数修改一下。

解决办法:

  1. 修改 tidb-ansible/conf/tidb.yml 的参数配置,调整到适合值,具体根据你的业务情况来设置,设置值大小不要超过 Max size。
  2. 可以通过 deploy.yml ,ansible-playbook deploy.yml -t tidb 将 conf/tidb.yml 参数推送到目标的 tidb 节点。
  3. 登录目标 tidb 节点,验证 ${deploy_dir}/conf/tidb.toml 参数设置是否生效,如果未生效可以登录到每台 tidb-server 一个一个配置文件修改。
  4. 通过 ansible-playbook start.yml -t tidb 启动 tidb

您好,改了还是报错:

Jan 6 07:26:46 tidb1 run_alertmanager.sh: level=error ts=2020-01-06T07:26:46.812842467Z caller=notify.go:339 component=dispatcher msg=“Error on notify” err=“require_tls: true (default), but “localhost:25” does not advertise the STARTTLS extension”

Jan 6 07:26:46 tidb1 run_alertmanager.sh: level=error ts=2020-01-06T07:26:46.812907414Z caller=dispatch.go:264 component=dispatcher msg=“Notify for alerts failed” num_alerts=1 err=“require_tls: true (default), but “localhost:25” does not advertise the STARTTLS extension”

Jan 6 07:26:58 tidb1 systemd: tidb-4000.service holdoff time over, scheduling restart.

Jan 6 07:26:58 tidb1 systemd: Stopped tidb-4000 service.

Jan 6 07:26:58 tidb1 systemd: Started tidb-4000 service.

  1. 看一下具体的报错日志,另外发一下操作步骤;
  2. 上面的报错是 altermanager 报错 和 tidb server 没有关系
Jan  6 07:25:10 tidb1 ansible-command: Invoked with warn=True executable=None _uses_shell=True _raw_params=pkill -f "ssh.*ansible.*" removes=None argv=None creates=None chdir=None stdin=None
Jan  6 07:25:11 tidb1 systemd-logind: Removed session 87.
Jan  6 07:25:11 tidb1 systemd: Removed slice User Slice of tidb.
Jan  6 07:25:11 tidb1 ansible-command: Invoked with warn=True executable=None _uses_shell=True _raw_params=pip list | grep -iw jmespath | wc -l removes=None argv=None creates=None chdir=None stdin=None
Jan  6 07:25:11 tidb1 systemd: tidb-4000.service holdoff time over, scheduling restart.
Jan  6 07:25:11 tidb1 systemd: Stopped tidb-4000 service.
Jan  6 07:25:11 tidb1 systemd: Started tidb-4000 service.
Jan  6 07:25:11 tidb1 systemd: tidb-4000.service: main process exited, code=exited, status=1/FAILURE
Jan  6 07:25:11 tidb1 systemd: Unit tidb-4000.service entered failed state.
Jan  6 07:25:11 tidb1 systemd: tidb-4000.service failed.
Jan  6 07:25:12 tidb1 ansible-command: Invoked with warn=True executable=None _uses_shell=True _raw_params=pip list | grep -iw jinja2 | wc -l removes=None argv=None creates=None chdir=None stdin=None
Jan  6 07:25:13 tidb1 ansible-command: Invoked with warn=True executable=None _uses_shell=True _raw_params=pip show jmespath | grep Version |grep -v Metadata-Version removes=None argv=None creates=None chdir=None stdin=None
Jan  6 07:25:14 tidb1 ansible-command: Invoked with warn=True executable=None _uses_shell=True _raw_params=pip show jinja2 | grep Version |grep -v Metadata-Version removes=None argv=None creates=None chdir=None stdin=None
Jan  6 07:25:14 tidb1 ansible-command: Invoked with warn=True executable=None _uses_shell=True _raw_params=python2 /home/tidb/tidb-ansible/scripts/inventory_check.py /home/tidb/tidb-ansible/inventory.ini removes=None argv=None creates=None chdir=None stdin=None
Jan  6 07:25:16 tidb1 systemd: Created slice User Slice of tidb.
Jan  6 07:25:16 tidb1 systemd-logind: New session 88 of user tidb.
Jan  6 07:25:16 tidb1 systemd: Started Session 88 of user tidb.
Jan  6 07:25:17 tidb1 ansible-stat: Invoked with checksum_algorithm=sha1 get_checksum=False follow=False path=/home/tidb/deploy get_md5=False get_mime=True get_attributes=True
Jan  6 07:25:19 tidb1 ansible-wait_for: Invoked with active_connection_states=['ESTABLISHED', 'FIN_WAIT1', 'FIN_WAIT2', 'SYN_RECV', 'SYN_SENT', 'TIME_WAIT'] host=10.0.0.3 port=4000 delay=0 msg=4000 already in use state=stopped sleep=1 timeout=3 exclude_hosts=None search_regex=None path=None connect_timeout=5
Jan  6 07:25:20 tidb1 ansible-wait_for: Invoked with active_connection_states=['ESTABLISHED', 'FIN_WAIT1', 'FIN_WAIT2', 'SYN_RECV', 'SYN_SENT', 'TIME_WAIT'] host=10.0.0.3 port=10080 delay=0 msg=10080 already in use state=stopped sleep=1 timeout=3 exclude_hosts=None search_regex=None path=None connect_timeout=5
Jan  6 07:25:21 tidb1 ansible-systemd: Invoked with no_block=False force=None name=tidb-4000.service enabled=False daemon_reload=False state=started masked=None scope=None user=None
Jan  6 07:25:22 tidb1 ansible-wait_for: Invoked with active_connection_states=['ESTABLISHED', 'FIN_WAIT1', 'FIN_WAIT2', 'SYN_RECV', 'SYN_SENT', 'TIME_WAIT'] host=10.0.0.3 port=4000 delay=0 msg=the TiDB port 4000 is not up state=started sleep=1 timeout=300 exclude_hosts=None search_regex=None path=None connect_timeout=5
Jan  6 07:25:26 tidb1 systemd: tidb-4000.service holdoff time over, scheduling restart.
Jan  6 07:25:26 tidb1 systemd: Stopped tidb-4000 service.
Jan  6 07:25:26 tidb1 systemd: Started tidb-4000 service.
Jan  6 07:25:26 tidb1 systemd: tidb-4000.service: main process exited, code=exited, status=1/FAILURE
Jan  6 07:25:26 tidb1 systemd: Unit tidb-4000.service entered failed state.
Jan  6 07:25:26 tidb1 systemd: tidb-4000.service failed.
Jan  6 07:25:42 tidb1 systemd: tidb-4000.service holdoff time over, scheduling restart.
Jan  6 07:25:42 tidb1 systemd: Stopped tidb-4000 service.
Jan  6 07:25:42 tidb1 systemd: Started tidb-4000 service.
Jan  6 07:25:42 tidb1 systemd: tidb-4000.service: main process exited, code=exited, status=1/FAILURE
Jan  6 07:25:42 tidb1 systemd: Unit tidb-4000.service entered failed state.
Jan  6 07:25:42 tidb1 systemd: tidb-4000.service failed.
Jan  6 07:25:57 tidb1 systemd: tidb-4000.service holdoff time over, scheduling restart.
Jan  6 07:25:57 tidb1 systemd: Stopped tidb-4000 service.
Jan  6 07:25:57 tidb1 systemd: Started tidb-4000 service.
Jan  6 07:25:57 tidb1 systemd: tidb-4000.service: main process exited, code=exited, status=1/FAILURE
Jan  6 07:25:57 tidb1 systemd: Unit tidb-4000.service entered failed state.
Jan  6 07:25:57 tidb1 systemd: tidb-4000.service failed.
Jan  6 07:26:01 tidb1 run_alertmanager.sh: level=error ts=2020-01-06T07:26:01.838830122Z caller=notify.go:339 component=dispatcher msg="Error on notify" err="require_tls: true (default), but \"localhost:25\" does not advertise the STARTTLS extension"
Jan  6 07:26:01 tidb1 run_alertmanager.sh: level=error ts=2020-01-06T07:26:01.838894609Z caller=dispatch.go:264 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="require_tls: true (default), but \"localhost:25\" does not advertise the STARTTLS extension"
Jan  6 07:26:01 tidb1 run_alertmanager.sh: level=error ts=2020-01-06T07:26:01.8388299Z caller=notify.go:339 component=dispatcher msg="Error on notify" err="require_tls: true (default), but \"localhost:25\" does not advertise the STARTTLS extension"
Jan  6 07:26:01 tidb1 run_alertmanager.sh: level=error ts=2020-01-06T07:26:01.838952053Z caller=dispatch.go:264 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="require_tls: true (default), but \"localhost:25\" does not advertise the STARTTLS extension"
Jan  6 07:26:12 tidb1 systemd: tidb-4000.service holdoff time over, scheduling restart.
Jan  6 07:26:12 tidb1 systemd: Stopped tidb-4000 service.
Jan  6 07:26:12 tidb1 systemd: Started tidb-4000 service.
Jan  6 07:26:12 tidb1 systemd: tidb-4000.service: main process exited, code=exited, status=1/FAILURE
Jan  6 07:26:12 tidb1 systemd: Unit tidb-4000.service entered failed state.
Jan  6 07:26:12 tidb1 systemd: tidb-4000.service failed.
Jan  6 07:26:27 tidb1 systemd: tidb-4000.service holdoff time over, scheduling restart.
Jan  6 07:26:27 tidb1 systemd: Stopped tidb-4000 service.
Jan  6 07:26:27 tidb1 systemd: Started tidb-4000 service.
Jan  6 07:26:27 tidb1 systemd: tidb-4000.service: main process exited, code=exited, status=1/FAILURE
Jan  6 07:26:27 tidb1 systemd: Unit tidb-4000.service entered failed state.
Jan  6 07:26:27 tidb1 systemd: tidb-4000.service failed.
Jan  6 07:26:43 tidb1 systemd: tidb-4000.service holdoff time over, scheduling restart.
Jan  6 07:26:43 tidb1 systemd: Stopped tidb-4000 service.
Jan  6 07:26:43 tidb1 systemd: Started tidb-4000 service.
Jan  6 07:26:43 tidb1 systemd: tidb-4000.service: main process exited, code=exited, status=1/FAILURE
Jan  6 07:26:43 tidb1 systemd: Unit tidb-4000.service entered failed state.
Jan  6 07:26:43 tidb1 systemd: tidb-4000.service failed.
Jan  6 07:26:44 tidb1 dhclient[1565]: DHCPREQUEST on eth0 to 169.254.169.254 port 67 (xid=0x6acd3eae)
Jan  6 07:26:44 tidb1 dhclient[1565]: DHCPACK from 169.254.169.254 (xid=0x6acd3eae)
Jan  6 07:26:44 tidb1 NetworkManager[1502]: <info>  [1578295604.0974] dhcp4 (eth0):   address 10.0.0.3
Jan  6 07:26:44 tidb1 NetworkManager[1502]: <info>  [1578295604.0978] dhcp4 (eth0):   plen 32 (255.255.255.255)
Jan  6 07:26:44 tidb1 NetworkManager[1502]: <info>  [1578295604.0978] dhcp4 (eth0):   classless static route 10.0.0.1/32 gw 0.0.0.0
Jan  6 07:26:44 tidb1 NetworkManager[1502]: <info>  [1578295604.0978] dhcp4 (eth0):   gateway 10.0.0.1
Jan  6 07:26:44 tidb1 NetworkManager[1502]: <info>  [1578295604.0979] dhcp4 (eth0):   lease time 3600
Jan  6 07:26:44 tidb1 NetworkManager[1502]: <info>  [1578295604.0979] dhcp4 (eth0):   hostname 'tidb1'
Jan  6 07:26:44 tidb1 NetworkManager[1502]: <info>  [1578295604.0979] dhcp4 (eth0):   nameserver '1.1.1.1'
Jan  6 07:26:44 tidb1 NetworkManager[1502]: <info>  [1578295604.0979] dhcp4 (eth0):   domain name 'xxx'
Jan  6 07:26:44 tidb1 NetworkManager[1502]: <info>  [1578295604.0979] dhcp (eth0):   domain search 'xxx'
Jan  6 07:26:44 tidb1 NetworkManager[1502]: <info>  [1578295604.0979] dhcp (eth0):   domain search 'xxx'
Jan  6 07:26:44 tidb1 NetworkManager[1502]: <info>  [1578295604.0979] dhcp (eth0):   domain search 'xxx'
Jan  6 07:26:44 tidb1 NetworkManager[1502]: <info>  [1578295604.0979] dhcp4 (eth0): state changed bound -> bound
Jan  6 07:26:44 tidb1 dbus[1476]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Jan  6 07:26:44 tidb1 systemd: Starting Network Manager Script Dispatcher Service...
Jan  6 07:26:44 tidb1 dhclient[1565]: bound to 10.0.0.3 -- renewal in 1647 seconds.
Jan  6 07:26:44 tidb1 dbus[1476]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan  6 07:26:44 tidb1 systemd: Started Network Manager Script Dispatcher Service.
Jan  6 07:26:44 tidb1 nm-dispatcher: req:1 'dhcp4-change' [eth0]: new request (3 scripts)
Jan  6 07:26:44 tidb1 nm-dispatcher: req:1 'dhcp4-change' [eth0]: start running ordered scripts...
Jan  6 07:26:46 tidb1 run_alertmanager.sh: level=error ts=2020-01-06T07:26:46.812842467Z caller=notify.go:339 component=dispatcher msg="Error on notify" err="require_tls: true (default), but \"localhost:25\" does not advertise the STARTTLS extension"
Jan  6 07:26:46 tidb1 run_alertmanager.sh: level=error ts=2020-01-06T07:26:46.812907414Z caller=dispatch.go:264 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="require_tls: true (default), but \"localhost:25\" does not advertise the STARTTLS extension"
Jan  6 07:26:58 tidb1 systemd: tidb-4000.service holdoff time over, scheduling restart.
Jan  6 07:26:58 tidb1 systemd: Stopped tidb-4000 service.
Jan  6 07:26:58 tidb1 systemd: Started tidb-4000 service.
Jan  6 07:26:58 tidb1 systemd: tidb-4000.service: main process exited, code=exited, status=1/FAILURE
Jan  6 07:26:58 tidb1 systemd: Unit tidb-4000.service entered failed state.
Jan  6 07:26:58 tidb1 systemd: tidb-4000.service failed.
Jan  6 07:27:13 tidb1 systemd: tidb-4000.service holdoff time over, scheduling restart.
Jan  6 07:27:13 tidb1 systemd: Stopped tidb-4000 service.
Jan  6 07:27:13 tidb1 systemd: Started tidb-4000 service.
Jan  6 07:27:13 tidb1 systemd: tidb-4000.service: main process exited, code=exited, status=1/FAILURE
Jan  6 07:27:13 tidb1 systemd: Unit tidb-4000.service entered failed state.
Jan  6 07:27:13 tidb1 systemd: tidb-4000.service failed.
Jan  6 07:27:28 tidb1 systemd: tidb-4000.service holdoff time over, scheduling restart.
Jan  6 07:27:28 tidb1 systemd: Stopped tidb-4000 service.
Jan  6 07:27:28 tidb1 systemd: Started tidb-4000 service.
Jan  6 07:27:28 tidb1 systemd: tidb-4000.service: main process exited, code=exited, status=1/FAILURE
Jan  6 07:27:28 tidb1 systemd: Unit tidb-4000.service entered failed state.
Jan  6 07:27:28 tidb1 systemd: tidb-4000.service failed.
Jan  6 07:27:43 tidb1 systemd: tidb-4000.service holdoff time over, scheduling restart.
Jan  6 07:27:43 tidb1 systemd: Stopped tidb-4000 service.
Jan  6 07:27:43 tidb1 systemd: Started tidb-4000 service.
Jan  6 07:27:43 tidb1 systemd: tidb-4000.service: main process exited, code=exited, status=1/FAILURE
Jan  6 07:27:43 tidb1 systemd: Unit tidb-4000.service entered failed state.
Jan  6 07:27:43 tidb1 systemd: tidb-4000.service failed.
Jan  6 07:27:58 tidb1 systemd: tidb-4000.service holdoff time over, scheduling restart.
Jan  6 07:27:58 tidb1 systemd: Stopped tidb-4000 service.
Jan  6 07:27:58 tidb1 systemd: Started tidb-4000 service.
Jan  6 07:27:58 tidb1 systemd: tidb-4000.service: main process exited, code=exited, status=1/FAILURE
Jan  6 07:27:58 tidb1 systemd: Unit tidb-4000.service entered failed state.
Jan  6 07:27:58 tidb1 systemd: tidb-4000.service failed.
Jan  6 07:28:13 tidb1 systemd: tidb-4000.service holdoff time over, scheduling restart.
Jan  6 07:28:13 tidb1 systemd: Stopped tidb-4000 service.
Jan  6 07:28:13 tidb1 systemd: Started tidb-4000 service.
Jan  6 07:28:13 tidb1 systemd: tidb-4000.service: main process exited, code=exited, status=1/FAILURE
Jan  6 07:28:13 tidb1 systemd: Unit tidb-4000.service entered failed state.
Jan  6 07:28:13 tidb1 systemd: tidb-4000.service failed.
Jan  6 07:28:28 tidb1 systemd: tidb-4000.service holdoff time over, scheduling restart.
Jan  6 07:28:28 tidb1 systemd: Stopped tidb-4000 service.
Jan  6 07:28:28 tidb1 systemd: Started tidb-4000 service.
Jan  6 07:28:28 tidb1 systemd: tidb-4000.service: main process exited, code=exited, status=1/FAILURE
Jan  6 07:28:28 tidb1 systemd: Unit tidb-4000.service entered failed state.
Jan  6 07:28:28 tidb1 systemd: tidb-4000.service failed.
Jan  6 07:29:01 tidb1 run_alertmanager.sh: level=error ts=2020-01-06T07:29:01.83911535Z caller=notify.go:339 component=dispatcher msg="Error on notify" err="require_tls: true (default), but \"localhost:25\" does not advertise the STARTTLS extension"
Jan  6 07:29:01 tidb1 run_alertmanager.sh: level=error ts=2020-01-06T07:29:01.839164011Z caller=notify.go:339 component=dispatcher msg="Error on notify" err="require_tls: true (default), but \"localhost:25\" does not advertise the STARTTLS extension"
Jan  6 07:29:01 tidb1 run_alertmanager.sh: level=error ts=2020-01-06T07:29:01.839200259Z caller=dispatch.go:264 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="require_tls: true (default), but \"localhost:25\" does not advertise the STARTTLS extension"
Jan  6 07:29:01 tidb1 run_alertmanager.sh: level=error ts=2020-01-06T07:29:01.839231136Z caller=dispatch.go:264 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="requi
这是 /var/log/messages 下的日志

然后 启动tidb 服务报下面的错误  ansible-playbook start.yml -t tidb 
    [10.0.0.3]: Ansible Failed! ==>
      changed=false 
      elapsed: 300
      msg: the TiDB port 4000 is not up

可以看一下 tidb.log,确认一下 tidb.service 启动失败的原因。

在配置文件钟设置了  conf/tidb.toml 
txn-total-size-limit=1000

然后用ansible-playbook start.yml -t tidb 这个方式启动tidb ,但是还是在继续报invalid config txn-total-size-limit should be less than 104857600 with binlog enabled

tidb_stderr.log  日志文件只有这个信息,别有别的了

我的环境是 tidb server 2台,pd+tikv server 3台(共用), tidb-ansible 部署的

提供一下具体 tidb.toml 配置文件以及操作步骤,你可以通过以下方式单独验证参数配置是否正确。

1. 登录目标 tidb server 节点,确认 tidb.toml 参数配置是否正确规范。报错显示应该是你调整参数没有生效。
vim $deploy_dir/conf/tidb.toml  
2. 通过 shell 脚本重启 tidb server
cd $deploy_dir/scripts/
./stop_tidb.sh
./start_tidb.sh
3. 通过  log 验证是否 tidb 正常启动
cat $deploy_dir/log/tidb.log|grep "txn-total-size-limit"
1、配置文件
 [tidb@tidb1 conf]$ pwd
/home/tidb/deploy/conf
 [tidb@tidb1 conf]$ cat tidb.toml
# TiDB Configuration.

compatible-kill-query = false
host = "0.0.0.0"
lease = "45s"
oom-action = "log"
socket = ""
store = "tikv"
token-limit = 1000

[log]
expensive-threshold = 10000
level = "info"
slow-threshold = 300

[security]
cluster-ssl-ca = ""
cluster-ssl-cert = ""
cluster-ssl-key = ""

[status]
metrics-addr = ""
metrics-interval = 15
status-host = "0.0.0.0"
status-port = 10080

[performance]
max-procs = 0
stats-lease = "3s"
stmt-count-limit = 5000

[proxy-protocol]

[prepared-plan-cache]
capacity = 100
enabled = false
memory-guard-ratio = 0.1

[opentracing]
enable = false
rpc-metrics = false

[opentracing.reporter]
buffer-flush-interval = 0
local-agent-host-port = ""
log-spans = false
queue-size = 0

[opentracing.sampler]
max-operations = 0
param = 1.0
sampling-refresh-interval = 0
sampling-server-url = ""
type = "const"

[tikv-client]
commit-timeout = "41s"
grpc-connection-count = 4
grpc-keepalive-time = 10
grpc-keepalive-timeout = 3

[txn-local-latches]
txn-total-size-limit=1000
[binlog]
ignore-error = false
write-timeout = "15s"

[pessimistic-txn]
enable = true
max-retry-count = 256

============================
2、启停脚本
[tidb@tidb1 scripts]$ ./start_tidb.sh
[tidb@tidb1 scripts]$ ps -ef|grep tidb-server
tidb     11594  7831  0 10:02 pts/0    00:00:00 grep --color=auto tidb-server
[tidb@tidb1 scripts]$ 
[tidb@tidb1 scripts]$ ./stop_tidb.sh

=================
3、tidb 日志
[tidb@tidb1 log]$ pwd
 /home/tidb/deploy/log
[tidb@tidb1 log]$ ll
    total 32
    -rw-r--r--. 1 tidb tidb   382 Jan  6 09:20 blackbox_exporter.log
    -rw-r--r--. 1 tidb tidb  3468 Jan  6 09:20 node_exporter.log
    -rw-r--r--. 1 tidb tidb  1586 Jan  6 09:20 prometheus.log
    -rw-r--r--. 1 tidb tidb   393 Jan  6 09:20 pushgateway.log
    -rw-r--r--. 1 tidb tidb 13158 Jan  6 10:00 tidb_stderr.log

[tidb@tidb1 log]$ cat /home/tidb/deploy/log/tidb_stderr.log|grep "txn-total-size-limit"
invalid config txn-total-size-limit should be less than 104857600 with binlog enabled
invalid config txn-total-size-limit should be less than 104857600 with binlog enabled
invalid config txn-total-size-limit should be less than 104857600 with binlog enabled

请将 txn-total-size-limit 参数放在 [performance] 参数组下面再试一下。

一样不行哦

辛苦提供下操作步骤 ,以及 tidb 的版本,当前最新的版本是 3.0.8,辛苦这边确认下版本,另外在 performance 下配置也是不可以的吗 ? 提供下 tidb.log 日志吧

https://github.com/pingcap/tidb/blob/ba2ff85c5849563ea4509d5ff14868c633b0e6fc/config/config.toml.example#L213-L217

我把deploy 目录下的数据全部删除了,重新启动集群,然后在启动的时候也是报 msg: the TiDB port 4000 is not up 这个问题,但是我去ps -ef 发现已经存在tidb 进程了
[tidb@tidb1 tidb-ansible]$ ps -ef|grep tidb-server
tidb     29571     1  1 06:53 ?        00:00:00 bin/tidb-server -P 4000 --status=10080 --advertise-address=10.0.0.3 --path=10.0.0.5:2379,10.0.0.6:2379,10.0.0.7:2379 --config=conf/tidb.toml --log-slow-query=/home/tidb/deploy/log/tidb_slow_query.log --log-file=/home/tidb/deploy/log/tidb.log

然后看tidb日志报了以下的错误:
[tidb@tidb2 log]$ more tidb.log 
[2020/01/07 14:47:35.807 +08:00] [INFO] [printer.go:41] ["Welcome to TiDB."] ["Release Version"=v4.0.0-alpha-1304-g2b7b657f4-dirty] ["Git Commit Hash"=2b7b657f428
80df9771cb82c75c19f16aa5d7952] ["Git Branch"=master] ["UTC Build Time"="2020-01-03 11:42:51"] [GoVersion=go1.13] ["Race Enabled"=false] ["Check Table Before Drop"
=false] ["TiKV Min Version"=v3.0.0-60965b006877ca7234adaced7890d7b029ed1306]

[2020/01/07 14:55:24.131 +08:00] [WARN] [session.go:1113] ["compile SQL failed"] [error="[schema:1146]Table 'mysql.tidb' doesn't exist"] [SQL="SELECT HIGH_PRIORITY VARIABLE_VALUE FROM mysql.tidb WHERE VARIABLE_NAME=\"bootstrapped\""]


我奇怪的是之前都不生成tidb.log 这个日志文件,现在有了,但是启动还是会报错