Problem on running 'ceramic daemon'

Devtools Ceramic SDKs
1

Hi guys hope you are doing fine .
I have an issue on running ceramic daemon command. this is the error that I’m getting :

1232×262 107 KB

I installed @ceramicnetwork/cli package and the package is fine.
Thanks for your time , I appreciate your answer.

2

Hey @Ali.hsz do you have any configurations added to your daemon config file? If yes, can you show me the anchor configuration you have there?

3

Hi @Ali.hsz,

What version of the CLI are you using?

4

Hey , No I didn’t add anything to the default configuration.

5

It’s the default version , it must be the latest.

6

OK, I think your anchor configuration is correct (it’s the default).

Can you please try again with --network testnet-clay added to your CLI command?

7

The error is a bit changed but it’s still there.

1130×460 186 KB

8

Oh, that’s a different error. We were undergoing some maintenance recently so that might explain it - you should not get ECONNREFUSED errors connecting to the Clay CAS node.

Are you getting this error repeatedly?

9

Hi, Julian again :slight_smile: haha
Yesterday it was working and now I’m getting this same error but I’m not getting the deadlines exceeded nor connection refused, just the ECONNREFUSED.

julianperassi@DESKTOP-8NL0MS3:~/brand/my-app$ ceramic daemon --network testnet-clay
(node:8054) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
Ceramic daemon failed to start up:
TypeError: fetch failed
    at Object.processResponse (node:internal/deps/undici/undici:6323:34)
    at node:internal/deps/undici/undici:6648:42
    at node:internal/process/task_queues:140:7
    at AsyncResource.runInAsyncScope (node:async_hooks:203:9)
    at AsyncResource.runMicrotask (node:internal/process/task_queues:137:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  cause: Error: connect ECONNREFUSED 127.0.0.1:5011
      at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1300:16) {
    errno: -111,
    code: 'ECONNREFUSED',
    syscall: 'connect',
    address: '127.0.0.1',
    port: 5011
  }
}
10

I ran it again and now I’m getting a different one, but as you can see most of the connections are refused. :slight_smile:

[2022-09-08T05:36:43.746Z] IMPORTANT: Connecting to ceramic network 'testnet-clay' using pubsub topic '/ceramic/testnet-clay'
[2022-09-08T05:37:16.588Z] WARNING: Can not connect to /dns4/go-ipfs-ceramic-private-clay-external.3boxlabs.com/tcp/4011/ws/p2p/QmQotCKxiMWt935TyCBFTN23jaivxwrZ3uD58wNxeg5npi
[2022-09-08T05:37:16.588Z] WARNING: HTTPError: connect QmQotCKxiMWt935TyCBFTN23jaivxwrZ3uD58wNxeg5npi failure: failed to dial QmQotCKxiMWt935TyCBFTN23jaivxwrZ3uD58wNxeg5npi:
  * [/ip4/127.0.0.1/tcp/4010] dial tcp4 127.0.0.1:4010: connect: connection refused
  * [/ip4/127.0.0.1/tcp/4011/ws] malformed HTTP response "\x13/multistream/1.0.0"
  * [/ip4/10.0.2.238/tcp/4010] dial tcp4 0.0.0.0:4011->10.0.2.238:4010: i/o timeout
  * [/ip4/3.129.182.68/tcp/4011/ws] dial tcp 3.129.182.68:4011: connect: connection refused
  * [/ip4/13.58.48.26/tcp/4011/ws] dial tcp 13.58.48.26:4011: connect: connection refused
  * [/ip4/10.0.2.238/tcp/4011/ws] dial tcp 10.0.2.238:4011: connect: connection refused
[2022-09-08T05:38:02.185Z] WARNING: Can not connect to /dns4/go-ipfs-ceramic-private-cas-clay-external.3boxlabs.com/tcp/4011/ws/p2p/QmbeBTzSccH8xYottaYeyVX8QsKyox1ExfRx7T1iBqRyCd
[2022-09-08T05:38:02.185Z] WARNING: HTTPError: connect QmbeBTzSccH8xYottaYeyVX8QsKyox1ExfRx7T1iBqRyCd failure: failed to dial QmbeBTzSccH8xYottaYeyVX8QsKyox1ExfRx7T1iBqRyCd:
  * [/ip4/3.135.27.57/tcp/4011/ws] dial tcp 3.135.27.57:4011: connect: connection refused
  * [/ip4/3.23.188.172/tcp/4011/ws] dial tcp 3.23.188.172:4011: connect: connection refused
[2022-09-08T05:38:22.265Z] IMPORTANT: Closing Ceramic instance
[2022-09-08T05:38:22.269Z] IMPORTANT: Ceramic instance closed successfully
Ceramic daemon failed to start up:
FetchError: request to https://cas-clay.3boxlabs.com/api/v0/service-info/supported_chains failed, reason: getaddrinfo EAI_AGAIN cas-clay.3boxlabs.com
    at ClientRequest.<anonymous> (/usr/local/lib/node_modules/@ceramicnetwork/cli/node_modules/node-fetch/lib/index.js:1491:11)
    at ClientRequest.emit (node:events:513:28)
    at ClientRequest.emit (node:domain:489:12)
    at TLSSocket.socketErrorListener (node:_http_client:494:9)
    at TLSSocket.emit (node:events:513:28)
    at TLSSocket.emit (node:domain:489:12)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'EAI_AGAIN',
  code: 'EAI_AGAIN'
11

This is very strange. Are you unable to bring your daemon up at all, or does this happen intermittently?

12

Yes that’s strange , actually this is the first time that I’m trying to build on ceramic and I want to test different features to see how exactly ceramic data models work , but unfortunately I couldn’t accomplish that yet .

13

Yeah :sob:

So, it does happen every time you start the daemon? Or sometimes?

14

it happens every time , I couldn’t manage to start the daemon yet.

15

Are you certain there’s no networking issue on your end? A firewall or something like that?

Where are you trying to run the daemon?