DAR Uploaded, but No Templates in Daml Navigator (Minikube + Canton Setup)

Questions
1

Setup Details:

We have set up a Kubernetes environment on Minikube to run Canton components, including:

  • canton-domain
  • canton-participant
  • http-json

This setup was deployed using Helm charts on our local Minikube cluster.

Problem:

We successfully uploaded a DAR file to our local participant ledger using the following command:

daml ledger upload-dar --host=localhost --port=4001 .packages/data-dependencies/.daml/dist/sor-mvp-data-dependencies-1.2.6.dar

However, after deploying the DAR, we are unable to see the expected templates in Daml Navigator and when I visited the navigator page I could not see any templates from the package that I had uploaded to the participant. The navigator correctly populates the users so I know that it is able to connect to the party management service.’

Questions:
What could be the possible reasons why the templates are not appearing in Navigator?
How can we troubleshoot and resolve this issue given our Minikube-based Canton setup

2

To start the debugging, you could use the Daml Assistant to query for the packages.

daml packages list --host localhost --port 4001

Does that list include your newly-uploaded packages?

4

let me check i have to check

5

daml packages list --host localhost --port 4004
daml-helper: GRPCIOBadStatusCode StatusResourceExhausted (StatusDetails {unStatusDetails = “Received message larger than max (5976487 vs. 4194304)”}) fromList we are getting this issue

6

I would try increasing the maximum gRPC message size. See the Max Inbound Message Size docs for an example:

canton.participants.participant2.ledger-api {
  address = "127.0.0.1"
  port = 5021
  max-inbound-message-size = 20971520
}
7

how can we do this in values.yaml via helm charts since we using that in minikube

8

@pratikkedia … as best I can tell the open-source Helm charts have not had that configuration included yet. Any chance you’d be willing to create a PR? This recent PR touched the same files.

9

Do we have separate enterprise helm charts or any such repo for enterprise? If yes could you please point to the concern team as we have enterprise license?

10

@pratikkedia, no there is no other Helm charts repo for Canton 2.x, aside from the open-sourced, community-supported ones.

11

image
image1920Ă—1318 134 KB

I have uploaded the dar and upload got succeeded but not showing up in UI
and using this cmd
daml ledger upload-dar --host=127.0.0.1 --port=4001 /Users/utilities/.daml/dist/sor-mvp-utilities-1.2.0.dar

Uploading /Users/.daml/dist/sor-mvp-utilities-1.2.0.dar to 127.0.0.1:4001

DAR upload succeeded. and I have increased as well what we have discussed
ledger-api {
address = “0.0.0.0”
port = 4001
max-inbound-message-size= 134217728
postgres-data-source.synchronous-commit = off

    command-service.max-commands-in-flight = 100
    max-contract-state-cache-size = 100
    max-contract-key-state-cache-size = 100
    max-transactions-in-memory-fan-out-buffer-size = 10
  } but still not showing up in UI

and output of the cmd is below
daml packages list --host 127.0.0.1 --port 4001

Available packages:

041ddaabb3926f0b666d5e0a36bc1ae8dbf7191d2889afed5d1631af4172fa6b (daml-prim-0.0.0)

057eed1fd48c238491b8ea06b9b5bf85a5d4c9275dd3f6183e0e6b01730cc2ba

10e0333b52bba1ff147fc408a6b7d68465b157635ee230493bd6029b750dcb05 (daml-stdlib-DA-Action-State-Type-1.0.0)

11bc90545e0175ecc241a88eb3adc8eeccf66f196c8f01da7afa30070a0fb2f0 (daml-script-2.8.1)

13aa0d182f60b0aa11dd3ecb4cc4f07f06a7d701b123f0461903104c54c52e43 (sor-mvp-models-1.2.22)

38e6274601b21d7202bb995bc5ec147decda5a01b68d57dda422425038772af7 (daml-prim-DA-Internal-NatSyn-1.0.0)

3f4deaf145a15cdcfa762c058005e2edb9baa75bb7f95a4f8f6f937378e86415 (daml-prim-DA-Exception-AssertionFailed-1.0.0)

40f452260bef3f29dede136108fc08a88d5a5250310281067087da6f0baddff7

41caecdf43548fa122bc810e5999b4050bdf207f66d2d25fb3c71432e65fb980 (sor-mvp-policy-1.2.22)

42be7a5c63bcc290fcca161850315b014c0d3f3014b872b13a2e2d9d9346efe1 (daml-stdlib-2.8.9)

518032f41fd0175461b35ae0c9691e08b4aea55e62915f8360af2cc7a1f2ba6c

