Closed qdrddr closed 5 months ago
Hi @qdrddr, nice to see you again =D
The log here indicates that you can connect to your Postgres server and run migration successfully.
Using Postgres
Batch 1 run: 17 migrations
The error logs below show that wren-ui is trying to connect to wren-engine with the endpoint https://wren-ui.myhost.net/v1/data-source/duckdb/settings/init-sql
.
I guess the Wren Engine endpoint might be like http://{wren-engine-service-name}:{port}/v1/.....
since you are running in k8s
[2024-06-06T15:04:51.080] [DEBUG] WrenEngineAdaptor - Endpoint: https://wren-ui.myhost.net/v1/data-source/duckdb/settings/init-sql
[2024-06-06T15:06:10.813] [DEBUG] WrenEngineAdaptor - Got error when init database: Error: connect ETIMEDOUT 86.109.5.12:443
[2024-06-06T15:06:10.815] [ERROR] APOLLO - == original error ==
[2024-06-06T15:06:10.816] [ERROR] APOLLO - Error: connect ETIMEDOUT 86.109.5.12:443
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
@wwwy3y3 but what about the SQLite then? Why itβs also not working then?
@qdrddr I don't think UI still have a dependency on volume if choosing postgres as backend. I'm actually testing deployment on GKE. Let me come back to this issue later.
Hi @qdrddr, nice to see you again =D
The log here indicates that you can connect to your Postgres server and run migration successfully.
Using Postgres Batch 1 run: 17 migrations
The error logs below show that wren-ui is trying to connect to wren-engine with the endpoint
https://wren-ui.myhost.net/v1/data-source/duckdb/settings/init-sql
. I guess the Wren Engine endpoint might be likehttp://{wren-engine-service-name}:{port}/v1/.....
since you are running in k8s[2024-06-06T15:04:51.080] [DEBUG] WrenEngineAdaptor - Endpoint: https://wren-ui.myhost.net/v1/data-source/duckdb/settings/init-sql [2024-06-06T15:06:10.813] [DEBUG] WrenEngineAdaptor - Got error when init database: Error: connect ETIMEDOUT 88.119.55.13:443 [2024-06-06T15:06:10.815] [ERROR] APOLLO - == original error == [2024-06-06T15:06:10.816] [ERROR] APOLLO - Error: connect ETIMEDOUT 88.119.55.13:443 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
Does this mean that the WREN_ENGINE_ENDPOINT
variable is expected to be not with the external URL publicly available to access UI, but instead should be populated with internal DNS name? @onlyjackfrost
I guess then the WREN_ENGINE_ENDPOINT
supposed to be set to http://wren-engine-svc:8080
in the k8s.
Opened PR https://github.com/Canner/WrenAI/pull/388
https://github.com/Canner/WrenAI/blob/main/deployment/kustomizations/base/cm.yaml#L26
Th issue is resolved. Problem was with WREN_ENGINE_ENDPOINT
supposed to be set to http://wren-engine-svc:8080
in the k8s.
Th issue is resolved.
Describe the bug The
DB_TYPE : postgres
orsqlite
for the UI container using the correct backend and seems to be working. In both cases, the UI ink8s
cannot create test data. There is no issue with it if running via docker-compose locally and it seems to be related to the k8s environment only.To Reproduce Steps to reproduce the behavior:
wren-ui
containerExpected behavior UI starting with version 0.60 is expected to be able to use the PostgreSQL backend
Screenshots
Server (please complete the following information):
WrenAI Information
Additional context
Is it possible that UI still have a dependency on having a persistent volume or volume that shared with the engine (that's the case for docker-compose but is not for k8s)? @wwwy3y3