New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
postgres rpc call errrors #2390
Comments
Hey @zhaojunfeng, welcome back to the quivr frontier! 🚀 Ready for another round of troubleshooting? 😜 Based on the context provided, here are some steps you can take to troubleshoot and resolve the PostgreSQL errors you're encountering:
Ensure that you have proper monitoring and alerting in place to detect such issues early. Regularly update your PostgreSQL and Supabase installations to the latest stable versions to benefit from fixes and improvements. Always test updates in a staging environment before applying them to production. Regarding the quivr codebase, it includes specific PostgreSQL configurations that could potentially lead to reported errors, particularly due to the extensive use of As for known issues in the quivr repository related to PostgreSQL that could be causing these errors, I wasn't able to find any. However, it's possible that there may be a better answer I wasn't able to find. If you have more information or specific error messages, please provide them so I can assist you better. Sources
|
curl -X POST 'http://192.168.1.84:54321/rest/v1/rpc/match_brain' \
|
What happened?
supabase: 1.149.4
quivr: v0.0.227
New deployment~
postgres error logs here:
n cancel request did not match any process
2024-03-30T01:58:39.575889645Z 172.19.0.6 2024-03-30 01:58:39.575 UTC [3927] [unknown]@[unknown] LOG: PID 2991 in cancel request did not match any process
2024-03-30T01:59:45.633833143Z 2024-03-30 01:59:45.633 UTC [10] LOG: server process (PID 3953) was terminated by signal 4: Illegal instruction
2024-03-30T01:59:45.633883348Z 2024-03-30 01:59:45.633 UTC [10] DETAIL: Failed process was running: WITH pgrst_source AS (SELECT "pgrst_call".* FROM (SELECT $1 AS json_data) pgrst_payload, LATERAL (SELECT CASE WHEN json_typeof(pgrst_payload.json_data) = 'array' THEN pgrst_payload.json_data ELSE json_build_array(pgrst_payload.json_data) END AS val) pgrst_uniform_json, LATERAL (SELECT "query_embedding", "match_count", "p_user_id" FROM json_to_recordset(pgrst_uniform_json.val) AS _("query_embedding" public.vector, "match_count" integer, "p_user_id" uuid) LIMIT 1) pgrst_body , LATERAL "public"."match_brain"("query_embedding" := pgrst_body."query_embedding", "match_count" := pgrst_body."match_count", "p_user_id" := pgrst_body."p_user_id") pgrst_call) SELECT null::bigint AS total_result_set, pg_catalog.count(_postgrest_t) AS page_total, coalesce(json_agg(_postgrest_t), '[]') AS body, nullif(current_setting('response.headers', true), '') AS response_headers, nullif(current_setting('response.status', true), '') AS response_status, '' AS response_inserted FROM (SELECT "record".* FROM "pgrst_source" AS "record"
2024-03-30T01:59:45.633902472Z 2024-03-30 01:59:45.633 UTC [10] LOG: terminating any other active server processes
2024-03-30T01:59:45.637535397Z 172.19.0.7 2024-03-30 01:59:45.637 UTC [3987] authenticator@postgres FATAL: the database system is in recovery mode
2024-03-30T01:59:45.637728815Z 172.19.0.7 2024-03-30 01:59:45.637 UTC [3988] authenticator@postgres FATAL: the database system is in recovery mode
2024-03-30T01:59:45.640194219Z 2024-03-30 01:59:45.640 UTC [10] LOG: all server processes terminated; reinitializing
2024-03-30T01:59:45.764674289Z 2024-03-30 01:59:45.764 UTC [3989] LOG: database system was interrupted; last known up at 2024-03-30 01:58:38 UTC
2024-03-30T01:59:45.765554810Z 172.19.0.8 2024-03-30 01:59:45.765 UTC [3992] supabase_storage_admin@postgres FATAL: the database system is in recovery mode
2024-03-30T01:59:45.811266962Z 2024-03-30 01:59:45.811 UTC [3989] LOG: database system was not properly shut down; automatic recovery in progress
2024-03-30T01:59:45.844150680Z 2024-03-30 01:59:45.843 UTC [3989] LOG: redo starts at 0/1CFDB58
2024-03-30T01:59:45.844597874Z 2024-03-30 01:59:45.844 UTC [3989] LOG: invalid record length at 0/1D00A20: wanted 24, got 0
2024-03-30T01:59:45.844630510Z 2024-03-30 01:59:45.844 UTC [3989] LOG: redo done at 0/1D009E8 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-03-30T01:59:45.942909290Z 2024-03-30 01:59:45.942 UTC [3990] LOG: checkpoint starting: end-of-recovery immediate wait
2024-03-30T01:59:46.101318082Z 2024-03-30 01:59:46.101 UTC [3990] LOG: checkpoint complete: wrote 7 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.003 s, sync=0.068 s, total=0.192 s; sync files=6, longest=0.048 s, average=0.012 s; distance=11 kB, estimate=11 kB
2024-03-30T01:59:46.143784959Z 2024-03-30 01:59:46.143 UTC [10] LOG: database system is ready to accept connections
2024-03-30T01:59:46.146045265Z 2024-03-30 01:59:46.145 UTC [3995] LOG: TimescaleDB background worker launcher connected to shared catalogs
2024-03-30T01:59:46.160735581Z 2024-03-30 01:59:46.160 UTC [3997] LOG: pg_cron scheduler started
2024-03-30T01:59:46.574284096Z 172.19.0.6 2024-03-30 01:59:46.574 UTC [4001] [unknown]@[unknown] LOG: PID 3922 in cancel request did not match any process
2024-03-30T01:59:46.575536625Z 172.19.0.6 2024-03-30 01:59:46.575 UTC [4002] [unknown]@[unknown] LOG: PID 3921 in cancel request did not match any process
2024-03-30T01:59:46.576857056Z 172.19.0.6 2024-03-30 01:59:46.576 UTC [4003] [unknown]@[unknown] LOG: PID 3920 in cancel request did not match any process
2024-03-30T01:59:47.573494021Z 172.19.0.6 2024-03-30 01:59:47.573 UTC [4010] [unknown]@[unknown] LOG: PID 3929 in cancel request did not match any process
2024-03-30T01:59:47.573937318Z 172.19.0.6 2024-03-30 01:59:47.573 UTC [4011] [unknown]@[unknown] LOG: PID 3928 in cancel request did not match any process
Relevant log output
No response
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered: