GRPCIOTimeout Errors on New Installation

New to Daml
1

I’m having an issue with running any DAML compilation due to gRPC errors that I can’t seem to debug.

OS: MacOS 13.4.1
Chip: Apple M2 Pro
DAML SDK: 2.6.5
JDK: Eclipse Temurin, OpenJDK20U-jdk_aarch64_mac_hotspot_20.0.2
JAVA_HOME=“/Library/Java/JavaVirtualMachines/temurin-20.jdk/Contents/Home”
Context: Initially worked on first installation with the above parameters, but started failing after I restarted work a few days later.

daml studio View -> Output Errors (x5):

2023-08-08 12:25:31.44 [INFO]  [LanguageServer] 
Flushed 0 logs
damlc: user error (Failed to start scenario service: BErrorClient (ClientIOError GRPCIOTimeout))
[Info  - 8:25:31 AM] Connection to server got closed. Server will restart.

daml test Error:

damlc: user error (Failed to start scenario service: BErrorClient (ClientIOError GRPCIOTimeout))

daml repl Error:

Package could not be loaded: BErrorClient (ClientIOError GRPCIOTimeout)
daml>

Attempted Resolution Steps:

  • Multiple Restarts
  • Multiple re-installations of DAML
  • Cleared JAVA_HOME and tried just using PATH to set the JDK path
  • HTTP_PROXY=HTTPS_PROXY="", and tried adding NO_PROXY=127.0.0.1 per an older resolution thread
  • Downgrading to 2.6.4
2

Hi Cody,

I’m sorry to learn that your are having difficulty with your installation. I suspect that the DAML version (i.e. 2.6.5 vs 2.6.4) is not the issue.

Can you do a few sense checks:

  • What is the output when you run, daml version?
  • Are you running inside of a daml project, and if so what is the output when you try running daml start
  • Does vs code start when you run daml studio?

One more suggestion:

  • Could you try setting the same environment variables, only in all lowercase?
    • so,
      • HTTP_PROXY becomes http_proxy
      • HTTPS_PROXY becomes https_proxy
      • NO_PROXY becomes no_proxy
    • I’m not actually sure if this will make a difference, but there was another user with a similar issue on StackOverflow

      It looks like it is possible to disable the proxy just for certain hosts. Try leaving https_proxy and http_proxy untouched and set no_proxy=“127.0.0.1”

Also please be advised that you can submit these types of errors to support.digitalasset.com for a quicker response!

Michael Godfrey

michael.godfrey@digitalasset.com
Technical Support | Digital Asset | Creators of DAML

3

Hey Michael!

To answer your questions:

  • Running daml version:

    SDK versions:
  2.6.5  (project SDK version from daml.yaml)

  • When running daml start within a sample DAML project:

    2023-08-09 12:57:44.81 [INFO]  [build]
Compiling create-api to a DAR.

2023-08-09 12:57:45.60 [INFO]  [build]
Created .daml/dist/create-api-0.0.1.dar
Waiting for canton sandbox to start.
Port file was not written to '/var/folders/kv/2l_t_brn0lv8grjnhf8xslv40000gq/T/extra-dir-5613656665/sandbox-portfile' in time.

    The process hangs until I kill it. Curiously, after some time after killing the process I’ll get the message:

    2023-08-09 09:01:58,407 [main] ERROR c.d.c.e.CommunityEnvironment tid:3b0ebfc343f9ea5b96ce9b577186f22d - Failed to start local: Failed to fetch handshake response from sequencer server: HandshakeRequestError(Request failed for sequencer. Is the server running? Did you configure the server address as 0.0.0.0? Are you using the right TLS settings?
  GrpcServiceUnavailable: UNAVAILABLE/Connection closing while performing protocol negotiation for [NettyClientHandler#0, WriteBufferingAndExceptionHandler#0, DefaultChannelPipeline$TailContext#0]
  Request: handshake,true)
2023-08-09 09:01:58,434 [canton-env-execution-context-49] WARN  c.d.c.d.s.s.SequencerWriter:domain=local tid:7dc078165ba8b8f640bf447ed48c0078 - Sequencer writer has completed with an unrecoverable error
akka.stream.AbruptStageTerminationException: GraphStage [akka.stream.impl.fusing.GraphStages$IgnoreSink$anon$10-ignoreSink] terminated abruptly, caused by for example materializer or actor system termination.

  • VS Code does start, but the script compiler fails after 5 retries with the error message I posted above.

  • Trying the lowercase http_proxy, https_proxy, and no_proxy="127.0.0.1" doesn’t change anything.

4

Thanks for the updated info,

Would you be willing to share the entire project that is producing this issue? We would like to confirm whether it is a configuration issue.

ps. log/canton.log is likely also useful

Michael Godfrey

michael.godfrey@digitalasset.com
Technical Support | Digital Asset | Creators of DAML

5

This occurs when using the default “skeleton” template or the Getting Started template.

I’m unable to upload the log file directly as a file, so apologies for posting it as text here:

2023-08-09 14:33:20,340 [main] INFO  c.d.canton.CantonCommunityApp$ - Starting Canton version 2.6.5
2023-08-09 14:33:20,344 [main] INFO  c.d.canton.CantonCommunityApp$ - Registered shutdown-hook.
2023-08-09 14:33:20,678 [main] INFO  c.d.c.c.CommunityConfigValidations$ - Domain local is using protocol version 4
2023-08-09 14:33:20,728 [main] INFO  c.d.c.e.CommunityEnvironment - Deriving 12 as number of threads from 'sys.runtime.availableProcessors()'. Please use '-Dscala.concurrent.context.numThreads' to override.
2023-08-09 14:33:20,822 [canton-env-execution-context-39] INFO  akka.event.slf4j.Slf4jLogger - Slf4jLogger started
2023-08-09 14:33:20,867 [main] INFO  c.d.c.e.CommunityEnvironment tid:1a3581be87574e513a3c1002029654ed - Automatically starting all instances
2023-08-09 14:33:20,940 [main] INFO  c.d.c.d.DomainNodeBootstrap:domain=local - Starting admin-api services on CommunityAdminServerConfig(127.0.0.1,Some(6868),None,Some(KeepAliveServerConfig(40s,20s,20s)),10485760)
2023-08-09 14:33:21,140 [canton-env-execution-context-40] INFO  c.d.c.d.DomainNodeBootstrap:domain=local - Node is not initialized yet. Performing automated default initialization.
2023-08-09 14:33:21,324 [canton-env-execution-context-39] INFO  c.d.c.d.t.DomainTopologyManager:domain=local tid:2b4ee22900ad6a4b8091d63903f88f26 - Applied topology transaction Add NamespaceDelegation(1220774b1ac5..., SigningPublicKey(id = 1220774b1ac5..., format = Tink, scheme = Ed25519), true) at 2023-08-09T18:33:21.323354Z
2023-08-09 14:33:21,345 [canton-env-execution-context-41] INFO  c.d.c.d.t.DomainTopologyManager:domain=local tid:2b4ee22900ad6a4b8091d63903f88f26 - Applied topology transaction Replace DomainParametersChange(
  local::1220774b1ac5...,
  DynamicDomainParameters(
    participant response timeout = 30s,
    mediator reaction timeout = 30s,
    transfer exclusivity timeout = 1m,
    topology change delay = 0.25s,
    ledger time record time tolerance = 1m,
    reconciliation interval = 1m,
    max rate per participant = 1000000,
    max request size = 10485760
  )
) at 2023-08-09T18:33:21.344346Z
2023-08-09 14:33:21,355 [canton-env-execution-context-39] INFO  c.d.c.d.t.DomainTopologyManager:domain=local tid:2b4ee22900ad6a4b8091d63903f88f26 - Applied topology transaction Add OwnerToKeyMapping(DOM::local::1220774b1ac5..., SigningPublicKey(id = 1220bbe4b48a..., format = Tink, scheme = Ed25519)) at 2023-08-09T18:33:21.354917Z
2023-08-09 14:33:21,362 [canton-env-execution-context-39] INFO  c.d.c.d.t.DomainTopologyManager:domain=local - Applied topology transaction Add OwnerToKeyMapping(MED::local::1220774b1ac5..., SigningPublicKey(id = 12207a15b8bc..., format = Tink, scheme = Ed25519)) at 2023-08-09T18:33:21.361852Z
2023-08-09 14:33:21,368 [canton-env-execution-context-41] INFO  c.d.c.d.t.DomainTopologyManager:domain=local - Applied topology transaction Add MediatorDomainState(Both, local::1220774b1ac5..., MED::local::1220774b1ac5...) at 2023-08-09T18:33:21.368284Z
2023-08-09 14:33:21,377 [canton-env-execution-context-44] INFO  c.d.c.d.t.DomainTopologyManager:domain=local - Applied topology transaction Add OwnerToKeyMapping(SEQ::local::1220774b1ac5..., SigningPublicKey(id = 122083f9f5f3..., format = Tink, scheme = Ed25519)) at 2023-08-09T18:33:21.377391Z
2023-08-09 14:33:21,381 [canton-env-execution-context-44] INFO  c.d.c.d.DomainNodeBootstrap:domain=local - Initializing node with id NodeId(local::1220774b1ac5...)
2023-08-09 14:33:21,505 [canton-env-execution-context-41] INFO  c.d.c.d.s.SequencerRuntime:domain=local tid:b5fa17ff4a0f866dc601994490385773 - Sequencer is healthy
2023-08-09 14:33:21,515 [canton-env-execution-context-47] INFO  c.d.c.d.DomainNodeBootstrap:domain=local - Starting public services with config CommunityPublicServerConfig(127.0.0.1,Some(6867),None,Some(KeepAliveServerConfig(40s,20s,20s)),1m,1h,None)
2023-08-09 14:33:21,614 [canton-env-execution-context-47] INFO  c.d.c.s.h.SequencerHandshake:domain=local/client=topology-manager tid:445c607f9a828618432881533bd9408a - The operation 'fetch handshake' was not successful. Retrying after 5 seconds. Result: Left(HandshakeRequestError(Request failed for sequencer. Is the server running? Did you configure the server address as 0.0.0.0? Are you using the right TLS settings?
  GrpcServiceUnavailable: UNAVAILABLE/Connection closing while performing protocol negotiation for [NettyClientHandler#0, WriteBufferingAndExceptionHandler#0, DefaultChannelPipeline$TailContext#0]
  Request: handshake,true)). 
2023-08-09 14:33:26,624 [canton-env-execution-context-40] INFO  c.d.c.s.h.SequencerHandshake:domain=local/client=topology-manager tid:445c607f9a828618432881533bd9408a - Now retrying operation 'fetch handshake'. 
2023-08-09 14:33:26,628 [canton-env-execution-context-40] INFO  c.d.c.s.h.SequencerHandshake:domain=local/client=topology-manager tid:445c607f9a828618432881533bd9408a - The operation 'fetch handshake' was not successful. Retrying after 5 seconds. Result: Left(HandshakeRequestError(Request failed for sequencer. Is the server running? Did you configure the server address as 0.0.0.0? Are you using the right TLS settings?
  GrpcServiceUnavailable: UNAVAILABLE/Connection closing while performing protocol negotiation for [NettyClientHandler#0, WriteBufferingAndExceptionHandler#0, DefaultChannelPipeline$TailContext#0]
  Request: handshake,true)). 
2023-08-09 14:33:31,629 [canton-env-execution-context-40] INFO  c.d.c.s.h.SequencerHandshake:domain=local/client=topology-manager tid:445c607f9a828618432881533bd9408a - Now retrying operation 'fetch handshake'. 
2023-08-09 14:33:31,634 [canton-env-execution-context-39] INFO  c.d.c.s.h.SequencerHandshake:domain=local/client=topology-manager tid:445c607f9a828618432881533bd9408a - The operation 'fetch handshake' was not successful. Retrying after 5 seconds. Result: Left(HandshakeRequestError(Request failed for sequencer. Is the server running? Did you configure the server address as 0.0.0.0? Are you using the right TLS settings?
  GrpcServiceUnavailable: UNAVAILABLE/Connection closing while performing protocol negotiation for [NettyClientHandler#0, WriteBufferingAndExceptionHandler#0, DefaultChannelPipeline$TailContext#0]
  Request: handshake,true)). 
2023-08-09 14:33:36,638 [canton-env-execution-context-39] INFO  c.d.c.s.h.SequencerHandshake:domain=local/client=topology-manager tid:445c607f9a828618432881533bd9408a - Now retrying operation 'fetch handshake'. 
2023-08-09 14:33:36,643 [canton-env-execution-context-40] INFO  c.d.c.s.h.SequencerHandshake:domain=local/client=topology-manager tid:445c607f9a828618432881533bd9408a - The operation 'fetch handshake' was not successful. Retrying after 5 seconds. Result: Left(HandshakeRequestError(Request failed for sequencer. Is the server running? Did you configure the server address as 0.0.0.0? Are you using the right TLS settings?
  GrpcServiceUnavailable: UNAVAILABLE/Connection closing while performing protocol negotiation for [NettyClientHandler#0, WriteBufferingAndExceptionHandler#0, DefaultChannelPipeline$TailContext#0]
  Request: handshake,true)).

The file repeats the last two logs a bunch of times, which I’ve truncated here for brevity.

6

Hi,

Can you provide me with a step-by-step way to reproduce the issue? I’m looking for something along the lines of the following.

  1. Reboot, open a fresh terminal, so we know we don’t have extra stateful things (ports busy etc.).
  2. Run cd $(mktemp -d) so we don’t mess up your files.
  3. Run java -version to check that works.
  4. Run daml version --assistant=yes
  5. Run daml new --template=skeleton my-project
  6. cd my-project
  7. daml start
7

Sure! Here’s the terminal printout. I also ran cat logs/canton.log and truncated the output.

Still seeing the same issues.

$ ~ % cd $(mktemp -d)
$ tmp.4I2VOYOg % java -version
openjdk version "20.0.2" 2023-07-18
OpenJDK Runtime Environment Temurin-20.0.2+9 (build 20.0.2+9)
OpenJDK 64-Bit Server VM Temurin-20.0.2+9 (build 20.0.2+9, mixed mode)
$ tmp.4I2VOYOg % daml version --assistant=yes
SDK versions:
  2.6.5  (default SDK version for new projects, daml assistant version)
$ tmp.4I2VOYOg % daml new --template=skeleton my-project
Created a new project in "my-project" based on the template "skeleton".
$ tmp.4I2VOYOg % cd my-project
$ my-project % daml start

2023-08-11 12:43:00.26 [INFO]  [build]
Compiling my-project to a DAR.

2023-08-11 12:43:00.91 [INFO]  [build]
Created .daml/dist/my-project-0.0.1.dar
Waiting for canton sandbox to start.
Port file was not written to '/var/folders/kv/2l_t_brn0lv8grjnhf8xslv40000gq/T/extra-dir-63383908755/sandbox-portfile' in time.
^C^C
$ my-project % ls
daml		daml.yaml	log
$ my-project % cd log
$ log % ls
canton.log		canton_errors.log
$ log % cat canton_errors.log
$ log % cat canton.log
2023-08-11 08:43:01,580 [main] INFO  c.d.canton.CantonCommunityApp$ - Starting Canton version 2.6.5
2023-08-11 08:43:01,583 [main] INFO  c.d.canton.CantonCommunityApp$ - Registered shutdown-hook.
2023-08-11 08:43:01,912 [main] INFO  c.d.c.c.CommunityConfigValidations$ - Domain local is using protocol version 4
2023-08-11 08:43:01,963 [main] INFO  c.d.c.e.CommunityEnvironment - Deriving 12 as number of threads from 'sys.runtime.availableProcessors()'. Please use '-Dscala.concurrent.context.numThreads' to override.
2023-08-11 08:43:02,057 [canton-env-execution-context-39] INFO  akka.event.slf4j.Slf4jLogger - Slf4jLogger started
2023-08-11 08:43:02,102 [main] INFO  c.d.c.e.CommunityEnvironment tid:5024ba846ea219d11a9b06bfb86816cf - Automatically starting all instances
2023-08-11 08:43:02,175 [main] INFO  c.d.c.d.DomainNodeBootstrap:domain=local - Starting admin-api services on CommunityAdminServerConfig(127.0.0.1,Some(6868),None,Some(KeepAliveServerConfig(40s,20s,20s)),10485760)
2023-08-11 08:43:02,674 [canton-env-execution-context-41] INFO  c.d.c.d.DomainNodeBootstrap:domain=local - Node is not initialized yet. Performing automated default initialization.
2023-08-11 08:43:02,849 [canton-env-execution-context-45] INFO  c.d.c.d.t.DomainTopologyManager:domain=local tid:b52674d54b6d49a56884fe3c1dda3b1e - Applied topology transaction Add NamespaceDelegation(12204911a8ef..., SigningPublicKey(id = 12204911a8ef..., format = Tink, scheme = Ed25519), true) at 2023-08-11T12:43:02.848059Z
2023-08-11 08:43:02,868 [canton-env-execution-context-40] INFO  c.d.c.d.t.DomainTopologyManager:domain=local tid:b52674d54b6d49a56884fe3c1dda3b1e - Applied topology transaction Replace DomainParametersChange(
  local::12204911a8ef...,
  DynamicDomainParameters(
    participant response timeout = 30s,
    mediator reaction timeout = 30s,
    transfer exclusivity timeout = 1m,
    topology change delay = 0.25s,
    ledger time record time tolerance = 1m,
    reconciliation interval = 1m,
    max rate per participant = 1000000,
    max request size = 10485760
  )
) at 2023-08-11T12:43:02.867276Z
2023-08-11 08:43:02,877 [canton-env-execution-context-40] INFO  c.d.c.d.t.DomainTopologyManager:domain=local tid:b52674d54b6d49a56884fe3c1dda3b1e - Applied topology transaction Add OwnerToKeyMapping(DOM::local::12204911a8ef..., SigningPublicKey(id = 12205b495225..., format = Tink, scheme = Ed25519)) at 2023-08-11T12:43:02.876700Z
2023-08-11 08:43:02,883 [canton-env-execution-context-39] INFO  c.d.c.d.t.DomainTopologyManager:domain=local - Applied topology transaction Add OwnerToKeyMapping(MED::local::12204911a8ef..., SigningPublicKey(id = 12208ddc515b..., format = Tink, scheme = Ed25519)) at 2023-08-11T12:43:02.883314Z
2023-08-11 08:43:02,889 [canton-env-execution-context-44] INFO  c.d.c.d.t.DomainTopologyManager:domain=local - Applied topology transaction Add MediatorDomainState(Both, local::12204911a8ef..., MED::local::12204911a8ef...) at 2023-08-11T12:43:02.889533Z
2023-08-11 08:43:02,899 [canton-env-execution-context-44] INFO  c.d.c.d.t.DomainTopologyManager:domain=local - Applied topology transaction Add OwnerToKeyMapping(SEQ::local::12204911a8ef..., SigningPublicKey(id = 1220e9035708..., format = Tink, scheme = Ed25519)) at 2023-08-11T12:43:02.898525Z
2023-08-11 08:43:02,900 [canton-env-execution-context-44] INFO  c.d.c.d.DomainNodeBootstrap:domain=local - Initializing node with id NodeId(local::12204911a8ef...)
2023-08-11 08:43:03,022 [canton-env-execution-context-40] INFO  c.d.c.d.s.SequencerRuntime:domain=local tid:01d4e2cdac9398a126284d73626afc5c - Sequencer is healthy
2023-08-11 08:43:03,031 [canton-env-execution-context-49] INFO  c.d.c.d.DomainNodeBootstrap:domain=local - Starting public services with config CommunityPublicServerConfig(127.0.0.1,Some(6867),None,Some(KeepAliveServerConfig(40s,20s,20s)),1m,1h,None)
2023-08-11 08:43:03,128 [canton-env-execution-context-40] INFO  c.d.c.s.h.SequencerHandshake:domain=local/client=topology-manager tid:6ce1490c1d5c16e0feb914b569373c9d - The operation 'fetch handshake' was not successful. Retrying after 5 seconds. Result: Left(HandshakeRequestError(Request failed for sequencer. Is the server running? Did you configure the server address as 0.0.0.0? Are you using the right TLS settings?
  GrpcServiceUnavailable: UNAVAILABLE/Connection closing while performing protocol negotiation for [NettyClientHandler#0, WriteBufferingAndExceptionHandler#0, DefaultChannelPipeline$TailContext#0]
  Request: handshake,true)).
2023-08-11 08:43:08,133 [canton-env-execution-context-40] INFO  c.d.c.s.h.SequencerHandshake:domain=local/client=topology-manager tid:6ce1490c1d5c16e0feb914b569373c9d - Now retrying operation 'fetch handshake'.
2023-08-11 08:43:08,135 [canton-env-execution-context-40] INFO  c.d.c.s.h.SequencerHandshake:domain=local/client=topology-manager tid:6ce1490c1d5c16e0feb914b569373c9d - The operation 'fetch handshake' was not successful. Retrying after 5 seconds. Result: Left(HandshakeRequestError(Request failed for sequencer. Is the server running? Did you configure the server address as 0.0.0.0? Are you using the right TLS settings?
  GrpcServiceUnavailable: UNAVAILABLE/Connection closing while performing protocol negotiation for [NettyClientHandler#0, WriteBufferingAndExceptionHandler#0, DefaultChannelPipeline$TailContext#0]
  Request: handshake,true)).
8

Hi Cody,

Another suggestion is to test whether your firewall is blocking localhost connections. I found a good explanation on StackOverflow:

Most likely it’s your Mac OSX Firewall.

Go to System Preferences / Security & Privacy / Firewall and see if it’s on. If it is, turn it off for a moment and see if you can ping localhost (please note, before you can turn the Firewall off, you’ll need to click on the padlock in the bottom left corner and authenticate).

Don’t leave your Firewall off though, unless you’re absolutely sure that your Mac is not exposed to any external traffic at all (i.e. it’s really only safe to do that when you’re in a completely isolated network). The procedure above is to verify that it is the Firewall and not something else that’s blocking the ICMP traffic to localhost.

9

Could you also try to list listening ports to see if 6867 is listened on?

sudo lsof -nP -i4TCP:6867 | grep LISTEN
10

The MacOS firewall is disabled, using Paloalto GlobalProtect as a VPN. I have multiple colleagues running GlobalProtect on the same OS version and they’re not experiencing these issues. I also was able to run DAML initially with the same configuration prior to the current set of errors.

I am able to get responses from ping localhost.

11

I did see a connection for a java process on that port after running daml start, which I suspect is due to the process not dying after the failed connections. Regardless, I manually killed that process and tried re-running DAML. No success.

12

I’m getting the same errors as @codyjgilbert, errors also show up in VB Studio when attempting to load the LanguageSever.

I’ve been able to narrow the issue down to gRPC issue, I also have no_proxy set to 127.0.0.1. I turned on extra debugging for gRPC and now I’m getting extra info in the error output, not sure if this helps.

2023-08-11 23:33:20.65 [DEBUG] [LanguageServer ScenarioService]
Starting scenario service…

2023-08-11 23:33:21.17 [DEBUG] [LanguageServer ScenarioService]
Scenario service backend running on port 51783

2023-08-11 23:33:21.17 [DEBUG] [LanguageServer ScenarioService]
SCENARIO SERVICE STDOUT: Server started.
E0811 19:33:21.187341000 13168140288 completion_queue.cc:780] Operation failed: tag=0x8000000000000000, error={“created”:“@1691796801.187312000”,“description”:“Failed to pick subchannel”,“file”:“external/com_github_grpc_grpc/src/core/ext/filters/client_channel/client_channel.cc”,“file_line”:3129,“referenced_errors”:[{“created”:“@1691796801.187312000”,“description”:“failed to connect to all addresses”,“file”:“external/com_github_grpc_grpc/src/core/lib/transport/error_utils.cc”,“file_line”:163,“grpc_status”:14}]}

2023-08-11 23:33:21.19 [INFO] [LanguageServer]
Flushed 0 logs
damlc: user error (Failed to start scenario service: BErrorClient (ClientIOError GRPCIOTimeout))
[Error - 7:33:21 PM] Connection to server got closed. Server will not be restarted.

13

In order to start successfully, the Canton server needs to open three ports, by default 6865, 6866 and 6867. If any of these ports is already opened by something else, the Canton server will fail to start.

Could you try running sudo lsof -i -P | grep :68 to see the list of processes that may be listening on a port that starts with 68? Ideally that command should return no output.

Note that you shouldn’t generally trust sudo commands from a random post on the web so I encourage you to do a bit of research on lsof and grep before running the above, if you’re not already familiar with them.

14

Running sudo lsof -i -P | grep :68 returns nothing, so nothing is reserving those ports prior to DAML execution. After running daml start I get:

java      84925   cody.gilbert   48u  IPv6 0x21508339b30a9963      0t0    TCP localhost:6868 (LISTEN)
java      84925   cody.gilbert   52u  IPv6 0x21508339b30aa163      0t0    TCP localhost:6867 (LISTEN)

It doesn’t appear to be starting processes for ports 6865 and 6866 whatsoever, so that may be a clue as to why it’s unable to find the gRPC server - It’s likely not starting. I’m not sure where I can find logs related to it. Is there a command I can run to only start the gRPC server?

That’s why motto is “YOLO!” and my System32 folder is barren.

15

We followed-up with our own Corporate IT to determine the issue. It appears to be due to our Next DLP client interfering with the ability to make connections, even to localhost. After disabling its Network Filtering functionality, we were able to run all DAML services.

Thanks everyone!

3 Likes