homer7-docker/heplify-server/hom7-prom-all -- postgres.go:283: ERR pq: no partition of relation "hep_proto_1_default

[khorsmann]

Hi sipcapture fans,

i tried homer-7 and there homer7-docker/heplify-server/hom7-prom-all
3963a6e
after 8 days uptime i saw that i got many errors from the heplify-server (see below):
And i could not find any things in the webgui.

Could that only solve with "docker-compose down" and "docker-compose up -d"

I am not sure how to debug the "rotation" process. Maybe that is not clean.

2020/04/09 19:05:08.923474 postgres.go:283: ERR pq: no partition of relation "hep_proto_1_default" found for row 2020/04/09 19:05:08.923529 postgres.go:283: ERR pq: no partition of relation "hep_proto_1_default" found for row 2020/04/09 19:05:08.923566 postgres.go:283: ERR pq: no partition of relation "hep_proto_1_default" found for row 2020/04/09 19:05:08.923857 postgres.go:291: ERR pq: Could not complete operation in a failed transaction 2020/04/09 19:05:08.923864 postgres.go:291: ERR pq: Could not complete operation in a failed transaction 2020/04/09 19:05:08.923886 postgres.go:291: ERR pq: Could not complete operation in a failed transaction 2020/04/09 19:05:08.925969 postgres.go:283: ERR pq: no partition of relation "hep_proto_1_default" found for row 2020/04/09 19:05:08.926138 postgres.go:291: ERR pq: Could not complete operation in a failed transaction

Cheers Karsten

[lmangani]

Hi @khorsmann The data is rotated out of the platform after 7 days or according to the heplify-server settings. Are those errors appearing upon search or on their own?

[khorsmann]

Hi @lmangani -

i searched first and found no calls. Then i go to the docker host and i got the errors in docker logs for the heplify-server (without pressing search).

I was very lazy and changed only the caddy port.

btw - i hate markdown ;-)

`
diff --git a/heplify-server/hom7-prom-all/docker-compose.yml b/heplify-server/hom7-prom-all/docker-compose.yml
index c28ae48..933df2c 100644
--- a/heplify-server/hom7-prom-all/docker-compose.yml
+++ b/heplify-server/hom7-prom-all/docker-compose.yml
@@ -105,7 +105,7 @@ services:
- "3000:3000"
- "9090:9090"
- "9093:9093"

•  - "9080:9080"
  

•  - "80:9080"
  

  volumes:
  - ./caddy/:/etc/caddy/
  environment:

`

[lmangani]

I guess if you look in a timerange that no longer exists, the error would be justified - the frontend will try query any range a user specifies - if it happens for recent traffic still in the DB then its a potential bug. The setting you should tweak is here

[khorsmann]

Hi Lorenzo,

Sorry that I am not clear enough.

I assume it's an bug with creation of the postgres dB after rotating. Cos I search for now() and there was no data (but it should).

Only if I take down and fire up the howl docker images the postgres error of heplify was gone.

[lmangani]

Sounds like a double of #70