Identity - Attestation Service Setup Issues

[abhayait]

I have setup attestation service for dapplooker baklava node. I am seeing below in logs:

2022-03-01T18:42:31.321Z attestation-service[84] INFO:  Initializing Database
2022-03-01T18:42:31.344Z attestation-service[84] INFO:  Initializing Contract Kit(s)
2022-03-01T18:42:35.705Z attestation-service[84] WARN:  Failed to connect to Celo node at http://localhost:8546
2022-03-01T18:42:35.715Z attestation-service[84] INFO:  Connected to Celo node at http://localhost:8545
2022-03-01T18:42:39.928Z attestation-service[84] INFO:  Registered delivery status handler
  method: "POST"
  url: "http://baklava-attestation.dapplooker.com/delivery_status_twilioverify"
2022-03-01T18:42:39.929Z attestation-service[84] INFO:  Registered delivery status handler
  method: "POST"
  url: "http://baklava-attestation.dapplooker.com/delivery_status_twiliomessaging"
2022-03-01T18:42:39.930Z attestation-service[84] INFO:  Attestation Service started
  port: "80"
  rateLimitReqsPerMin: 100


2022-03-01T18:43:39.943Z attestation-service[84] INFO:  Initializing Contract Kit(s)
2022-03-01T18:43:44.251Z attestation-service[84] WARN:  Failed to connect to Celo node at http://localhost:8546
2022-03-01T18:44:39.949Z attestation-service[84] INFO:  Initializing Contract Kit(s)
2022-03-01T18:44:44.168Z attestation-service[84] WARN:  Failed to connect to Celo node at http://localhost:8546
2022-03-01T18:45:40.016Z attestation-service[84] INFO:  Initializing Contract Kit(s)
2022-03-01T18:45:44.723Z attestation-service[84] WARN:  Failed to connect to Celo node at http://localhost:8546
2022-03-01T18:46:40.047Z attestation-service[84] INFO:  Initializing Contract Kit(s)

CELO_PROVIDERS variable is already set.

echo $CELO_PROVIDERS
http://127.0.0.1:8545,https://forno.celo.org

Why the warning is coming continously?

[arthurgousset]

Hey @napolean0, thanks for posting the question here! I think @eelanagaraj might be best placed to answer your question :)

[eelanagaraj]

Hey @napolean0 thanks for your question. What version of the attestation service are you using? Also, are you using a configuration file in addition to the env-vars that you set? The default config file has CELO_PROVIDERS=CELO_PROVIDERS=http://localhost:8545,http://localhost:8546, and wondering if for some reason dotenv is not recognizing the env var that you set 🤔
Do you still get this error if you update CELO_PROVIDERS in the config file directly?

[abhayait]

Thanks @eelanagaraj for the help. Warning goes away after updating CELO_PROVIDERS with below values.

CELO_PROVIDERS=http://localhost:8545

Facing 1 more issue. Running below command gives error:

celocli identity:test-attestation-service --from $CELO_ATTESTATION_SIGNER_ADDRESS --phoneNumber +918605237441 --message "hello" --provider twillio

ERROR

Running Checks:
   ✔  0xcCcDa38130dC8DAE12A6Bbd114d92860caDEEd97 is Signer or registered Account 
   ✔  Account can sign 

Request was not successful
Status: 500
Response: {"success":false,"error":"SQLITE_ERROR: no such table: Attestations"}
Sending request to http://baklava-attestation.dapplooker.com/test_attestations... done
Something went wrong
TypeError: body used already for: http://baklava-attestation.dapplooker.com/test_attestations
    at Response.consumeBody (/root/.nvm/versions/node/v12.18.3/lib/node_modules/@celo/celocli/node_modules/cross-fetch/node_modules/node-fetch/lib/index.js:343:30)
    at Response.text (/root/.nvm/versions/node/v12.18.3/lib/node_modules/@celo/celocli/node_modules/cross-fetch/node_modules/node-fetch/lib/index.js:283:22)
    at TestAttestationService.<anonymous> (/root/.nvm/versions/node/v12.18.3/lib/node_modules/@celo/celocli/lib/commands/identity/test-attestation-service.js:76:59)
    at Generator.next (<anonymous>)
    at fulfilled (/root/.nvm/versions/node/v12.18.3/lib/node_modules/@celo/celocli/lib/commands/identity/test-attestation-service.js:5:58)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

How to fix it?

[abhayait]

These are attestation env variable values:

export CELO_ATTESTATION_SIGNER_ADDRESS=0xcCcDa38130dC8DAE12A6Bbd114d92860caDEEd97
export CELO_ATTESTATION_SIGNER_SIGNATURE=xxxxxxxxxxxxx
export KEYSTORE_PARENT_DIR=/mnt/attestation
export VOLUME_DIRPATH=/root/.celo
export CONFIG=/mnt/attestation/attestation-service-config
export TAG=attestation-service-baklava
export CELO_ATTESTATION_SERVICE_URL=http://baklava-attestation.dapplooker.com
export CELO_PROVIDERS=http://127.0.0.1:8545

[eelanagaraj]

@napolean0 I'm guessing the docker process doesn't have permissions to access the sqlite file since it wasn't created by the docker process.

That said, if it's just for testing, you can use the dev command as before and update your config to point to the correct dev.db; if it's for production use, we recommend you do not use sqlite, but instead use a full DB instance/cloud solution--please check out this section of the docs for more guidance.

[abhayait]

@eelanagaraj with postgres setup attestation service working fine 👍
Thanks for keeping up with me and helping debug this 🙏 .
Some of above points can be mentioned in docs I think which will help others.

[eelanagaraj]

Great to hear, and of course! Thanks for the feedback -- if you have specific points that you think should be in the docs (or that were there but were hard to find), we're open to hearing more! (Or feel free to submit a PR to the celo-docs repo! 😄)

[abhayait]

Sounds Great 👍