cerc-io/testnet-laconicd-stack
18
0
Fork 1
Code Issues 3 Pull Requests Packages Projects Releases Wiki Activity

laconic2d shows as unhealthy but is producing blocks #4

New Issue
Closed
opened 2024-07-12 20:59:15 +00:00 by zramsay · 9 comments
zramsay commented 2024-07-12 20:59:15 +00:00
Member
Copy Link

following stack instructions, docker ps shows Up 8 hours (unhealthy) and docker logs shows blocks coming in

following stack instructions, `docker ps` shows `Up 8 hours (unhealthy)` and `docker logs` shows blocks coming in
zramsay commented 2024-07-12 21:46:11 +00:00
Author
Member
Copy Link

possibly related to being unable to talk to the chain remotely, i.e., Invalid registry RPC endpoint

possibly related to being unable to talk to the chain remotely, i.e., `Invalid registry RPC endpoint`
ashwin commented 2024-07-15 12:17:29 +00:00
Member
Copy Link

Repro steps: https://gist.github.com/zramsay/87f37ce0c557a93c335cb23a37c227c1

Repro steps: https://gist.github.com/zramsay/87f37ce0c557a93c335cb23a37c227c1
nabarun commented 2024-07-16 11:13:33 +00:00
Member
Copy Link

Hi @zramsay

following stack instructions, docker ps shows Up 8 hours (unhealthy) and docker logs shows blocks coming in

The healthcheck in fixturenet stack laconicd container was incorrect and has been fixed

possibly related to being unable to talk to the chain remotely, i.e., Invalid registry RPC endpoint

In the repro steps, it can be seen that you are trying to install laconic-registry-cli version 0.2.0 but no such version has been published.
To connect with remote laconic2d node, laconic-registry-cli branch laconic2 needs to be used.
laconic-console stack can also be used to connect with remote laconic2d node.

