check-if-email-exists
check-if-email-exists copied to clipboard
reacherhq
Docker : backend:v0.4.0
Email to check
gmail, hotmail
From where did you run check-if-email-exists?
Digital Ocean
Version of check-if-email-exists (if running it yourself)
v0.4.0
What happened?
After the upgrade to latest v0.4.0 and when running a bulk process it shows error while connecting to the database.
We are testing with 100 emails and errors come up.
The main DB server is full of resources available with no changes.
Relevant log output
Rust Log:
===
[2023-10-23T16:22:42Z WARN sqlx::query] SELECT mq_keep_alive(ARRAY[$1], $2); rows affected: 0, rows returned: 0, elapsed: 961.253s
[2023-10-23T16:22:42Z ERROR sqlxmq::runner] Failed to keep job 52b7dfaa-988b-4725-87a4-12b8fc584a47 alive: error communicating with database: Operation timed out (os error 110)
[2023-10-23T16:22:42Z WARN sqlx_core::pool::connection] error occurred while testing the connection on-release: error communicating with database: Broken pipe (os error 32)
[2023-10-23T16:23:43Z WARN sqlx_core::pool::connection] error occurred while testing the connection on-release: error communicating with database: Operation timed out (os error 110)
===
PostgreSQL log:
===
2023-10-23 16:22:36.994 UTC [2443] CONTEXT: SQL function "mq_uuid_exists" during inlining
automatic analyze of table "ms01.public.mq_msgs"
2023-10-23 16:22:44.396 UTC [2444] ERROR: function uuid_nil() does not exist at character 35
2023-10-23 16:22:44.396 UTC [2444] HINT: No function matches the given name and argument types. You might need to add explicit type casts.
2023-10-23 16:22:44.396 UTC [2444] QUERY:
SELECT id IS NOT NULL AND id != uuid_nil()
===
Was this a fresh postgres db or an existing one? Which version of postgres?
Hi!
Existing one
PG_VERSION=12.16-1.pgdg110+1
No changes on PgSQL since last 0.4.0-beta install
Do you remember which beta version you were using? If it was an older one, then the Postgres table schema did change a slightly bit, and this might be the error.
In this case, I recommend simply purging the whole DB, and start with a fresh one (if that's possible for you).
Hello!
Yes, the prior version was "reacherhq/backend:v0.4.0-beta31"
Regarding the DB I already did that. I mean create a brand new DB set but the error continue with same message (using last v0.4.0 release)