Skip to content
This repository has been archived by the owner on Dec 8, 2022. It is now read-only.

SMASH server doesn't list pool but every other pool fetching site does #190

Open
Seaside-Staking opened this issue Jan 19, 2022 · 5 comments

Comments

@Seaside-Staking
Copy link

Hi

I recently updated my pool's metadata and every website like pool.vet , pooltool.io , adapools.org says the new metadata is correct.
I can also reproduce the hash on my node with :
cardano-cli stake-pool metadata-hash --pool-metadata-file <(curl -s -L https://git.io/Jtrej)
and this outputs the correct registered metadata.
Only Daedelus' smash server has an issue.
Any way I can fix this?

Thanks,

Hans from SEA

@RSVpool
Copy link

RSVpool commented Jan 27, 2022

I've had a similar problem. I thought I had resolved it by re-updating my pool, but I'm still not shown in daedalus and it looks like the api returns "missing from the DB" about 50% of the time. These four identical queries occurred on after the other:

`curl -X GET https://smash.cardano-mainnet.iohk.io/api/v1/metadata/1be0613ee44270f56b5fbb71f667528e1d877d77d349dd7324d50869/e5f97a5fe7709298da38063f905ad6993a696e3b162a00265508ef5abc168c19
{"code":"DbLookupPoolMetadataHash","description":"The metadata with hash PoolMetadataHash "e5f97a5fe7709298da38063f905ad6993a696e3b162a00265508ef5abc168c19" for pool PoolId "1be0613ee44270f56b5fbb71f667528e1d877d77d349dd7324d50869" is missing from the DB."}

curl -X GET https://smash.cardano-mainnet.iohk.io/api/v1/metadata/1be0613ee44270f56b5fbb71f667528e1d877d77d349dd7324d50869/e5f97a5fe7709298da38063f905ad6993a696e3b162a00265508ef5abc168c19
{
"name": "Reservoir Node",
"description": "Two locations. 100% solar energy. 25% of fixed fee donated to americanforests.org",
"ticker": "RSV",
"homepage": "https://reservoir.network",
"extended": "https://reservoir.network/rsv-extended.json"
}

curl -X GET https://smash.cardano-mainnet.iohk.io/api/v1/metadata/1be0613ee44270f56b5fbb71f667528e1d877d77d349dd7324d50869/e5f97a5fe7709298da38063f905ad6993a696e3b162a00265508ef5abc168c19
{"code":"DbLookupPoolMetadataHash","description":"The metadata with hash PoolMetadataHash "e5f97a5fe7709298da38063f905ad6993a696e3b162a00265508ef5abc168c19" for pool PoolId "1be0613ee44270f56b5fbb71f667528e1d877d77d349dd7324d50869" is missing from the DB."}

curl -X GET https://smash.cardano-mainnet.iohk.io/api/v1/metadata/1be0613ee44270f56b5fbb71f667528e1d877d77d349dd7324d50869/e5f97a5fe7709298da38063f905ad6993a696e3b162a00265508ef5abc168c19
{
"name": "Reservoir Node",
"description": "Two locations. 100% solar energy. 25% of fixed fee donated to americanforests.org",
"ticker": "RSV",
"homepage": "https://reservoir.network",
"extended": "https://reservoir.network/rsv-extended.json"
}`

@cardanoeconews
Copy link

I would like to +1 this issue. TIM1 staking pool (registered Jan 19, 2022) is appearing on all of the pool listing sites, and in every wallet, except Daedalus.

I mention it because yesterday someone commented on a Cardano Ecosystem News video that they were not able to find TIM1 in Daedalus.

Is there anything I can do to have it added it Daedalus? Thank you!

@RSVpool
Copy link

RSVpool commented Feb 18, 2022

@cardanoeconews If you confirm your metatdata is correct with tools like pool.vet, I suggest you contact iohk support: https://iohk.zendesk.com/hc/en-us by clicking 'submit request' at the top of the page.

@rknightion
Copy link

rknightion commented Feb 25, 2022

Our ISPO pool (FLICK) had this happen after a metadata update (upped pledge and tweaked the name/description).
The metadata is correct and pool.vet shows green, but querying the IOHK SMASH server gives the following:

<!DOCTYPE html>
<html>
  <head>
    <title>503 Backend fetch failed</title>
  </head>
  <body>
    <h1>Error 503 Backend fetch failed</h1>
    <p>Backend fetch failed</p>
    <h3>Guru Meditation:</h3>
    <p>XID: 287648186</p>
    <hr>
    <p>Varnish cache server</p>
  </body>
</html>
rob@fido:/opt/cardano/cnode/scripts$

We've logged a zendesk ticket but as this is impacting us during a critical time during the ISPO commenting it here as well incase anyone has a solution known? - I did re-register the pool again just to see if it would help but so far no dice.

@lemmon-714
Copy link

It seems that redirects are not working anymore - see #192
The way you can verify that that's your issue is by using curl without -L.

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

No branches or pull requests

5 participants