Skip to content

Troubleshooting

Jump to bottom
Ken Ellorando edited this page May 8, 2024 · 2 revisions

This page stores observed errors and known/potential fixes for them. If you encounter an issue with your Cadence stack, try searching this page for relevant keywords. If you need any help at all, feel free to open a new issue.

Symptoms:

cadence     | 2024/05/08 22:58:38 ERROR Could not query DB. func=searchByTitleArtist error="pq: rel
ation \"metadata\" does not exist"                                                                 
cadence     | 2024/05/08 22:58:38 ERROR Unable to search by title and artist. func=NowPlayingMetada
ta error="pq: relation \"metadata\" does not exist"  

...

cadence     | 2024/05/08 22:58:41 ERROR Database search failed. func=searchByQuery error="pq: relation \"metadata\" does not exist"
cadence     | 2024/05/08 22:58:41 ERROR Unable to execute search by query. func=Search error="pq: relation \"metadata\" does not exist"

Comments:

The log messages are indicative that the postgres service may have failed to start, or may have started but failed to complete configuration of the table which stores music metadata.

Restart the stack using docker compose down and docker compose up.

Symptoms:

Error response from daemon: network 1d6c2faac211ab322b1f21a54a0ddcd3a0d48e54112c6bd707c13a712c05bb0
7 not found

Comments:

The error is output from your computer/server's Docker service when your stack gets into a weird state.

This has been historically fixed using an imprecise destructive action docker system prune, which destroys all unused resources (stopped containers, dangling images, more) including those you have on your system outside of the scope of the Cadence stack. This has not been tried yet, but this also indicates it may also be fixed by searching for the network in the error message and removed using it docker network rm <network id>.

Symptoms:

  • Unable to connect to the browser UI, but can directly connect to the audio services.

Comments:

  • If you launched the stack using the install script AND enabled the reverse proxy, the nginx service may have failed to start. Check the logs to see if an nginx service was started or is spitting out messages. If it is not, try re-running the install
  • If you launched the stack using docker commands directly AND need the Cadence-provided reverse proxy, note that ``docker compose upwill **not** start the reverse proxy. The provided reverse proxy is by an optional, non-default component. Instead, you need to usedocker compose --profile nginx up`.
  • You might need to check your firewall for the port Cadence UI is running on, default 8080. You may have something in conflict with the port.
Clone this wiki locally