Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

panic: interface conversion: interface {} is nil, not string #95

Open
ChristopherLeaWacom opened this issue Apr 12, 2022 · 0 comments
Open

Comments

@ChristopherLeaWacom
Copy link

ChristopherLeaWacom commented Apr 12, 2022

Hi there,

Go-Quorum v22.1.1
quorumengineering/quorum-reporting:latest

I'm trying to get Quorum-Reporting running against my cluster and hitting this issue:

2022-04-12T12:35:09.568271114Z INFO [2022-04-12T12:35:09Z] Config file found filename=/reporting/config.toml
2022-04-12T12:35:09.598035392Z WARN [2022-04-12T12:35:09Z] tuning.BlockProcessingQueueSize below limit new value=100 old value=0
2022-04-12T12:35:09.652249805Z INFO [2022-04-12T12:35:09Z] Dial to WebSocket endpoint success rawUrl="ws://...:23000"
2022-04-12T12:35:09.720307069Z panic: interface conversion: interface {} is nil, not string
2022-04-12T12:35:09.720337668Z
2022-04-12T12:35:09.720342268Z goroutine 1 [running]:
2022-04-12T12:35:09.720346168Z quorumengineering/quorum-report/client.Consensus(0x1112200, 0xc00025d710, 0xc00023c601, 0x23, 0xc00025d710, 0x0)
2022-04-12T12:35:09.720350168Z /quorum-reporting/client/utils.go:91 +0x385
2022-04-12T12:35:09.720354368Z quorumengineering/quorum-report/core.New(0xc00023c481, 0x1e, 0xc000010740, 0x1, 0x1, 0xc0001a9ac0, 0x3, 0x3, 0x0, 0x0, ...)
2022-04-12T12:35:09.720358168Z /quorum-reporting/core/backend.go:47 +0x2b1
2022-04-12T12:35:09.720361968Z main.run(0x0, 0x0)
2022-04-12T12:35:09.720365468Z /quorum-reporting/main.go:81 +0x4a2
2022-04-12T12:35:09.720369068Z main.main()
2022-04-12T12:35:09.720372568Z /quorum-reporting/main.go:20 +0x26

I have covered my IP address for this, but it connects ok I believe on both WS and GraphQL.

The node I'm trying to connect to is running with the following command:
'PRIVATE_CONFIG='ignore' nohup $BIN_GETH --datadir $NODE_DATA_DIR --nodiscover --revertreason --permissioned --http --http.corsdomain=* --http.vhosts=* --http.addr 0.0.0.0 --http.api admin,db,eth,debug,miner,net,shh,txpool,personal,web3,quorum,raft,quorumPermission --ws --ws.addr 0.0.0.0 --ws.origins=* --ws.api admin,db,eth,debug,miner,net,shh,txpool,personal,web3,quorum,raft,quorumPermission --graphql --graphql.corsdomain=* --graphql.vhosts=* --verbosity 1 --networkid 10 --http.port "$RPC_PORT" --ws.port "$WS_PORT" --port "$GETH_PORT" --raft --raftport "$RAFT_PORT" --gcmode=archive --txlookuplimit=0 2>>"$GETH_LOG" &
'
I have Cakeshop connected fine and the chain (with 7 nodes total) is running fine with several contracts deployed. I just want to be able to inspect the historic state of my contract using QR.

I have previously set up QR against another chain but it was not running in Archive mode, so I wanted to try QR against a new chain with archive mode turned on from the start to see how it worked.

Any ideas?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant