tursodatabase / tursodatabase/libsql

"SqliteFailure" with a remote replica

Open
#2,110 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
17.2k
Forks
531
Avg merge
1h 12m
Merged PRs (30d)
1

Description

Hi! I've been using libsql for my project, and lately I've been having this problem:

thread 'actix-server worker 2' panicked at /var/home/sergio/Documentos/staticcms/rusty/src/db.rs:539:40:
: SqliteFailure(11, "malformed database schema (?)")
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I've tried other modes to see if I could harvest more info:

In local replica mode:

thread 'actix-server worker 2' panicked at /var/home/sergio/Documentos/staticcms/rusty/src/db.rs:343:22:
Compilation of SQL sentence failed: Misuse("Cannot describe in local replica mode.")

(Honestly, this might be something I'm doing wrong, but could be of interest).

In local only:
It works fine, but I get:
2025-06-26T20:28:26.488910Z ERROR libsql::local::connection: Failed to clear authorizer during disconnect

In remote:
It also works fine.

Some details:

  • I'm using 0.9.3, I can't use anything newer due to the bug that requires a multithreaded runtime, however I can't use it.
  • Reading works fine, and even removing, seems like this error is cause by an insert (haven't tried modifications).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the insert failure with libsql 0.9.3 in remote replica mode, then compare it with local replica, local-only, and remote modes while enabling RUST_BACKTRACE=1. Inspect the reported db.rs locations around lines 539 and 343 and determine the conditions that produce the malformed schema error. Done means the failure has a confirmed cause and a verified fix or clear reproduction boundary.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust, sqlite
Domain
databases, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.