composedb model:list --table
or
composedb model:list --network=testnet-clay --table
I will get
fetch failed
composedb model:list --table
or
composedb model:list --network=testnet-clay --table
I will get
fetch failed
Hello @weijiuyang !
Thanks for bringing this to our attention - the nodes that the cli uses are currently under maintenance, so I will notify you when they are back up and running.
Are you just getting started with ComposeDB/Ceramic? If so, the best way to get started for most builders would be using OrbisDB: https://useorbis.com/
Happy to help assist if you have any questions! I’ll follow up again once the nodes that the CLI uses are back online.
Oh, we are currently evaluating options for a suitable distributed database. As you may know, Composedb and OrbisDB are among your company’s offerings. We would greatly appreciate your insights on these solutions. Additionally, we are mindful that switching databases after the system is fully implemented could be quite challenging, so we want to make an informed decision.
OrbisDB will have the strongest ecosystem and plugin architecture support moving forward. Definitely recommended as the way to go.
I ran into this same issue. I started with OrbisDB but it throws an error when trying to create a Context using ceramic. (error below). AFter that I tried the composedb cli command to list models and get the ‘fetch failed’ error. Leading me to believe there may be something wrong with my whole configuration.
I am running locally on mac sequoia 15.3.1
Installed ceramic-one using brew. version 0.43.0
installed ceramic using npm. version 6.11.0
installed composedb cli with npm. version 0.7.1
configured ceramic to use postgres@17
installed latest version of orbisdb with npm.
ceramic-one starts with no errors logged. ceramic starts, connects to postgres and ceramic-one. there is one error in ceramic
[2025-03-15T01:32:49.241Z] ERROR: Error loading Model kjzl6hvfrbw6cb9pd0bl7zmm28h3qszh56ccpn50vsmrl7clroy4fvln00z7q6q used to publish Node Metrics: HTTPError: block was not found locally (offline)
which looks like I can ignore this based on other forum postings?
OrbisDB start with no error and creates table in postgres which look fine as far as I can tell. but trying to create a Context produces
ERROR: Error loading stream kjzl6hvfrbw6c6lqihb9i25vyr4hob667w8otxyzw7fohetbaqkjqrgjvll1h4b: HTTPError: block was not found locally (offline)
[2025-03-14T01:54:01.814Z] ERROR: HTTPError: block was not found locally (offline)
and I get the fetch failed error with composedb.
Can someone help me get things configured and working? Or point me in the right direction to diagnose what’s happening to get things working?
Thanks!