The br log start success, but actually unable to write to the br log #46363
Labels
affects-6.5
affects-7.1
component/br
This issue is related to BR of TiDB.
severity/moderate
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
tiup br:v6.5.3 log start --task-name=pitr1 --pd="172.16.114.81:2389" --storage='/data1/nfs/pitr-backup/log-backup'
[2023/08/23 17:51:00.971 +08:00] [INFO] [collector.go:73] ["log start"] [streamTaskInfo="{taskName=pitr1,startTs=443753210121551876,endTS=999999999999999999,tableFilter=.}"] [pausing=false] [rangeCount=2]
[2023/08/23 17:51:04.462 +08:00] [INFO] [collector.go:73] ["log start success summary"] [total-ranges=0] [ranges-succeed=0] [ranges-failed=0] [total-take=3.563272246s]
2. What did you expect to see? (Required)
tiup br:v6.5.3 log status --task-name=pitr1 --pd="172.16.114.81:2389"
Starting component
br
: /root/.tiup/components/br/v6.5.3/br log status --task-name=pitr1 --pd=172.16.114.81:2389Detail BR log in /tmp/br.log.2023-08-23T18.16.48+0800
● Total 1 Tasks.
3. What did you see instead (Required)
Because the permissions are incorrect, the br log cannot be written. This should be detected during startup, and it should prompt 'fail' along with listing the reason for the error.
[root@vm172-16-114-81 ~]# cd /data1/nfs/pitr-backup/log-backup
[root@vm172-16-114-81 log-backup]# ll
-rw-r--r-- 1 root root 78 8月 23 17:49 backup.lock
-rw-r--r-- 1 root root 214274 8月 23 17:49 backupmeta
4. What is your TiDB version? (Required)
6.5.3
The text was updated successfully, but these errors were encountered: