Canton restart failed as kubernetes pod

Questions
1

I got this error after deleting the canton pod.

Initialized local nodes: participant1, participant3, participant2, myDomain, fabricSequencer1, fabricSequencer3, fabricSequencer2, mediator1
Running demo script
ERROR c.d.c.c.EnterpriseConsoleEnvironment - Unable to ping PAR::participant2::1220823bff9e... within 1 minute
  Command ParticipantHealthAdministration.ping invoked from Main.sc:44
ERROR c.d.c.ConsoleInteractiveRunner - Running bootstrap script failed with an exception (Command execution failed.)!
Command execution failed.

The worker nodes have enough resources.

2

Hi @joney_hsiao

Can you give us more details about how to reproduce the behaviour you are seeing? Also, the error mentions “running bootstrap script failed”, can you tell us what bootstrap script are using?

Thanks.

3

canton-configmap.yaml (16.0 KB)
Hi @rohitt , could you check my configmap.yaml? it was started by this command CANTON_CONF=/etc/config/fabric-config-1.conf,/etc/config/fabric-config-2.conf,/etc/config/fabric-config-3.conf,/etc/config/demo.conf && bin/canton daemon -Dscala.concurrent.context.numThreads=12 -c $$CANTON_CONF --bootstrap /etc/config/demo.canton.

Thank you.

4

hi @joney_hsiao ,

Are you using the Daml Enterprise edition of the Canton ledger ? Fabric-based domains are only available in the enterprise edition.

5

Hi @rohitt , yes, enterprise 2.4.

6

Hi @joney_hsiao

For enterprise customers, we offer a dedicated support portal. Please open a support ticket with us at support.digitalasset.com and we will help you in troubleshooting this.

Thanks.