PostHog / PostHog/HouseWatch

After docker-compose up and i go to the site, method /api/analyze/query_graphs return 500

Open
#12 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
631
Forks
45
PR merge metrics
No merged PRs in 30d

Description

Hi! I decided to try your tool, but I can't use it

In localhost:3000 i see erros:

backend: http api method /api/analyze/query_graphs return 500 with body {"type":"server_error","code":"error","detail":"A server error occurred.","attr":null}

frontend:
Screenshot 2023-07-14 at 15 43 14

logs:

housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 GET /
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 Returned 304 in 7 ms
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 GET /static/css/1.f7ef86df.chunk.css
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 GET /static/css/main.6e4c166f.chunk.css
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 Returned 304 in 5 ms
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 Returned 304 in 5 ms
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 GET /static/js/1.fb96ed73.chunk.js
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 GET /static/js/main.a91ea030.chunk.js
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 Returned 304 in 2 ms
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 Returned 304 in 2 ms
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 GET /static/css/main.6e4c166f.chunk.css.map
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 GET /static/css/1.f7ef86df.chunk.css.map
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 Returned 304 in 1 ms
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 Returned 304 in 1 ms
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 GET /static/js/1.fb96ed73.chunk.js.map
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 GET /static/js/main.a91ea030.chunk.js.map
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 Returned 304 in 1 ms
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 Returned 304 in 2 ms
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 GET /static/media/HindSiliguri-Medium.41fd138d.ttf
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 Returned 304 in 1 ms
housewatch-app-1 | [14/Jul/2023 12:45:08] "GET /api/analyze/hostname HTTP/1.1" 200 29
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 GET /favicon.ico
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 Returned 304 in 2 ms
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 GET /manifest.json
housewatch-web-1 | HTTP 7/14/2023 12:45:08 PM 172.18.0.1 Returned 304 in 1 ms
housewatch-app-1 | [14/Jul/2023 12:45:08] "GET /api/analyze/query_graphs HTTP/1.1" 500 86

I use environment variables: CLICKHOUSE_SECURE=False, CLICKHOUSE_HOST , CLICKHOUSE_CLUSTER, CLICKHOUSE_USER and CLICKHOUSE_PASSWORD

With respect, Andrei

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the project with docker-compose and the reported CLICKHOUSE_* environment variables, then request /api/analyze/query_graphs while checking the housewatch-app logs. Trace the 500 response from that endpoint and compare it with the successful /api/analyze/hostname request; done means the query_graphs request works without a server error in the reported setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
clickhouse, django, docker-compose, react, typescript
Domain
api, backend, databases, devops, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.