Hi @zramsay > following stack instructions, `docker ps` shows `Up 8 hours (unhealthy)` and `docker logs` shows blocks coming in The healthcheck in fixturenet stack laconicd container was incorrect and has been fixed > possibly related to being unable to talk to the chain remotely, i.e., `Invalid registry RPC endpoint` In the [repro steps](https://gist.github.com/zramsay/87f37ce0c557a93c335cb23a37c227c1), it can be seen that you are trying to install laconic-registry-cli version `0.2.0` but no such version has been published. To connect with remote laconic2d node, `laconic-registry-cli` branch [laconic2](https://gist.github.com/zramsay/87f37ce0c557a93c335cb23a37c227c1) needs to be used. [laconic-console stack](https://git.vdb.to/cerc-io/testnet-laconicd-stack/src/branch/main/stack-orchestrator/stacks/laconic-console) can also be used to connect with remote laconic2d node.
zramsay commented 2024-07-16 12:48:48 +00:00
Author
Member
Copy Link

yea i built laconic-registry-cli from the laconic2 branch (yarn && yarn install) and the version it builds is 0.2.0 per this commit: 9c992ebe71 (diff-7030d0b2f71b999ff89a343de08c414af32fc93a)

yea i built `laconic-registry-cli` from the `laconic2` branch (yarn && yarn install) and the version it builds is `0.2.0` per this commit: https://git.vdb.to/cerc-io/laconic-registry-cli/commit/9c992ebe71b6ba40d39f8fd9a3e496b1a650ca86#diff-7030d0b2f71b999ff89a343de08c414af32fc93a
zramsay commented 2024-07-16 12:51:27 +00:00
Author
Member
Copy Link

see also https://git.vdb.to/zramsay/birbit/src/branch/main/.github/workflows/publish.yaml#L39. The CI fails with the same Invalid registry RPC endpoint

see also https://git.vdb.to/zramsay/birbit/src/branch/main/.github/workflows/publish.yaml#L39. The CI fails with the same `Invalid registry RPC endpoint`
zramsay commented 2024-07-18 15:33:43 +00:00
Author
Member
Copy Link

now i'm getting this error:

# laconic-so deployment --dir laconic-console-deployment exec cli "laconic registry status"
laconic registry status

Get registry status.

Options:
      --version   Show version number                                  [boolean]
  -v, --verbose   Verbose output                      [boolean] [default: false]
  -c, --config    Config file path.             [string] [default: "config.yml"]
  -o, --output    Gives output in json format when specified.           [string]
      --user-key                                                        [string]
      --tx-key                                                          [string]
      --bond-id                                                         [string]
      --chain-id                                                        [string]
  -f, --filename
      --id                                                              [string]
      --address                                                         [string]
      --gas                                                             [string]
      --fees                                                            [string]
      --help      Show help                                            [boolean]

{
  errors: [
    {
      message: 'Cannot query field "latest_block_hash" on type "SyncInfo". Did you mean "latestBlockHash", "latestBlockHeight", or "latestBlockTime"?',
      locations: [Array],
      extensions: [Object]
    },
    {
      message: 'Cannot query field "latest_block_height" on type "SyncInfo". Did you mean "latestBlockHeight", "latestBlockHash", or "latestBlockTime"?',
      locations: [Array],
      extensions: [Object]
    },
    {
      message: 'Cannot query field "latest_block_time" on type "SyncInfo". Did you mean "latestBlockTime", "latestBlockHash", or "latestBlockHeight"?',
      locations: [Array],
      extensions: [Object]
    },
    {
      message: 'Cannot query field "catching_up" on type "SyncInfo". Did you mean "catchingUp"?',
      locations: [Array],
      extensions: [Object]
    },
    {
      message: 'Cannot query field "voting_power" on type "ValidatorInfo". Did you mean "votingPower"?',
      locations: [Array],
      extensions: [Object]
    },
    {
      message: 'Cannot query field "voting_power" on type "ValidatorInfo". Did you mean "votingPower"?',
      locations: [Array],
      extensions: [Object]
    },
    {
      message: 'Cannot query field "proposer_priority" on type "ValidatorInfo". Did you mean "proposerPriority"?',
      locations: [Array],
      extensions: [Object]
    },
    {
      message: 'Cannot query field "num_peers" on type "Status". Did you mean "numPeers" or "peers"?',
      locations: [Array],
      extensions: [Object]
    },
    {
      message: 'Cannot query field "is_outbound" on type "PeerInfo". Did you mean "isOutbound"?',
      locations: [Array],
      extensions: [Object]
    },
    {
      message: 'Cannot query field "remote_ip" on type "PeerInfo". Did you mean "remoteIp"?',
      locations: [Array],
      extensions: [Object]
    },
    {
      message: 'Cannot query field "disk_usage" on type "Status". Did you mean "diskUsage"?',
      locations: [Array],
      extensions: [Object]
    }
  ],
  data: null
}
container command returned error exit status
now i'm getting this error: ``` # laconic-so deployment --dir laconic-console-deployment exec cli "laconic registry status" laconic registry status Get registry status. Options: --version Show version number [boolean] -v, --verbose Verbose output [boolean] [default: false] -c, --config Config file path. [string] [default: "config.yml"] -o, --output Gives output in json format when specified. [string] --user-key [string] --tx-key [string] --bond-id [string] --chain-id [string] -f, --filename --id [string] --address [string] --gas [string] --fees [string] --help Show help [boolean] { errors: [ { message: 'Cannot query field "latest_block_hash" on type "SyncInfo". Did you mean "latestBlockHash", "latestBlockHeight", or "latestBlockTime"?', locations: [Array], extensions: [Object] }, { message: 'Cannot query field "latest_block_height" on type "SyncInfo". Did you mean "latestBlockHeight", "latestBlockHash", or "latestBlockTime"?', locations: [Array], extensions: [Object] }, { message: 'Cannot query field "latest_block_time" on type "SyncInfo". Did you mean "latestBlockTime", "latestBlockHash", or "latestBlockHeight"?', locations: [Array], extensions: [Object] }, { message: 'Cannot query field "catching_up" on type "SyncInfo". Did you mean "catchingUp"?', locations: [Array], extensions: [Object] }, { message: 'Cannot query field "voting_power" on type "ValidatorInfo". Did you mean "votingPower"?', locations: [Array], extensions: [Object] }, { message: 'Cannot query field "voting_power" on type "ValidatorInfo". Did you mean "votingPower"?', locations: [Array], extensions: [Object] }, { message: 'Cannot query field "proposer_priority" on type "ValidatorInfo". Did you mean "proposerPriority"?', locations: [Array], extensions: [Object] }, { message: 'Cannot query field "num_peers" on type "Status". Did you mean "numPeers" or "peers"?', locations: [Array], extensions: [Object] }, { message: 'Cannot query field "is_outbound" on type "PeerInfo". Did you mean "isOutbound"?', locations: [Array], extensions: [Object] }, { message: 'Cannot query field "remote_ip" on type "PeerInfo". Did you mean "remoteIp"?', locations: [Array], extensions: [Object] }, { message: 'Cannot query field "disk_usage" on type "Status". Did you mean "diskUsage"?', locations: [Array], extensions: [Object] } ], data: null } container command returned error exit status ```
prathamesh commented 2024-07-22 08:16:48 +00:00
Member
Copy Link

yea i built laconic-registry-cli from the laconic2 branch (yarn && yarn install) and the version it builds is 0.2.0 per this commit: 9c992ebe71 (diff-7030d0b2f71b999ff89a343de08c414af32fc93a)

see also https://git.vdb.to/zramsay/birbit/src/branch/main/.github/workflows/publish.yaml#L39. The CI fails with the same Invalid registry RPC endpoint

@zramsay The config required for laconic-registry-cli v2 (laconic2 branch) is a little different than that of v1. Needs to be created as such wherever required (when creating manually or in the script).
Can refer to setup for the same.

> yea i built laconic-registry-cli from the laconic2 branch (yarn && yarn install) and the version it builds is 0.2.0 per this commit: 9c992ebe71 (diff-7030d0b2f71b999ff89a343de08c414af32fc93a) > see also https://git.vdb.to/zramsay/birbit/src/branch/main/.github/workflows/publish.yaml#L39. The CI fails with the same Invalid registry RPC endpoint @zramsay The config required for `laconic-registry-cli` v2 ([laconic2](https://git.vdb.to/cerc-io/laconic-registry-cli/src/branch/laconic2) branch) is a little different than that of v1. Needs to be created as such wherever required (when creating manually or in the [script](https://git.vdb.to/zramsay/birbit/src/branch/main/scripts/publish-app-record.sh#L20)). Can refer to [setup](https://git.vdb.to/cerc-io/laconic-registry-cli/src/branch/laconic2#setup) for the same.
prathamesh commented 2024-07-22 08:19:25 +00:00
Member
Copy Link

now i'm getting this error:
...
{
errors: [
{
message: 'Cannot query field "latest_block_hash" on type "SyncInfo". Did you mean "latestBlockHash", "latestBlockHeight", or "latestBlockTime"?', ....

The registry-sdk dependency had to be upgraded after latest changes to laconic2d, should be handled by PR cerc-io/laconic-registry-cli#70
@zramsay Can you check if it works for you now? (make sure to rebuild the images with latest code)

> now i'm getting this error: ... { errors: [ { message: 'Cannot query field "latest_block_hash" on type "SyncInfo". Did you mean "latestBlockHash", "latestBlockHeight", or "latestBlockTime"?', .... The `registry-sdk` dependency had to be upgraded after latest changes to laconic2d, should be handled by PR https://git.vdb.to/cerc-io/laconic-registry-cli/pulls/70 @zramsay Can you check if it works for you now? (make sure to rebuild the images with latest code)
zramsay commented 2024-07-22 13:03:47 +00:00
Author
Member
Copy Link

ah, so restEndpoint became rpcEndpoint. all three issues in this issue have been address

ah, so `restEndpoint` became `rpcEndpoint`. all three issues in this issue have been address
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
  
Copied from Github

An issue or PR manually copied from GitHub.

  
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No Label
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/testnet-laconicd-stack#4
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?