R
Railway5mo ago
jeremy

Database unreachable after getting "Client network socket disconnected"

Hey there, I created a temporary libSQL database to test out some upcoming migration I will need to run on production. I deployed the database using Brody's template https://railway.app/template/p121Tx The migration runs a schema migration first (step 1), successfully, a data migration (step 2), moving data from firebase to libsql, successfully and lastly a migration to move images around in Cloudflare R2 (step 3), which fails. In the last migration; I'm getting all the data migrated from step 2 in order to do some operation with R2. I have about ~45000 rows to go through, which I need to update back to the database using the libsql client. When trying to run an libsql.execute statement I'm getting the following error:
FetchError: request to https://URL.up.railway.app/v2/pipeline failed, reason: Client network socket disconnected before secure TLS connection was established
FetchError: request to https://URL.up.railway.app/v2/pipeline failed, reason: Client network socket disconnected before secure TLS connection was established
After getting this error, my database becomes unaccessible for some time. In general, it takes about 1/2 hours before I can connect to it again. I'm using TablePlus to connect to it, and it just stays stuck in the "Connecting to database..." until it fails. Even after trying to redeploy the database, it's still unreachable. I don't have any errors in the database logs either. Service has V2 runtime and beta edge proxy enabled. 34849d22-d685-4e73-8858-fbd4fe42ea65
Solution:
Alright, I actually updated the @libsql/client package to latest version and it works without the error above and successfully migrate everything. Let's just ignore this
Jump to solution
5 Replies
Percy
Percy5mo ago
Project ID: 34849d22-d685-4e73-8858-fbd4fe42ea65
Brody
Brody5mo ago
are you seeing the same issue if you disable the edge proxy on the libsql service?
jeremy
jeremyOP5mo ago
will give it a try, and let you know
Solution
jeremy
jeremy5mo ago
Alright, I actually updated the @libsql/client package to latest version and it works without the error above and successfully migrate everything. Let's just ignore this
Brody
Brody5mo ago
awesome!
Want results from more Discord servers?
Add your server