warpgate icon indicating copy to clipboard operation
warpgate copied to clipboard

Warpgate stops servicing logins, db locked

Open jho1670 opened this issue 3 months ago • 1 comments

Running in docker-compose. "ghcr.io/warp-tech/warpgate@sha256:2d80f41e315b32d28b30e2023037d383a2c2e0cd35ddcf428565c85cc480f8e8"

I'm running proxmox. Kernel 6.14.8-2-pve. Docker version 28.3.3, build 980b856.

The lines of log leading up to the failure:

17:34:01 ERROR Session failed error=early eof
17:34:01  INFO Closed session
17:34:01  INFO SSH: Client session closed session=5ad78118-50bd-4547-bbb7-e72bbdc8b252
17:34:01  INFO SSH: Closed connection session=5ad78118-50bd-4547-bbb7-e72bbdc8b252
17:34:06  INFO SSH: Password auth as <root for > session=7461279e-baf8-4bfb-89f7-0d326daed8c4 client_ip=::ffff:164.90.223.73
17:34:06 ERROR SSH: Selected user not found: root session=7461279e-baf8-4bfb-89f7-0d326daed8c4 client_ip=::ffff:164.90.223.73
17:34:06 ERROR SSH: Failed to verify credentials error=user root not found session=7461279e-baf8-4bfb-89f7-0d326daed8c4 client_ip=::ffff:164.90.223.73
17:34:08 ERROR Session failed error=early eof
17:34:08  INFO Closed session
17:34:08  INFO SSH: Client session closed session=7461279e-baf8-4bfb-89f7-0d326daed8c4
17:34:08  INFO SSH: Closed connection session=7461279e-baf8-4bfb-89f7-0d326daed8c4
17:34:11  INFO SSH: Password auth as <root for > session=ca08629e-c236-4d19-9468-c414369343ec client_ip=::ffff:164.90.223.73
17:34:11 ERROR SSH: Selected user not found: root session=ca08629e-c236-4d19-9468-c414369343ec client_ip=::ffff:164.90.223.73
17:34:11 ERROR SSH: Failed to verify credentials error=user root not found session=ca08629e-c236-4d19-9468-c414369343ec client_ip=::ffff:164.90.223.73
17:34:13 ERROR Session failed error=early eof
17:34:13  INFO Closed session
17:34:13  INFO SSH: Client session closed session=ca08629e-c236-4d19-9468-c414369343ec
17:34:13  INFO SSH: Closed connection session=ca08629e-c236-4d19-9468-c414369343ec
17:34:18  INFO SSH: Password auth as <root for > session=9a97a767-824b-4f6d-9371-46e4f376a80a client_ip=::ffff:164.90.223.73
17:34:18 ERROR SSH: Selected user not found: root session=9a97a767-824b-4f6d-9371-46e4f376a80a client_ip=::ffff:164.90.223.73
17:34:18 ERROR SSH: Failed to verify credentials error=user root not found session=9a97a767-824b-4f6d-9371-46e4f376a80a client_ip=::ffff:164.90.223.73
17:34:20 ERROR Session failed error=early eof
17:34:20  INFO Closed session
17:34:20  INFO SSH: Client session closed session=9a97a767-824b-4f6d-9371-46e4f376a80a
17:34:20  INFO SSH: Closed connection session=9a97a767-824b-4f6d-9371-46e4f376a80a
17:34:20 ERROR Server error error=protocol server: SSH

Caused by:
    0: getting peer address
    1: Transport endpoint is not connected (os error 107)
17:34:21  INFO Warpgate version=v0.15.0
17:34:21  INFO Using config: "/data/warpgate.yaml"
17:34:26 ERROR Fatal error error=database error: Execution Error: error returned from database: (code: 5) database is locked

After upgrading, I'm still not able to get warpgate to start:

04:15:38  INFO Warpgate version=v0.16.0-modified
04:15:38  INFO Using config: "/data/warpgate.yaml"
04:15:44 ERROR Fatal error error=Execution Error: error returned from database: (code: 5) database is locked

Caused by:
    0: error returned from database: (code: 5) database is locked
    1: error returned from database: (code: 5) database is locked
    2: (code: 5) database is locked
04:15:44  INFO Warpgate version=v0.16.0-modified
04:15:44  INFO Using config: "/data/warpgate.yaml"

jho1670 avatar Sep 08 '25 04:09 jho1670

The initial cause might be the same as #1288, but clearly it leads to a database problem when it happens.

kruton avatar Oct 04 '25 01:10 kruton