What means: "failing link: temporary circuit error: cannot add duplicate keystone with error: non-fatal circuit map error"?

[Perlover]

Hello,

I have a node in Tor. And I often observe such errors (failing link: temporary circuit error: cannot add duplicate keystone with error: non-fatal circuit map error), after which the channel on my part becomes disabled (I see this by lncli getchaninfo short_id_number command) and remains in this status for quite a long time.

Accordingly, payments have not been made on it all this time. What could be the reason? The anonymized logs are below:

2024-01-16 02:27:12.838 [INF] DISC: GossipSyncer(remote_pub_key): applying gossipFilter(start=2024-01-16 02:27:12.838465933 +0100 CET m=+302822.573499578, end=2160-02-22 08:55:27.838465933 +0100 CET)
2024-01-16 02:41:17.036 [INF] DISC: GossipSyncer(remote_pub_key): applying gossipFilter(start=0001-01-01 00:00:00 +0000 UTC, end=0001-01-01 00:00:00 +0000 UTC)
2024-01-16 02:43:17.935 [ERR] HSWC: ChannelLink(channel_point:N): failing link: unable to complete dance with error: remote unresponsive
2024-01-16 02:43:17.936 [INF] HSWC: ChannelLink(channel_point:N): exited
2024-01-16 02:43:18.522 [INF] HSWC: ChannelLink(channel_point:N): stopping
2024-01-16 02:43:18.524 [INF] PEER: Peer(remote_pub_key): disconnecting remote_pub_key@remote_IP:9735, reason: link requested disconnect
2024-01-16 02:43:18.626 [INF] DISC: Removing GossipSyncer for peer=remote_pub_key
2024-01-16 02:43:22.609 [INF] SRVR: Established connection to: remote_pub_key@remote_IP:9735
2024-01-16 02:43:22.609 [INF] SRVR: Finalizing connection to remote_pub_key@remote_IP:9735, inbound=false
2024-01-16 02:43:23.780 [INF] PEER: Peer(remote_pub_key): Loading ChannelPoint(channel_point:N), isPending=false
2024-01-16 02:43:23.783 [INF] HSWC: ChannelLink(channel_point:N): starting
2024-01-16 02:43:23.784 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(channel_point:N)
2024-01-16 02:43:23.785 [INF] HSWC: ChannelLink(channel_point:N): HTLC manager started, bandwidth=19583244075 mSAT
2024-01-16 02:43:23.785 [INF] HSWC: ChannelLink(channel_point:N): Attempting to re-synchronize channel: SCID=scid_number, status=ChanStatusDefault, initiator=false, pending=false, local commitment has height=41741, local_htlc_index=16426, local_log_index=21803, remote_htlc_index=5377, remote_log_index=21803, remote commitment has height=41245, local_htlc_index=16426, local_log_index=21803, remote_htlc_index=5377, remote_log_index=21803
2024-01-16 02:43:23.786 [INF] PEER: Peer(remote_pub_key): Negotiated chan series queries
2024-01-16 02:43:23.787 [INF] DISC: Creating new GossipSyncer for peer=remote_pub_key
2024-01-16 02:43:23.789 [INF] HSWC: ChannelLink(channel_point:N): received re-establishment message from remote side
2024-01-16 02:44:10.570 [ERR] HSWC: ChannelLink(channel_point:N): failing link: temporary circuit error: cannot add duplicate keystone with error: non-fatal circuit map error
^^^^^^^^^^^^^^^^^^^^^^^^^ error preceding channel disabling

2024-01-16 02:44:10.570 [INF] HSWC: ChannelLink(channel_point:N): exited
2024-01-16 02:44:10.570 [INF] HSWC: ChannelLink(channel_point:N): stopping
2024-01-16 03:05:06.119 [INF] NANN: Announcing channel(channel_point:N) disabled [detected]
^^^^^^^^^^^^^^^^^ After a while, the channel is disabled.
......... For example, at the moment he is no longer working for more than 16 hours.

2024-01-16 04:40:47.521 [INF] DISC: GossipSyncer(remote_pub_key): applying gossipFilter(start=2024-01-16 04:40:47.521817539 +0100 CET m=+310837.256851221, end=2160-02-22 11:09:02.521817539 +0100 CET)
2024-01-16 05:41:17.037 [INF] DISC: GossipSyncer(remote_pub_key): applying gossipFilter(start=0001-01-01 00:00:00 +0000 UTC, end=0001-01-01 00:00:00 +0000 UTC)
2024-01-16 05:50:49.403 [INF] DISC: GossipSyncer(remote_pub_key): applying gossipFilter(start=2024-01-16 05:50:49.403138407 +0100 CET m=+315039.138172052, end=2160-02-22 12:19:04.403138407 +0100 CET)

May be is this bug? I didn't find an info about same problem...

Thanks for helping!