57b5c520512c24035057aa4c783cb7ac7f3f49db29806280962e188be7aadb66 (daml-prim-0.0.0)

5921708ce82f4255deb1b26d2c05358b548720938a5a325718dc69f381ba47ff (daml-stdlib-DA-Stack-Types-1.0.0)

60a84e86479ee4c61e7192b173032aff93ef62ea82fd75312cc689c03092e230 (sor-mvp-product-1.2.22)

65921e553a353588e950cbc87e98a127730e63295f7ad8d3adae952ef0133b3e (AdminWorkflows-0.27.0)

6839a6d3d430c569b2425e9391717b44ca324b88ba621d597778811b2d05031d

6c2c0667393c5f92f1885163068cd31800d2264eb088eb6fc740e11241b2bf06

6df2d1fd8ea994ed048a79587b2722e3a887ac7592abf31ecf46fe09ac02d689 (daml-stdlib-DA-Internal-Interface-AnyView-Types-1.0.0)

733e38d36a2759688a4b2c4cec69d48e7b55ecc8dedc8067b815926c917a182a

76bf0fd12bd945762a01f8fc5bbcdfa4d0ff20f8762af490f8f41d6237c6524f

845119f5175079e9c8e42caf5ce47cc6f1bf24176f57743d9edda4d87c8cc63f (sor-mvp-utilities-1.2.0)

852d8e3a8ccf952acc73e17522846bc1eb41498e840d637e519ddcca7dbc7671 (daml-stdlib-1.16.0.20210802.7499.0)

86828b9843465f419db1ef8a8ee741d1eef645df02375ebf509cdc8c3ddd16cb (daml-prim-DA-Exception-GeneralError-1.0.0)

8a7806365bbd98d88b4c13832ebfa305f6abaeaf32cfa2b7dd25c4fa489b79fb

90cba7c57711ef02ef53935f378e4282e4c17f3693e5758bf7886f68232b72d9 (daml-stdlib-2.8.1)

97b883cd8a2b7f49f90d5d39c981cf6e110cf1f1c64427a28a6d58ec88c43657 (daml-stdlib-DA-Set-Types-1.0.0)

99a2705ed38c1c26cbb8fe7acf36bbf626668e167a33335de932599219e0a235

a566728bb2d4ad0103eb11ff8140296f4cea4fc94f1f95ddc6c3e4f983d107f1 (daml-prim-0.0.0)

bfcd37bd6b84768e86e432f5f6c33e25d9e7724a9d42e33875ff74f6348e733f

c1f1f00558799eec139fb4f4c76f95fb52fa1837a5dd29600baa1c8ed1bdccfd

cb0552debf219cc909f51cbb5c3b41e9981d39f8f645b1f35e2ef5be2e0b858a (daml-prim-DA-Exception-ArithmeticError-1.0.0)

cc348d369011362a5190fe96dd1f0dfbc697fdfd10e382b9e9666f0da05961b7

d14e08374fc7197d6a0de468c968ae8ba3aadbf9315476fd39071831f5923662

d58cf9939847921b2aab78eaa7b427dc4c649d25e6bee3c749ace4c3f52f5c97

d7bdb0d58347c7079c0f5079364fe93ab7e39bd485d4fc20af76d5096e758821 (sor-mvp-data-dependencies-1.2.6)

db1ed657133ff274c6a63c54df8cebfba63113c6ccac38d4b504994b8896b00b (AdminWorkflowsWithVacuuming-2.8.1)

e22bce619ae24ca3b8e6519281cb5a33b64b3190cc763248b4c3f9ad5087a92c

e491352788e56ca4603acc411ffe1a49fefd76ed8b163af86cf5ee5f4c38645b

e4cc67c3264eba4a19c080cac5ab32d87551578e0f5f58b6a9460f91c7abc254 (daml-stdlib-DA-Random-Types-1.0.0)

ec5fb553c7228f6654a69a03ad43a3faf73ef840a14b4484d9e438cfc100e575 (sor-mvp-deltas-1.2.12)

f20de1e4e37b92280264c08bf15eca0be0bc5babd7a7b5e574997f154c00cb78 (daml-prim-DA-Exception-PreconditionFailed-1.0.0)

12

@pratikkedia … thank you for the Navigator screenshot and the output of daml packages list.

One possibility is that Navigator is not looking at the ledger at port 4001.

How are you starting Navigator? Is it with daml start, for example?

13

