Issue: Sequencer and Participant health.status does not match

Questions
1

Hi there.

When I connect a participant to a sequencer. They are showing different health status. The participant is showing it connected but the sequencer is showing not. Any idea what went wrong and how could I check further?

From sequencer:

@ sequencer2.health.status 
res43: com.digitalasset.canton.health.admin.data.NodeStatus[sequencer2.Status] = Sequencer id: domain::1220adce9650aeed4123399106a3858997b8ce199d6eaeb1514b02c5f093822552ad
Domain id: domain::1220adce9650aeed4123399106a3858997b8ce199d6eaeb1514b02c5f093822552ad
Uptime: 2h 10m 1.080577s
Ports: 
	public: 20018
	admin: 20019
Connected Participants: None
Sequencer: SequencerHealthStatus(isActive = true)
details-extra: None

From Participant

@ health.status 
res3: EnterpriseCantonStatus = Status for Domain 'remoteDomain1':
Domain id: domain::1220adce9650aeed4123399106a3858997b8ce199d6eaeb1514b02c5f093822552ad
Uptime: 2h 10m 40.612574s
Ports: 
	public: 20018
	admin: 20019
Connected Participants: None
Sequencer: SequencerHealthStatus(isActive = true)

Status for Participant 'participant2':
Participant id: PAR::participant2::122093be87c9917d1184e67910f59029cb4b28d082c47953c02608e5e4330c43c78d
Uptime: 34m 14.866176s
Ports: 
	ledger: 10021
	admin: 10022
Connected domains: 
	domain::1220adce9650...
Unhealthy domains: None
Active: true
2

Hi @Frankie

Are you using the following to connect a participant to a sequencer?

participant2.domains.connect_local(sequencer2)
3

Hi @rohitt

I was using
participant2.domains.connect_local(sequencer2)

I reset the whole setup and it’s now working. I suspect that it might because participant2 was connected sequencer1 and it wasn’t disconnected properly.

What is the procedure to disconnect/deregister from one sequencer and connect to another sequencer? I’d like to try that.