BR: PiTR unable to communicate with PD(etcd) via TLS

[db-will]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

use v6.2 br backup and restore data to new cluster

2. What did you expect to see? (Required)

should be able to restore data to new cluster successfully

3. What did you see instead (Required)

Detail BR log in /var/log/br.log Error: restore log from A_CURRENT_TIMESTAMP to A_PAST_TIMESTAMP, but the current existed log from A_PAST_TIMESTAMP to A_PAST_TIMESTAMP: [BR:Common:ErrInvalidArgument]invalid argument

A_PAST_TIMESTAMP are the same timestamp point

4. What is your TiDB version? (Required)

6.2

[db-will]

@3pointer

[3pointer]

The root cause is checkpoint didn't moving forward.

And the reason of checkpoint didn't moving forward is TiKV didn't start watch task thread.

{"level":"WARN","caller":"errors.rs:135","message":"backup stream meet error","time":"xxx","err":"during connecting to the etcd: Etcd meet error transport error: transport error","context":"failed to start watch tasks"}

we should keep retrying to start the watch threads and I think we need add some check before we start log backup via br. @joccau

[YuJuncen]

Are you using the client key with SEC1 EC format? For now, tonic supports PKCS #8 and RSA keys only.

You can use the following command to transform the SEC-1 EC key into PKCS #8 key:

openssl pkcs8 -in $key -nocrypt -topk8 -out $key.pk8

And we can try to use the new generated key then.

[3pointer]

Are you using the client key with SEC1 EC format? For now, tonic supports PKCS #8 and RSA keys only.

You can use the following command to transform the SEC-1 EC key into PKCS #8 key:

openssl pkcs8 -in $key -nocrypt -topk8 -out $key.pk8

And we can try to use the new generated key then.

please give more information about why tonic not support SEC1 EC keys