apiVersion: apps/v1
kind: Deployment
metadata:
name: daml-navigator
namespace: canton
labels:
app: daml-navigator
spec:
replicas: 1
selector:
matchLabels:
app: daml-navigator
template:
metadata:
labels:
app: daml-navigator
spec:
containers:
- name: daml-navigator
image: digitalasset/daml-sdk:1.18.1
command: [“daml”, “navigator”, “server”, “–port”, “7500”]
args: [“zsor-participant-canton-participant”, “4001”]
ports:
- containerPort: 7500

apiVersion: v1
kind: Service
metadata:
name: daml-navigator
namespace: canton
spec:
selector:
app: daml-navigator
ports:
- protocol: TCP
port: 7500
targetPort: 7500
type: ClusterIP%

via the deployment yaml

14

It appears that pod is starting a very old version of Navigator:

image: digitalasset/daml-sdk:1.18.1

Try changing it to a 2.8.x SDK:

image: digitalasset/daml-sdk:2.8.12

Or even the latest SDK:

image: digitalasset/daml-sdk:2.10.0

Do the templates then appear in Navigator?

You can see the list of available daml-sdk images here.

15

image
image1078Ă—660 30.5 KB

when i use 2.10.0 tag or 2.8.12 tag

but when i use this old tag 1.18.1 it show participant but with new tag is not showing

image
image1920Ă—916 29.3 KB

16

Ah, right. I could have anticipated that for you. :melting_face:

So with 2.x, Canton added the concept of users in addition to parties.

  • The default for Navigator 1.x was to login with parties. That’s why you see participant::12203... in the old version of Navigator.
  • The default for Navigator 2.x is to login with users. I’m guessing that your participant is not yet configured with a user. Possibly that’s why the drop-down is empty.

The two solutions for you are to either (1) setup users in your participant or (2) tell Navigator to login with parties instead of users.

You can see the option to revert to the party-based login by running the following:

docker run -it --rm digitalasset/daml-sdk:2.10.0 daml navigator server --help

Usage: navigator [server|dump-graphql-schema|create-config] [options] <args>...

  -h, --help               prints this usage text
        :
        :
  --feature-user-management <value>
        By default, the login screen is now populated by
        quering the user mgmt service. Disable to query
        party mgmt instead (the pre-2.0 default).

Try --feature-user-management false as a quick solution for using Navigator:

image: digitalasset/daml-sdk:2.10.0
command: ["daml", "navigator", "server", "–port", "7500", "--feature-user-management", "false"]
args: ["zsor-participant-canton-participant", "4001"]
17

image
image1920Ă—1048 117 KB

now templates are being seen which i uploaded
Thanks so much

18

We have recently encountered an issue while uploading DAR files to my Canton participant, and I wanted to share my experience .

Issue:

While uploading multiple DAR files to my Canton participant, one of the uploads failed with the following error:

An exception was thrown during the upload-dar command
- GRPCIOTimeout

This occurred while uploading sor-mvp-init-1.2.22.dar , which is 5.1MB in size. The error message suggests that the DAR file size might exceed the gRPC maximum message size, which is typically set to 4MB by default.

My Setup:

  • Participant Configuration:
ledger-api {
    address = "0.0.0.0"
    port = 4001
    postgres-data-source.synchronous-commit = off
    max-inbound-message-size = 209715200
    command-service.max-commands-in-flight = 100
    max-contract-state-cache-size = 100
    max-contract-key-state-cache-size = 100
    max-transactions-in-memory-fan-out-buffer-size = 100
}
  • DAR File Sizes:
    • sor-mvp-data-dependencies-1.2.6.dar ( Uploaded successfully)
    • sor-mvp-models-1.2.22.dar (Uploaded successfully)
    • sor-mvp-integration-acord-1.2.0.dar ( Uploaded successfully)
    • sor-mvp-init-1.2.22.dar ( Failed due to GRPCIOTimeout)

Possible Causes:

1. Increase gRPC Maximum Message Size

Since my participant configuration already sets max-inbound-message-size = 209715200 (200MB), the issue might not be the default 4MB limit

I have set the max-inbound-message-size = 209715200 as we have discussed
and we are using port forward cmd while we upload the dar

daml ledger upload-dar --host=127.0.0.1 --port=4001 /Users/zinnia_india/Documents/qa_deployment/deleting_daml_backup/SOR-DAML/.packages/init/.daml/dist/sor-mvp-init-1.2.22.dar

Port forward cmd

kubectl port-forward svc/partcipant-service-name 4001:4001 -n canton

and this cmd says connection lost and ledger participant pod get restarted when we upload dar

19

@pratikkedia Would you be willing to move your new question to a new post, since it’s not really related to Navigator? It’s just helpful in the long term to keep threads centered around a single topic. :slight_smile:

20

done created new topic

1 Like